Sold by: Pulumi
Deployed on AWS
Pulumi is the AI-native infrastructure platform. Cloud engineering teams define, deploy, and manage cloud infrastructure as code using general-purpose programming languages like Python, TypeScript, Go, C#, and Java so infrastructure evolves the same way software does and speaks the same language as AI coding agents. Pulumi works across AWS and hundreds of cloud and service providers.
4.7
Overview
Pulumi is the AI-native infrastructure platform, built for engineering teams who need cloud infrastructure to move at the speed of software development. With Pulumi, teams can define, deploy, and manage cloud infrastructure as code using general-purpose programming languages including Python, TypeScript, Go, C#, and Java, with full software engineering practices including loops, functions, tests, packages, and IDE support. One workflow delivers and secures infrastructure and applications on any cloud, public, private, or hybrid, across AWS and hundreds of integrated cloud and service providers.
Pulumi Neo, Pulumi's AI infrastructure agent, works inside your existing workflows to accelerate Terraform migrations, enforce policy, and manage multi-cloud deployments - proposing changes, running previews, responding to failures, and opening PRs in tight feedback loops, all while respecting your RBAC roles, policies, and human-in-the-loop approvals.
Pulumi's Enterprise Edition brings the platform to your entire organization for easier collaboration and governance across teams. Features include:
- State, secrets, and composable configuration (Pulumi ESC), with dynamic, short-lived credentials
- CI/CD integrations including AWS CodePipeline, GitHub Actions, GitLab CI, and more
- Role-based access control (RBAC) with unlimited teams and users
- SAML/single sign-on (SSO)
- Audit logs and drift detection
- Insights & governance: multi-cloud resource search and policy-as-code enforcement
- Developer self-service via reusable components exposed through code, low-code, or no-code interfaces
- Fully interoperable with Terraform and OpenTofu, with first-class support for HashiCorp Configuration Language (HCL)
For custom pricing, Business Critical features like advanced policy as code, compliance, SCIM, 24x7 support, self-hosted Pulumi, or private contracts, contact hello+aws@pulumi.com .
Highlights
- Learn how Pulumi can accelerate your infrastructure projects on AWS: https://www.pulumi.com/case-studies/supabase
- Want volume pricing? Contact us at hello+aws@pulumi.com for a private offer
Get personalized pricing in minutes - New
If qualified, an express private offer gets you custom pricing and terms. Finalize your purchase in the AWS Marketplace console.
Details
Sold by
Delivery method
Deployed on AWS
Features and programs
Buyer guide
Gain valuable insights from real users who purchased this product, powered by PeerSpot.
Financing for AWS Marketplace purchases
AWS Marketplace now accepts line of credit payments through the PNC Vendor Finance program. This program is available to select AWS customers in the US, excluding NV, NC, ND, TN, & VT.
Pricing
Pricing is based on the duration and terms of your contract with the vendor, and additional usage. You pay upfront or in installments according to your contract terms with the vendor. This entitles you to a specified quantity of use for the contract duration. Usage-based pricing is in effect for overages or additional usage not covered in the contract. These charges are applied on top of the contract price. If you choose not to renew or replace your contract before the contract end date, access to your entitlements will expire.
Additional AWS infrastructure costs may apply. Use the AWS Pricing Calculator to estimate your infrastructure costs.
Dimension | Description | Cost/12 months |
|---|---|---|
Pulumi Enterprise | 2500 Resources, 15 team members w/ 12x5 support (21.9M Pulumi Credits) | $32,850.00 |
Dimension | Cost/unit |
|---|---|
100K Additional Pulumi Credits (1 Credit = 1 Resource/Hour) | $300.00 |
Dimensions summary
You buy Pulumi Cloud through two contract dimensions. The Pulumi Enterprise unit is the base subscription. It covers 2,500 resources, 15 team members, and 12x5 support, funded by a pool of 21.9M Pulumi Credits. One credit equals one resource managed for one hour. The second dimension adds 100K Pulumi Credits when your usage exceeds the base pool. Buy as many credit packs as you need to extend capacity. Credits meter all usage, so the add-on scales your subscription without changing the base plan.
Top-of-mind questions for buyers
A resource is anything declared in a Pulumi program. This includes provider resources like a storage bucket, component resources that group several resources like a managed cluster, and stacks such as dev, test, and prod. Each managed resource draws one credit per hour, with partial hours billed as full hours.
Once you use up the included credits, buy 100K Additional Pulumi Credit packs to extend capacity. Each pack adds 100,000 credits, where one credit covers one resource for one hour. You can add as many packs as your usage needs without changing the base Enterprise subscription.
Credits are the single currency for all Pulumi Cloud usage. They meter managed IaC resources, ESC secrets, secret API calls beyond included amounts, workflow minutes, and AI token consumption. Every service draws from the same credit pool at its own rate, so mixed usage all reduces one shared balance.
pulumi.com
Helpful?
Vendor refund policy
All fees are non-cancellable and non-refundable except as required by law.
Custom pricing options
Request a private offer to receive a custom quote.
Legal
Vendor terms and conditions
Upon subscribing to this product, you must acknowledge and agree to the terms and conditions outlined in the vendor's End User License Agreement (EULA) .
Content disclaimer
Vendors are responsible for their product descriptions and other product content. AWS does not warrant that vendors' product descriptions or other product content are accurate, complete, reliable, current, or error-free.
Delivery details
Software as a Service (SaaS)
SaaS delivers cloud-based software applications directly to customers over the internet. You can access these applications through a subscription model. You will pay recurring monthly usage fees through your AWS bill, while AWS handles deployment and infrastructure management, ensuring scalability, reliability, and seamless integration with other AWS services.
Support
Vendor support
Basic Support is available Monday - Friday during normal business hours. To open a support ticket or view service status, please visit https://support.pulumi.com . Contact us at hello+aws@pulumi.com for Enterprise support options.
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
Updated weekly
By Pulumi
By Spacelift Inc.
Top
10
In Testing, Infrastructure as Code
Top
10
In Software Development, Infrastructure as Code, Continuous Integration and Continuous Delivery
Top
50
In High Performance Computing
Sentiment is AI generated from actual customer reviews on AWS and G2
Functionality
Ease of use
Customer service
Cost effectiveness
Positive reviews
Mixed reviews
Negative reviews
AI generated from product descriptions
Infrastructure as Code with General-Purpose Languages
Define, deploy, and manage cloud infrastructure using Python, TypeScript, Go, C#, and Java with full software engineering practices including loops, functions, tests, packages, and IDE support.
Multi-Cloud Provider Support
Works across AWS and hundreds of integrated cloud and service providers with support for public, private, and hybrid cloud deployments.
AI-Powered Infrastructure Agent
Pulumi Neo AI infrastructure agent accelerates Terraform migrations, enforces policy, manages multi-cloud deployments, proposes changes, runs previews, responds to failures, and opens pull requests with human-in-the-loop approvals.
Enterprise Governance and Access Control
Role-based access control (RBAC) with unlimited teams and users, SAML/single sign-on (SSO), audit logs, drift detection, and policy-as-code enforcement across multi-cloud resources.
State Management and Secrets Configuration
Centralized state, secrets, and composable configuration management with dynamic, short-lived credentials and CI/CD integrations including AWS CodePipeline, GitHub Actions, and GitLab CI.
Infrastructure as Code Orchestration
Supports orchestration of multiple IaC tools including Terraform, OpenTofu, CloudFormation, Pulumi, and Ansible for unified infrastructure provisioning and configuration management.
Automated Drift Detection and Remediation
Automatically detects infrastructure drift and restores resources to their expected state through drift remediation capabilities.
AI-Powered Natural Language Interface
Provides an AI infrastructure assistant that enables understanding, designing, deploying, and governing infrastructure using natural language queries and commands.
Policy-Based Governance Framework
Implements governance controls with custom policy definitions, Golden Paths, integration with third-party security vulnerability scanning tools, and best-practice policy templates.
Multi-Tool Workflow Integration
Combines infrastructure provisioning, configuration management, container orchestration, and governance policies into integrated workflows with dependency management and shareable outputs.
AWS Service Integration
Full Ansible collection for AWS with native integrations including EC2, CloudFormation, VPC, ALB, AMI, Security Groups, key pairs, EFS, EBS, S3, RDS, Lambda, and AWS Secrets Manager
Multi-Environment Deployment
Capability to deploy and run on AWS cloud with extension to private clouds, on-premise datacenters, edge locations, and hybrid cloud environments
Workflow Orchestration
End-to-end automation platform for configuring systems, deploying software, and orchestrating advanced workflows across enterprise infrastructure
OpenShift Compatibility
Installation support via operator on Red Hat OpenShift on AWS (ROSA) or OpenShift running directly on AWS infrastructure
Included RHEL Subscriptions
Offering includes up to 10 Red Hat Enterprise Linux subscriptions for deploying Ansible Automation Platform
Standard contract
No
No
Customer reviews
Zvonimir Burić
Infrastructure as code has streamlined multi-account cloud provisioning and consistent deployments
Reviewed on Aug 26, 2026
Review from a verified AWS customer
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been using Pulumi for six years.
What other advice do I have?
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.
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)
Thiago Chaves
Infrastructure as code has streamlined environment management and reduced operational overhead
Reviewed on Aug 24, 2026
Review from a verified AWS customer
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been using Pulumi Enterprise for four years.
What do I think about the stability of the solution?
Pulumi Enterprise is stable because since we started working with it, we haven't had any issue with Pulumi's cloud going down.
What do I think about the scalability of the solution?
In my experience, the scalability of Pulumi Enterprise is very good and it suits us perfectly.
How are customer service and support?
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.
Which solution did I use previously and why did I switch?
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.
What was our ROI?
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.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup costs, and licensing was very good for the team we had. For the team size, it suited us perfectly.
What other advice do I have?
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.
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)
reviewer2891127
Automated tests have increased confidence and simplify managing Azure infrastructure changes
Reviewed on Aug 24, 2026
Review provided by PeerSpot
What is our primary use case?
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.
How has it helped my organization?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I've been using Pulumi Enterprise for around nine or 10 months.
What do I think about the stability of the solution?
Pulumi Enterprise is stable.
What do I think about the scalability of the solution?
We find Pulumi Enterprise very scalable.
How are customer service and support?
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.
Which solution did I use previously and why did I switch?
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.
How was the initial setup?
There were no issues with the initial setup that I could think of.
What about the implementation team?
I wasn't too involved with that part of the process.
What was our ROI?
The ROI was quite good, actually.
Which other solutions did I evaluate?
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.
What other advice do I have?
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.
reviewer2890914
Infrastructure as code has improved Azure deployments but still needs faster updates and value
Reviewed on Aug 22, 2026
Review provided by PeerSpot
What is our primary use case?
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.
How has it helped my organization?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been using Pulumi Enterprise for over five years.
What do I think about the stability of the solution?
Pulumi Enterprise is stable in my experience.
What do I think about the scalability of the solution?
Pulumi Enterprise is scalable for my team's needs as it has done what is needed.
Which solution did I use previously and why did I switch?
I did not previously use a different solution.
Which other solutions did I evaluate?
My advice to others looking into using Pulumi Enterprise is to consider Terraform first.
What other advice do I have?
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.
Harsh-Kumar
Automating infrastructure with familiar languages has streamlined deployments and collaboration
Reviewed on Aug 21, 2026
Review from a verified AWS customer
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
At my recent company, I was introduced to Pulumi Enterprise, and I have been using it for almost eight months.
What other advice do I have?
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.
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)