PROVIDER - orchestration and governance for infrastructure as code

Spacelift

Spacelift orchestrates 5 IaC tools - Terraform, OpenTofu, Pulumi, CloudFormation and Kubernetes - governing plans and approvals with OPA/Rego policies while drift detection and private workers support multi-account estates; per-stack billing and Rego effort are the two things to weigh.

Developer Tools United States 2026.11.19
3.7pts

Detailed Notes

Pros 5 items

An orchestration platform for 5 IaC tools: Terraform, OpenTofu, Pulumi, CloudFormation and Kubernetes
Policy as code is central, with OPA/Rego covering 3 control points: plan, approval and access
Automatic drift detection compares declarations against real resources on schedules from 1 hour to 1 day and alerts on divergence
Private workers deploy inside your own network, keeping 2 sensitive assets, credentials and state files, internal
3 mechanisms - stack dependencies, shared contexts and blueprints - support multi-account, multi-environment governance

Cons 4 items

Sits above IaC, so Terraform modules and cloud account structure remain your responsibility
Billed by stack and concurrency, which grows quickly for environment-heavy organisations
Learning Rego takes effort that small, simple workflows may not repay
Limited coverage of non-IaC workflows such as application builds and deployments

Service Overview

Spacelift orchestrates and governs infrastructure as code, bringing Terraform, OpenTofu, Pulumi, CloudFormation and Kubernetes runs into one system of stacks, policies and audit trails.

In the development tools category it represents the control plane above IaC: answering who changed what, whether it is compliant, and whether reality has drifted.

Key Strengths

  • One platform, many tools: 5 IaC tools share one run and audit model
  • Policy as code: OPA/Rego covers 3 control points - plan, approval and access
  • Drift detection: scheduled comparison between real resources and declarations raises alerts
  • Private workers: execution nodes run inside the network so credentials stay put
  • Stacks and blueprints: dependencies and templates reuse configuration across environments

Product Ecosystem

Platform capabilities

Stack management, run orchestration, a policy engine, drift detection and context or credential handling.

Integrations

Native connections to GitHub, GitLab, Bitbucket, Slack, AWS, Azure and GCP accounts.

Typical scenarios

Multi-account IaC governance, compliance approval gates and standardised platform engineering delivery.

Limitations

  • IaC dependency: module quality and cloud account design remain yours
  • Billing model: stack and concurrency pricing grows expensive with many environments
  • Policy barrier: Rego needs study and may not pay off for simple flows
  • Scope: non-IaC workflows such as application builds are covered thinly

Use Cases

  • Multi-environment Terraform governance (★★★★★): approvals plus drift detection close the loop
  • Organisations with compliance duties (★★★★): policies and audit logs are complete
  • Platform engineering teams (★★★★): blueprints and contexts standardise delivery
  • Small personal projects (★★): calling Terraform directly is lighter

Pricing

Item Price Notes
Free tier $0 Limited stacks and concurrency
Team plan Billed by stack and concurrency Fits mid-size estates
Enterprise Contract Adds private workers and SSO

Small setups validate on the free tier, then subscribe by stack count and concurrency.

FAQ

  • Must all IaC move to Spacelift? No. Start with critical environments and extend approvals and drift detection stack by stack.
  • Which policy language is used? OPA/Rego, controlling plan output, approvals and access at fine granularity.
  • Is self-hosting available? Private workers can be self-hosted while the control plane stays in the cloud; fully offline runs need the enterprise tier.

Code Examples

A plan policy in Rego

package spacelift

deny["public bucket is not allowed"] {
  some resource in input.plan.resource_changes
  resource.type == "aws_s3_bucket_acl"
  resource.change.after.acl == "public-read"
}

The policy blocks non-compliant changes at plan time, since a deny hit prevents the apply.

A stack configuration fragment

stack: prod-network
terraform:
  version: 1.9.5
  workflow: custom
policies:
  plan: [deny-public-buckets]
worker_pool: private-vpc

worker_pool selects private workers and policies.plan binds plan-stage policies.

Community & Resources

Visit Spacelift Website → https://spacelift.io/
Visit Website ↗