Pulumi Enterprise Reviews

My main use case for Pulumi Enterprise is that it is an infrastructure as code tool. We're slowly importing legacy infrastructure and creating all new infrastructure with Pulumi.

A quick specific example of how I'm using Pulumi Enterprise in my infrastructure is that we provision all AWS resources and generally all cloud resources with Pulumi, including SSO, EKS cluster, databases, and everything. Everything is managed by Pulumi.

Something unique about my use case with Pulumi Enterprise is how it manages secrets. It's quite convenient as it is able to encrypt secrets right in the repository with a KMS key. Additionally, AI works quite well with Pulumi. It helps generate code and it works well for the development team. They prefer it much more than Terraform. It is more aligned with what they see daily, making it a more developer-friendly toolset.

The best features Pulumi Enterprise offers for my team is a combination of a high-level infrastructure as code tool and all the capability of a general programming language. We use Pulumi runtime for TypeScript and Pulumi with Python.

Using TypeScript or Python with Pulumi makes things easier for my team because it is fast and reliable, and the team is able to use a language that they are familiar with. This is important when the infrastructure or platform team collaborates closely with the back-end team as they don't need a translation layer between Terraform and what they work with. TypeScript really helps there. Additionally, Pulumi has been linked to all major programming languages, making it definitely helpful.

Pulumi Enterprise has impacted my organization positively as it is a modern infrastructure as code tool that helps us manage resources efficiently and reduce delivery time.

Regarding improvements for Pulumi Enterprise, it would be beneficial to move a Pulumi-generated plan from an experimental feature to general availability. It works, but I don't feel confident when I have to enable an experimental flag in a production environment.

I have been using Pulumi Enterprise for approximately three years.

Pulumi Enterprise is stable enough.

Pulumi Enterprise's scalability is limited as it is not particularly scalable. You should keep the project relatively small to avoid simultaneous Pulumi runs.

Regarding customer support, we use the open-source version, so I have never communicated with customer support.

I had experience with various infrastructure as code tools with my previous employers, and we also used Terraform in some projects. There was no particular reason why we switched to Pulumi; we started using it from the beginning in that infrastructure. We simply tried it, and it works well.

I have seen a return on investment using Pulumi as we need fewer employee resources, and we spend much less time on routine tasks. We probably saved two engineer times with Pulumi.

Before choosing Pulumi Enterprise, I evaluated other options, including Terraform.

Pulumi has reduced delivery time by transitioning from a lengthy process to provision a new environment to a repeatable process. You do it once and then do it again and again.

On a scale of one to ten, I would rate Pulumi Enterprise an eight.

I say eight because this annoying experimental feature keeps it from being a ten. We really want to have a deterministic plan, review the deterministic plan before we apply it in production, and now it is possible only when we enable it as an experimental feature, which I don't feel comfortable doing in a production environment. The second consideration is that sometimes readability could be better, and I have experienced some issues with Pulumi state, though I don't recall exact details.

Regarding Pulumi Enterprise's AI capabilities, I think it provides a pretty good output; however, I haven't used it thoroughly, so I'm not familiar with this part of the product.

I actually had some experience with Pulumi Enterprise AI capability, and I found that its output is pretty inaccurate compared to a general AI model. I stopped using it, and they probably have improved it significantly in the last couple of years.

We don't purchase Pulumi Enterprise; we use the open-source version.

The advice I would give to others looking into using Pulumi Enterprise is that it is one of many infrastructure as code tools. Try it and see if it works for your particular use case. The main advantage is that the team is able to write code in a general programming language, not a domain-specific language like Terraform. On a scale of one to ten, I rate Pulumi Enterprise an eight.

My main use case for Pulumi Enterprise is to store infrastructure stacks. Pulumi Enterprise is used in my organization to bring up infrastructure and store the stacks, so we have all the states there. When I want to bring up new infrastructure for a service within AWS, we use Pulumi Enterprise.

The best features that Pulumi Enterprise offers are its deployment capabilities and stack separation. The separation of environments and permission control help in my daily work because if we want to bring up a stack in production or a stack in some staging environment, we have all this separation within Pulumi Enterprise.

