Terms of service

Last updated: October 27, 2026

These terms cover your use of knotless.dev. By logging in, you agree to them. If you don't agree, don't log in. You can still read public pages without an account.

What knotless.dev is

knotless keeps git repositories in atproto accounts. Your account lives on a PDS (personal data server), the host that stores your public records; it is named by a DID, a permanent identifier, and shown by a handle such as alice.example.com. A repository, and the pulls, issues and comments people write about it, are records in their authors' own accounts.

knotless.dev is one server running knotless. It indexes those records, caches git data, draws the web pages, and runs hosted CI. It is run by the knotless project's maintainers.

knotless is open source, under MIT or Apache-2.0, and anyone can run their own server. These terms cover knotless.dev only. Other servers set their own.

Who may use it

You must be at least 16 years old to log in.

You need an atproto account to log in. If you don't have one, "Create one" in the login dialog makes an account on selfhosted.social, a PDS run by others, under their own terms. knotless.dev then logs in to it as it would any account. atmosphereaccount.com explains these accounts, and atproto.com the protocol.

If you use knotless.dev for an organization, you agree to these terms for it.

What you own

You own what you write. Your repositories, pulls, issues and comments are records on your PDS, and your PDS is where they live. knotless.dev does not take ownership of any of it, and these terms grant it no license beyond what it needs to do what this page says.

Public records on a PDS can be read by anyone, and knotless.dev reads them as anyone can. It indexes your public records, caches your git data, and shows them on its pages and to clones.

knotless.dev writes to your account only when you, or someone you allowed, acts. When you open a pull, comment or star on its pages, or push or work through its gateway or MCP server, it writes those records through the OAuth session you gave it. When you delegate a repository to its gateway, your collaborators' pushes and the merge queue's merges are written to your account through that delegation. It never writes on its own.

Respect other people's licenses. Code you push should be yours to share, or shared under terms that allow it.

The rules

What you may and may not do here is set out in the community guidelines. They apply to people and to the agents (MCP clients, bots) that act for them. An account's agents are its owner's responsibility.

If you break them

Anyone logged in can report an account, repository or record with the report action in the app. The maintainers read reports and decide what to do.

When the maintainers take down an account, repository or record, knotless.dev stops showing it. It leaves the index, its pages and clones answer "not found", and it is published as a !takedown label. A takedown of an account also stops it logging in to knotless.dev and ends its MCP tokens. A takedown lasts through rebuilds of the index.

A takedown does not touch your PDS. Your records stay in your account, and you can take them elsewhere, including to another knotless server.

If you think a takedown was a mistake, ask for a review by opening an issue on the knotless issue tracker. Say what was taken down and why you think it should come back. If your account can no longer log in, open it from another account. The maintainers will read it and answer there.

The maintainers may also stop serving an account or repository to keep knotless.dev working, for example one whose CI is using the runners for something else.

Hosted CI

knotless.dev runs workflows for repositories that ask for its runners. Each run is in a sandbox with 2 CPUs, 3 GiB of memory, 4,096 processes and one hour. An owner has two jobs running at once. Over 30 days, an owner gets 2,000 minutes on public repositories and 500 on private ones, and past that runs one job at a time.

A run cannot reach the server it runs on, private networks, cloud metadata addresses or mail ports.

Workflows from other people's pulls run only when the repository's owner asks. Pulls never get secrets, and secrets are masked in logs. The minutes public repositories use are published as records; the minutes of private ones are not.

CI is offered as is, for building and testing the code in the repository. There is no promise that a runner will be free, that a run will finish, or that the limits will stay the same. The maintainers may pause a repository's runs when they are used for something else, such as cryptomining.

No warranty

knotless.dev is provided as is and as available, without warranty of any kind. It may be down, lose cached data, or change. Your records are on your PDS, so keep what matters there, and keep your own copies of your code.

Limitation of liability

To the extent the law allows, the knotless project's maintainers are not liable for any indirect or consequential loss, or for lost data, profit or work, arising from your use of knotless.dev or from its being unavailable.

Ending

You can stop using knotless.dev at any time: log out, and delete your repositories or your account at its PDS. The maintainers may stop serving any account or repository that breaks these terms or the guidelines, or close knotless.dev altogether. What these terms say about ownership, warranty and liability still holds after that.

Changes to these terms

The maintainers may change these terms. When they do, the date at the top changes. If you keep using knotless.dev after a change, you accept the new terms.

Contact

Open an issue on the knotless issue tracker, or report something with the report action in the app. There is no email address.