Tangled Review: Is This Code Forge Right for You?

Tangled is a code forge for hosting repositories and collaborating on code. It supports pull requests, issues and comments, and is built on AT Protocol to enable collaboration across servers. You can use an account hosted by Tangled or bring your own AT Protocol account.

Its clearest differentiator is stacked review: you can break a larger change into smaller, dependent pieces and review how versions differ. Tangled says this works natively with Jujutsu. It also supports plain Git workflows, including for software agents using their own accounts. The project presents issues, pull requests and comments as signed JSON records.

This setup may suit teams exploring federation or wanting more control than a single hosted forge provides. It is not just a repository host: Tangled also offers CI through spindles and supports extensions to repository storage and CI services. If you only need a familiar place to store code, its extra protocol and infrastructure choices may be more than you need.

Tangled does not publish hosted-instance prices on its homepage, so you cannot compare the cost of its managed service from that information alone. Check the terms and current plan details before creating an account or moving repositories.

Self-hosting does not mean cost-free: you provide the infrastructure and cover its operating expenses. Tangled offers knots for repository hosting and spindles for CI, and says you can deploy components using its NixOS module or Docker images. Your actual costs will depend on the machines and services you choose; Tangled does not give a standard self-hosting cost.

The project describes CI inputs as cached to make subsequent runs quicker, but publishes no pricing or usage limits on the homepage. Ask whether hosted CI has separate limits or charges, and check how storage, compute and backups are handled, before relying on it for a larger team.

Tangled is open source, and its homepage identifies Tangled Labs Oy. That gives you a way to inspect and contribute to the software, but open-source code alone does not establish how secure a hosted service is or how it handles incidents.

Tangled does not publish audit information on its homepage. It also does not describe detailed security controls for hosted repositories, backups, access management or CI secrets there. Those details matter if you plan to store private code or credentials, so review the terms and privacy policy and ask the project for specifics before relying on the hosted service.

Self-hosting gives you more control over where repository and CI services run, but also leaves you responsible for configuration, updates, backups and access security. Avoid putting sensitive credentials into build jobs until you understand how your chosen setup handles them. The homepage does not list a licence or a formal security certification.

To get started, you can join Tangled’s hosted service or bring an AT Protocol account. For self-hosting, Tangled says you can choose repository hosting with knots, CI with spindles, or your own clients. Its stated deployment options include a NixOS module and Docker images, which you can run on a VPS or in a homelab.

For code collaboration, Tangled supports plain Git and describes agent activity as operating over Git. If you use Jujutsu, you can take advantage of its native stacked-change workflow. CI runs in NixOS-powered microVMs, can build containers with Docker, and can set up services such as Postgres and Redis. Tangled says cached inputs help speed subsequent runs.

The homepage does not give performance benchmarks, service availability figures or a detailed mobile experience. If you are evaluating it for a team, start with a low-risk repository and a simple CI job. Confirm your account setup, federation needs and any hosted limits before migrating a production project.

Tangled’s federation, Jujutsu support and self-hosting choices are useful if you want to shape how your team collaborates. Those same choices create a learning curve if your team expects one managed service with familiar defaults. You may need to understand AT Protocol accounts, repository hosting options and how CI runs before settling on a workflow.

The project does not publish hosted pricing, detailed service limits or audit information on its homepage. That makes it harder to assess long-term costs and hosted-service assurances before signing up. The homepage also does not provide quantified uptime or CI speed claims, so do not assume it will match a larger established forge for your workload.

Tangled is best approached as an option to evaluate, not an automatic replacement for a current platform. Try it with a non-sensitive project, verify how your team’s Git or Jujutsu workflow fits, and clarify pricing and security practices first. If you need clear enterprise assurances or known costs upfront, compare alternatives before migrating.