Plan, approve, and apply from pull request comments. Policy, RBAC, and cost in every review.
Runs any IaC engine
Connect GitHub or GitLab, open a pull request, get your first plan. Quickstart · Join our Slack
Stategraph gives you complete visibility into every change before it hits production.
The plan
Approve and apply
Approval Requirements
malcolm approved these changesjoshcommentedApplies ✅
| Directory | Workspace | Result |
|---|---|---|
production/compute | default | Applied ✅ |
production/network | default | Applied ✅ |
Apply complete. Resources: 2 added, 1 changed, 0 destroyed.
Your engines, your directory layout, your runners.
One pull request workflow for every tool.
Read the docsSee the bill before you merge.
Read the docsproduction/**team:platformiam/**team:securitysandbox/**everyoneWho can plan and apply, per directory and workspace.
Read the docsproduction/networkdriftproduction/computein syncscheduledailyScheduled plans find changes made outside your code.
Read the docsStategraph Cloud, or self-hosted on your infrastructure.
Read the docsstategraph planstategraph applyPlan, apply, and approve from comments.
Read the docsEvery change meets your rules before it applies.
-/+ google_sql_database_instance.main must be replaced
Gate added: database replacement
To approve, comment:
stategraph gate approve db-replace“We wanted to keep everything in the pull request flow. Stategraph gave us everything we needed, and it was significantly cheaper.”
“Fast forward to the integration with Stategraph… I’ve been totally removed from that loop.”
“I think 10 minutes later, I was actually shipping something through it.”
“We were looking for a centralized way to run Terraform, and that’s when we found Stategraph.”
Infrastructure as a Database moves your state into PostgreSQL as a dependency graph. Locks are per resource, so pull requests on one state apply together.
Orchestration with a state file: lock per directory
With Infrastructure as a Database: lock per resource
No meter per resource, user, or run. The same price on Stategraph Cloud or self-hosted.
See pricingusersunlimitedplans and appliesunlimitedconcurrent workersunlimitedprivate runnersincludedAdd every engineer and run as many plans at once as you need. The price does not change.
See pricingEvery Orchestration feature is in the one price, with priority support and an onboarding session.
See pricingStategraph Orchestration is open source under MPL-2.0, and its source is on GitHub. Orchestration Pro and Infrastructure as a Database are commercial. See the license page.
Yes. Every edition runs on your own infrastructure, with Docker Compose, Kubernetes, Amazon ECS, or Google Cloud Run. The Open Source edition needs no license key. See self-hosting.
Each migration guide has a script that writes .stategraph/config.yml from your current setup and reports what to resolve by hand. Your Terraform and OpenTofu code stays as it is. You then roll out on a pull request. See migration.
The Open Source edition is free to self-host, and Stategraph Cloud has a Free plan. Orchestration Pro is one flat yearly price, with no limit on users or runs. See pricing.
Orchestration runs Terraform from pull requests, and your state stays in your own backend. Infrastructure as a Database replaces that backend with PostgreSQL. It comes in the Pro + Infrastructure as a Database plan, from $25,000 a year.
Stategraph brings GitOps, policy, and automation to your infrastructure stack.
Plans 👍
production/computedefaultproduction/networkdefaultStategraph Plan Output 👍
Expand for plan output details
Cost Estimation
To apply all these changes, comment:
stategraph apply