Pulumi Enterprise Reviews

I use Pulumi Enterprise mainly for provisioning and creating infrastructure within AWS cloud and managing the infrastructure as code.

For one of our websites that we created for Seven West Media, we had to create the infrastructure such as S3 buckets, EC2 instances, CloudFront distribution, and all the connections along with the VPC. We did all of that in Pulumi Enterprise. We also had to convert a lot of the code from Terraform to Pulumi Enterprise.

We've been using the AI tool that Pulumi Enterprise provides for converting Terraform to Pulumi Enterprise. It converts Terraform to Pulumi Enterprise, and it's very useful and highly recommended. The Terraform to Pulumi Enterprise AI command is excellent.

The best feature of Pulumi Enterprise is that it is platform agnostic, so you can deploy to AWS or Azure. We use TypeScript for Pulumi Enterprise, and you can use any programming language such as Python as well. This is very useful because I'm familiar with TypeScript, so I've used that with Pulumi Enterprise.

I used to use Terraform before, and Terraform uses the HashiCorp language which is a bit different. That takes some time to learn. However, TypeScript is a familiar language for me because I've used it in university. I definitely used it very easily in Pulumi Enterprise because things such as for loops, if statements, and the way you write the syntax of the code is quite useful. I haven't tried Pulumi Enterprise in other languages, but I have seen the documentation in Python mostly. Pulumi Enterprise documentation is very detailed, and I highly recommend it because it's very easy to look at.

We've been changing from Terraform to Pulumi Enterprise and converting all the codebases from Terraform to Pulumi Enterprise. It has made things better and more standardized. Pulumi Enterprise is a great infrastructure as code tool.

It has definitely saved time and actually improved confidentiality as well because Pulumi Enterprise stores secrets in a very secure way. The infrastructure as code that we've written is very easy to write, and you can write in TypeScript quite easily as compared to other languages.

We had an issue once with Pulumi Enterprise versioning where one of the versions didn't work for us. I had to downgrade the Pulumi Enterprise version to make things work. I suggest ensuring that the higher versions of Pulumi Enterprise always work without issues.

When the Pulumi Enterprise seminars and webinars happen, they're always dedicated to other time zones. Having a time zone for Australia Perth time would be nice because all the seminars are always at 2:00 a.m. in the morning for me at Perth or maybe after 5:00 p.m. or before 8:00 a.m. would be ideal. I enjoy attending the Pulumi Enterprise seminars, but they're just at odd times.

I've been using Pulumi Enterprise at Seven West Media for about one and a half years.

Pulumi Enterprise is definitely stable. Pulumi Enterprise is a great company and provides a very stable environment.

It's highly scalable. We're a big company, Seven West Media, and Pulumi Enterprise has definitely scaled to that level to manage its resources.

I personally haven't tried the customer support line for Pulumi Enterprise, but I'm confident it will be good.

We previously used Terraform as infrastructure as code, but it was very hard to manage. Terraform is a bit harder to manage. However, Pulumi Enterprise is very easy to manage the codebase, and the file structures make sense.

I could definitely say that fewer employees are now needed because everything is automated and the AI capabilities handle it. Pulumi Enterprise definitely saves time and saves money that way for companies.

We mostly evaluated against Terraform. Pulumi Enterprise has a better way of handling secrets and is platform-agnostic, so we went with Pulumi Enterprise.

Pulumi Enterprise is a great tool for infrastructure as code deployments, and you can do it with any programming language, so it's quite useful. The documentation is quite detailed, and I definitely recommend it. One thing I've realized with Pulumi Enterprise is that you can also import resources that you've already got in AWS. If you created a resource on AWS manually, you can still import it with Pulumi Enterprise. The way you do it in Pulumi Enterprise is very easy.

Pulumi Enterprise is a great tool, and I definitely recommend it. Pulumi Enterprise has very good videos introducing someone to it. If you look at the starting website for a first-timer getting into Pulumi Enterprise, it's very easy to set up. Getting someone started is the biggest thing, and Pulumi Enterprise has nailed it.