Pulumi Enterprise has had a positive impact on my organization by enabling better acceleration in our environment to bring things up and organize them. We can see what is happening, see the diffs within Pulumi Enterprise, and this helps us a lot with troubleshooting.

Pulumi Enterprise has a lot of good features and I don't think there's anything to improve. There isn't any detail or adjustment that could make using Pulumi Enterprise even more practical or efficient for me because it's perfect.

I have been using Pulumi Enterprise for four years.

Pulumi Enterprise is stable because since we started working with it, we haven't had any issue with Pulumi's cloud going down.

In my experience, the scalability of Pulumi Enterprise is very good and it suits us perfectly.

Pulumi Enterprise's customer support is very good. We had a small issue, and when we needed to contact them, we got a response in less than 24 hours. I would rate customer support as a 10 on a scale from 1 to 10.

We don't use a different solution. When I joined the company, they were already using Pulumi Enterprise, so I don't have information about evaluating other options.

We have already seen a return on investment because we had a reduction in the team. The team used to have 15 people, and today the team has seven people, so the team was cut in half. In terms of cost savings within AWS itself, we can already achieve that with Pulumi as well.

My experience with pricing, setup costs, and licensing was very good for the team we had. For the team size, it suited us perfectly.

The advice I would give to other people who are thinking about using Pulumi Enterprise is that the money invested is very worthwhile. I would rate this review a 10.

My main use case for Pulumi is provisioning cloud resources.

For provisioning cloud resources, we have repositories for basic setup for AWS account, Kubernetes resources, and network provisioning. We also have GitHub workflows that encapsulate Pulumi. When a team needs an S3 bucket or other resources such as SQS or SNS, they run our workflow in GitHub, which hides the complexity of Pulumi. They simply write a YAML file where they define what resources they need, and it performs the provisioning. All of this is in the same config file, but we have different actions handling it.

The best features Pulumi offers are that it functions as a framework inside a programming language. You can use multiple programming languages, and we use TypeScript. This gives you all the flexibility and features of the programming language you chose, such as functions and loops. You can even connect with APIs and external services to have the logic of creating and managing those resources.

Using TypeScript with Pulumi has helped my team because this flexibility enables us to connect different things. It is not static the way it is with Terraform, but rather super dynamic as it is when you program any custom code. This flexibility has helped us.

Pulumi has impacted my organization positively because before Pulumi, we did not have any real infrastructure as code, and having multiple environments and AWS accounts that we needed to manage was difficult.

I cannot quantify the positive outcomes, but we definitely have a more professional setup now than we used to have before. When we develop a feature, we know for certain that it gets from dev to stage and prod with the same infrastructure.

Pulumi has some issues worth mentioning. The stacks can grow and the execution time appears to grow exponentially when the number of resources increases. We have had to implement workarounds, such as introducing micro stacks.

I believe Pulumi could be improved by hiding the complexity of micro stacks so that users do not need to know about it. In my opinion, this is achievable because you can separate resources that are related to each other, such as parent and child resources, and the ones that are not related could be saved in a separate stack, as we are doing with micro stacks. I think this could be improved.

This is the only serious limitation of Pulumi that I have seen so far. Most of the issues I have encountered come from the providers. For example, when using AWS, there is an annoying issue of conflicts when you have both a SecurityGroup and SecurityGroupRule defined. The same applies to RouteTable and Route, creating conflicts between them.

I have been using Pulumi for six years.

Before we wrap up, I have additional thoughts about Pulumi. There is something I would mention that is not about Pulumi itself, but rather how you use it. For example, I discussed how you can connect different APIs. It is really important to do proper error handling. When you fetch things from APIs or any website, you need to perform proper error handling because if you do not do it, resources could get deleted on transient errors, such as network errors. If you fetch something and you expect a resource to be returned or you expect some information to be returned, you need to distinguish error codes. For example, not found means you can delete it, but if you have any kind of network error or an internal server error, it should definitely break the execution of Pulumi and not delete things. This is a technique, but it is not related to Pulumi itself. It is about how you use things.

If you have complex infrastructure, you should definitely use Pulumi. However, for small setups, it might be an overkill for you. If you can stay with Terraform, I see no reason why you should not.

