tangled

Name: tangled
Brand: tangled

AI Native

Tangled is a decentralized Git hosting and code collaboration platform that provides self-hostable Git servers (knots), a federated web appview for cross-knot discovery, stacked pull request workflows using Jujutsu change IDs, issues/discussions, and self-hostable CI runners (spindles) built on the AT Protocol identity/data layer.

Est 2025|Raised $5.6M|5 Ref Customers

Website|FTEs 2

MarketsSource Code Management (SCM)

01Competitive Landscape

Narrative analysis

Areas where Tangled shows strengths - Architecture choice (AT Protocol): Tangled’s use of AT Protocol can enable portable identity and social-graph integration that differs from traditional Git forges. - Workflow support: Tangled supports round-based PRs, inter-diffing between rounds, and stacked PRs using Jujutsu change IDs. - Self-hosting model: Knots are positioned as first-class, self-hostable components rather than an afterthought. Where competitors are stronger - GitHub and GitLab: larger ecosystems, broader integration catalogs, compliance attestations, and mature CI marketplaces. - Radicle: stronger local-first/offline collaboration model without a central appview requirement. - Codeberg/Forgejo: established nonprofit hosting options for OSS with clear governance and predictable constraints. Market adoption signals (cautious) - Tangled’s self-reported figures: a modest number of users and repositories. - Press coverage indicates community presence, but those metrics are not independently audited.

	Tangled	GitLab	Codeberg / Forgejo-hosted
Starting Price	Public documentation indicates hosted services are free (pricing not formalized)	Free tier; paid plans publicly listed (example: Premium at listed price points)	Free (donation/nonprofit model); quotas/limits may apply
Primary use case	Independent developers and OSS projects seeking a self-hostable Git service integrated with AT Protocol features	Teams needing mature CI/CD, enterprise controls, and integrated DevSecOps	OSS projects seeking a nonprofit/community host with Forgejo UX
Noted strengths	Federated architecture with knots, stacked PR model, AT Protocol integration	Broad feature set, mature CI/CD, enterprise governance/security features	Community-run hosting model, familiar Git hosting experience
Noted weaknesses	Early-stage product with a smaller ecosystem; limited public documentation of enterprise features and certifications; trade-offs in decentralization design	Can be complex for some workflows; enterprise features behind paid tiers; usage costs for CI minutes/storage	Storage limits/quotas; fewer workflow innovations compared with newer designs

01Competitive Landscape

Narrative analysis

Areas where Tangled shows strengths

Architecture choice (AT Protocol): Tangled’s use of AT Protocol can enable portable identity and social-graph integration that differs from traditional Git forges.
Workflow support: Tangled supports round-based PRs, inter-diffing between rounds, and stacked PRs using Jujutsu change IDs.
Self-hosting model: Knots are positioned as first-class, self-hostable components rather than an afterthought.

Where competitors are stronger

GitHub and GitLab: larger ecosystems, broader integration catalogs, compliance attestations, and mature CI marketplaces.
Radicle: stronger local-first/offline collaboration model without a central appview requirement.
Codeberg/Forgejo: established nonprofit hosting options for OSS with clear governance and predictable constraints.

Market adoption signals (cautious)

Tangled’s self-reported figures: a modest number of users and repositories.
Press coverage indicates community presence, but those metrics are not independently audited.

	Tangled	GitLab	Codeberg / Forgejo-hosted
Starting Price	Public documentation indicates hosted services are free (pricing not formalized)	Free tier; paid plans publicly listed (example: Premium at listed price points)	Free (donation/nonprofit model); quotas/limits may apply
Primary use case	Independent developers and OSS projects seeking a self-hostable Git service integrated with AT Protocol features	Teams needing mature CI/CD, enterprise controls, and integrated DevSecOps	OSS projects seeking a nonprofit/community host with Forgejo UX
Noted strengths	Federated architecture with knots, stacked PR model, AT Protocol integration	Broad feature set, mature CI/CD, enterprise governance/security features	Community-run hosting model, familiar Git hosting experience
Noted weaknesses	Early-stage product with a smaller ecosystem; limited public documentation of enterprise features and certifications; trade-offs in decentralization design	Can be complex for some workflows; enterprise features behind paid tiers; usage costs for CI minutes/storage	Storage limits/quotas; fewer workflow innovations compared with newer designs