Pulumi Enterprise's AI capabilities are quite good. It is quite secure, and I've used the AI feature to convert from Terraform to Pulumi Enterprise, and it gives great results. Pulumi Enterprise's AI capabilities are quite accurate and reliable, and I definitely trust Pulumi Enterprise's AI tooling and Pulumi Enterprise itself. I would give this review a rating of nine out of ten.

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 deploy resources to our main project called MIA, which is basically an AI assistant. We use resources from AWS, including S3, EC2, ECS, ECR, Lambda, SNS, SQS, and others.

For example, we have a notifier service where we have a Lambda worker that sends messages to an SQS queue, and with this, we have a consumer that sends WhatsApp messages and SMS messages to our customers.

We are using Pulumi Enterprise with our AI assistant, which is Cloud Code. We encountered some difficulties integrating this with our code assistant, so I believe it could be easier to integrate. I remember a time when Cloud Code made a mistake in the documentation, creating a non-existent parameter and props, which is a common issue I see during my workflow.

Pulumi Enterprise offers very good features. I really appreciate the access control with permissions and detailed permissions by role or team, which we use for our developer team. This is the main feature I appreciate, as there are different levels within our team. Policy management, policy as code, and audit logs are also beneficial because when a starter developer makes a mistake, we can check the audit log.

Pulumi Enterprise has positively impacted our organization by enabling fast deployments and providing a centralized configuration for our two environments, development and production. With separated stacks, we can replicate the same environment on both sides.

Before using Pulumi Enterprise, our deployment time was between thirty minutes to an hour. Now with Pulumi Enterprise, we can change anything in our cloud environment in just a few minutes, like two or three minutes. Of course, there are more complex situations that differ in time, but in general, we have reduced time by about sixty to seventy percent.

The main feature that could be improved would be better integration with AI. For instance, having an assistant in the platform, as a chat, to ask questions and make changes with this conversational model would be beneficial.

The main improvement for Pulumi Enterprise could be the integration with AI, allowing it to learn and make changes to accounts or stacks. My main concern is really the AI integration. Regarding documentation, it could be interesting to have a markdown copy button. When I go to S3 documentation or Lambda documentation, it would be great to have a copy as markdown button, as I have seen in other documentations, which is very good for providing context to AI.

Regarding Pulumi Enterprise's AI capabilities, we currently have good control over security and governance, but it is difficult to give control to AI. There is a good approach from AWS where the AI functions more as a supporter rather than a manager, acting as a consultant where you can get information and ask questions without losing control or granting high permissions to AI.

In the past year, I remember instances when Cloud Code searched for documentation from Pulumi and usually returned a non-existent parameter, which caused me to spend a lot of time finding and removing the incorrect parameter. I think it could be easier for AI to crawl documentation pages and handle such tasks.

I have been using Pulumi Enterprise for two years, two and a half to be precise.

Pulumi Enterprise is stable, and we have never encountered any stability issues.

Pulumi Enterprise offers good scalability because we can add more members and create new stacks, migrating with ease, which is beneficial for us.

Pulumi Enterprise is a very good solution for scalable teams, and we are trying to get better with this.

To be honest, I have never required specific support, but the main, first-level support has been very good.

We used to deploy and make infrastructure and cloud changes manually. Our process before Pulumi Enterprise was very hard and slow.

We have seen a return on investment because it is easier to make infrastructure changes, even without designated DevOps personnel. Developers can make these changes, and we save time due to these automations, allowing us to change environments in less time than we could two years ago.

My experience regarding pricing, setup cost, and licensing has been good, without any problems. We find the situation stable and plan to continue using Pulumi Enterprise for many years.

I evaluated Terraform, but we chose Pulumi Enterprise as the option for us because of the programming language. We prefer using Python since our main stack here in our project is based on Python, which most developers work with, while Terraform uses a different language.

I would advise that Pulumi Enterprise is a good option, but it is important to study and gain context before asking AI questions. It is crucial to understand what you are doing in the cloud environment, particularly regarding AWS or other providers. I would rate my overall experience with Pulumi Enterprise an eight out of ten.

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.

Pulumi Enterprise is way better than Terraform in my opinion because it has a declarative syntax that Terraform does not have, which is really valuable.

