Changelog

Today is a big day for us here at Spacelift. We’ve been working hard on some very exciting new functionality. Today, we are pleased to announce Spacelift Intelligence, a set of AI capabilities built directly into the Spacelift platform. It includes two components that work together: an AI Infrastructure Assistant we’re calling Infra Assistant and a natural language deployment model called Intent.

Why This, Why Now?

IaC and GitOps are still the right foundation for managing infrastructure. That's not changing. But those workflows were designed for production. As development velocity increases, especially for experiments, sandboxes, and POCs, the IaC and GitOps pipeline starts to get clogged. AI tools have accelerated the development cycle, but infrastructure hasn’t kept up.

Spacelift Intelligence is our answer to closing this new AI-velocity gap. The goal isn't to replace your Terraform code or your GitOps workflow. It's to give you an AI-native operations layer that gives your platform team the speed of AI without sacrificing the governance, visibility, and control you depend on.

Infra Assistant

Infra Assistant is an AI chat interface embedded in Spacelift. You can ask it infrastructure-related questions and get guidance without leaving the platform.

• “Please find any public s3 buckets across all my stacks”

• “Do I have any CVE vulnerabilities in my environment?”

• “What would you recommend I do to optimize my production deployments?”

Infra Assistant is context-aware, understands your stacks, runs, and the state of your infrastructure, so answers are grounded in your actual environment rather than generic documentation. Whether you're debugging a failed run, exploring a configuration change, or trying to understand what a proposed change will do, the assistant has the context to be useful.

Spacelift Intent

Spacelift Intent is AI-powered infrastructure provisioning through natural language. Rather than asking a question and receiving an answer or getting generated Terraform code, you describe what you want your infrastructure to do. Intent interprets that, translates it into the appropriate configuration, and acts on it. No code involved at all. Intent talks directly to the providers and deploys what you need, when you need it.

• “I need an S3 bucket to store some temporary files. Adhere to any company policies.”

• “Please create and test a policy to not allow public ec2 instances.”

• “Please build 3 ec2 instances in us-west-1 so I can test a prototype.”

You speak it, and Spacelift Intent builds it. No code, no repository, no waiting. You can use Spacelift Intent by chatting with Infra assistant or have your developers connect their agent or LLM of choice to our MCP server.

Getting Started

Spacelift Intelligence is available now. For more information, check out the blog here. Also, sign up for the upcoming webinar where we will discuss Spacelift Intelligence in depth here, and see it in action here!

Maybe you’ve seen this issue before. In complex organizations where multiple teams share a Spacelift account, spaces often end up with the same name in different branches of the hierarchy, like having a us-east-1 space under both production and staging. Without the ability to customize the subject claim, those spaces produce identical OIDC tokens, making it impossible for cloud providers like AWS, GCP, or Azure to tell them apart and apply the right permissions.

You can now customize the OIDC subject claim that Spacelift includes in tokens generated for cloud provider authentication. Previously, the subject claim was always built from the space slug, which caused a frustrating problem in hierarchical space structures: two spaces in different branches of your organization but with the same name, like /root/production/us-east-1 and /root/staging/us-east-1, would produce identical subject claims. That made it impossible to write cloud provider trust policies that distinguished between them.

The new subject template setting lets you define your own claim format using a set of available placeholders, including {spacePath}, which resolves to the full hierarchical path of the space. This unlocks two things that were not possible before: you can now differentiate between identically-named spaces in different branches, and you can write a single wildcard trust policy that covers an entire branch of your space hierarchy, like all production spaces, without needing to update the policy every time a new space is added. The setting is available in Organization Settings under Security, requires admin access, and comes with a migration guide to help you update existing trust policies without causing authentication failures during the transition.

You can read the full documentation here! 

In our continued effort to bring you the best possible platform for your IaC management, today we are happy to announce that Terragrunt is now officially a first-class citizen in Spacelift! What does that mean exactly? The biggest news is that we now support native state management inside the platform. That means you can now let Spacelift do what Spacelift does best, while using your Terragrunt projects. Previously, you had to use remote state configurations if you wanted to use Terragrunt inside Spacelift, but not anymore.

This is a big win for all of our users, and provides even more options and flexibility when it comes to working with multiple frameworks across clouds. Be sure to give it a go, and let us know how you like it. Your feedback and input is critical for us.

Note: In the process of delivering the functionality for Spacelift to manage the state of Terragrunt projects natively, previously the behavior of selecting to “Delete Resources” when deleting a stack was that none of the resources would actually be removed. So whether you picked to keep or delete resources, they would simply remain. This non-expected behavior has now been remediated. Now, the expected behavior should be exactly what you select when deleting resources. When deleting the stack, resources will either stay or be deleted based on which option you select.

For more info on Terragrunt support in Spacelift, and to get started, check out the blog, video, and Documentation.

