Something went wrong. Try again.
Monorepo for Tangled tangled.org
Something went wrong. Try again.
123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165---atroot: truetemplate:slug: forgerkey: 3myvay62j2u22title: The federated code forgesubtitle: date: 2026-10-30announce: trueimage: https://assets.tangled.network/blog/forge/og.pngvideo: https://assets.tangled.network/blog/forge/og.mp4authors: - name: Anirudh email: anirudh@tangled.org handle: anirudh.fidraft: false ---
import ForgeTimeline from "../src/components/ForgeTimeline.svelte";import Ripple from "../src/components/Ripple.astro";import OrganizationsEmbed from "../src/components/embeds/OrganizationsEmbed.svelte";import PullStackEmbed from "../src/components/embeds/PullStackEmbed.svelte";import TicketsEmbed from "../src/components/embeds/TicketsEmbed.svelte";import TimelineEmbed from "../src/components/embeds/TimelineEmbed.svelte";
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 findeach other. Forges offered convenience in exchange for centralisation.
But the centralised forge is crumbling. Relying on someone else for uptime, forfeatures, 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 -- anopen protocol -- to talk about it. At the cost of user experience, however.
<ForgeTimeline client:visible={{ rootMargin: "200px" }} />
Tangled aims to give you the best of both: the longevity of an openprotocol, with the convenience and polish of a proper forge.
It's the first truly federated code forge -- you can host code on your ownservers and still collaborate seamlessly with others. Our approach ispragmatic: self-host just the parts you want, like Git hosting or CI runners,or all of it, including the API server and UI. Whatever [youchoose](https://tangled.org/docs/self-hosting), you can still talk to everyoneelse.
Owning your infrastructure also means you can hack on, extendand customise your forge as you see fit. Because Tangled isbuilt on the AT Protocol, you can build your own extensions,subscribe to the firehose, or even write entirely custom knots,like [this one](https://tangled.org/oppi.li/naut) that runs onCloudflare Workers and uses their Artifacts product for gitstorage. Or an entirely custom spindle such as[mitchellh.com/tack](https://tangled.org/mitchellh.com/tack). Goeven further and host our [ultralight APIserver](https://tangled.org/docs/self-hosting/indexer) and buildyour own custom forge.
Agents have made building such hyper-personalized software trivial, andespecially so when software is designed with hackability in mind from theget-go. Tangled is incredibly [agent](https://tangled.org/docs/api/bobbin/)[friendly](https://atproto.com/guides/identity).
The future of software engineering may be a moving target, but our betson open protocols and developer agency give us the agility to move withit, and to become <Ripple text="your code forge for the next decade" />.
# Product updates
## A fresh look!
The obvious big one: with this release, Tangled has a whole new look.We've redone the UI on top of our new architecture (described furtherbelow), in Svelte. Things should now be quicker, visually consistent andprettier! The keen eyed of you might've also spotted that we've swappedout Inter for [Timeless Sans](https://timeless.co/type).
<TimelineEmbed client:visible={{ rootMargin: "200px" }} />
## A bobbin near you
Until now, Tangled's web UI and backend were a single Go monolith called the`appview`. The appview service handled AT Protocol indexing, caching,off-protocol data and UI rendering using `html/template` + htmx. It ran on asingle SQLite database on one medium-sized server in Sweden.
This was great as long as you were ~50–100 ms away from Sweden, but mostof our users aren't! We rearchitected: we built a new standalonefrontend app in Svelte, deployed at the edge. It is populated by our newdiskless, entirely in-memory indexer service written in Rust: [bobbin](https://tangled.org/docs/api/bobbin/).Bobbins are deployed globally in over 11+ regions, ensuring users aroundthe world get the best API and UI performance.
The astute reader might've noticed: bobbin is purely read-only and onlydeals with AT Protocol data. What of the rest? That functionality (andmore) has been delegated to a new set of supporting services.
## The new data model and repo-owned data
First, the data model itself: we have a new set of lexicons, and everything nowlives under `org.tangled.*`, replacing the old `sh.tangled.*` records.
Knot2 is our aptly named, second implementation of the knot server, this timerewritten in Rust. Knot2 bakes a fully custom Git server, and also bundles inan SSH server in the same binary.
With knot2, we've also changed where some of that data lives. Issues, pullrequests, comments, reactions and labels are now stored on the knot, right nextto the code, as collaborative objects (COBs). A COB is just a chain of Gitobjects in the repo itself. Collaborators, knot members and the blocklist arealso stored the same way.
In that sense, knots now behave a lot like a PDS: they hold signed records,full history included, for everything that belongs to a repo and much like aPDS, these records are synced via the standard AT Protocol firehose.
But why? A project's issues and pull requests are as much a part of it as its code,so they should live with it, wherever you choose to host it. This gives yourproject maximum portability.
If the knot writes your issues and comments, what stops it from putting wordsin your mouth? Attestations. Every time you create or edit a record on a knot,the web app also writes an `org.tangled.graph.attestation` record to your ownPDS, pointing at that exact version of the record and the COB change behind it.Two-way verification!
<TicketsEmbed client:visible={{ rootMargin: "200px" }} />
Self-hosters will have to upgrade their knots to the v1.20.0 by [following theupgrade guide]( https://tangled.org/docs/upgrading/knots-and-spindles/).
## Organizations
Organization accounts are here! An Organization on Tangled is a real ATProtocol account, with its own DID and handle, hosted on a [TranquilPDS](https://tangled.org/tranquil.farm/tranquil-pds) instance. They'repasswordless, delegated accounts: you create one from the [NewOrganization](https://tangled.org/organizations/new) page, and you get`<name>.tngl.sh` with yourself as its owner. Owners can invite members, andanyone in the Organization can act as it when creating or forking repositories.Like any other account, you can swap the handle out for a domain you own. Ifyou've been running a regular account as a stand-in "org", hang tight -- we'reworking on a way to move those over. Read more in the[docs](https://tangled.org/docs/guides/organizations).
<OrganizationsEmbed client:visible={{ rootMargin: "200px" }} />
## Stacked PRs for everyone
Our PR flow has been overhauled. The new flow gives everyone, regardlessof whether you use Jujutsu or just vanilla Git, the ability to submitand review stacked PRs. If you're using Git, you now get the ability tointerdiff between versions (previously called rounds). JJ users get tointerdiff between individual changes as well.
<PullStackEmbed client:visible={{ rootMargin: "200px" }} />
## Launch weeks ahead
This isn't all. We're staggering this launch across the next few weeks. Up nextare private repos, a CLI, SDKs for different languages and skills for youragent.
Until then, enjoy every part of this launch equally.