Frequently asked
questions

No code changes required. Your Terraform configurations, modules, and providers remain exactly the same. You just use the Stategraph CLI (a drop-in replacement for the Terraform CLI) and update your backend configuration to point to Stategraph.

Stategraph imports your existing .tfstate file on first run. Every resource, every attribute, every piece of metadata is preserved and migrated into the database. The import process is non-destructive, and you can always export back to standard .tfstate format if needed.

Stategraph builds a complete dependency graph of your resources and only parallelizes truly independent subgraphs. We enforce explicit barriers for dependencies and use transactional writes. If resources depend on each other, they run in order. If they don't, they run in parallel.

All state data is encrypted at rest (AES-256) and in transit (TLS 1.3). Provider credentials are never stored in state. Resource-level RBAC means teams only see what they need. Every access and modification is logged with full attribution.

You need PostgreSQL 14+, but you have options: self-hosted on your infrastructure, managed services like RDS or Cloud SQL, or local PostgreSQL for development. The database requirements are minimal — any PostgreSQL instance can handle thousands of resources.

Terraform's pg backend just stores the state file as a blob in PostgreSQL. Stategraph actually parses and normalizes the state into a proper database schema. Every resource becomes a queryable entity with relationships, history, and ownership. The pg backend stores a file in a database — Stategraph IS a database.

We're targeting our first release early Q1 2026. Design partners get early access starting soon. Sign up for updates to be the first to know when we launch.

Yes. We'll offer both cloud-hosted options (multi-tenant and single-tenant private cloud) as well as a self-hosted version for teams that need complete control over their infrastructure state.

We haven't finalized our licensing model yet. We're taking time to make a thoughtful decision that ensures long-term sustainability. We're exploring open-source, source-available, and proprietary options to find the right balance between openness and sustainability. See our license page for our current thinking.