Stategraph
by Stategraph • • Infrastructure as Code (IaC) Tools
Stategraph is infrastructure as code software for Terraform and OpenTofu teams, pairing pull request automation with state kept in PostgreSQL. Open source core.
Stategraph removes the single state lock that makes Terraform teams queue changes, split state files and wait on slow plans. It keeps Terraform state as a dependency graph in PostgreSQL, so a plan reads only the part a change reaches. Stategraph is made by Terrateam B.V., a bootstrapped and independent company registered in Amsterdam. Its orchestration engine began in 2021 as Terrateam, went open source under MPL-2.0 in 2024 and now runs as Stategraph Orchestration. Orchestration plans every pull request on GitHub or GitLab and posts the plan, the cost change, the policy checks and the approvals in the review. The apply runs on merge or on a comment, layer by layer in dependency order. Apply requirements set who signs off in each environment, and Gatekeeper opens a named gate when a Checkov, Conftest, OPA or custom check fails. Drift detection runs plans on a schedule, and Infracost adds the cost of each change. Infrastructure as a Database brings resource-level locks, conflicts settled at commit, multi-state transactions, SQL over every resource and blast radius across states. The product suits platform and infrastructure teams running Terraform or OpenTofu in monorepos, multi-environment setups or regulated industries. Infrastructure as a Database is built for teams whose large states make plans slow and applies queue, and it works with or without Orchestration. A small team can let Stategraph Cloud host the orchestration. An organisation with stricter rules can self-host Orchestration and run Infrastructure as a Database in its own infrastructure, air-gapped if needed. The open-source edition suits engineers who want to run the engine themselves. Each infrastructure change begins as a pull request, where reviewers read the plan comment and see which approvals production still needs before merging. Runs execute on the team's own GitHub Actions or GitLab CI runners, and private runners reach APIs and databases inside a private network. Credentials for AWS, Azure and Google Cloud come from static keys or OIDC. Engineers ask questions of their estate with stategraph query and check what a change touches with stategraph blast-radius. Gap analysis compares an AWS or GCP account with its states and writes the import blocks for anything no state manages yet.
Pricing
View plans-
Free
Free
- Hosted on Stategraph Cloud
- Up to 3 users, 50 runs a month and 1 concurrent worker
- Every Orchestration feature
- SSO, RBAC, CODEOWNERS, Gatekeeper and centralized config
- Drift detection
- 30-day audit retention
- Community support
- New accounts start with 30 days of Orchestration Pro, no credit card, then move to Free
-
Orchestration Pro
$1,000 per month
Per month, billed annually as $12,000 a year; no per-seat or per-run fees
- Same price on Stategraph Cloud or self-hosted
- Everything in Free with unlimited users, runs and concurrent workers
- Self-hosted adds RBAC, CODEOWNERS enforcement, approval gates, multiple drift schedules and API access tokens
- 365-day audit retention
- Priority support by email and Slack
- Onboarding session with Stategraph engineers
- 30-day trial, no credit card
-
Infrastructure as a Database
$25,000 per year
Starting price per year, annual contract through sales
- Plans read only what a change reaches
- Changes that do not overlap apply at the same time
- Multi-state transactions and SQL across every state
- Single-tenant on Stategraph Cloud, with an isolated Postgres
- Self-hosted and air-gapped, or run by Stategraph in your AWS, GCP or Azure account
- Dedicated support and a custom SLA
- 30-day trial, no credit card
- Works without Orchestration
-
Open Source (self-hosted)
Free
- MPL-2.0 license, run in your own infrastructure
- Every core Orchestration workflow
- Terraform, OpenTofu, Terragrunt, Pulumi and CDKTF
- Up to 3 active users a month per GitHub or GitLab installation
- Unlimited runs and concurrent workers
- One drift schedule per repository
- Community support
Features
- Included: Providers for AWS, Azure and Google Cloud
- Included: Execution plan preview before apply
- Included: Remote state with locking
- Included: Drift detection against deployed cloud state
- Not included: Private module registry
- Included: Infrastructure in general-purpose languages
- Included: Policy-as-code checks at plan time
- Included: Pull-request plans from version control
- Included: Cost estimate on each plan
- Included: Import of existing cloud resources
- Not included: Encrypted workspace variables
- Included: Per-workspace access control
- Included: Approval required before apply
- Not included: Auto-destroy of temporary environments
- Included: Cross-stack output references
- Included: Self-hosted agents for private networks
- Included: Open source IaC engine
Additional Features
- Pull request plans posted as review comments
- Apply on merge or on a stategraph apply comment
- Layered runs and stacks in dependency order
- Apply requirements per environment
- Gatekeeper approval gates on failed checks
- CODEOWNERS enforcement
- Checkov, Conftest and OPA checks
- Scheduled drift detection, hourly to monthly
Best for
- Terraform and OpenTofu teams whose changes queue behind one state lock
- Platform teams running Terraform in monorepos or multi-environment setups
- Teams in regulated industries that need per-environment sign-off before apply
- Small teams wanting hosted Terraform automation without running it themselves
- Teams whose infrastructure code lives on GitHub or GitLab
- Organisations that want to self-host the orchestration engine
- Teams with large states whose plans take too long to refresh
Use cases
- Planning every Terraform pull request and applying on merge
- Running applies to different resources at the same time
- Querying resources across every state with SQL
- Checking what a change touches before it merges
- Requiring platform and security approval before production applies
- Blocking non-compliant plans with OPA or Conftest policies
- Showing the monthly cost change of each pull request
- Finding drift between code and cloud on a schedule
- Bringing unmanaged AWS or GCP resources under Terraform
- Running plans on runners inside a private network
- Planning a producer and a consumer state in one change
- Running Terraform state as a database in an air-gapped network
Screenshots & Videos
Explore Stategraph in action
User Reviews
Compare with Similar Software
Click to compare side by side with Stategraph