Production
What to harden before a self-hosted Future AGI instance goes live
Everything past a local trial happens here. The default Docker Compose stack boots with placeholder secrets, no TLS, and compose-managed data stores. That’s fine on a laptop. Before real traffic reaches the instance, work through the flow below in order, then keep each page as a runbook.
In this page
Production readiness for a self-hosted instance breaks into five steps. Do them in order the first time.
Before you go live
Checklist
The go-live pass: secrets, prod runtime flags, and managed data stores
Security & TLS
Terminate TLS in front of the stack and lock down secrets
Operating it
Was this page helpful?
Questions & Discussion