I give this review a rating of nine.

We use Pulumi Enterprise with the Python runtime to provision our Azure platform, essentially our managed identities, CosmoDB containers, their data planes and role assignments, Key Vault access, event hub RBAC, and that sort of layer. It's split into per-service stacks at the moment that each own their own resources inside shared infrastructure, so it means one team can essentially add what they need without touching another's.

Pulumi Enterprise has allowed us to be much more confident in the code changes that we are actually deploying and releasing, and just as an example, I mentioned earlier, we're now unit testing all of our Pulumi Enterprise infrastructure as part of the CI pipeline. So we know quite confidently that the change is actually going to be successful before it's actually been deployed, which has been hugely beneficial for us.

It's definitely saved time and accuracy in the development space because we're now spending less time testing, debugging code, and worrying about manual infrastructure. We now do all of the DevOps ourselves, so definitely saved time there. I wouldn't really want to give a specific number on it here, but it has been very beneficial.

Another good point for us is that we're on Pulumi Cloud as an organization, so state is managed rather than us babysitting a blob storage backend, and every stack has a browsable update history. For example, I just ran a prod change this morning that was update 10 on that stack, and it gave me a shareable URL for the preview diff and the apply. The feature we lean on most is ESC, their environments and config layer, so we get one shared environment that supplies the tenant subscription ID and cluster coordinates to every stack that imports it, meaning there's nothing environment specific, essentially, which is a huge benefit for us.

The main feature we use, to be honest, is state management.

I think debugging can sometimes be less intuitive; for example, because you're executing actual code to produce infrastructure, there's a mental gap between the code I'm writing, the Pulumi Enterprise engine, the desired state that we're after once the code actually executes, the provider, for example, in this case Azure, and the cloud resource. When something doesn't behave as expected, there's another layer of abstraction to understand. You're not just debugging your code; you're debugging how Pulumi Enterprise interprets that code and interacts with the provider as well. So it can be an extra mental layer to get your head around.

The quality of the experience with Pulumi Enterprise definitely depends somewhat on the provider and the resource that you're working with. For us with Azure, we've found it to be very useful, but I could definitely see that if there isn't the same sort of level of quality with other providers, then we would probably have a more negative experience.

In engineering, there's always something that can be improved even if the consumers don't know what they need, and I'm sure there is definitely room for improvement.

I've been using Pulumi Enterprise for around nine or 10 months.

Pulumi Enterprise is stable.

We find Pulumi Enterprise very scalable.

I've actually never needed to reach out to customer support, so I'm not sure, but I would imagine it's quite good because it feels like quite a modern system with modern support.

We used Terraform, and we switched because we just found the state management quite cumbersome. New people that were trying to use Terraform got quite confused by that, and also it wasn't really testable, and we found that our complicated business logic wasn't really suitable for Terraform.

There were no issues with the initial setup that I could think of.

I wasn't too involved with that part of the process.

The ROI was quite good, actually.

We did evaluate other options before choosing Pulumi Enterprise, but I can't remember now; as I say, it's been nine or 10 months, and they weren't good enough to remember.

I would rate Pulumi Enterprise an eight out of ten.

I've been using Pulumi Enterprise with Claude as a plugin for a while, and to be honest, I found the governance and security very good with Claude Code. I haven't really been concerned about it at all, and it's been very good at what it does.

It's been very accurate to me; previously to this, I used Copilot with Terraform, and I found that to be very inaccurate. So coming from that to Pulumi Enterprise and Claude Code has been wonderful.

I'd definitely recommend installing the Claude plugin and just getting a general overview on how Pulumi Enterprise can help improve your infrastructure.

My main use case for Pulumi Enterprise is deploying infrastructure into Azure cloud.

Recently, I deployed a Kubernetes cluster using Pulumi Enterprise, so I wrote the code out and then used our CI/CD pipeline to deploy the infrastructure.

Pulumi Enterprise fit into my CI/CD pipeline for that Kubernetes deployment, but it did not make any particular part of the process easier or more efficient compared to Terraform, for example.

Pulumi Enterprise has made our infrastructure deployment more efficient.

