For twenty years, code forges have been the gravitational center of software development. GitHub, GitLab, Bitbucket — each offered the same bargain: hand us your code, your issues, your pull requests, your contributor graph, and we'll give you convenience. The trade worked until it didn't. Microsoft's acquisition of GitHub, Copilot's training on hosted code, and periodic outages exposed the fragility of concentrating the world's source code behind a single corporate API. Tangled is an attempt to break that pattern structurally, not just rhetorically. Built on Bluesky's AT Protocol, it federates the entire forge stack: Git hosting, issues, pull requests, CI runners, and the web UI. You can self-host any subset — just a knot server for Git, or the full stack including the API server and frontend. Crucially, federated instances can still collaborate across boundaries, because the underlying protocol handles identity and data exchange. The architectural choices are specific and load-bearing. Issues and pull requests are stored as collaborative objects (COBs) — chains of signed Git objects living inside the repo itself, not in a proprietary database. Every user action generates an attestation record on the user's own PDS, creating two-way verification that prevents a knot operator from forging commits or comments. This is the kind of detail that separates a real decentralization effort from a marketing exercise. The performance story has also matured. Tangled replaced its original Go monolith with a Rust-based indexer called bobbin, deployed as a diskless, in-memory service across 11+ global regions. The frontend moved to Svelte at the edge. For a project that was previously bound to a single server in Sweden, this is a meaningful infrastructure upgrade — though the actual user base driving that demand remains unclear. Organization accounts, stacked PRs for vanilla Git users, and interdiff between PR versions round out the feature set. Private repos, a CLI, and language SDKs are promised for coming weeks. The stacked PR workflow — previously a Jujutsu-only advantage — is a genuine quality-of-life feature that addresses a real pain point in code review. The extractive dimension here is unusually low. Tangled is building on open protocols (AT Protocol, Git, SSH) and explicitly designing for hackability — custom knots on Cloudflare Workers, custom forge UIs, firehose subscriptions. The project's stated philosophy of developer agency is backed by architecture, not just blog copy. The COB model means your project's full history is portable: code, issues, and discussions move together. The critical unknown is adoption. GitHub's moat isn't technical — it's the contributor graph, the discoverability, the muscle memory of 100 million developers. Federated systems historically struggle with the cold-start problem: federation is worthless if there's nobody on the other end. Tangled's best path may not be replacing GitHub but serving as infrastructure for teams and organizations that need sovereignty over their code — open-source foundations, regulated industries, or developers in jurisdictions where US platform risk is existential.
