Self-host

The server and web application are AGPL-3.0-or-later. A self-hosted deployment runs the same software this instance runs — there is no reduced community edition and no hosted-service dependency for login, mail, storage, search, analytics, or the collaboration loop.

What you provide

• PostgreSQL — the transactional source of truth, and the analytics store. No separate warehouse is required to start.
• A Forgejo instance — the repository substrate. Prompts are real git repositories, which is why export is trivial and lock-in is not possible.
• Any standards-compliant OIDC provider — this deployment uses IDConnect; yours can use Keycloak, Authentik, Zitadel, or anything else that speaks OIDC. Identity is an adapter, not a hard dependency (ADR-005).

Where the instructions are

infra/SELF-HOSTING.md in the source repository. It covers the configuration contract, the order the first run has to happen in, upgrades, backup and restore, and the reverse-proxy and origin settings that are the most common way a self-hosted install goes wrong. Every variable in it was derived from the code rather than remembered.

What is not done yet

Nobody has yet stood this up on a clean host using only the published instructions and nothing else. Until that rehearsal has happened, treat the guide as a good-faith description written by the people who built it rather than as a tested runbook — the gap between those two is where every self-hosting afternoon is lost. Restore is the one exception: it has been verified by actually restoring from the offsite backup and comparing the recovered bytes against production.

If you try it, the failures you hit are the most useful contribution available right now.