Editions and pricing

Stategraph Orchestration has an Open Source edition and an Enterprise edition, and you can add Infrastructure as a Database to them. You self-host them, or use a Stategraph Cloud plan.

Feature matrix

The Infrastructure as a Database column shows it with Orchestration Enterprise. Without Orchestration, you get only the rows that are No for Open Source and Enterprise.

Stategraph Orchestration Open Source

Open Source is the full core of Orchestration, with unlimited runs. Enterprise and Stategraph Cloud add the Enterprise features below. The source is on GitHub. You self-host it with Docker Compose: see Self-hosted Open Source.

Besides its Yes rows in the matrix, Open Source includes:

• Automerge and rollbacks.
• Hooks, and parallel, batch, and layered runs.
• All IaC tool integrations (Terraform, OpenTofu, Terragrunt, Pulumi, CDKTF), and all cloud provider integrations.
• Plan file storage.

What happens past 3 active users

Each GitHub or GitLab installation allows up to 3 active users per month.

• The first 3 users who run a plan or apply in a calendar month keep working all month.
• For other users, the plan or apply does not run. Orchestration posts an Open Source Tier Limit Reached comment on the pull request that lists the active users of the month.
• Drift detection is not affected.
• The count resets at the start of each calendar month.

What happens if you enable an Enterprise feature

If .stategraph/config.yml turns on an Enterprise-only setting on an Open Source server, Orchestration rejects the configuration when it loads it, and a pull request comment names the feature. Open Source rejects:

• access_control.enabled: true
• More than one entry under drift.schedules
• Any apply_requirements.checks[].approved.require_completed_reviews: true
• notifications.summary.enabled: true
• A stategraph gate approve <token> comment, or any workflow gate with a token

Open Source reads only the .stategraph/config.yml in each repository, so it has no centralized configuration. It does not register the API access token routes.

Stategraph Orchestration Enterprise

Enterprise is Open Source with no user limit, plus these governance features, marked Enterprise in the docs:

• Access control / RBAC: control who can plan, apply, apply-force, apply-autoapprove, unlock, and update CI or Stategraph configuration. Rules match users, teams, or repository roles, per tag query, and can use super-approval. See RBAC and the access_control reference.
• CODEOWNERS enforcement: with the require_completed_reviews apply requirement, each reviewer that CODEOWNERS requires must approve before an apply can run. See CODEOWNERS.
• Gatekeeper: when a gated workflow step fails, such as a security scan, a policy check, or a custom validation, the workflow records a gate and blocks the apply. Authorized users approve with a stategraph gate approve <token> comment. See Gatekeeper.
• Centralized configuration: global and per-repository defaults, overrides, and forced configuration, kept in one repository and layered onto the .stategraph/config.yml of each repository. See Centralized configuration.
• Multiple drift schedules: for example, hourly and tag-scoped for production, daily for staging. See Drift detection.
• API access tokens: create, list, refresh, and delete scoped tokens for KV store reads and writes and other operations. See Access tokens.

How to get Enterprise

• Stategraph Cloud: every plan includes all Enterprise features, on from the start. Sign up at app.stategraph.cloud.
• Self-hosted: the Pro plan includes a licensed Enterprise build that you run yourself, for $12,000 per year, the same price as Pro on Stategraph Cloud. Enterprise is a different server image from Open Source, the one that Stategraph Cloud runs. Contact sales for a license, then deploy it: see Self-hosted Enterprise. Your repositories and .stategraph/config.yml carry over.

Infrastructure as a Database

Orchestration decides when and how changes run. Infrastructure as a Database scopes each operation to the resources that changed, not to a locked and replayed state file. Operations run at the same time without a global lock, and leave a complete record of your infrastructure that you can query.

• With Orchestration: set the engine to stategraph to run each pull request through it. See Use with Orchestration.
• Without Orchestration: use the stategraph CLI under your existing CI/CD or orchestration workflows. See Infrastructure as a Database and CI and orchestrators.
• Deployment: Stategraph Cloud, self-hosted, air-gapped, or BYOC (Stategraph engineers operate it in your AWS, GCP, or Azure account).
• Pricing: from $25,000 per year, on an annual contract, with dedicated support and a custom SLA. It is priced separately from Orchestration. Contact sales for a quote, then follow Setup.

Stategraph Cloud plans

Free and Pro include every Orchestration feature and differ only by these limits. A run is one plan or apply that Stategraph executes. New accounts start on Pro for 30 days, with no credit card, then move to Free with every feature at the Free limits. To stay on Pro, add a card at any time.

Managing a subscription

Manage your subscription, payment method, and invoices in the Stripe customer portal.

Choosing an edition

You can move from Open Source to Enterprise, then add Infrastructure as a Database. Each step keeps your repositories and your .stategraph/config.yml. Self-hosted, Open Source and Enterprise are different server images, so the move to Enterprise is a new deployment.

Choose Open Source when:

• One team or a few repositories need none of the Enterprise features.
• GitHub branch protection or GitLab protected branches are enough, without CODEOWNERS or fine-grained RBAC in the apply flow.
• You are comfortable with self-hosting and upgrades.

Choose Enterprise when:

• You need any of its governance features, such as RBAC for teams that share infrastructure.
• More than 3 users run plans or applies on one installation in a month.
• You want a managed service with no infrastructure to operate.

Choose Infrastructure as a Database when:

• Plans and applies are slow because each run replays the full state.
• Teams wait behind one lock per state, although their changes touch different resources.
• You want SQL over your infrastructure, or blast radius and cost before apply.
• You want a complete, queryable record of each change, from CI, laptops, and AI agents.

Next steps

• Stategraph Cloud quickstart: sign up and run your first plan.
• Self-hosted Open Source quickstart: run Open Source with Docker Compose.
• Self-hosted Enterprise quickstart: run the Enterprise build with Docker Compose and a license key.
• Governance: the Enterprise governance features.
• Infrastructure as a Database: scoped plans, locks, transactions, and SQL.