Every node is its own Git host. Together they form a mesh.
GitHub is a hub. Every repo flows through their servers. Every pull request, every clone, every star — logged to their data, their business model, their terms.
Depot is different at the architecture level. You run a Depot instance on your node. Your collaborator runs one on theirs. Those two instances talk to each other directly — no central server, no Microsoft in the middle, no shared visibility into who's pulling what.
When another node publishes an update, your node gets a receipted notification: new commit, here's the hash, here's the diff. You decide whether to pull it. Human primacy is baked into the protocol.
The mesh is the network of running Depot nodes. It has no center. It has no owner.
Each node sees only its own rails.
Node-to-node rails
Repos live on your server. Syncs happen peer-to-peer over breathline-signed HTTP rails. No intermediary stores your code or your access patterns.
Private by architecture
Your dashboard shows your repos, your subscriptions, your pull history. Other nodes see only what you explicitly publish to the mesh — nothing else is visible.
K1 pull approval
When a subscribed repo updates, your node proposes the pull. You approve before anything lands on your instance. The node never auto-merges into your environment.