Works with your existing Terraform/OpenTofu

Terraform & OpenTofu without the
state file bottleneck

Stategraph replaces the flat state file with a database-backed graph. Independent changes can run in parallel, and the state becomes queryable and auditable. No code changes.

Parallel teams No lock waiting Audit-ready state
Demo Day · February 25
--
Days
:
--
Hours
:
--
Mins
:
--
Secs
Click to register →

Plans in seconds, not minutes

Same infrastructure. Same change. Dramatically different wait time.

Traditional Backend
$ terraform plan
Refreshing state... [2847 resources]
! 3m 47s elapsed...
Still refreshing: aws_instance.web[142]
Stategraph
$ stategraph plan
Computing change cone... [12 resources]
✓ Plan ready in 2.3s
Skipped 2835 unchanged resources

Learn how it works →

One transaction across all your states

Atomic multi-state operations. No more sequential plan→apply→plan→apply chains or external orchestration scripts.

Sequential Orchestration

State A
→
State B
State A
→
State B

4 operations
Sequential, incomplete visibility

Multi-State Transaction

State A
State B

txn_abc123

1 operation
Atomic, complete visibility

Learn about multi-state transactions →

What Stategraph makes possible

∥

Teams run in parallel

If resources don't overlap, everyone ships
?

Query your infrastructure

SQL-queryable state, not JSON parsing
◉

Resource-level control

Resource-level locking & RBAC
∥

Teams run in parallel

If resources don't overlap, everyone ships

?

Query your infrastructure

SQL-queryable state, not JSON parsing

◉

Resource-level control

Resource-level locking & RBAC

From flat files to dependency graphs

OLD MODEL
State as a file
Global locks
Serial execution
Audit via CI logs
→
STATEGRAPH
State as a database
Resource ownership
Parallel where safe
SQL queries and diffs

Under the hood: API and database

Stategraph has two parts: a CLI that provides the same interface as Terraform, and a backend that fundamentally reimagines how state is stored and processed—as a dependency graph in PostgreSQL, not a flat file. The CLI doesn't orchestrate Terraform; it executes graph-aware operations directly against the database.

stategraph plan
stategraph apply
stategraph query

STATEGRAPH CLI

Replaces Terraform & OpenTofu CLI
Manages Graph-aware execution
Provides Query interface
Replaces
Terraform & OpenTofu CLI
Manages
Graph-aware execution
Provides
Query interface

HTTP API SERVER

POST /transactions
GET /transactions/{id}
GET /graph
POST /query

POSTGRESQL DATABASE

id
type
name
depends_on
status
1
aws_vpc
main
NULL
active
2
aws_subnet
public-1a
1
active
3
aws_subnet
public-1b
1
active
4
aws_security_group
web-sg
1
active
5
aws_instance
web-server-1
2,4
active
6
aws_instance
web-server-2
3,4
pending
7
aws_alb
main-lb
2,3
active
8
aws_db_instance
postgres-prod
3
active
Resources as rows • Dependencies as foreign keys • Graph traversal via SQL joins
Parallel-safe
Disjoint ops run together
SQL-queryable
Direct database access
Graph-native
Dependencies as edges
Audit-ready
Every change tracked

Visual interface

Visualize the dependency graph, run SQL queries, and browse transactions — all in one place.

Stategraph mock UI showing a dependency graph, SQL query panel, and transaction log Stategraph mock UI showing a dependency graph, SQL query panel, and transaction log
Graph explorer SQL results Transaction log Resource ownership
shell
$ # Want this in your hands? $ echo "Notify me when Stategraph launches" | \ mail -s "Launch Updates" hello@stategraph.com

See the difference

Watch how Stategraph parallelizes your infrastructure operations

Traditional Backend

terraform apply 00:00
[VPC ] waiting
[Subnets ] waiting
[Security ] waiting
[RDS ] waiting
[ALB ] waiting
[ASG ] waiting
[Route53 ] waiting
[CloudFront ] waiting

Stategraph

stategraph apply 00:00
[VPC ] waiting
[Subnets ] waiting
[Security ] waiting
[RDS ] waiting
[ALB ] waiting
[ASG ] waiting
[Route53 ] waiting
[CloudFront ] waiting
Parallel Team execution
Graph Dependency aware
SQL Queryable state

Get launch updates

Be the first to know when Stategraph launches.

Why Terraform & OpenTofu need a new backend

FILE
State is stored as a monolithic JSON file. Every plan loads the entire file. Result: slow plans at scale.
LOCK
Global lock blocks all teams. Even those working on unrelated resources. Result: teams queue behind each other.
BLIND
State is opaque binary data. No queries. No insights. No audit trail. Result: Debugging via CI logs.
SERIAL
Resources execute one at a time. Even when operating on completely separate parts of the tree. Result: Wasted time waiting for unrelated changes.

Get started in 5 minutes

Point your Terraform backend at Stategraph. Your state gets stored as a graph in PostgreSQL, and you instantly get the full infrastructure database.

backend.tf
terraform {
backend "http" {
address = "http://stategraph.local/api/v1/states/backend/prod"
}
}

What you get immediately

Everything you need to query, analyze, and ship infrastructure faster

Web Console

Inventory, insights, blast radius analysis, and gap detection

SQL Queries

Query your infrastructure with MQL—SQL for cloud resources

Complete History

Every state change, every transaction, fully auditable

PostgreSQL Storage

ACID guarantees, structured data, relational queries

Parallel Execution

Graph-aware parallelization, 10x faster than serial

Resource Locking

Fine-grained locks, teams work in parallel

View quickstart guide →

Frequently Asked Questions

Contact

Contact us
$ echo "your message" | mail -s "Stategraph Inquiry" hello@stategraph.com