This shift to everything as code has led to measurable changes such as faster deployments. Deployments are faster because we already have everything in one place, so we know where to change things. The main benefit is the history: we know everything that changed and we can track everything.

Reusable components and infrastructure testing in a real language have helped my team a lot because we can test things before shipping it and before making changes, which is really useful. If something is going to break, we know in advance.

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. The client was using Azure platform to create or manage the resources. We started providing them solutions with Pulumi Enterprise and it worked very well because it was managing the managed identities, the DB containers, and the Key Vault access, event hub, and all kinds of these layers. This was incorporated in Pulumi Enterprise. This was our main case for provisioning the infrastructure for our client with the help of Pulumi Enterprise.

Pulumi Enterprise has allowed us to be more confident in the code changes because we have many teams. For example, for development, we have a couple of teams who are working on the development applications, and then there are a couple of teams who are working continuously on the production instances. Pulumi Enterprise has helped us in the code changes that we are actually deploying and releasing. We are doing unit testing with the help of Pulumi Enterprise's infrastructure as part of the pipeline because it helped to add the Azure DevOps pipeline and it worked for the part of the CI pipeline and then we did the CD, the configuration or the continuous deployment with the help of it.

As soon as we see the changes are integrating into the pipeline and it is getting deployed and we get the GUI, proper GUI where we can simply differentiate what is actually applying or what is actually deleting from our infrastructure. This has helped significantly.

The best feature that Pulumi Enterprise offers is the deployment, running, creating the stack, managing all those stacks. For example, for development, we have an individual stack for development. For QA, we have another stack. And for production, for non-prod, for other stacks also, they have independent stacks that are totally independent on their own. Nothing is dependent on any other stack. As soon as we are deploying any changes on the development, it is going to be deployed on the development only.

The deployment checks stand out the most valuable for me because it allows me to debug my environment. For example, if I run any change in the production environment, it will give me a URL which will show a preview of what is the difference we are going to apply on our current infrastructure and what was earlier. I can share that URL with my peers, with my colleagues, and they can also see what is actually going to happen with this change. That is the most valuable thing I have personally perceived, and my other team members also feel it is a very important feature of this.

For improvement, I feel there can be other things. Sometimes I feel that the state and the stacks get large eventually and sometimes they give the output in a very long format and it is difficult to really understand what is happening on it. I feel that it can be improved by Pulumi to manage those long and large stacks.

I think the cost was very high when I had discussions with the customers. They felt that Terraform has less capability, but it is not that costly compared to Pulumi Enterprise. If the cost can be a little reduced, I think it is going to capture most of the market.

I have used Pulumi Enterprise for one of my customers, and it was used only for five to six months. I have utilized my expertise for Pulumi Enterprise for six months.

Pulumi Enterprise is very stable.

We are using the enterprise version, so it is very scalable. Many users in our company are using it and they have not faced any scalability issues till now.

We were using Terraform, Terraform Cloud to provision all the infrastructure, but it has some limitations. Pulumi Enterprise has provided many other features which allowed our customer to change their decision to come and start using Pulumi instead of Terraform.

We were using Terraform, Terraform Cloud. There were many reasons for switching from Terraform to Pulumi. First of all, the licensing. Earlier the Terraform Cloud license was almost free, and after HashiCorp sold it to IBM, it became costly and it is not still confirmed on the licensing thing from Terraform Cloud. The second thing is that Terraform uses its own language, HCL, HashiCorp configuration language, which does not allow us to use any programming skills such as for loops or if/else statements and other languages. Pulumi is providing six languages to use and set up the infra with. These are the main features that Pulumi has also, which allows us to switch from Terraform to Pulumi.

The setup is very easy. I would say one of the main features I think I forgot to add in my initial questions. The setup to use Pulumi Enterprise is very flawless and easy to use for any layman guy. If I give it to configure and start using Pulumi Enterprise to an intern, he will start using it in five minutes. The setup to use Pulumi Enterprise is very easy.