As always, you’ve been asking, and we’ve been listening. I’m sure you’re already very familiar with Blueprints in Spacelift. A Blueprint is like a template for a stack and its configuration. The blueprint contains variables that can be filled in by providing inputs when creating a stack from the Blueprint. The blueprint can also contain a list of other resources that will be created when the stack is created.

This is all well and good, but we really wanted to step it up a notch. And with that being said, I’d like to introduce you to Templates! Templates provide a self-service approach to infrastructure provisioning, making it easier for application developers to deploy infrastructure without deep IaC or Spacelift knowledge. Templates focus on enabling end users to deploy infrastructure through a simplified, form-based interface.

Now, I know what you’re thinking. That kinda sounds like Blueprints. But, while both features enable infrastructure provisioning, they have fundamentally different approaches and serve different use cases:

Blueprints are a creation tool that generates stacks which then live independently:

• Creates stacks that become regular, fully editable Spacelift stacks

• Once created, stacks can be modified manually like any other stack

• No ongoing relationship between the blueprint and the created stacks

• Stacks continue to evolve independently after creation

• Blueprint changes don't affect previously created stacks

Templates are a lifecycle management tool that maintains control over deployed infrastructure:

• Creates stacks through deployments that are fully managed by the template

• Stacks created from templates are immutable - cannot be edited manually, even by admins

• The only way to modify infrastructure is by:

  1. Updating the template deployment to use a different version

  2. Creating a new template version with changes and update deployment to use it

  3. Modifying deployment inputs

• Deployments maintain a permanent link to the template version

• Templates ensure consistency across all deployments

There are 2 main interfaces for Templates. The Templates Workbench is designed for platform teams and template authors. The Templates List is designed for application developers and end users.

Templates are now available for any customers with Business plans and above!

For more information, check out the documentation. And be sure to let us know how it goes. Your feedback is important to us!

Happy New Year! We’ve been hard at work, back after a great holiday season. And now we’re ready to share a cool new update we have for module sharing permissions. Previously, to be able to share a module with a space, you needed the following permissions:

• Admin access on the space where the module belongs, AND

• Write access on the space where the module belongs

We know that it wasn’t exactly ideal to have to provide admin or write access to the entire space just for module sharing. We heard your requests, so now we are introducing a new action to advanced access. The SPACE_SHARE_MODULE control allows sharing a module with a space without giving admin or write access to the target space!

Note: that the role should be assigned to the space you want to share with, and not the space of the module itself.

This was a highly requested feature, so we are really happy to deliver it to you. You can read more about module registry permissions in the documentation here. And, as always, your feedback is important to us. So take it for a spin, and let us know how you like it.

Have you found yourself creating a new stack, and wish that your cloud integration would simply just be available and attach automatically? Your day has come. Auto-attach for cloud integrations is now GA in Spacelift!

Whenever you create or edit a cloud integration, you can now toggle Enable auto-attach. Once that is done, just add a label to the integration that says autoattach:<your_label>. Any stack that has <your_label> on it will automatically attach the cloud integration. It is as simple as that!

This was one of the most requested features, so we are really happy to deliver it. Take it for a spin, and be sure to let us know what you think. We always want to hear from you.

For more info, check out the documentation here.

Yep! You heard that right! Early Access to Spacelift Intent is now available for everyone!

What is Spacelift Intent?

Spacelift Intent lets you provision and manage infrastructure by describing what you need in natural language. Instead of writing Terraform/OpenTofu code, your MCP client (e.g. Claude Code) calls Spacelift Intent, which directly interacts with provider schemas under Spacelift’s guardrails (policies, audit trail, state, permissions).

Are you ready to deploy and manage infrastructure using natural language through the LLM tools that you’re already using? Then be sure to take Intent for a spin. For more information on Spacelift Intent, you can read up in the documentation here.

Spacelift Intent is still in early access, so we're looking for your feedback. Is it helpful? How could it be more useful to you? We definitely want to hear how it is working for you and what you think of it, so make sure to leave us feedback and reach out if you'd like to talk with a member of our product team about it.

You can check out a quick video about how to configure Intent with Claude and get started here.

Yet again, you asked, and we listened! Today we would like to announce that the Command Pallete is now available in beta!

You can find it up in the top left corner of the UI, or access it quickly with command+K. You’ve now got quick access to a multitude of actions, from one simple menu:

From shortcuts like Create New Stack, and Create New Module, to navigation shortcuts like Dashboard, and Resources. You can also toggle the Theme of the UI, and search for things that may be harder to look for. This feature will be handy for new and experienced Spacelift users alike. You can open this box, and navigate, all with your keyboard. Or use the mouse and click around like you normally do.

As I mentioned before, this feature is in beta for now. So, take it for a test drive, and make sure to leave us feedback. We always want to make sure that we are not only building the features you want and need, but that we’re implementing them in the right ways. Your feedback is always welcome. Stay tuned for more exciting things heading your way!