About

State management
reimagined

Stategraph solves the fundamental mismatch between how Terraform stores state and how teams actually work.

Years of operational experience Built from customer pain
Why we built it Design Partners

The Problem We're Solving

Why state management needs a new approach

stategraph-origin.txt
$ cat stategraph-origin.txt THE PATTERN Every Terraform team hits the same walls: • State locks blocking deployments • Teams splitting state files to reduce contention • Engineers coordinating in Slack: "who has the lock?" • Drift detection jobs creating bottlenecks THE INSIGHT Terraform state is a coordination problem, but it's stored as a file. Most changes touch only a few resources, but Terraform locks 100% of the state. THE SOLUTION: STATEGRAPH A database-backed approach to state: • Graph structure matching resource relationships • Resource-level locking for parallel operations • SQL queries for infrastructure insights • ACID transactions for consistency THE EXPERIENCE Built by the team behind Terrateam, drawing from years of operating Terraform at scale. # State management, reimagined

Universal Pain Points

The same problems, everywhere

Lock Contention

Teams constantly coordinate around state locks. "Is anyone using state?" and "Can you release the lock?" become daily interruptions.

State Sprawl

Starting with one state file, teams end up with dozens. Not for logical separation, but to reduce lock contention.

All or Nothing

Small changes lock the entire state. A single resource update blocks all other teams, even those working on unrelated infrastructure.

Built From Experience

What we learned operating Terrateam since 2021

Monorepos to Multi-Cloud

From single repositories with thousands of resources to distributed multi-cloud architectures. The state lock problem scales linearly with team size, not infrastructure complexity.

Enterprises to Startups

Financial services with strict compliance needs. High-growth startups moving fast. Same bottleneck: waiting for state locks while simple changes queue behind complex operations.

Head-to-Head Platform Wins

Teams chose Terrateam over much larger, well-funded alternatives. Not for features, but for workflow flexibility and PR-native operations that match how developers actually collaborate.

Engineering Rigor at Speed

20,000+ automated tests. Daily production releases. OCaml core for correctness without compromise. These aren't nice-to-haves. They're table stakes for infrastructure tooling.

The Pattern We Couldn't Ignore

After years of building workarounds (lock queuing, automatic retries, state splitting) we realized we were treating symptoms, not the disease. The problem isn't how we manage locks. It's that there's only one lock for everything.

Why Build Stategraph?

Tools shouldn't dictate how teams organize their infrastructure

We're personally offended that state locking forces teams to split their repositories in unnatural ways. You shouldn't have to architect around tool limitations. Your repository structure should reflect how humans think about infrastructure, not how a file lock works.

Teams split state files not for logical separation, but to avoid lock contention. That's backwards.

Stategraph lets you design your infrastructure as you see fit. One repository, multiple repositories, whatever makes sense for your team. The tooling adapts to you, not the other way around.

Learn more about Terrateam, our GitOps automation solution for Terraform.

Stop coordinating. Start shipping.

Resource-level locking. Graph-based state. SQL queries on your infra.
Teams work in parallel. No more lock contention.

// Zero spam. Just progress updates as we build Stategraph.