I would think the return on investment is that earlier only the infra guys were using any tool to deploy the infra, but in my team, I can see the development team is also encouraged and happy to use Pulumi Enterprise to configure the resources on Azure cloud because they have the programming skills and Pulumi Enterprise is providing features in their tool. I have seen the development team and the testing team who feel or want to do cross-team work, and they are very encouraged and happy to start using Pulumi Enterprise. I think that is how I can say time is being saved, and people are getting encouraged to use any infra tool to configure their infra as per their requirement. That is my experience with me and the other team members and that is what I feel as a return on investment on Pulumi Enterprise.

The pricing I would have already confirmed is high for enterprise; otherwise, it is available free of cost also. The enterprise version is a little bit high, and the licensing and setup are totally okay and we are very happy to use them. The setup is very easy.

If you have a complex infrastructure, start using Pulumi Enterprise. If you have a very small team to use any of these infra IAC tools, then use Terraform Cloud. Otherwise, if you have a complex infrastructure or a big team, start using Pulumi Enterprise without any second thought. It is going to give you a very good return on investment, and you will feel very happy after using it. My overall review rating is not available.

My main use case for Pulumi Enterprise is infrastructure as code, provisioning resources on Azure. For provisioning resources on Azure, it is heavily used for creating Kubernetes clusters, using for example a CI/CD pipeline with Azure DevOps.

The main reason for adopting Pulumi Enterprise regarding the infrastructure-as-code part is the ability to use the .NET language. Since our products were developed in .NET, we understood that it would be interesting to have an infrastructure-as-code tool that could be used with the same language we already had knowledge of.

I believe that the best features Pulumi Enterprise offers us are the stacks, which allowed us to separate the development, staging, and production environments, and to have a YAML configuration file where we defined the different tiers per environment. Additionally, the built-in secret management was invaluable. We were able to create Pulumi secrets without needing to use an external provider, a Key Vault, or HashiCorp Vault.

Regarding the environment separation and the built-in secrets management, these features had a positive impact on my day-to-day work and the security of operations. With separation by stacks, we did not need to keep duplicating code. We used the same code for all environments, but changed the particulars related to compute power size, number of replicas in a given cluster, etc. As for secrets, it made things much easier because we did not need to point to a source or an external vault. This also helped a lot from a security standpoint because we did not need to have the password hardcoded.

Pulumi Enterprise has had a positive impact on my organization in terms of agility, standardization, and governance in the infrastructure-as-code area.

Regarding how these improvements in agility, standardization, and governance showed up in practice within my team, we were able to maintain a standardized structure for multiple resources. If I were to do it manually, I would probably have many resources in different forms, done by different people. When we use infrastructure as code, we can have code that is easily replicated and distributed for the creation of multiple resources while maintaining the standard. There is also the governance part because we can organize who is creating the resources. We have a code repository in Git, so we can track who made the change, who made the pull request, and at what time the pipeline ran. Additionally, there is agility in the process. In a use case where we had to create, for example, 200 computers or 200 virtual machines, if I had to do that 200 times manually, it would take much longer. Using a for loop, for example, we did this in a few minutes.

I see Pulumi Enterprise as a very complete tool. I worked with Terraform, which I believe is Pulumi Enterprise's main competitor, and I do not see many things that Pulumi Enterprise could improve, at least based on what I used. What I missed was integration with other tools. For example, Infracost, which is a tool for cost analysis in the pipeline, only worked with Terraform at the time. I missed having that integration, but that is more because of Infracost than because of Pulumi Enterprise. Additionally, I think the modules part is a bit weak. Terraform's module system is better and much better defined.

I used Pulumi Enterprise for about 5 years.

Pulumi Enterprise has been stable in my experience.

Pulumi Enterprise has high scalability.

I had no need to contact customer support for Pulumi Enterprise.

I did not use a different solution for infrastructure as code. Pulumi Enterprise was the first tool.

Pulumi Enterprise's pricing, setup costs, and licensing are not high. There is a cost, but there is also the open-source option which works very well.

Before choosing Pulumi Enterprise, I evaluated Terraform as another option.

The advice I would give to others who are thinking about using Pulumi Enterprise is to use it if you have development knowledge in some language that Pulumi Enterprise supports, because it is very interesting when you already have a development stack. I would rate this product an 8 out of 10.

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.