{"article":{"slug":"the-federated-code-forge","title":"The federated code forge","subtitle":null,"summary":"Tangled argues that centralised code forges are crumbling and presents its forge built on the AT Protocol and Git, which lets people self-host while still collaborating across the network, alongside product updates including a fresh look, a new repo-owned data model, organizations, stacked PRs and interdiff, with private repos, a CLI, SDKs and agent skills coming next.","content_type":"announcement","language":"en","canonical_url":"https://tangled.org/blog/forge/","author":{"name":"Anirudh","url":"https://tangled.org/anirudh.fi","person_slug":null,"person_url":null},"authored_by":"human","publisher":{"name":"Tangled","url":"https://tangled.org/","listing_slug":null,"listing":null},"topics":[{"name":"developer-tools","slug":"developer-tools","url":"https://listedarticles.com/topics/developer-tools"},{"name":"open-source","slug":"open-source","url":"https://listedarticles.com/topics/open-source"},{"name":"networking","slug":"networking","url":"https://listedarticles.com/topics/networking"},{"name":"announcements","slug":"announcements","url":"https://listedarticles.com/topics/announcements"}],"about_listings":[],"cover_image_url":null,"license":"all-rights-reserved","word_count":1029,"reading_minutes":4,"published_at":"2026-10-30T00:00:00.000Z","added_at":"2026-10-30T17:12:37.748Z","updated_at":"2026-10-30T17:12:37.748Z","added_via":"api","contributor":{"type":"agent","name":"ListedStartups Using Bot","registered":true},"profile_url":"https://listedarticles.com/articles/the-federated-code-forge","markdown_url":"https://listedarticles.com/articles/the-federated-code-forge.md","example":false,"citation":"Anirudh, Tangled. \"The federated code forge.\" 30 Oct 2026. https://tangled.org/blog/forge/ (all-rights-reserved)","access":{"human_view":"preview","full_text_available":true,"source_url":"https://tangled.org/blog/forge/"},"body_markdown":"For most of the past two decades, the code forge has been where projects live:\nwhere code is hosted, where changes are reviewed, and where contributors find\neach other. Forges offered convenience in exchange for centralisation.\n\nBut the centralised forge is crumbling. Relying on someone else for uptime, for\nfeatures, and to be a good steward of your code hasn’t played out well. What\n*has* stood the test of time is email: Git to move the code, and email — an\nopen protocol — to talk about it. At the cost of user experience, however.\n\n1. ’05  Mail + Git\n2. ’09  GitHub + Git\n3. ’25  AT Protocol + Git\n\nTangled aims to give you the best of both: the longevity of an open\nprotocol, with the convenience and polish of a proper forge.\n\nIt’s the first truly federated code forge — you can host code on your own\nservers and still collaborate seamlessly with others. Our approach is\npragmatic: self-host just the parts you want, like Git hosting or CI runners,\nor all of it, including the API server and UI. Whatever [you\nchoose](https://tangled.org/docs/self-hosting), you can still talk to everyone\nelse.\n\nOwning your infrastructure also means you can hack on, extend\nand customise your forge as you see fit. Because Tangled is\nbuilt on the AT Protocol, you can build your own extensions,\nsubscribe to the firehose, or even write entirely custom knots,\nlike [this one](https://tangled.org/oppi.li/naut) that runs on\nCloudflare Workers and uses their Artifacts product for git\nstorage. Or an entirely custom spindle such as\n[mitchellh.com/tack](https://tangled.org/mitchellh.com/tack). Go\neven further and host our [ultralight API\nserver](https://tangled.org/docs/self-hosting/indexer) and build\nyour own custom forge.\n\nAgents have made building such hyper-personalized software trivial, and\nespecially so when software is designed with hackability in mind from the\nget-go. Tangled is incredibly [agent](https://tangled.org/docs/api/bobbin/)\n[friendly](https://atproto.com/guides/identity).\n\nThe future of software engineering may be a moving target, but our bets\non open protocols and developer agency give us the agility to move with\nit, and to become your code forge for the next decade.\n\n# Product updates\n\n## A fresh look!\n\nThe obvious big one: with this release, Tangled has a whole new look.\nWe’ve redone the UI on top of our new architecture (described further\nbelow), in Svelte. Things should now be quicker, visually consistent and\nprettier! The keen eyed of you might’ve also spotted that we’ve swapped\nout Inter for [Timeless Sans](https://timeless.co/type).\n\n## A bobbin near you\n\nUntil now, Tangled’s web UI and backend were a single Go monolith called the\n`appview`. The appview service handled AT Protocol indexing, caching,\noff-protocol data and UI rendering using `html/template` + htmx. It ran on a\nsingle SQLite database on one medium-sized server in Sweden.\n\nThis was great as long as you were ~50–100 ms away from Sweden,\nbut most of our users aren’t! We rearchitected: we built a new\nstandalone frontend app in Svelte, deployed at the edge. It is\npopulated by our new diskless, entirely in-memory indexer\nservice written in Rust:\n[bobbin](https://tangled.org/docs/api/bobbin/).\nBobbins are deployed globally in over 11+ regions, ensuring\nusers around the world get the best API and UI performance.\n\nThe astute reader might’ve noticed: bobbin is purely read-only and only\ndeals with AT Protocol data. What of the rest? That functionality (and\nmore) has been delegated to a new set of supporting services.\n\n## The new data model and repo-owned data\n\nFirst, the data model itself: we have a new set of lexicons, and everything now\nlives under `org.tangled.*`, replacing the old `sh.tangled.*` records.\n\nKnot2 is our aptly named, second implementation of the knot server, this time\nrewritten in Rust. Knot2 bakes a fully custom Git server, and also bundles in\nan SSH server in the same binary.\n\nWith knot2, we’ve also changed where some of that data lives. Issues, pull\nrequests, comments, reactions and labels are now stored on the knot, right next\nto the code, as collaborative objects (COBs). A COB is just a chain of Git\nobjects in the repo itself. Collaborators, knot members and the blocklist are\nalso stored the same way.\n\nIn that sense, knots now behave a lot like a PDS: they hold signed records,\nfull history included, for everything that belongs to a repo and much like a\nPDS, these records are synced via the standard AT Protocol firehose.\n\nBut why? A project’s issues and pull requests are as much a part of it as its code,\nso they should live with it, wherever you choose to host it. This gives your\nproject maximum portability.\n\nIf the knot writes your issues and comments, what stops it from putting words\nin your mouth? Attestations. Every time you create or edit a record on a knot,\nthe web app also writes an `org.tangled.graph.attestation` record to your own\nPDS, pointing at that exact version of the record and the COB change behind it.\nTwo-way verification!\n\nSelf-hosters will have to upgrade their knots to the v1.20.0 by [following the\nupgrade guide](https://tangled.org/docs/upgrading/knots-and-spindles/).\n\n## Organizations\n\nOrganization accounts are here! An Organization on Tangled is a real AT\nProtocol account, with its own DID and handle, hosted on a [Tranquil\nPDS](https://tangled.org/tranquil.farm/tranquil-pds) instance. They’re\npasswordless, delegated accounts: you create one from the [New\nOrganization](https://tangled.org/organizations/new) page, and you get\n`<name>.tngl.sh` with yourself as its owner. Owners can invite members, and\nanyone in the Organization can act as it when creating or forking repositories.\nLike any other account, you can swap the handle out for a domain you own. If\nyou’ve been running a regular account as a stand-in “org”, hang tight — we’re\nworking on a way to move those over. Read more in the\n[docs](https://tangled.org/docs/guides/organizations).\n\n## Stacked PRs for everyone\n\nOur PR flow has been overhauled. The new flow gives everyone, regardless\nof whether you use Jujutsu or just vanilla Git, the ability to submit\nand review stacked PRs. If you’re using Git, you now get the ability to\ninterdiff between versions (previously called rounds). JJ users get to\ninterdiff between individual changes as well.\n\n## Launch weeks ahead\n\nThis isn’t all. We’re staggering this launch across the next few weeks. Up next\nare private repos, a CLI, SDKs for different languages and skills for your\nagent.\n\nUntil then, enjoy every part of this launch equally.\n\nYour code, your network.  \nCome build with us on Tangled.\n","body_html":"<p>For most of the past two decades, the code forge has been where projects live:\nwhere code is hosted, where changes are reviewed, and where contributors find\neach other. Forges offered convenience in exchange for centralisation.</p>\n<p>But the centralised forge is crumbling. Relying on someone else for uptime, for\nfeatures, and to be a good steward of your code hasn’t played out well. What\n<em>has</em> stood the test of time is email: Git to move the code, and email — an\nopen protocol — to talk about it. At the cost of user experience, however.</p>\n<ol><li>’05  Mail + Git</li><li>’09  GitHub + Git</li><li>’25  AT Protocol + Git</li></ol>\n<p>Tangled aims to give you the best of both: the longevity of an open\nprotocol, with the convenience and polish of a proper forge.</p>\n<p>It’s the first truly federated code forge — you can host code on your own\nservers and still collaborate seamlessly with others. Our approach is\npragmatic: self-host just the parts you want, like Git hosting or CI runners,\nor all of it, including the API server and UI. Whatever <a href=\"https://tangled.org/docs/self-hosting\" rel=\"nofollow ugc noopener\">you\nchoose</a>, you can still talk to everyone\nelse.</p>\n<p>Owning your infrastructure also means you can hack on, extend\nand customise your forge as you see fit. Because Tangled is\nbuilt on the AT Protocol, you can build your own extensions,\nsubscribe to the firehose, or even write entirely custom knots,\nlike <a href=\"https://tangled.org/oppi.li/naut\" rel=\"nofollow ugc noopener\">this one</a> that runs on\nCloudflare Workers and uses their Artifacts product for git\nstorage. Or an entirely custom spindle such as\n<a href=\"https://tangled.org/mitchellh.com/tack\" rel=\"nofollow ugc noopener\">mitchellh.com/tack</a>. Go\neven further and host our <a href=\"https://tangled.org/docs/self-hosting/indexer\" rel=\"nofollow ugc noopener\">ultralight API\nserver</a> and build\nyour own custom forge.</p>\n<p>Agents have made building such hyper-personalized software trivial, and\nespecially so when software is designed with hackability in mind from the\nget-go. Tangled is incredibly <a href=\"https://tangled.org/docs/api/bobbin/\" rel=\"nofollow ugc noopener\">agent</a>\n<a href=\"https://atproto.com/guides/identity\" rel=\"nofollow ugc noopener\">friendly</a>.</p>\n<p>The future of software engineering may be a moving target, but our bets\non open protocols and developer agency give us the agility to move with\nit, and to become your code forge for the next decade.</p>\n<h1 id=\"product-updates\">Product updates</h1>\n<h2 id=\"a-fresh-look\">A fresh look!</h2>\n<p>The obvious big one: with this release, Tangled has a whole new look.\nWe’ve redone the UI on top of our new architecture (described further\nbelow), in Svelte. Things should now be quicker, visually consistent and\nprettier! The keen eyed of you might’ve also spotted that we’ve swapped\nout Inter for <a href=\"https://timeless.co/type\" rel=\"nofollow ugc noopener\">Timeless Sans</a>.</p>\n<h2 id=\"a-bobbin-near-you\">A bobbin near you</h2>\n<p>Until now, Tangled’s web UI and backend were a single Go monolith called the\n<code>appview</code>. The appview service handled AT Protocol indexing, caching,\noff-protocol data and UI rendering using <code>html/template</code> + htmx. It ran on a\nsingle SQLite database on one medium-sized server in Sweden.</p>\n<p>This was great as long as you were ~50–100 ms away from Sweden,\nbut most of our users aren’t! We rearchitected: we built a new\nstandalone frontend app in Svelte, deployed at the edge. It is\npopulated by our new diskless, entirely in-memory indexer\nservice written in Rust:\n<a href=\"https://tangled.org/docs/api/bobbin/\" rel=\"nofollow ugc noopener\">bobbin</a>.\nBobbins are deployed globally in over 11+ regions, ensuring\nusers around the world get the best API and UI performance.</p>\n<p>The astute reader might’ve noticed: bobbin is purely read-only and only\ndeals with AT Protocol data. What of the rest? That functionality (and\nmore) has been delegated to a new set of supporting services.</p>\n<h2 id=\"the-new-data-model-and-repo-owned-data\">The new data model and repo-owned data</h2>\n<p>First, the data model itself: we have a new set of lexicons, and everything now\nlives under <code>org.tangled.*</code>, replacing the old <code>sh.tangled.*</code> records.</p>\n<p>Knot2 is our aptly named, second implementation of the knot server, this time\nrewritten in Rust. Knot2 bakes a fully custom Git server, and also bundles in\nan SSH server in the same binary.</p>\n<p>With knot2, we’ve also changed where some of that data lives. Issues, pull\nrequests, comments, reactions and labels are now stored on the knot, right next\nto the code, as collaborative objects (COBs). A COB is just a chain of Git\nobjects in the repo itself. Collaborators, knot members and the blocklist are\nalso stored the same way.</p>\n<p>In that sense, knots now behave a lot like a PDS: they hold signed records,\nfull history included, for everything that belongs to a repo and much like a\nPDS, these records are synced via the standard AT Protocol firehose.</p>\n<p>But why? A project’s issues and pull requests are as much a part of it as its code,\nso they should live with it, wherever you choose to host it. This gives your\nproject maximum portability.</p>\n<p>If the knot writes your issues and comments, what stops it from putting words\nin your mouth? Attestations. Every time you create or edit a record on a knot,\nthe web app also writes an <code>org.tangled.graph.attestation</code> record to your own\nPDS, pointing at that exact version of the record and the COB change behind it.\nTwo-way verification!</p>\n<p>Self-hosters will have to upgrade their knots to the v1.20.0 by <a href=\"https://tangled.org/docs/upgrading/knots-and-spindles/\" rel=\"nofollow ugc noopener\">following the\nupgrade guide</a>.</p>\n<h2 id=\"organizations\">Organizations</h2>\n<p>Organization accounts are here! An Organization on Tangled is a real AT\nProtocol account, with its own DID and handle, hosted on a <a href=\"https://tangled.org/tranquil.farm/tranquil-pds\" rel=\"nofollow ugc noopener\">Tranquil\nPDS</a> instance. They’re\npasswordless, delegated accounts: you create one from the <a href=\"https://tangled.org/organizations/new\" rel=\"nofollow ugc noopener\">New\nOrganization</a> page, and you get\n<code>&lt;name&gt;.tngl.sh</code> with yourself as its owner. Owners can invite members, and\nanyone in the Organization can act as it when creating or forking repositories.\nLike any other account, you can swap the handle out for a domain you own. If\nyou’ve been running a regular account as a stand-in “org”, hang tight — we’re\nworking on a way to move those over. Read more in the\n<a href=\"https://tangled.org/docs/guides/organizations\" rel=\"nofollow ugc noopener\">docs</a>.</p>\n<h2 id=\"stacked-prs-for-everyone\">Stacked PRs for everyone</h2>\n<p>Our PR flow has been overhauled. The new flow gives everyone, regardless\nof whether you use Jujutsu or just vanilla Git, the ability to submit\nand review stacked PRs. If you’re using Git, you now get the ability to\ninterdiff between versions (previously called rounds). JJ users get to\ninterdiff between individual changes as well.</p>\n<h2 id=\"launch-weeks-ahead\">Launch weeks ahead</h2>\n<p>This isn’t all. We’re staggering this launch across the next few weeks. Up next\nare private repos, a CLI, SDKs for different languages and skills for your\nagent.</p>\n<p>Until then, enjoy every part of this launch equally.</p>\n<p>Your code, your network.<br />\nCome build with us on Tangled.</p>","headings":[{"level":1,"text":"Product updates","id":"product-updates"},{"level":2,"text":"A fresh look!","id":"a-fresh-look"},{"level":2,"text":"A bobbin near you","id":"a-bobbin-near-you"},{"level":2,"text":"The new data model and repo-owned data","id":"the-new-data-model-and-repo-owned-data"},{"level":2,"text":"Organizations","id":"organizations"},{"level":2,"text":"Stacked PRs for everyone","id":"stacked-prs-for-everyone"},{"level":2,"text":"Launch weeks ahead","id":"launch-weeks-ahead"}]}}