From Terrateam to Stategraph
We ran Terraform automation for thousands of teams before we touched the state file. This is the road here.
2021
First commit
Two longtime collaborators — one from backend engineering and programming languages, one from SRE and platform operations — started building Terrateam: GitOps for Terraform, with the engine in OCaml from day one.
2022
First customers
Teams scaling Terraform in monorepos, multi-environment setups, and regulated industries adopted Terrateam and put it in the middle of their deploy path.
2023
Competing with giants
Terrateam won head-to-head evaluations against much larger, funded companies — on workflow flexibility and PR-native operations, not feature count.
2024
Open source
The engine went open source under MPL-2.0, with the core logic maintained in the open.
2025
The lesson becomes a product
Years of operating Terraform for other teams kept pointing at the same wall: the global state lock. Lock queues, retries, and state splitting all treated symptoms — the problem lives in the data model. Stategraph began: Terraform state as a database.
Today
One platform
Terrateam's orchestration engine lives on as Stategraph Orchestration. Stategraph stores state as a queryable dependency graph in PostgreSQL: plans from pull requests, conflicts detected per resource, SQL over everything you run.
Founders
Teams hit the same limits and then design around them. They split state, they wrap commands, they wait on a lock. Nobody should have to shape their infrastructure around a tool's constraints.
Infrastructure should be boring. It should work the same way every time. But it also needs to be flexible enough to reflect the way your team works. Not how some vendor thinks you should.
How we work
Independent by choice. We answer to the teams that pay us, and we build at a pace we can sustain.
The engine is a small, clean OCaml codebase. Infrastructure tooling has to be right before it is fast — ours is both.
Releases go out every day, and every change runs through more than 20,000 automated tests first.
Open source core, public roadmap, direct support from the people who wrote the code.