Sold by
Spacelift
Spacelift is the infrastructure orchestration platform built for the AI-accelerated software era. Its platform manages the full lifecycle for both traditional IaC and AI-provisioned infrastructure. Spacelift Intelligence adds an AI-powered layer for natural language provisioning, diagnostics and operational insight across both traditional and AI-driven workflows, helping organizations deliver secure, compliant infrastructure at scale. Spacelift works with tools like Terraform, OpenTofu, CloudFormation, Pulumi and Ansible. Visit spacelift.io/customers to see how Duolingo, Figma, Moodys, Checkout.com, 1Password, Redfin and others manage infrastructure for the AI-accelerated software era with Spacelift.
Reviews (29)
Rahul Aher
Cloud automation has streamlined multi-account IaC deployments and now saves time and resources
Reviewed on Jun 22, 2026
Review from a verified AWS customer
What is our primary use case?
My main use case for Spacelift is to manage the infrastructure and accounts stacks for AWS and Azure. I use Spacelift to manage my AWS and Azure stacks by using Terraform integration with the Spacelift YML file, where I provision the spaces and manage the different stacks under the different spaces. For the state augmentation and state management, I use Spacelift since it is an independent solution, which proves useful for end-user developers to deploy their resources to the cloud directly.
What is most valuable?
Spacelift offers the best features that allow me to manage the stacks for different AWS and Azure accounts with different cloud providers while supporting additional services including OpenTofu, Terraform, Azure ARM templates, and CloudFormation.
The best feature I appreciate about Spacelift is that I can immediately back out the resources that are provided with Terraform in Spacelift. When I want to provision a new resource, I simply need to publish code and push it to the repository. The CI/CD automatically triggers the stack, and the stack allows me confirmation before deploying the resource and providing me with complete details of the resources that are deployed through the stacks. Regarding AWS and Azure specifically, they provide clear visibility for the resources that are deployed. With the templates and the secret variable management, I can keep everything secured.
Spacelift has positively impacted my organization by automating deployed nodes for Linux virtual machines, which provide high availability for stack deployment. The runs that have been triggered are quite fast, with no need for dependency on other teams to get them deployed or approved. The overall support for particular stack failures has been fabulous and has really impacted the company as it moves forward.
Regarding Spacelift specifically, if I have ten runs scheduled at a time, based on the particular Linux virtual machines that Spacelift uses, and if I have provisioned multiple nodes or Docker containers, all ten runs that are scheduled are executed quickly and saves a considerable amount of time rather than entering a pending state until the first run is completed. Therefore, efficiency has improved significantly.
What needs improvement?
Spacelift is good overall, but there are little explanatory aspects, such as navigating particular stacks, that are somewhat difficult to understand for newcomers, especially regarding the process, stack setup, and variable setup for deployments. If the documentation were more narrative, it would be much better.
The authentication for end-users requires access, and if there could be a read-only space where non-authorized users can see a non-authorized page, that would be helpful. A non-authorized user who wants to see some progress with read-only access could do so.
I have not yet interacted with the AI capabilities of Spacelift, but if they are improved, I think the Git-based tools will provide the same type of stability, and governance will be managed specifically as Spacelift is already taking care of governance for other applications and tools with respect to company policies.
For how long have I used the solution?
I have been using Spacelift for the last two years.
What do I think about the stability of the solution?
Spacelift is stable.
What do I think about the scalability of the solution?
Spacelift's scalability is quite good. Based on the requests and the Linux Docker machines I provision, it becomes more stable, and the runs happen very quickly.
How are customer service and support?
Customer support has been good overall, but I have not engaged it much as I can fix things internally with the documents and different blogs available on the internet.
Which solution did I use previously and why did I switch?
I previously used Terraform Cloud. I switched from Terraform Cloud to Spacelift based on pricing and the processing model, along with some additional features that Spacelift provides.
How was the initial setup?
It was reasonably easy for my team to adopt and start using Spacelift, coming from a cloud background. If it were made more narrative, it would be easier for non-technical people to become accustomed to Spacelift. I describe the learning curve for Spacelift as straightforward but requiring some support at the initial stage.
What about the implementation team?
I incorporated Spacelift directly with the Spacelift support and sales team rather than purchasing through the AWS Marketplace.
What was our ROI?
I have seen a return on investment. The metrics show that fewer employees are needed, money is saved based on past experiences with different cloud management or Infrastructure as Code management tools, and efficiency has improved significantly in terms of Infrastructure as Code deployment.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing has been based on the stacks, states, and resources provisioned or processed by Spacelift, which incurred different costs. The spaces have been a major aspect of managing things, and the contacts for the resources I provide internally in Spacelift are quite affordable, effective, and useful.
Which other solutions did I evaluate?
Only Spacelift was evaluated after Terraform Cloud.
What other advice do I have?
I would advise others looking into using Spacelift to give it a try first, as you will love it. I suggest everyone look at Spacelift and dip their toes into it first, as you will definitely love it and will want to use it in the future. I gave this review a rating of eight out of ten.
Which deployment model are you using for this solution?
Hybrid Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
reviewer2857095
Versioning has accelerated AWS deployments and supports safe rollbacks across environments
Reviewed on Jun 15, 2026
Review from a verified AWS customer
What is our primary use case?
We manage a lot of AWS deployments with Spacelift configs, so we have a main use case for it. We also use it for versioning and spinning up new environments.
Recently we used Spacelift for deploying our custom cloud code deployment platform on AWS. We used Spacelift to have A/B testing for different versions of our custom pipeline.
How has it helped my organization?
Spacelift has positively impacted our organization by speeding up our deployments and easing a lot of pain with infrastructure deployments, especially because a lot of teams are working simultaneously on the same code base using the same configs.
Every engineer in the team takes on their own infrastructure in their branch, controlling the version and using it without merging to master. Using Spacelift has improved collaboration and speed.
What is most valuable?
The best feature Spacelift offers is probably its versioning, which provides another layer above infrastructure as code. With versioning, you can do rollbacks and have different versions of the same infrastructure in different environments and jurisdictions, making it very useful.
We use the rollback feature all the time, especially every time we deploy to a new environment.
What needs improvement?
It would be nice to have out-of-the-box A/B testing with Spacelift because we still use some custom features for that.
Out-of-the-box A/B testing is the main thing I would like to add about the needed improvements, maybe with the custom solution not being declarative configuration but more like Pulumi.
For how long have I used the solution?
I have been using Spacelift for four years already.
What do I think about the stability of the solution?
Spacelift is stable.
What do I think about the scalability of the solution?
Spacelift's scalability is okay.
How are customer service and support?
The customer support for Spacelift is okay.
I would rate the customer support for Spacelift as nine on a scale of 1 to 10.
Which solution did I use previously and why did I switch?
We used Argo CD previously, and we switched from Jenkins because it is too hard to manage. Jenkins is even worse than Spacelift in terms of learning curve.
How was the initial setup?
The learning curve for new users getting started with Spacelift is very steep.
What was our ROI?
I cannot share any metrics related to return on investment, such as money saved, time saved, or fewer employees needed.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing was that licensing was somewhat unclear when HashiCorp changed their own licensing.
Which other solutions did I evaluate?
We evaluated a few options with Pulumi before choosing Spacelift.
What other advice do I have?
Spacelift does not handle compliance requirements in our organization.
SpaceLift helps with managing secrets and sensitive data very effectively, but we still use a lot of AWS secrets for production.
I already covered how Spacelift supports multiple teams or users working on the same infrastructure.
I monitor and troubleshoot issues within Spacelift through logging.
SpaceLift handles infrastructure drift detection by checking the version control.
We do not use Spacelift for supporting automation for repetitive tasks.
We integrate Spacelift with our existing CI/CD pipelines through GitHub Actions.
SpaceLift is deployed in our organization as a private cloud.
We mostly use AWS with Spacelift.
We did not purchase Spacelift through the AWS Marketplace as we have a custom setup.
SpaceLift's AI capabilities are very good regarding accuracy and reliability of output because it uses declarative configs, so most of the time they are accurate.
I would rate Spacelift a nine on a scale of 1 to 10.
I do not have any special advice to give to others looking into using Spacelift. Pulumi is also a viable option.
Which deployment model are you using for this solution?
Private Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Harsh Goenka
Automated policies and drift detection have improved our infrastructure deployments and visibility
Reviewed on Jun 14, 2026
Review provided by PeerSpot
What is our primary use case?
I use Spacelift in my current environment for deploying Terraform resources. Spacelift is deployed to manage resources in my Kubernetes environment, and I have given it access to my environment where it detects configuration drift and other critical functions. I have created a workflow through which I deploy resources.
How has it helped my organization?
Spacelift has positively impacted our organization because we do not have to detect drift or manage Terraform basics ourselves; Spacelift handles this for us with strong governance and security policies based on GitOps principles, which saves considerable time.
Deployment time has been reduced by 20% specifically because of the policies I have created in Spacelift and the way it automatically checks for drift and handles deployments if those resources are not deployed. Additionally, Spacelift detects changes so that we are aware of what is being changed and by whom.
What is most valuable?
The best features Spacelift offers are policies as code, state management, drift detection, and dependency checks.
I have defined rules for basic validations in Spacelift, and the OPA agent enforces guardrails and prevents any wrong deployments through the use of policy as code.
What needs improvement?
Spacelift could be improved by implementing some of the many AI-based tools available that support a variety of tools like Pulumi, CloudFormation, OpenTofu, and Terraform.
I would like to have simpler onboarding and setup processes for new users and broader integrations with other cloud and DevOps tools.
For how long have I used the solution?
I have been using Spacelift for the past one year.
Which other solutions did I evaluate?
I would advise others to use Spacelift while keeping in mind that it is not free; it is free for certain users, but if Spacelift features are truly needed, they should explore it because not every environment would find these solutions necessary, as there are alternative options available.
What other advice do I have?
I believe we have discussed everything regarding how I use Spacelift, the features offered, and the improvements needed. I give Spacelift an overall rating of 10.
Rodrigo Aires
Governance controls have improved our Terraform deployments and speed up secure AWS delivery
Reviewed on Jun 09, 2026
Review from a verified AWS customer
What is our primary use case?
My main use case for Spacelift involves an implementation of a CI/CD pipeline that deploys Terraform code in AWS, so we manage all the profiles for the developers and manage all the AWS resources.
A specific example of how we use Spacelift in our pipeline is for Terraform deploys, managing all the resources with Spacelift and having profiles including developer profiles, DevOps profiles, and the cloud management profile, so we manage all the Terraform operations in Spacelift.
What is most valuable?
The best features Spacelift offers include the management capability where you can deny certain resources that developers can deploy. For example, if you want, you can deny the developer from creating a new VPC or a new cluster, allowing you to specify the resources that developers could deploy.
This feature impacts my workflow by making it easier because it facilitates the review of pull requests, as Spacelift will block anything that is not allowed, making it easier to review pull requests.
SpaceLift impacts my organization positively by giving more agility to the teams when they are deploying, allowing us to manage the AWS resources using Spacelift, so our cloud organization improves after this implementation.
The improvement I noticed after using Spacelift includes an increase in the deployment speed and in the review of pull requests, as we can make the deployments faster.
What needs improvement?
I think Spacelift can be improved by incorporating some kind of architecture for the resources being deployed, such as using AI to provide some drawn architecture.
Regarding Spacelift's AI capabilities, I think for reliability, if the platform is still running with no downtime or that does not impact the deploys, it is good output for reliability.
For how long have I used the solution?
I have been working in this position for two years.
What do I think about the stability of the solution?
Spacelift is stable.
What do I think about the scalability of the solution?
We did not scale the environment because we deployed it with the right sizing.
How are customer service and support?
The customer support experience is good as they assist when we have some doubt or an issue.
My experience with customer support is that they are responsive and helpful, with the SLO and SLA being really fast to answer.
Which solution did I use previously and why did I switch?
Prior to Spacelift, I used a simple GitHub Actions pipeline for Terraform deploying, and we switched because Spacelift provides more governance over Terraform.
How was the initial setup?
Spacelift was deployed in a containerized cluster.
What was our ROI?
I can see the return on investment by specifically looking at the time saved.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing was really clear, so I did not encounter any problems.
Which other solutions did I evaluate?
We did not evaluate other options before choosing Spacelift; we just looked for Spacelift.
What other advice do I have?
My advice for others looking into using Spacelift is that the governance is valuable. I would rate this review an 8.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Carlton Mascarenhas
Streamlined infrastructure orchestration has reduced drift and clarifies Terraform workflows
Reviewed on Jun 05, 2026
Review from a verified AWS customer
What is our primary use case?
My main use case for Spacelift is infrastructure orchestration, where I'm currently working on S3 and SQS.
I use Spacelift with S3 and SQS by having a config setup for the S3 module as well as SQS, and we use GitHub actions. Whenever a Terraform module change on that git is done, a GitHub action is executed which in turn does an action on Spacelift that creates the plan, and then it executes the plan after the approval of the ongoing process where the IAM is used for three sets of people: the approver, who is the main administrator, and us, who will be the creators.
In Spacelift, the three steps we follow are plan creation, which is done via GitHub actions, and the approver has to go and approve this particular plan so that it can be available for execution. Currently, we have disabled any delete modules as we don't want to give that feature right now, and we are just focusing on read and write of Terraform modules.
What is most valuable?
The best features Spacelift offers include the drift detection feature, which is the most useful one for us, as well as comparison of the modules in versions, which we weren't able to do in our in-house tooling.
The drift detection has helped my team by addressing the major problem we faced in our internal tooling for infrastructure orchestration, which was if there were any manual changes done on AWS or the console itself missing the updates in the saved modules. Now these Terraform module versioning is done by Spacelift, which helps us compare what was there earlier and if any changes were done outside of the set system.
SpaceLift has positively impacted my organization by reducing a lot of confusion with the integration of Terraform modules, because a lot of our tooling involved direct and indirect Terraform module creations; now it is more streamlined for each and every resource that we control.
What needs improvement?
I'm new to Spacelift integration, and so far I have not seen anything that needs significant improvement; the UI is great, the functionality is great, and the drift detection features are great. There are more features that are onboarded every day, so for me, I have not hit any bottlenecks that need to be improved.
If I had to think of one area where Spacelift could improve, it would be the graph where we orchestrate, as the graph looks very complicated and complex, so perhaps it could be simplified.
I would find it helpful to have a flowchart similar to Argo CD so that we know what the orchestration metrics are and everything.
For how long have I used the solution?
I have been using Spacelift for just over a year.
What other advice do I have?
I purchased Spacelift through the AWS Marketplace.
My advice to others looking into using Spacelift is to be open to OpenTofu as well as Terraform so that you are able to identify issues and also understand the integrations that Spacelift provides. I rate this product an 8 out of 10.
Which deployment model are you using for this solution?
Private Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Sjamjam Jamjan
Automated infrastructure as code has transformed drift control and daily server operations
Reviewed on Jun 02, 2026
Review from a verified AWS customer
What is our primary use case?
My main use case for Spacelift is to automate and provision infrastructure as code, specifically by integrating our IaC Terraform with Spacelift.
A quick, specific example of how I use Spacelift with Terraform in my setup is that we write Terraform templates and integrate our Terraform code with Spacelift, using Spacelift to provision the infrastructure as a CI/CD tool, which helps us detect drift and assists with remediation.
I have more to add about my main use case with Spacelift, mainly on drift detection, as we are handling around 900 to 1,000 servers for Linux, so we use Terraform templates with Spacelift to manage our large-scale infrastructure operations.
What is most valuable?
The best features Spacelift offers include drift detection, multi-IaC support, and an open policy as code with Open Policy Agent.
The major impact that Spacelift has had on our organization is mainly related to detecting drift, especially as we maintain around a thousand servers. Additionally, Spacelift facilitates faster infrastructure delivery, allowing us to deploy our infrastructure with one click. Governance and compliance have improved, significantly reducing the majority of our security risks and enhancing the security of our current server strategies.
What needs improvement?
I mention the need for improvement of Spacelift.
I specifically wish to see improvements in Spacelift's user interface, making it more useful and easier for the team to understand. Additionally, enhancing the remediation capabilities on a broader scale would benefit our teams.
Another improvement I suggest is enhancing the templates for Terraform that can be integrated with Spacelift, allowing Spacelift to maintain default templates for these IaCs. If the team could integrate AI-assisted infrastructure operations, that would also be helpful.
For how long have I used the solution?
I have been using Spacelift for around eight months, which is between eight to one year.
What do I think about the stability of the solution?
Spacelift is stable.
What do I think about the scalability of the solution?
Spacelift can handle increased workloads well, managing more servers as our organization grows, and it is indeed scalable.
How are customer service and support?
The customer support experience involves sending an email, but I have never requested customer support so far to resolve any issues.
Which solution did I use previously and why did I switch?
I did not previously use a different solution.
How was the initial setup?
My experience with pricing shows that the setup cost is reasonable, and the licensing also seems reasonable. The setup takes very little time since it integrates with our SVN or source code repository, and then we are good to go.
What was our ROI?
We have seen a return on investment, as the time saved for our DevOps team is significant. In terms of costs, identifying drift detection helps us remove unused servers, benefitting our application management.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing shows that the setup cost is reasonable, and the licensing also seems reasonable.
Which other solutions did I evaluate?
We have not evaluated any other options before choosing Spacelift.
What other advice do I have?
After using Spacelift, I noticed a 90% reduction in time saved for repetitive infrastructure tasks, as the cloud configuration speed has doubled. For instance, if we previously deployed a server in ten minutes, we now do it in three to four minutes, along with increased deployment frequency for both Kubernetes and cloud deployments, greatly enhancing our metrics.
I have mentioned the improvements needed for Spacelift.
My advice for others looking into using Spacelift is that if there is a possibility of exploring more tools, they can consider alternatives, but from our experience, we are satisfied with what we are currently using. I would rate this product a 9 out of 10.
reviewer2847912
Collaboration has improved as my team manages shared Terraform changes safely and transparently
Reviewed on Jun 01, 2026
Review from a verified AWS customer
What is our primary use case?
My main use case for Spacelift is using it as a Terraform collaboration provider tool.
Day-to-day, when I create a PR and get it merged, I am able to review the Terraform plan in Spacelift and then verify that it contains the changes that I am looking to make. If so, then I can apply it.
I also use Spacelift as a registry for Terraform modules.
How has it helped my organization?
Spacelift has positively impacted my organization because it works well; it allows everybody to collaborate in the same Terraform repo without stepping on each other's toes. I think that is the number one feature that is most required from using Spacelift or obtaining it.
What is most valuable?
The best features Spacelift offers include the ability to ensure that only one change is merged in at a time and ensure that everybody sees that unified page where it shows all of the runs that were already executed.
That unified view of runs helps my team because it allows anybody, whether they are technical or not very technical, to review the page and understand what got applied. It also makes it easy to use so that less technical or less DevOps engineers are able to create change requests into our Terraform.
What needs improvement?
I think an improvement for Spacelift would be a feature to run multiple stacks.
What I mean by that is if you have multiple stacks that rely on each other, it would be nice to detect that. For example, if you modify a module, it would be beneficial to have this capability.
There are no other improvements needed for Spacelift that I have not mentioned.
For how long have I used the solution?
I have been using Spacelift for over one year, approximately two years.
What other advice do I have?
My advice to others looking into using Spacelift is to use it and review all the TACO platforms and see if you really need it before purchasing it because for some simple workflows, you can get away with something simple. I would rate this product an 8 out of 10.
Which deployment model are you using for this solution?
Hybrid Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
reviewer2847357
Automated policies and collaboration have improved our infrastructure workflows and reduced incidents
Reviewed on May 30, 2026
Review from a verified AWS customer
What is our primary use case?
I used Spacelift for one project with a duration of around six months.
Spacelift was used mainly for automating client infrastructure using Terraform and applying OPA policies to automate Terraform as an integrating tool that controls the whole infrastructure-as-code part.
In the project, we used a single GitHub repository for storing the infrastructure code and Terraform for the infrastructure-as-code. Terraform commands such as plan and apply were automated using Spacelift, which was integrated with OPA policies to check authorization, authentication, and whether the developer had permission to perform actions such as creating a virtual machine in the correct region. All this process was monitored using Spacelift.
We also integrated monitoring tools such as Grafana and Prometheus with Spacelift, but it was not completed unfortunately because the project duration ended. In summary, we used Spacelift for automating the infrastructure side and for role-based access control level user access to clients and applying the policies that they need in the organization.
How has it helped my organization?
Spacelift impacted our organization positively in several areas. Time-saving was achieved by eliminating the need for coordination runs. Before Spacelift, engineers had to coordinate via Slack to ensure no conflicting Terraform applies were running, saving each engineer roughly 30 to 45 minutes per deployment cycle just in coordination overhead.
Error reduction was another clear benefit, as the mandatory plan review step before any apply and OPA policies blocking non-compliant changes meant that a whole category of human errors simply could not happen. For team collaboration, Spacelift was transformative, allowing the whole team to safely propose, review, and apply changes, improving knowledge sharing across the team.
Before Spacelift, we averaged around two to three infrastructure-related incidents per month, such as state conflicts or unreviewed manual changes causing unexpected behavior. After adopting Spacelift, that dropped to roughly one every six to eight weeks, representing a 60 to 70% reduction in incidents. On time savings, our team of four engineers was collectively spending around six to eight hours per week on deployment coordination and managing run order manually, which came down to roughly two hours per week after Spacelift, freeing up meaningful time for actual feature work and improvements.
What is most valuable?
One thing that stood out unexpectedly was how well Spacelift handles drift detection in Terraform workflows, catching discrepancies early, which saved us significant troubleshooting time. The best features in my opinion are policies-as-code using OPA policies, stack dependencies, and Git-driven workflows. Overall, Spacelift bridges the gap between raw Terraform and enterprise-grade infrastructure management in a way that tools such as Jenkins or Cloud Build could not match natively.
One specific situation where drift detection really saved us was when a team member manually adjusted a security group rule directly in the AWS console during an incident, intending to revert it later but never did. Without Spacelift's drift detection, it would have silently remained out of sync with our Terraform state indefinitely. Spacelift flagged it within the next scheduled detection cycle, allowing us to review and reconcile the state before it caused compliance issues.
On stack dependencies, we had a layered setup where our networking stack had to be fully applied before the compute stack, and the compute stack before the application stack. Previously, we managed this manually, but with Spacelift's stack dependencies, we defined those relationships once, and it handled the trigger chain automatically, preventing partial deployment failures we used to deal with regularly.
The UI is one of Spacelift's stronger points, as the run view is clean and gives a clear timeline of what happened at each stage with easy-to-navigate logs. For team members who were not deeply technical on the Terraform side, the interface was approachable. The GitHub integration was seamless, as pull request comments with plan output worked out of the box, making code reviews much more collaborative. We also integrated it with Slack for notifications, so the team got alerts on failed runs or drift detection events without having to actively monitor the dashboard. That kind of passive visibility is underrated; it keeps everyone aware without adding overhead, and the integration ecosystem felt mature, not something bolted on as an afterthought.
Spacelift's documentation is quite thorough compared to some other tools in this space, with well-explained concepts and practical examples that cover edge cases. The documentation had enough working examples for us to adapt OPA policies without needing to dig through community forums or raise support tickets. The API support is also solid, exposing a GraphQL API that gives a lot of flexibility for automation, along with a Terraform provider for managing Spacelift itself as code, allowing version control of configurations such as stacks, policies, and contexts.
What needs improvement?
There are a few areas where there is room for improvement, particularly the initial setup and onboarding experience, which has a learning curve around understanding the concept of contexts. Better onboarding wizards would help new users get productive faster. The OPA policy writing is not very beginner-friendly either, and the error messages when a policy fails are not always clear. Pricing transparency is another area that could improve, as smaller teams or startups would benefit from clear tier breakdowns rather than having to go through a sales conversation.
For how long have I used the solution?
I have been working in my current field for around three years.
What other advice do I have?
My main advice would be to start with a clear understanding of your Terraform structure before onboarding Spacelift, as it works best when the infrastructure is reasonably modular. Spacelift fills a real gap in the infrastructure-as-code tooling landscape, providing a layer of workflow management that Terraform alone does not scale well without. For any team that has grown beyond a single engineer running Terraform locally, it is worth evaluating seriously, as the investment in setup pays off quickly in reduced incidents and improved confidence around infrastructure changes. I would rate this product an 8.
Ilan Bowen
Module management has become streamlined and supports controlled Terraform changes across environments
Reviewed on May 30, 2026
Review from a verified AWS customer
What is our primary use case?
My main use case for Spacelift is to host our Terraform modules that we call from our environment infrastructure creation.
A specific example of how we use Spacelift for hosting those Terraform modules is that we use Terragrunt and call modules that are hosted in Spacelift. They're nested modules, so we have a high level module and then more specific modules. Sometimes they're shared modules that we use for different services.
It's useful to have the different versions with Spacelift because every time we make a change to a particular module, we can then choose to call that module from different environments. So if we are upgrading a module, we can gradually deploy it for different services. If there's an issue, we can always use an older version.
What is most valuable?
The best features Spacelift offers include a great interface, the ability to see the history of any particular module, a clear pipeline-like syntax of what actually happened, and it is a very useful tool.
What I appreciate about the interface and the history tracking is that it's very clear. You can see all of the modules, search by name, see the history of any changes made, and it's very easy to use by choosing a particular version of the module. You can easily use that specific module from your code.
Spacelift has positively impacted my organization by making it very easy to manage the different modules with a very clear interface. You create so many different modules and so many different versions. Having a very easy way to navigate and search through them all, and the fact that you can actually see the commit ID and description really helps in discovering what was actually in that version of the module. This makes life a lot easier and more efficient.
What needs improvement?
I'm not sure how Spacelift can be improved, as I think it's a very good tool and it's giving us all of the functionality that we expect. Nothing comes to mind regarding needed improvements.
For how long have I used the solution?
I have been using Spacelift for six months.
What do I think about the stability of the solution?
I haven't noticed any issues with Spacelift; it seems to be running smoothly.
What do I think about the scalability of the solution?
I don't know how to answer regarding Spacelift's scalability, as I haven't seen a situation where scalability was really an issue.
How are customer service and support?
I haven't had an opportunity to deal with customer support, as I haven't needed any support.
Which solution did I use previously and why did I switch?
The previous solution we used was GitHub repositories for the different modules, which wasn't a competitor. It was a good switch.
What was our ROI?
I don't know about the return on investment, but from what I can see, there's always a question of whether taking on a new tool that you're paying for is worth it. In terms of ease of use, it makes life a lot easier. Anything that reduces the amount of work needed to do repetitive tasks is a bonus. From what I understand, the person that made the decision is still happy to continue using it, so it must be giving enough value for it to continue to be used.
Which other solutions did I evaluate?
I personally didn't evaluate other options before choosing Spacelift, as Spacelift was apparently chosen because it appeared to provide a better solution than what we were using and was probably the most appropriate one for the tasks needed.
What other advice do I have?
My advice for others looking into using Spacelift is that it's a very useful tool if the only other option being used is GitHub repositories. It makes the whole process much more easily defined and integrated with pipelines, so it's worth checking out.
Before we started using Spacelift, we were hosting the different modules in Git repositories, which means that you need to navigate to the specific Git repository to find that particular module. It's not designed just for Terraform modules, whereas Spacelift appears to be a far more focused tool that allows you to see all of the things that are relevant to maintaining a Terraform module in a very clear and easy way.
I give this review a rating of nine out of ten.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
reviewer2847312
Automation has reduced manual server setup and still needs broader capabilities
Reviewed on May 29, 2026
Review from a verified AWS customer
What is our primary use case?
My main use case for Spacelift is for configuration management, and I used it for automation using Ansible playbooks.
A quick specific example of how I used Spacelift for configuration management and automation with Ansible playbooks is that we previously used Ansible for Linux-based tasks such as the creation of users, patching of the servers, and installation of agents. If a server is built new, we need to install multiple tools and security tools, and for the installation of those agents on the endpoint servers, we used Spacelift.
Regarding my use case with Spacelift, one more use case I have used is that we previously saved the Ansible playbook scripts locally or in a shared drive, then we used a GitLab repo which was integrated with Spacelift. This was helpful for us to manage the codes through GitLab repos and integrating that with Spacelift.
What is most valuable?
Spacelift offers compatibility with multiple clouds, which I have seen used for the implementation.
I have used Spacelift with AWS and Oracle Cloud, and that flexibility helped my team.
Regarding features, we integrated Spacelift with the GitLab repo, which is one important integration, and along with that, you can use webhooks. I have not used it much because my scope was very small, but I have seen in the Spacelift GUI that many capabilities, such as using it as a CI/CD pipeline, exist.
Spacelift has positively impacted my organization by reducing manpower, as it reduced the efforts of resources in the team, where previously a job done by two or three engineers can now be easily managed by one engineer using Spacelift.
What needs improvement?
Regarding how Spacelift can be improved, I do not have much idea since my scope of usage was very minimal. I do not have much to add about needed improvements or anything I found confusing.
For how long have I used the solution?
I have used Spacelift for a period of six to twelve months.
What was our ROI?
About measuring that impact, I have seen a basic observation, but I do not remember the real calculations done as I have used this around two or three years back. The calculations were done and given by the management, not by me.
Which other solutions did I evaluate?
I chose a rating of six out of ten because I think multiple other tools similar to Spacelift exist, for example, many automation tools such as Jenkins or other cloud-native tools that perform efficiently compared to Spacelift.
What other advice do I have?
My advice to others looking into using Spacelift is that it would be a good, user-friendly tool. If you are more aware of the concepts from the basics, you will understand it better. If you directly use Spacelift through the graphic user interface without that knowledge, you might not get the basics, for example, regarding Ansible.
Spacelift is an easy to use tool that makes life easy by not burdening you with configuring a configuration management tool, as it comes ready-made.