It has made deployment more efficient in a mixture of ways, so it is definitely been faster deployment times. We have templated our infrastructure as well, so we are now rolling out full infrastructures for projects within an hour or two. It is naturally obvious that there is much less reduced manual work and much less config drift.

The best features Pulumi Enterprise offers include very good dependency management and the ability to use multiple languages to deploy the infrastructure. We use C# as that is our company language, but there are many languages that can be used. That is probably the best feature wherein you are not restricted to a custom-made language as you are with Terraform.

That flexibility has positively impacted my team's workflow and productivity as it has meant that new people joining the company, for example, as I was once upon a time, find it makes integration much easier. For those that have never used Terraform, they are required to learn HCL, whereas with Pulumi Enterprise, everyone has at some point learned some element of coding, so it makes it much easier to integrate other people.

I would say Pulumi Enterprise is a bit behind Terraform in its speed. Obviously, it is a wrapper sitting on top of Terraform, so it can be a bit slower in releasing certain new resources or being up-to-date with Terraform. But overall, it is fairly easy to use. Additionally, I do prefer the config structure within Pulumi Enterprise. I feel it is much easier to manage than it is with Terraform. The versioning is also much easier; in Terraform, you need a versioning file, but you do not have that issue with Pulumi Enterprise.

Pulumi Enterprise can be improved by being more up to date with Terraform. Additionally, I sometimes struggle to see what we are paying for; we use Enterprise, but does the money justify what you are being offered when you have Terraform for free which offers a majority of the features already?

Regarding Pulumi Enterprise's governance and security, I think they are adequate; I do not think they are spectacular and I do not think they are bad. They are something we are still exploring.

Regarding Pulumi Enterprise's accuracy and reliability of output, I think they are fairly accurate.

I have been using Pulumi Enterprise for over five years.

Pulumi Enterprise is stable in my experience.

Pulumi Enterprise is scalable for my team's needs as it has done what is needed.

I did not previously use a different solution.

My advice to others looking into using Pulumi Enterprise is to consider Terraform first.

I found this interview because someone reached out to me on LinkedIn. I think a higher incentive should be offered, but the rest was fine.

I use Pulumi Enterprise to manage infrastructure, specifically cloud-based infrastructure. I manage infrastructure, SSO and security, create infrastructure and secure it, manage identity and access, and manage configuration in cloud or multi-cloud environments.

The best features of Pulumi Enterprise include state management, which involves tracking and keeping track of the infrastructure. State management helps my workflow and solves problems for me by ensuring my infrastructure data is in sync.

Pulumi Enterprise increases efficiency and reliability by providing seamless automation processes and tools while considering security and making secure infrastructure easy. Pulumi Enterprise has positively impacted my organization by making automation seamless and efficient.

For efficiency, it helps in managing multiple infrastructures because once I write my code, I can reuse it for different projects.

Pulumi Enterprise could accept more automation, such as creating workflows or frameworks for platforms like YouTube and Spotify. Additionally, it should allow for creating resources on the cloud console with less friction.

I would like the documentation feature to enable me to download the documents of my infrastructure from Pulumi Enterprise once it is written. I do not want to have to rewrite documentation after coding; once my infrastructure is written with Pulumi Enterprise, I should be able to get the documentation seamlessly.

There should be more investment in building a stronger community around Pulumi Enterprise, as the Pulumi Enterprise community is not that strong compared to its capabilities.

I have been using Pulumi Enterprise for two years.

Pulumi Enterprise is stable. However, there are still many improvements that can be made.

Pulumi Enterprise's scalability scales easily and efficiently, thanks to its modularity and the options it provides, along with the opportunity to reuse code for different projects.

Customer support is present, and so far, I have not had any cause for alarm. My experience has been fair.

On a scale of one to ten, I rate customer support a three because I have not needed to consult them much at all.

My fundamental experience in infrastructure as code is with Terraform. However, after joining this new company where they have been using Pulumi Enterprise, I continued using Pulumi Enterprise with them and see no need to switch the entire organization's infrastructure to Terraform.

