Tangled launches a self-hostable federated code forge
Tangled developers say the release introduces a federated code forge built on the AT Protocol, allowing users to self-host components such as Git hosting, CI runners, the API server and the UI while collaborating with others. The update replaces the Go monolith with a Svelte frontend, an in-memory Rust indexer named bobbin, and Knot2, a Rust Git and SSH server; it also adds organization accounts and stacked pull requests for both Jujutsu and standard Git users. Future plans include private repositories, a CLI, SDKs and skills for agents.
The release combines developer-controlled hosting with open-protocol collaboration and an extensible architecture that the developers describe as agent-friendly, while adding practical forge features such as organization accounts and stacked pull requests.
For most of the past two decades, the code forge has been where projects live: where code is hosted, where changes are reviewed, and where contributors find each other. Forges offered convenience in exchange for centralisation.
But the centralised forge is crumbling. Relying on someone else for uptime, for features, and to be a good steward of your code hasn’t played out well. What has stood the test of time is email: Git to move the code, and email — an open protocol — to talk about it. At the cost of user experience, however.
Tangled aims to give you the best of both: the longevity of an open protocol, with the convenience and polish of a proper forge.
It’s the first truly federated code forge — you can host code on your own servers and still collaborate seamlessly with others. Our approach is pragmatic: self-host just the parts you want, like Git hosting or CI runners, or all of it, including the API server and UI. Whatever you choose, you can still talk to everyone else.
#Tangled#AT Protocol#Svelte#Rust#bobbin#Knot2#Tranquil PDS#Git#Jujutsu