Self-hosted

Run Stategraph in your own infrastructure.

Docker Compose, Kubernetes, Amazon ECS, or Google Cloud Run. Open Source is free, with no license key. Enterprise has every feature of the hosted service. Your state and data stay inside your own environment.

Docker Compose Kubernetes Amazon ECS Air-Gapped

Where Stategraph runs

Run it managed, run it yourself, or have us run it inside your account.

Managed

Stategraph Cloud

The fastest way to start — we run the server, upgrades, and availability. See pricing →

We run it, in your cloud

Bring Your Own Cloud

We operate Stategraph inside your AWS, GCP, or Azure account. Enterprise →

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.

Docker Compose Development · small teams · evaluation

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 →
Kubernetes Production · scaling · existing K8s

Deploy with the official Helm chart. Native liveness and readiness probes plug straight into your cluster's health checks and rollouts.

Kubernetes guide →
Amazon ECS AWS-native · managed containers

Stand it up on ECS Fargate with the official Terraform module — managed container orchestration without running a cluster yourself.

Amazon ECS guide →
Google Cloud Run GCP-native · serverless

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 server images, Open Source and Enterprise, the Helm chart, and ECS Terraform module are public.

The same Stategraph, in your environment

Self-hosting changes where it runs. The edition sets what you get.

Two editions, one server

CLI API Console
Enterprise: identical to hosted

Open Source runs Orchestration with the console and the API, free under MPL-2.0. Enterprise adds Infrastructure as a Database, Insights, Inventory, Cost, and AI Agents, and works exactly as Stategraph Cloud does. Compare editions →

Your data, your perimeter

Your infrastructure
state · database · never leaves

State lives in a PostgreSQL database you run. Air-gap it entirely if your compliance posture requires it.

Credentials stay local

CLI → Your Cloud
server never sees them

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.

stategraph — operations
[liveness] GET /health/live — for orchestrator restart probes [readiness] GET /health/ready — 200 only when the backend is serving [config] environment variables — no config files to template [state] PostgreSQL — your database, your backups [auth] Local, Google OAuth, or OIDC — wire in your IdP [upgrades] pull a new image tag on your own schedule

Run it your way

Start with Open Source: clone the repository and run docker compose up -d. For Enterprise, tell us your stack and compliance posture, and we get you running.

Start with Open Source Talk to sales