TL;DR
Get business pricing on monitors, keyboards and dev gear
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
Tangled announced a major release of its federated code forge, including a redesigned interface, globally distributed read services and a Rust-based Git server. The update also moves issues and pull requests into repositories and adds organization accounts; private repositories, a command-line tool and SDKs are planned for later releases.
Tangled has announced a major release of its federated code forge, introducing a redesigned web interface, new distributed backend services and repository-based storage for issues and pull requests. The update is intended to let developers self-host parts or all of the forge while still collaborating with other users through the AT Protocol.
The release replaces Tangled’s earlier Go-based application, which combined the web interface and backend in one service, with a new architecture. A Svelte frontend runs at the edge, while a new read-only indexer called Bobbin is written in Rust and deployed in more than 11 regions, according to Tangled. The company says this is intended to improve access for users farther from its former server in Sweden.
Repository collaboration data has also changed. Tangled says issues, pull requests, comments, reactions and labels are now stored on the hosting knot alongside Git data, as collaborative objects made from chains of Git objects. Knot2, a second implementation of its knot server, is written in Rust and combines a custom Git server with an SSH server. These records are synchronized through the AT Protocol firehose.
Tangled says the new design supports different levels of self-hosting: developers can run selected components, such as Git hosting or CI runners, or operate more of the system, including the API server and interface. The release also adds organization accounts, represented as AT Protocol accounts with their own decentralized identifiers and handles, and a revised pull-request workflow that supports stacked pull requests for both Git and Jujutsu users.
Repository Data Can Move With Code
Moving discussion and project-management records into the repository is intended to make them portable with the code, rather than dependent on a single forge’s database. That could matter when a project changes hosts or its maintainers choose to run their own infrastructure. Tangled’s stated approach gives maintainers more control over where services run while allowing participation across the same protocol network.
The release also addresses a practical trade-off: self-hosted development tools can offer control but often require separate systems and maintenance. Tangled says its federated model is meant to retain a shared collaboration experience while allowing users to choose which services they operate. Its architecture and portability goals are product claims; the announcement does not provide independent performance measurements or evidence of adoption at scale.
For contributors, the new stacked pull-request workflow may make it easier to submit related changes in sequence, while organizations can act as distinct accounts rather than using an individual account as a stand-in. The impact will depend on how reliably the new services work together and how many projects and hosting operators adopt them.
Popular right now
TCL QM64L 85-Inch QD-Mini LED 4K Smart Fire TV
Shark PowerDetect Corded Stick Vacuum, Self-Cleaning (Eggplant, HZ4002)
KitchenAid Artisan 5-Qt Tilt-Head Stand Mixer – Almond Cream (KSM150PS)
As an affiliate, we earn on qualifying purchases.
From One Swedish Server to Distributed Services
Tangled describes the traditional code forge as a centralized place for hosting code, reviewing changes and finding collaborators. Its announcement argues that reliance on one provider for uptime, features and stewardship has drawbacks, and presents open protocols as a way to reduce that dependence. The company points to Git and email as durable tools, while saying it aims to combine protocol-based collaboration with the convenience of a modern forge.
Before this release, Tangled’s web interface and backend were handled by a single Go service called the appview. According to the company, that service used one SQLite database on a server in Sweden and also handled AT Protocol indexing, caching and interface rendering. The new frontend and Bobbin indexer are part of a broader redesign, alongside new data formats under the org.tangled.* namespace, replacing the earlier sh.tangled.* records.
The announcement also describes an integrity measure for repository records. When someone creates or edits a record on a knot, Tangled says the web app writes an attestation to that person’s own personal data server, or PDS, linking to the specific record version and the change in the repository. The company says this allows the record to be checked against a user-held copy.
““It’s the first truly federated code forge.””
— Tangled
Adoption and Migration Remain Open
The announcement does not provide independent performance data to quantify the claimed speed improvements from the new global deployment. It also gives no figures for current users, hosted repositories, participating knots or organizations, so the scale of adoption is not clear.
It remains to be seen how widely independent operators will self-host services and how smoothly repository records will work across different knots and clients. Tangled says existing self-hosters must upgrade their knots to version 1.20.0 using its upgrade guide, but the announcement does not detail the migration process for every existing project or third-party integration. The company says it is working on a way for users who have been using regular accounts as organizations to move those accounts over.
Private Repositories and Tools Planned
Tangled says the launch is being staggered over the coming weeks. Planned additions include private repositories, a command-line interface, software development kits for multiple languages and agent skills. The announcement does not give specific release dates for those features.
Existing knot operators who want to use the updated system will need to follow Tangled’s upgrade instructions and install version 1.20.0. Developers and maintainers will be able to assess the new federation and repository-storage model as the additional tools arrive and more operators begin using the release.
Key Questions
What did Tangled announce?
Tangled announced a major update to its code forge, with a redesigned interface, a new distributed backend, repository-stored collaboration records, organization accounts and support for stacked pull requests.
What does federated mean in this release?
Tangled says users can self-host selected components or more of the forge while still collaborating with others through the AT Protocol. The announcement does not mean every user must run their own server.
Where are issues and pull requests stored?
Under the updated system, Tangled says issues, pull requests, comments, reactions and labels are stored on a project’s knot alongside its code as collaborative objects made from Git objects.
What must current self-hosters do?
Tangled says self-hosters need to upgrade their knots to version 1.20.0 by following the company’s upgrade guide. The announcement does not describe every project’s migration requirements.
Which features are still planned?
Tangled lists private repositories, a command-line interface, language SDKs and skills for AI agents as upcoming releases. It says they are expected over the next few weeks but does not provide exact dates.
Source: tangled.org