Pulumi Enterprise saves time when creating infrastructure, as once I create it once, I can reuse what I have written before. It saves time and also reduces the need for more hires in terms of manpower.

My experience with pricing, setup costs, and licensing is that it is fair; there is not much stress regarding that, but I still believe improvements can be made.

Before choosing Pulumi Enterprise, I evaluated other options, including Terraform and Ansible.

Regarding integrations with other tools, I use Pulumi Enterprise for multi-cloud environments, including AWS, Azure, GCP, and others.

I purchased Pulumi Enterprise through the AWS marketplace.

My advice for others looking into using Pulumi Enterprise is that the onboarding process from other solutions like Terraform is seamless and not stressful, as it is basically the same. Additionally, the opportunity it gives to write infrastructure in any programming language is significant.

I rate this product a seven point five out of ten.

Pulumi Enterprise serves as the main platform for deploying both production and development environments in my organization. Since many developers are involved and frequent code changes occur, Pulumi Enterprise provides an effective way to quickly manage and deploy infrastructure at scale while monitoring operations.

Regarding my primary use case with Pulumi Enterprise, secret management is invaluable, and automated state management is equally beneficial. Through Pulumi Enterprise's secure service, I can collaborate across large teams and mitigate locking and concurrency issues that are often associated with local state files, which has proven to be very useful.

One of the best features Pulumi Enterprise offers is the ability to be configured using multiple high-level languages such as Python, Node.js, and Go, allowing seamless integration with existing applications in development workflows and testing frameworks. Another valuable feature is testability, as it uses standardized programming languages that teams can easily integrate into infrastructure, treating it exactly as software.

Regarding how the use of multiple languages and testability impacts my day-to-day work and my team's productivity, a practical example is that we do not have to learn a new language or new configuration or work outside the box to understand everything. With basic existing knowledge, we can understand most nuances and configuration change management in infrastructure easily.

Pulumi Enterprise has positively impacted my organization because it has saved considerable time. We do not have to spend extensive time debugging or going through countless pages of cloud logs. We can see everything in one place, and with a single command and button push, we can deploy, roll back, see what is happening, receive notifications, and access everything in one location, effectively saving significant time and effort.

Pulumi Enterprise can be improved by providing much better support rather than relying solely on AI.

User experience with Pulumi Enterprise is acceptable, but integrations could be more expanded. The remainder of everything appears satisfactory to me.

Every product has room for improvement, which is why I rate Pulumi Enterprise a nine out of ten. There is still room for improvement as AI is advancing, how Pulumi Enterprise can support increasingly more capabilities, new technologies emerging, security considerations, and integration with additional platforms. There is always room for improvement across any product.

At my recent company, I was introduced to Pulumi Enterprise, and I have been using it for almost eight months.

I would advise others considering Pulumi Enterprise to start experimenting with multiple use cases and different scenarios. Begin as soon as possible, learn the nuances and configuration details, understand the way of working, determine how it could be efficient, and assess how it could integrate into your existing workflow. Gradually migrate the entire infrastructure to Pulumi Enterprise instead of managing it manually. I rate Pulumi Enterprise a nine out of ten.

My main use case for Pulumi Enterprise is managing and running infrastructures across my projects, specifically cloud infrastructure.

For example, my product, Resume AI, has multiple stacks, and I use Pulumi Enterprise to check my deployments to ensure that everything is running smoothly and to add members to the group so that they can monitor their deployments as well.

The best features Pulumi Enterprise offers include checking out the deployment, running, creating the stack, managing my stack, and access keys.

Out of those features, the deployment check stands out the most for me because it allows me to debug my environment.

Pulumi Enterprise positively impacts my organization as it enables us to manage stacks across different environments.

I have not yet understood how the pricing model works, and I would appreciate a clearer and more precise explanation.

I have been using Pulumi Enterprise for two years.

I have not yet used the AI capabilities of Pulumi Enterprise, and I do not see how I would use that.

I have not seen any specific outcome or benefit that I have measured so far, such as saving time, reducing errors, or helping my team in a measurable way.

I did not purchase Pulumi Enterprise through the AWS Marketplace.

My advice for others looking into using Pulumi Enterprise is to pursue it. I gave this review a rating of 9.