Operations
One database, one process
A forge you can run on a machine you already have, without operating a queue cluster before the first repository exists.
What it needs to run
Bun, MySQL or Postgres, and the git binary. The local environment is provisioned by pantry, which installs the toolchain, starts the database, and creates it from your environment file.
- No message broker required to start
- No object store required to start
- No separate worker fleet to operate
Your code stays on your infrastructure
That is the whole point of self-hosting, and it matters more when agents are involved: the code they read and write never leaves the machines you control.
Backups are ordinary
Repositories are bare git directories on disk and forge metadata lives in MySQL or Postgres. Back up those directories and the database. If packages are enabled, include Pantry's artifact storage and metadata too.
Scale later, in the usual places
Queues, caches, and search are drivers rather than requirements. Turn them on when there is a reason to, not because the install guide said so.
Run it this afternoon
MIT licensed, open source, and yours to operate.