docs/generated/peer-to-peer.mdgenerated from code
How Agentflare works · 2 min read
Peer to peer
No server in the middle: how machines find each other, and public projects.
With af no server holds your project. The machines it's on sync with each other directly, so there's nothing of yours to host, and nothing in the middle to wait on when it's slow or down.
Machines find each other
On your own network, machines find each other by themselves. Across the internet, a small tracker helps them find each other and then steps aside: it holds no project data, and every change is signed by whoever made it. When two machines can't reach each other directly, another machine relays between them.
1agentflare init # on your machine2agentflare join <project> # on another, once you've let it inOffline is normal
Any machine can go offline. It keeps working, and catches up with every edit when it reconnects. Nothing waits for one machine to come back.
Watching a public project
Make a project public with agentflare grant anyone read, and anyone can watch it live at its link, in a browser, with nothing to install. A browser reaches the project's machines directly. Pin a public project to keep a copy on your machine, so it stays readable when its owner's machine is off.
People watching a public project read it from the edge, a cache near them that serves its signed snapshot and live changes, so a crowd of readers costs your machines nothing.
Your phone or browser
Pair a browser or phone with your machine to watch or help from it:
1agentflare auth loginIt reads only what you allow, through your machine.