stategraph.com

What It Is

Stategraph positions itself as an “infrastructure database,” targeting long-standing pain points in Terraform/OpenTofu state management: file-based state leads to global locks, teams waiting in queues, state-splitting complexity, and bottlenecks in drift detection. It replaces the traditional file-locking model with a database-backed state model, graph-structured resource relationships, and ACID transactions, with the goal of bringing infrastructure resources, changes, and execution agents into a single system of record.

Core Capabilities

Based on the main text, the Free tier already includes hosted PostgreSQL state storage, search, blast-radius analysis, and a graph browser. Paid tiers add resource-level parallel plan/apply, multi-state operations, immutable audit logs, inventory dashboards, SQL queries, gap analysis, Webhooks, PR automation, and drift detection. Security and enterprise features include SSO/SAML, RBAC, a complete API, and single-tenant isolated Postgres. Terraform/OpenTofu support is explicitly stated, and BYOC can be deployed into AWS, GCP, or Azure accounts, but there is no mention of other IaC tools or language SDKs.

Pricing and Deployment

Pricing is enterprise-oriented: Free is free but limited to 1,000 BIUs and shared tenancy; Starter starts at about $999/month annually; Professional starts at about $1,499/month annually; Enterprise starts at about $2,083/month annually. Paid tiers include 10,000 BIUs by default, with additional packages purchased based on infrastructure scale. Its BIU definition excludes IAM, security groups, route tables, data sources, and other “free wiring” resources, avoiding the penalty of charging by every terraform state list entry. Self-hosting, air-gapped deployment, and BYOC are only available on Enterprise.

Pros and Cons

The main strengths are a clearly defined problem and a direct focus on the lock contention and state-splitting issues common in Terraform/OpenTofu teams. Single-tenant Postgres, audit logs, SQL querying, and BYOC also make it suitable for compliance-oriented environments. The downsides are the high commercial entry point, with key capabilities such as the complete API, RBAC, SQL, and self-hosting concentrated in Enterprise. The main text also does not provide a migration process, performance data, SLA figures, or documentation examples, so real-world implementation complexity still needs to be validated through a trial.

Who It’s For and Access from China

Stategraph is better suited to mid-to-large platform engineering, SRE, and DevOps teams—especially organizations where multiple teams frequently modify Terraform/OpenTofu, are often blocked by state locks, and need auditing plus inventory queries. For small teams that only need remote state, Free or a traditional backend may be more economical. Access from China, payment methods, and network connectivity are not disclosed in the main text, so they should be treated as “unknown.” Comparable options include Terraform Cloud/Enterprise, Spacelift, Env0, Scalr, Atlantis, Terragrunt, or OpenTofu’s native remote backends.