Pulumi

“When we demonstrated to people that what used to take a week and a half now, with Pulumi, took under a day, they were shocked.”

“The Pulumi policy packs are one element of the guardrails, and it’s defense in depth. We have so many guardrails in place that are automatically enforced, and violations are automatically reported. And that’s what allows us to be able to proceed with the velocity that we do.”

“We use Pulumi Cloud Deployments for all deployments rather than GitHub Actions, and Neo’s really good at driving that itself.”

“When we have cross-cutting infrastructure configuration, we can change that in one place, and we know that all of the infrastructure is going to be updated.”

“We can create composable blocks of configuration and use the Pulumi ESC’s import functionality to dynamically build those in,”

“Pulumi is a key component of our strategy to pick the best tools that will help us grow on this agentic journey.”

“By using stack references, we ensure that all the dependencies for an application that we deploy in Pulumi are up to date. If I have any changes in a VPC, it’s very easy to cascade that through all the other projects that we manage with Pulumi. When I started using Pulumi for this it was love at first sight.”

“With Pulumi Policies we can provide reusable infrastructure components to our application teams and ensure that their implementations adhere to company standards.”

“Once you use a familiar programming language to tackle a problem, you see that you can do way more in less time. Pulumi was a natural choice based on the background and skills of our people in DevOps.”

““Terraform was slowing down our growing team of software engineers,” says Christian Theilemann, Staff Software Engineer at Aptos Labs. “Switching to Pulumi for our IaC needs helped us massively accelerate development velocity by increasing the level of automation and making infrastructure maintainable by every software engineer, not just the infrastructure team.””

““Terraform was slowing down our growing team of engineers. Switching to Pulumi for our IaC needs helped us massively accelerate development velocity, while upgrading the security, compliance, and cost control policies.””

“It would be a huge win for us to enforce our policy packs with the Automation API, to ensure that we can never create any non-compliant infrastructure. That’s the big one that’s on our radar next,”

“Instead of having our centralized infrastructure repos with huge blobs of Terraform that developers have to maintain and care about, we have an internal developer platform and we move the configurations into the service repos themselves. It’s a big win for our developers. They don’t have to go hunting around in multiple places to find where their infrastructure is defined,”

“We moved from a lower-level Terraform and HCL-based interface to something built with Pulumi and the Automation API, to define this really custom, high-level, and much simpler YAML schema. We’ve identified really common business cases that our developers need out of the infrastructure, and made those into built-in defaults. They can just plug in a few standard GitHub Actions workflows and they have infrastructure right in their repo,”

“Number one for us is the ability to use general-purpose programming languages. For that ‘batteries included’ experience we wanted to provide, being able to have the full power of Python at our fingertips to handle all those sorts of specialized cases is really, really powerful.”

“A big problem we had before was that we used Terraform in conjunction with Terragrunt, and that’s pretty heavily dependent on your on-disk structure,” Forcier said. “We found that it was difficult for developers to understand how they needed to plug in outputs from different modules, or reference across different parts of the infrastructure. It was a challenge for us to maintain.”

“For that ‘batteries included’ experience we wanted to provide, being able to have the full power of Python at our fingertips to handle all those sorts of specialized cases is really, really powerful.”

“Pulumi has emerged as a key element in our strategy, creating tangible value for us by reducing infrastructure deployment time, up-skilling our team, and accelerating our time to market.”

““Pulumi has changed how our team works by giving us deployment superpowers. It’s great to run ‘pulumi up’ and not have to worry about deploying an invalid configuration.””

“I would recommend using Pulumi for everybody who starts on a Green Field approach with infrastructure as code because I’m quite sure and confident to be able to say that it is the most powerful and versatile tool out there. You will run into limits with Terraform, you will run into limits with CDK. Your biggest chance to not run into troubles and limitations is to use Pulumi.”

“It was cheaper for us to pay the subscription fee than to have two people on the payroll who try to maintain and understand all the tooling that we would otherwise have built ourselves.”

“You will run into limits with Terraform. You will run into limits with CDK. Your biggest chance to not run into troubles and limitations is to use Pulumi. It is the most powerful and versatile tool out there.”

““Pulumi was an option that we looked at, and we found that it was pretty easy to get started,” Tyler said. “As the work progressed, we saw that using general-purpose programming languages (in their case, TypeScript) to express our infrastructure resources yielded noticeable improvements. Plus, Pulumi’s state dependency management was a natural fit.””

““The Pulumi Automation API made [deploying the application and its infrastructure] a much cleaner process. With the old architecture, it was much more manual, stitched together with bash scripts, and then wrapped in another tool with its DSL.””

“When implementing Pulumi, we noticed also by using the Pulumi Cloud that we can easily see what’s going on, we can easily find what resources are up and what are down. We can easily manage our stacks and everything is very, very comfortable.”