← Back to all sparks
S

Spacelift

INFRA · APIS
Velocity0.0

Infrastructure as Code platform for Terraform, OpenTofu, Pulumi and CloudFormation

Spacelift's AI stopped explaining infrastructure and started deploying it.

iacagentic-deploysmcppolicy-governanceenterprise-identity
Current state
The dated window ends in March with Spacelift Intelligence, first-class Terragrunt support, OIDC subject claim customisation and a self-service Templates release. Everything since sits in undated rows and is the more consequential half: a remote MCP server in May, SCIM 2.0 provisioning in June, and in July the ability to ask Intelligence to deploy a module by name, resolved against the Module Registry. An August notice warns that the API will start returning HTTP 500 on internal errors instead of 200.
Where it's heading
The arc is easy to trace: Intent opened to everyone in December, Intelligence launched in March, an MCP server exposed the platform to outside assistants in May, and by July the AI is performing deployments rather than describing them. Running underneath is the governance work that makes that defensible — module sharing permissions, OIDC claims, SCIM — because an agent that can deploy is only sellable if the registry and the identity provider bound what it can reach. Terragrunt support and the plan-policy cleanup show the core IaC engine still being maintained rather than neglected for the AI work.
Prediction
Deployment by name is the narrow case; the obvious next step is Intent handling multi-stack changes with policy checks in the loop, and the permission model being extended to describe what the AI specifically is allowed to deploy rather than what a user is.

Recent moves

  1. 6d ago

    API will return HTTP 500 on internal errors instead of 200

    Spacelift's API has been answering its own internal failures with HTTP 200, and that is being corrected to 500. Anyone whose automation infers success from the status code has to check their error handling before the change lands.

  2. 1mo ago

    Ask Spacelift Intelligence to deploy a module by name

    ⚡ SPARK

    Intelligence stops describing infrastructure and starts deploying it: ask for a module by name and Intent resolves it against the Module Registry. This is the step the March Intelligence launch set up, and it moves the AI from a read surface to a write one.

  3. 2mo ago

    SCIM provisioning available in Spacelift!

    A repeat crawl of the SCIM provisioning announcement. Same item, no new detail.

  4. 2mo ago

    Learning Certificates now available in Spacelift!

    A repeat crawl of the Learning Certificates announcement. Same item, no new detail.

  5. 2mo ago

    Announcing the Spacelift Remote MCP Server!

    A repeat crawl of the Remote MCP Server announcement. Same item, no new detail.

  6. 4mo ago

    Launchpad Learn: Structured hands-on training for Spacelift

    A four-module hands-on training experience built into Launchpad — Foundations, Operational Safety, Configuration Reuse, Delivery at Scale. Pulls onboarding into the product instead of docs, useful as Spacelift layers on a complex AI-native surface and self-service Templates that need an explainer flow.

    View source ↗