Compare
Compare Stategraph to other IaC solutions
Most Terraform tools are runners around the same state file. Stategraph replaces the file with a database. Compare the tool you run today.
Teams running Terraform on Stategraph
Comparisons
The engine itself
Terraform and OpenTofu vs Stategraph
Same HCL, modules, and providers. State moves from a JSON file behind one lock to a graph in PostgreSQL.
See the features →
1 fileone global lock, every plan walks it all
→
1 graphlocks per resource, plans sized to the change
Open source
Atlantis vs Stategraph
One server runs Terraform with your credentials and holds a lock until the pull request merges. Keep it with Stategraph underneath, or replace it.
Read the comparison →
1 lockper project, per PR
→
0 locksdisjoint changes apply together
Hosted SaaS
HCP Terraform vs Stategraph
One lock per workspace, one run at a time, and a bill for every resource, every hour.
Read the comparison →
$0.99per resource per month, Premium list
→
Flatusers, runs, workers. Never resources
Your own CI pipeline
Build your own vs Stategraph
CI jobs, a bucket, and a lock table work until two pull requests touch the same state. The Stategraph CLI runs in that same pipeline.
Read the comparison →
3+ hoursno-op plan, 800 MB state
→
97 ssame state, same change
Wrapper
Terragrunt vs Stategraph
Units with a state file each, wired with a second configuration language. Stategraph fixes the state layer, so there is nothing to wrap.
Read the comparison →
N unitsN state files, N locks, mocked outputs
→
1 planacross every state a change touches
Hosted orchestration
Spacelift vs Stategraph
The most configurable orchestration in the category. Each stack still locks one state file, and concurrency is a number of workers you buy.
Read the comparison →
1 workerequals 1 concurrent run
→
Unlimitedconcurrent workers on Pro
At a glance
Feature comparison
Every tool in this category runs plan and apply. The differences are in the state underneath, the locking, and what you can query afterward.
| Capability | Stategraph | Atlantis | HCP Terraform | Terragrunt | Spacelift | Build your own |
|---|---|---|---|---|---|---|
| Where state lives | ✓PostgreSQL graph |
✗JSON file in your backend |
✗JSON file per workspace
✗JSON file per unit ✗JSON file per stack ✗JSON file in a bucket | |||
| Plan scope | ✓Only the affected subgraph |
✗Whole root module |
✗Whole workspace |
✗Whole unit |
✗Whole stack |
✗Whole state file |
| Lock scope | ✓The resources a change touches |
✗Project, for the life of the PR |
✗Workspace, one run at a time |
✗One lock per unit |
✗Stack lock, one run at a time |
✗Whole file, via a lock table |
| A change across states | ✓One atomic transaction |
✗Sequenced by hand |
●Run triggers, or Stacks |
✗run --all, applied outputs or mocks |
●Downstream runs after upstream apply |
✗Sequential jobs |
| Query your infrastructure | ✓SQL across every state |
✗Not available |
●Workspace metadata filters |
✗Not available |
●Resources view, no query language |
✗Grep the JSON |
| Who runs Terraform | ✓Your runner. The server never sees your cloud |
✗The Atlantis server, with your credentials |
●HashiCorp's VMs, or your agents |
✓Your runner, one process per unit |
●Spacelift's workers, or private ones on paid plans |
✓Your runner |
| Pricing unit | ✓Flat. $12,000 a year, no limits |
●Free. You operate everything |
✗Every resource, every hour |
●MIT. Scale from $500/mo at 200 units |
✗Annual plan sized by workers |
●Your engineers' time |
Customers
Customer quotes
“Stategraph has been a game-changer for us. Transitioning from Atlantis was smooth, and the support from their team was exceptional.”
Marko Kuljanski, Engineering at Patients Know Best · Case study →“We wanted to keep everything in the pull request flow. Stategraph gave us everything we needed, and it was significantly cheaper.”
Security Engineer at Zip, after evaluating Atlantis, Spacelift, and Terraform Cloud · Case study →Try it with your own state
Import a state file and run your first plan in under 30 minutes. Pro is free for 30 days, no credit card.