Monorepo for Tangled forked from tangled.org/core
core docs DOCS.md
83 kB · 2812 lines
Markdown

--- title: Tangled docs author: The Tangled Contributors date: 21 Sun, Dec 2025 abstract: | Tangled is a decentralized code hosting and collaboration platform. Every component of Tangled is open-source and self-hostable. [tangled.org](https://tangled.org) also provides hosting and CI services that are free to use. There are several models for decentralized code collaboration platforms, ranging from ActivityPub’s (Forgejo) federated model, to Radicle’s entirely P2P model. Our approach attempts to be the best of both worlds by adopting the AT Protocol—a protocol for building decentralized social applications with a central identity Our approach to this is the idea of “knots”. Knots are lightweight, headless servers that enable users to host Git repositories with ease. Knots are designed for either single or multi-tenant use which is perfect for self-hosting on a Raspberry Pi at home, or larger “community” servers. By default, Tangled provides managed knots where you can host your repositories for free. The appview at tangled.org acts as a consolidated "view" into the whole network, allowing users to access, clone and contribute to repositories hosted across different knots seamlessly. --- # Quick start guide ## Login or sign up You can [login](https://tangled.org) by using your AT Protocol account. If you are unclear on what that means, simply head to the [signup](https://tangled.org/signup) page and create an account. By doing so, you will be choosing Tangled as your account provider (you will be granted a handle of the form `user.tngl.sh`). In the AT Protocol network, users are free to choose their account provider (known as a "Personal Data Service", or PDS), and login to applications that support AT accounts. You can think of it as "one account for all of the atmosphere"! If you already have an AT account (you may have one if you signed up to Bluesky, for example), you can login with the same handle on Tangled (so just use `user.bsky.social` on the login page).…