llms.txt
# Firetower
> Run any coding agent, on your own servers, from anywhere.
Firetower is an open-source control plane for coding agents. Point it at a server you can SSH into, describe some work, and it cuts a branch, opens a worktree, starts tmux and keeps the agent running — attach from a browser or a phone, review the diff, ship the branch.
It runs on hardware you already have. There is no account, no telemetry
endpoint, and no hosted service in the loop. AGPL-3.0-only.
## Documentation
- [Getting started](https://usefiretower.com/docs/getting-started): Two ways to run Firetower — host it yourself today, or the cloud when it arrives. What each one asks of you.
- [Key concepts](https://usefiretower.com/docs/self-hosting): The three parts of Firetower — the Firetower itself, a worker on every machine that should run agents, and the client you open — and how they fit together.
- [Install the Firetower](https://usefiretower.com/docs/self-hosting/app/install): Install the Firetower — the control plane — with the CLI: what it asks, what it checks, and what it writes.
- [Add a machine](https://usefiretower.com/docs/self-hosting/machines/install): Run sessions on a machine you already own: give it Firetower's key, add it over SSH, and Firetower installs the worker.
- [Connect GitHub](https://usefiretower.com/docs/connect-github): Register the OAuth application a Firetower authorises against, turn on its device flow, and connect your GitHub account — with the one checkbox everybody forgets.
- [Users and teams](https://usefiretower.com/docs/permissions/people): Adding a person: the form, the password the server makes and shows once, and the one thing they have to do before anything else works. Resetting a password, switching somebody off, and removing them.
- [Permissions](https://usefiretower.com/docs/permissions): The four layers of permissions: people, teams, directories and resources. How ownership follows a directory, what stays yours whatever happens, and how to share one thing with one person.
- [Organise your resources](https://usefiretower.com/docs/organise): What to set up at three sizes: on your own, two to five people, and ten or more with different infrastructure. Why a team says who somebody is and a directory says which pool they reach, and when you need both.
- [Sharing a resource](https://usefiretower.com/docs/permissions/sharing): Two ways to let somebody at one of your things: move it into a directory and hand it over, or name them on it and keep it. Which to pick, and how to do each.
- [Sharing a workspace](https://usefiretower.com/docs/permissions/workspaces): A workspace holds a place and the conversations in it. The place is shared like anything else; a conversation belongs to whoever started it, because it spends their subscription and commits in their name.
- [Update](https://usefiretower.com/docs/update): Updating from the Updates screen: check for a release, see what the run would write and what it would end, watch it go, and bring each machine level with the deployment. Who may update what.
## Source
- [Repository](https://github.com/firetower-cloud/firetower): the control plane, the worker, and the protocol
between them.
