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 has introduced a major redesign and infrastructure overhaul for its federated code forge, including a Svelte frontend, Rust services and globally deployed read-only indexers. The project says repositories can carry issues, pull requests and related records with their code, while planned additions such as private repositories and a CLI are due in coming weeks.
Tangled has released a redesigned version of its federated code forge, replacing its previous single-server application with a distributed architecture and moving issues, pull requests and other collaboration records into repositories. The changes are intended to let projects host code and project history on infrastructure they control while continuing to collaborate through the AT Protocol.
The release replaces Tangled’s earlier Go application, which combined its web interface, backend and AT Protocol indexing on one server in Sweden. The company says the new frontend is built with Svelte and deployed at the edge, while a read-only indexer called bobbin, written in Rust, runs in more than 11 regions. Tangled says the arrangement should improve access for users far from its former server; it did not provide performance measurements in the announcement.
Other functions now sit in supporting services. Tangled’s second knot server, knot2, is also written in Rust and combines a custom Git server with an SSH server. Issues, pull requests, comments, reactions, labels and membership information are stored on the knot alongside the code as collaborative objects, or COBs. Tangled says those records are synced through the AT Protocol firehose, making project discussions and history portable with the repository.
The release also introduces organization accounts as AT Protocol accounts with their own decentralized identifiers and handles. Owners can invite members, and members can create or fork repositories on behalf of the organization. The updated pull-request workflow supports stacked changes for Git and Jujutsu users, with interdiffs available between versions for Git and between individual changes for Jujutsu. Existing self-hosters must upgrade their knots to version 1.20.0, according to the project’s upgrade instructions.
Project History Moves With Code
Storing issues and review discussions with a repository addresses a practical limitation of centralized forges: a project can move its source code while leaving years of decisions, bug reports and contributor discussion behind. Tangled’s design makes those records part of the project’s portable history, while its federated approach is intended to let different operators host infrastructure and still communicate.
The change also gives maintainers more control over where code and services run. Tangled says users can self-host selected components, such as Git hosting or CI runners, or operate more of the system, including the API server and interface. That flexibility may appeal to teams concerned about dependence on a single provider’s availability or product decisions. The announcement describes the architecture and its aims, but does not establish how widely it is adopted or how it performs under real-world load.
For contributors, the revised pull-request flow broadens access to stacked reviews beyond users of Jujutsu, a version-control tool. Organizations also gain dedicated accounts rather than relying on individual accounts as stand-ins. Together, these features position the release as both an infrastructure change and a usability update, rather than a change to Git itself.
Products Worth Considering
Anker SOLIX S2000 Portable Power Station, 2,010Wh, 1,500W
Jackery Explorer 1000 v2 Portable Power Station
Logitech MX Mechanical Wireless Illuminated Performance Keyboard – Clicky
As an affiliate, we earn on qualifying purchases.
From One Server To Federation
Tangled frames the release as an alternative to code forges that centralize hosting and collaboration. In its original report, the project argued that Git and email have endured as open tools for exchanging code and discussing changes, while centralized forge services can leave users dependent on a provider. Tangled’s stated aim is to combine open-protocol longevity with the convenience of a hosted forge.
Before this release, Tangled’s web interface and backend were a single Go service known as the appview. It handled AT Protocol indexing, caching, other data and page rendering, using one SQLite database on a server in Sweden. The new architecture separates the frontend, protocol indexer and repository-hosting functions. Tangled says its new lexicons use the org.tangled.* namespace in place of the former sh.tangled.* records.
The project says it uses attestations to address whether a knot could misrepresent a person’s contribution. When a user creates or edits a record on a knot, the web app also writes an attestation to that user’s personal data server, pointing to the record version and the related repository change. Tangled describes this as two-way verification. The announcement does not report an independent security review of the mechanism.
“It’s the first truly federated code forge.”
— Tangled
Adoption And Performance Remain Open
Tangled has not published benchmarks quantifying the speed changes from moving the frontend to the edge or deploying bobbin in more than 11 regions. The announcement also does not give adoption figures, service-availability data or details of independent testing of the new architecture and attestation system. Those measures will help show how the design performs beyond the project’s stated goals.
Several announced features are not available in this release. Tangled lists private repositories, a command-line interface, language SDKs and agent skills as upcoming work. It also says it is working on a way for users who have been using ordinary accounts as organizations to migrate them; timing and migration details were not provided.
More Launch Features Planned
Tangled says it will stagger the launch over the next few weeks, with private repositories, a CLI, language SDKs and agent skills among the planned additions. The project has not provided specific release dates for those features. Self-hosters who want to use the new system need to follow the upgrade guide and move their knots to version 1.20.0.
Users running individual accounts as informal organizations will need to wait for Tangled’s planned migration path. Further updates may clarify how those accounts can move, when the remaining tools will ship and whether the new distributed services meet the performance and portability goals described in the announcement.
Key Questions
What has Tangled announced?
Tangled released a redesigned and rearchitected version of its federated code forge, including a Svelte frontend, globally deployed read indexers and a new knot server.
Where are issues and pull requests stored?
Tangled says issues, pull requests, comments, reactions and labels are stored on the repository’s knot alongside the code as collaborative objects, then synced through the AT Protocol firehose.
Does the release include private repositories and a CLI?
No. Tangled lists private repositories, a command-line interface, language SDKs and agent skills as features planned for the coming weeks. It has not announced exact release dates.
What must current self-hosters do?
Tangled says self-hosters need to upgrade their knots to version 1.20.0 and follow the project’s upgrade guide.
Source: tangled.org
