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 redesigned, federated code forge built on the AT Protocol, with infrastructure that lets users self-host selected services while collaborating with others. The release includes a new Svelte interface, globally deployed Rust indexing services, repository-stored issues and pull requests, organization accounts and stacked pull requests. Private repositories, a command-line tool, software development kits and agent skills are listed as upcoming work.
Tangled has announced a rebuilt version of its code forge, a platform for hosting code and coordinating software projects, designed to let users host parts of the service themselves while still collaborating across the network. The release moves the platform onto the AT Protocol and introduces new infrastructure, repository-based project records, organization accounts and support for stacked pull requests.
The announcement describes the service as a federated code forge: users can choose to self-host parts such as Git hosting or continuous-integration runners, or run more of the system, including its API server and interface. Learn more about low-code development platforms. Tangled says those choices do not prevent users from communicating with other participants. The company frames the design as an effort to combine the portability of open protocols with the convenience of a hosted forge.
The launch includes a new Svelte frontend deployed at the edge and a Rust indexing service called bobbin, alongside developments in AI-assisted coding. Tangled says bobbin is read-only, processes AT Protocol data and runs across more than 11 regions. The previous web interface and backend were a Go monolith running on one server in Sweden, according to the announcement. Other functions have been split into supporting services, including knot2, a Rust rewrite that combines a custom Git server with an SSH server.
Project discussions and administration data are also changing location, a topic closely related to code review software. Issues, pull requests, comments, reactions and labels are now stored on the knot alongside repository code as collaborative objects made from Git objects. Tangled says this is intended to make project records portable with the repository. To address whether a host could misrepresent a user’s edits, the service says the web app writes an attestation to that user’s personal data server, or PDS, pointing to the corresponding record and repository change.
Project Data Moves With Repositories
The design could give teams more control over where their code and project discussions are stored. On a conventional hosted forge, repository data and collaboration tools depend heavily on the platform operator. Tangled’s approach aims to let maintainers host selected components themselves while keeping a way to collaborate with users on other instances.
Storing issues and review discussions beside code also changes what portability means: moving a project could include more than its Git history. Tangled says knot records are signed and synchronized through the AT Protocol firehose, while attestations in users’ PDS accounts are intended to support verification of authorship. Those are design claims in the launch post; the announcement does not provide independent testing of how the system performs in practice or how easy migrations will be.
The release is relevant to developers and organizations concerned about platform dependence, but self-hosting also means taking responsibility for operating infrastructure and keeping it updated. Tangled says self-hosters must upgrade knots to version 1.20.0 and follow its upgrade guide. The practical balance between user control, maintenance work and a consistent experience will depend on adoption and implementation.
Popular right now
Shark Rotator Lift-Away Vacuum with DuoClean PowerFins (LA555) – Dark Grey
De'Longhi 15-Bar Pump Espresso Machine with Milk Frother & Temperature Control
Breville Bambino Espresso Machine, Brushed Stainless Steel (BES450BSS)
As an affiliate, we earn on qualifying purchases.
From One Server to Distributed Services
Tangled’s post places the release against the long-standing role of centralized code forges, which combine code hosting, review tools and contributor discovery in one service. It argues that relying on a single provider for availability, features and stewardship can be limiting, and points to Git and email as durable open tools. The company’s stated aim is to retain a polished web experience while using protocols that support independent hosting.
Before this release, Tangled’s web UI and backend were combined in an appview, a Go service that handled indexing, caching, other data and page rendering. It used a single SQLite database on a server in Sweden. Tangled says that setup worked for users close to the server but was less suitable for users farther away. The new frontend and globally distributed bobbin services are part of its response, alongside a revised data model using records under the org.tangled.* namespace instead of the former sh.tangled.* records.
The update also adds organization accounts as AT Protocol accounts with their own decentralized identifiers and handles. Tangled says these passwordless, delegated accounts are hosted on a Tranquil PDS instance, can invite members and can use a domain-owned handle. The company says owners of ordinary accounts used as stand-in organizations should wait for a migration option, which is still being developed.
“you can host code on your own servers and still collaborate seamlessly with others”
— Tangled, in its launch post
Migration and Operations Still Developing
The announcement does not give independent performance measurements for the new architecture, nor does it report how many users or projects have adopted self-hosted knots. Tangled says bobbin runs in more than 11 regions, but provides no comparison figures for response times or availability. The benefits users will experience may vary depending on location and which services they choose to operate.
Some migration and product details remain open. Tangled says it is working on a way to move regular accounts used as organizations into the new organization-account model, but gives no timetable. It also says private repositories, a CLI, language SDKs and agent skills are due in the coming weeks without specifying release dates. The announcement does not detail operational requirements or recovery procedures for teams running all components themselves.
More Tools Planned in Coming Weeks
Tangled says it will stagger the rollout over the next few weeks. The items it names are private repositories, a command-line interface, SDKs for different programming languages and skills designed for software agents. The post does not attach dates to those releases, so their sequencing and availability remain to be confirmed.
Self-hosters should consult Tangled’s upgrade guide before updating knots to v1.20.0. Further details on migration for existing organization-like accounts are also expected, though no schedule has been announced. As the rollout proceeds, users will be able to judge how the new hosting choices, repository-stored collaboration records and distributed services work in day-to-day projects.
Key Questions
What did Tangled announce?
Tangled announced a rebuilt federated code forge using the AT Protocol. It includes a redesigned interface, distributed indexing services, repository-stored collaboration records, organization accounts and stacked pull-request tools.
What does federated hosting mean on Tangled?
Tangled says users can host selected components, such as Git hosting or CI runners, on their own infrastructure, or self-host more of the service. The company says users can still collaborate with others across the network.
Where are issues and pull requests stored?
The release places issues, pull requests, comments, reactions and labels on the repository’s knot as collaborative objects built from Git objects. Tangled says this is intended to keep project records portable with the code.
What features are planned next?
Tangled lists private repositories, a CLI, language SDKs and agent skills as upcoming additions, expected over the next few weeks. It has not published specific release dates.
Source: tangled.org
