Where Stategraph runs
Run it managed, run it yourself, or have us run it inside your account.
Stategraph Cloud
The fastest way to start — we run the server, upgrades, and availability. See pricing →
Self-hosted
The server image in your own infrastructure — four supported methods, fully air-gapped if you need it. Detailed below.
Bring Your Own Cloud
We operate Stategraph inside your AWS, GCP, or Azure account. Enterprise →
Four ways to self-host
Pick the method that fits your stack. The server is a container backed by PostgreSQL — it runs anywhere you run containers.
The quickest path to a running server. One compose file brings up the server and its PostgreSQL database for evaluation or a small team.
Docker Compose guide →Deploy with the official Helm chart. Native liveness and readiness probes plug straight into your cluster's health checks and rollouts.
Kubernetes guide →Stand it up on ECS Fargate with the official Terraform module — managed container orchestration without running a cluster yourself.
Amazon ECS guide →Run the server as a serverless, fully managed container on Cloud Run — scale to your load with no infrastructure to manage.
Cloud Run guide →The same Stategraph, in your environment
Self-hosting changes where it runs, not what you get.
Full feature parity
The identical CLI, API, and console. Velocity, Insights, Inventory, Cost, Orchestration, and AI Agents all work exactly as they do on Stategraph Cloud.
Your data, your perimeter
State lives in a PostgreSQL database you run. Nothing phones home; air-gap it entirely if your compliance posture requires it.
Credentials stay local
The CLI runs Terraform/OpenTofu locally against your cloud with your own credentials. The server coordinates state — it never runs Terraform and never sees your cloud credentials. More on security →
Built to operate
The hooks your orchestrator already expects.
Run it your way
Tell us your stack and compliance posture and we'll send the server image, the Helm chart, and the ECS module — and get you running.