Blazing fast Terraform plan and apply
Replace the flat state file with a database-backed dependency graph. Independent changes run in parallel. Change multiple states in one transaction. Plan what changed, not everything.
The Speed Difference
Same infrastructure. Same change. Dramatically different wait time.
What Makes Velocity Fast
Subgraph Execution
Only process resources affected by your change. The dependency graph tells us exactly which resources need to be evaluated—skip the rest.
Parallel Operations
When changes don't overlap, run them simultaneously. Multiple teams can work on the same codebase without waiting in a queue.
Resource-Level Locking
Lock only what you need. No more global state locks that block everyone while one person runs a plan on a single resource.
Incremental Refresh
Refresh only changed resources, not the entire state. For large deployments, this means seconds instead of minutes.
SQL-Queryable State
Your infrastructure state lives in PostgreSQL. Query it directly, build dashboards, integrate with your existing tools.
Drop-in CLI
Replace `terraform` with `stategraph`. Same commands, same workflow, dramatically faster execution.
How It Works
Traditional Terraform backends store state as a flat JSON file. Every operation loads the entire file, locks globally, and processes resources serially.
Stategraph Velocity stores state as a directed acyclic graph in PostgreSQL. When you run a plan, we compute the minimal "change cone": only the resources affected by your changes. Independent subgraphs can execute in parallel, with resource-level locks that don't block unrelated work.
Multi-State Transactions
Keep your multi-state setup. Lose the orchestration complexity.
Sequential Orchestration
4 operations
Sequential, incomplete visibility
Multi-State Transaction
txn_abc123
1 operation
Atomic, complete visibility
One plan. One apply. All your states.
Most teams split infrastructure across multiple states for organization. But this creates a painful problem: changes that cross state boundaries require sequential orchestration. Plan state A, apply it, then plan state B with A's outputs, apply it, and so on.
Stategraph changes this. Plan changes across state boundaries in a single unified operation. No sequential steps. No output mocking. No orchestration scripts.
True Blast Radius
See the actual impact across all states in a single plan. No mocked outputs, no guessing.
No Orchestration
No multi-step plan/apply workflows. No waiting for sequential state updates.
Keep Your Structure
Organize code across states however makes sense. No refactoring required.
Example: You change a VPC in state A that state B depends on. Traditional approach: plan A, apply A, wait, then plan B with A's new outputs. With Stategraph: one unified plan shows you the full impact across both states. One apply executes the entire change safely.
Start with Stategraph Inventory today. Add Velocity when it launches.