MPL-2.0 · Built in the open

Run Terraform in pull requests without the constraints

Plan, approve, and apply from pull request comments. Policy, RBAC, and cost in every review.

Connect GitHub or GitLab, open a pull request, get your first plan. Quickstart · Join our Slack

A pull request in the Stategraph console: its stacks in plan order with their status, and the plan and apply runs A pull request in the Stategraph console: its stacks in plan order with their status, and the plan and apply runs
Open Source

Infrastructure changes, right in your pull requests

Stategraph gives you complete visibility into every change before it hits production.

The plan

stategraphbot
commented

Plans 👍

DirectoryWorkspaceResultCreateUpdateReplaceDelete
production/computedefault✅2000
production/networkdefault✅0100
Total2100

Stategraph Plan Output 👍

Expand for plan output details
production/compute✓ Success
+ google_compute_instance.api_server
        n2-standard-4 instance in us-central1-a

    + google_compute_disk.data
        500GB SSD persistent disk

    Plan: 2 to add, 0 to change, 0 to destroy

Cost Estimation

+$266.24 USD
Total Monthly Difference (+14%)

To apply all these changes, comment:

stategraph apply

Approve and apply

Approval Requirements

Platform team1/1 approved
Security team1/1 approved
malcolm approved these changes
joshcommentedstategraph apply
stategraphbot
commented

Applies ✅

DirectoryWorkspaceResult
production/computedefaultApplied ✅
production/networkdefaultApplied ✅

Apply complete. Resources: 2 added, 1 changed, 0 destroyed.

Zip logo PrizePicks logo Haus logo Avaloq logo Xanadu logo January logo Patients Know Best logo NOV logo Mixpanel logo Notable Health logo Skool logo

Works with the setup you have

Your engines, your directory layout, your runners.

Security and governance

Every change meets your rules before it applies.

  • Policy checksOPA, Conftest, or Checkov in every plan.
  • GatekeeperApprovals decided by what the plan changes.
  • Approval rulesNamed users or teams, per directory.
  • Audit trailEvery plan, apply, and drift run.
  • Your CI, your credentialsOrchestration never needs your cloud keys.
  • Your state backendState stays in S3, GCS, or Azure Storage.
stategraphbot
commented
production/databaseplan
-/+ google_sql_database_instance.main must be replaced

Gate added: database replacement

Approval requiredteam:dba

To approve, comment:

stategraph gate approve db-replace

Teams running Stategraph in production

Customer success
“We wanted to keep everything in the pull request flow. Stategraph gave us everything we needed, and it was significantly cheaper.”
Victor ChenSecurity Engineer, Zip
Read the case study
130+
engineers managing infrastructure
  • Near-instant Terraform plans on self-hosted runners
  • Security-led rollout with built-in guardrails
“Fast forward to the integration with Stategraph… I’ve been totally removed from that loop.”
Jeff Bragdon, PrizePicks
“I think 10 minutes later, I was actually shipping something through it.”
Martin Delisle, Haus
“We were looking for a centralized way to run Terraform, and that’s when we found Stategraph.”
Alberto Fumagalli, Xanadu

All case studies

Infrastructure as a Database

When your team grows

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

state: production Queued
#479add read replica applying
#481rotate tls cert waiting
#482resize payments db waiting
#483widen subnet cidr waiting
one pull request at a time1 lock

With Infrastructure as a Database: lock per resource

state: production Parallel
#479add read replica applied
#481rotate tls cert applied
#482resize payments db applied
#483widen subnet cidr applied
no queuelocks per resource

Why teams switch

Common questions

Is it open source?

Stategraph 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.

Can I self-host it?

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.

How do I move from Atlantis, Terraform Cloud, Spacelift, env0, or Digger?

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.

How is it priced?

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.

What is the difference between Orchestration and Infrastructure as a Database?

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.

All questions

Infrastructure orchestration that fits your workflow

Stategraph brings GitOps, policy, and automation to your infrastructure stack.

  • No credit card
  • MPL-2.0 open source
  • Cloud or self-hosted