Spacelift Brought Scale to Your IaC Provisioning. Now We’re Automating Everything That Happens After.

For two decades, the way we provision and configure infrastructure has kept getting better.

Puppet and Chef turned server configuration into code. Terraform made infrastructure declarative and repeatable across clouds. OpenTofu, which Spacelift helped found, kept that foundation open and is now driving IaC forward, shipping features like native state encryption and OpenTelemetry support, and setting the new standard for how teams define infrastructure.

Each step gave platform teams more speed and more control over how infrastructure gets created and changed. Spacelift has been at the forefront of this effort, helping teams centralize, govern, and scale IaC provisioning across every tool and cloud they run. What happens after provisioning is a different story, and it’s where most of your team’s time actually goes.

Provisioning is a moment. Everything after it is where most of the work happens – patching, rotating certificates, responding to incidents, granting access, cleaning up idle resources, and working through the request a developer filed last Tuesday. Platform teams spend roughly 80% of their time there, and in most organizations that work still runs on a patchwork of cron jobs, scripts, and Lambda functions.

Ask a platform team what automations are running in their environment and you’ll usually get a pause. Nobody has the full inventory. The script that rotates credentials was written by someone who left a year ago, and no one wants to touch it. When something breaks, production is the one that tells you. New automation requests turn into big engineering projects, so they sit at the bottom of the backlog and take weeks to build once they finally reach a sprint.

AI is making this harder. Developers are writing code faster than ever, which means more infrastructure reaching production and more Day 2 work landing on the same platform team. Agents want in on the infrastructure action too. Today they often run on an engineer’s credentials or a shared key, with no audit trail of what they changed.

At Spacelift we brought order to provisioning. Unfortunately, Day 2 remains the wild west.

Today we’re launching Spacelift Flows, a new part of the Spacelift platform that brings the same rigor, observability, and control to Day 2 operations that we brought to IaC. Flows is visual workflow automation built for platform and DevOps teams.

With Flows, you can see every automation. Each automation runs on a visual canvas with a step-by-step execution trail, so you can watch live, replay in whole or from any step, and know exactly what ran and what failed.

You can stand up an automation in an afternoon instead of weeks. Start from pre-built blocks for the tools you already use, write code, or describe what you want and let our AI assistant build it. There are no containers or hosting to manage, and every automation can also be managed as code through our Terraform provider.

“With Flows, we had something working in a few hours, instead of four weeks later and still struggling with auth, which is usually the pattern,” said Parker Cameron, senior manager of cloud engineering at Discovery Education.

Flows provides agents a governed path into your infrastructure, by exposing internal systems as Model Context Protocol (MCP) servers with private network access and approval gates. Each agent authenticates as itself and appears in the audit trail as its own user, so every action is attributable to the agent that took it.

Developers get real self-service. A developer fills out a form, Flows checks budget, quota, and policy, and the request is done in minutes instead of turning into a ticket for your team.

The Spacelift Platform now offers full stack infrastructure orchestration. Alongside Flows, the IaC and GitOps capabilities you know and love as Spacelift now have a name of their own, Spacelift Deploy. Nothing changes about how it works, your contract, or your access.

Spacelift Deploy, Spacelift Flows, and Spacelift Intelligence form a single control plane for platform teams. A deployment can trigger a Flows automation, and an automation can trigger a deployment. The same policy, role-based access control, and audit history apply to a provisioning run and to the Day 2 automations that respond to it. And with Spacelift Intelligence, all of it runs through a single assistant, so you can understand, design, deploy, and govern your infrastructure in plain language.

For the first time, platform teams get speed, control, and observability across the full time continuum of their infrastructure, from the first plan through every change, patch, and incident that follows.

If you run Spacelift, your infrastructure is already defined in code, governed by policy, and auditable. Flows extends that investment to the work that follows, using the same policies and the same audit trail, instead of adding another disconnected tool to your stack.

Join our live demo webinar on November 5 https://events.spacelift.io/from-deploy-to-destroy, or explore Flows at https://spacelift.io/platform/flows.

I hope you are as excited about this next chapter in infrastructure automation, and Spacelift, as I am.