GitForest
decentralized p2p git hosting
GitForest
decentralized p2p git hosting
GitForest is decentralized P2P git hosting. You host your own repos, share them over a BitTorrent-style DHT network, and collaborate directly with other peers. Seeder and leecher counts are your quality signals — no company controls the network.
Git is already a decentralized VCS — GitForest just gives it a proper P2P hosting layer.
Repos are announced over a Kademlia DHT and discovered via mDNS on your LAN. Clone and push directly peer-to-peer over the Git protocol — no servers in the middle.
Large file storage for ML model weights, datasets, and big artifacts. Content-addressed blobs with adaptive chunking and BitTorrent-style piece verification.
A decentralized CI/CD system. Submit jobs, or offer your own compute and get paid in crypto — Lightning, Ethereum L2, and Solana backends.
Your Ed25519 public key is your identity. gitforest init and you're on the network — no accounts, no passwords, no signups.
Signed patches, fork + merge requests, and access control lists — collaboration primitives designed for a network with no central authority.
Manage repos, blobs, compute jobs, and peers from the local web dashboard at 127.0.0.1:7878 or from the terminal.
No accounts. No hosting bills. Just a keypair and a daemon.
gitforest init
Generates an Ed25519 keypair at ~/.config/gitforest/. Your public key is your peer ID.
gitforest add ./myrepo
Registers any local git repo to share on the network.
gitforest daemon
Announces your repos on the DHT and starts the Git protocol server for direct P2P clone/push.
git clone gitforest://<peer_id>/repo
From any other machine running GitForest. That's it.
Binaries are built in CI on every release tag and published to Google Cloud Storage.
Prefer a script? Install via curl script · All versions and checksums in the manifest.
Getting started, CLI reference, LFS, the compute marketplace, and the full architecture.
Browse the docs Source code