Plans for teams of all sizes

The Essentials, Pro, and Enterprise editions are available month to month with a credit card. You will be charged an up-front fee at the beginning of each monthly term. The up-front fee will create a pool of Pulumi Credits. Unused monthly credits expire at the end of each monthly term. If your usage exceeds your Pulumi Credit pool, you will be billed in arrears for your usage at the end of the monthly term.

Annual commitment pricing is available on Pro and Enterprise only. Contact sales to receive a discount for a committed amount of usage paid up-front. If you subsequently consume all up-front purchased usage, you will be billed in arrears as you go beyond that amount of usage. The details are specified in your contract.

Pulumi Credits are the single currency for Pulumi Cloud. One Pulumi Credit costs $1 USD, and you can pre-purchase Pulumi Credits as needed to cover expected usage through a monthly up-front fee or, on Pro and Enterprise, an annual agreement. All usage of Pulumi services will draw from the pool of Pulumi Credits at the rates above or as listed on your order form. Once the pool of Pulumi Credits is exhausted, you'll be billed in arrears for additional use at the rates above or as listed on your order form.

IaC resources are billed hourly at the rate of $0.00025 for Essentials ($0.1825 per resource per month) and starting at $0.0005 for Pro ($0.365 per resource per month). These hourly rates cover managing a resource for a full hour.

Pro receives volume discounts, so the incremental rate decreases as resource use increases.

Enterprise starts at $2,000/month, with 2,000 Pulumi Credits covering up to 4,750 managed resources. Additional IaC resources start at $0.00075 per resource-hour ($0.5475 per resource per month). Enterprise is available month to month, or you can contact sales for contract pricing.

For billing purposes, a partial resource hour used is billed as a full hour and we count any resource that's declared in a Pulumi program. This includes provider resources (e.g., an Amazon S3 bucket), component resources which are groupings of resources (e.g., an Amazon EKS cluster), and stacks which contain resources (e.g., dev, test, prod stacks).

The Essentials edition includes up to 500 IaC resources to get started with.

You could manage 500 EKS clusters or EC2 instances for a month using this amount. As another example, you could manage something more complex like a production Amazon EKS cluster with associated IAM roles, VPC, subnets, gateway route tables, and a small microservice deployed into the cluster.

This is more than enough to get started with production workloads. The Pro edition includes up to 2,000 resources.

There are several ways you can estimate the number of resources you have managed with Pulumi.

• If you are using Pulumi Cloud: Navigate to the dashboard and review the resource graph titled “Resource Count over Time.”

• If using Pulumi with a DIY backend: Export your stack state and count the number of lines with a universal resource name (URN). You can pipe the state through a grep command for "urn" to estimate the number of resources.

• If you haven't deployed anything with Pulumi: See the previous FAQ for a few examples of applications and their number of resources.

Serverless API with Amazon API Gateway and AWS Lambda (Estimated resources: 9)

This scenario is a stack with an Amazon API Gateway, an AWS Lambda event handler, and associated IAM roles.

Amazon EKS running in a VPC (Estimated resources: 20)

This scenario is a stack with an Amazon VPC (including subnets, internet gateway, security groups, and route table), Amazon EKS cluster and node group, and associated IAM roles.

Amazon ECS cluster and RDS backend running in a VPC (Estimated resources: 24)

This scenario is a stack with an Amazon VPC (including subnets, security groups, and route table associations), Amazon ECS (including cluster and service, load balancer resources, and IAM resources), and Amazon RDS (including RDS instance and subnet group). Each group of resources (VPC, ECS, RDS) is represented by a component resource.

ESC secrets are billed hourly at the rate of $0.000685 for Essentials ($0.50 per secret per month), $0.001 for Pro ($0.75 per secret per month), and $0.00137 for Enterprise ($1.00 per secret per month). This is the cost of managing an ESC secret for a full hour.

For example, if you have your secrets stored for 4 days on the Pulumi Cloud Essentials edition, the price you pay would be 4 x 24 x 0.5 / 730 = $0.0657

Secrets include both static secrets and dynamic secrets/credentials. When using the Pulumi ESC Document Editor, each definition of fn::secret:* and fn::open::* (except Pulumi-stacks provider) is counted as a secret. The number of secrets only from the latest environment revision is counted towards your billing.

You pay $0 for the first free 10K API calls / month to the ReadOpen API endpoint. Once you hit 10,000 API calls, you are metered at $0.1 for 10K API calls. For example, 15,000 API calls in a month include 10,000 free calls and 5,000 billable calls, costing $0.05.

API usage includes any calls from the CLI, SDK, Pulumi Cloud provider, direct REST API call that hits the ReadOpen API endpoint

Workflow minutes represent the total time used across both Discovery and Deployments. All usage draws from a single, shared pool of minutes. For Discovery, workflow minutes measure the time spent on discovery and policy execution. Deployments also consume workflow minutes by measuring the duration of each deployment process.

Customers on the self-service Essentials and Pro editions can buy discounted credit top-ups in Pulumi Cloud. Self-service top-ups are not yet available for contracted credit pools. Annual commitments are available on Pro and Enterprise only; contact sales to discuss commitment pricing.

Neo tokens are the metering method for Neo-powered features (Neo tasks, pull-request annotations, and natural-language search) and cost $3 per million tokens. The volume of tokens used by any given activity varies with the number, complexity, and duration of Neo activities.

Yes. The Enterprise edition includes bring your own key (BYOK) for Neo. Organizations on the legacy Business Critical edition also have access. Neo currently supports Anthropic's Claude models. Your model provider bills you directly for BYOK model usage, and Pulumi does not charge Neo tokens for those requests. Other Pulumi usage remains subject to your edition's pricing and contract. See Bring your own model provider for setup instructions.

Neo features can be managed in the Pulumi Cloud dashboard under Settings → Neo Settings. Neo integration with your version control system is located under Management → Version Control.

Pulumi's Infrastructure as Code CLI and SDK are an open-source project that is supported by an active community. Pulumi Cloud is a managed service for the open source CLI and SDK. It tracks your infrastructure’s state and coordinates updates with the CLI, which creates or updates resources to reach your infrastructure’s desired state. It also manages secrets, supports SAML SSO, integrates with CI/CD pipelines, enforces compliance rules, and much more.

You're not required to use Pulumi Cloud. You can use any cloud or on-premises storage to build and run your own backend.

Yes. There are two ways to use Pulumi for free.

First, the Pulumi Cloud Free edition costs nothing and supports one user. It includes automatic state management, Pulumi Deployments, basic Pulumi ESC, unlimited projects and stacks, and unlimited updates and history. It does not limit the number of managed resources. It does not include Pulumi Neo, Resource Search, or Property Search.

Second, Pulumi is an open-source project. You can run Pulumi entirely offline without the online service's features, and manage state yourself, instead of using the online service. There are no restrictions — it's all there in the open for you to use freely as you'd like.

The Free edition is great for single users with private projects. However, if you are working within a team, you'll typically want to share your projects, for which you need to create an organization. The Essentials edition is designed for teams to collaborate on shared infrastructure projects. The Pro edition offers more sophisticated organization management facilities, including RBAC for advanced policy controls.

Pulumi projects and stacks are a way to organize Pulumi code. You can consider a Pulumi project to be analogous to a GitHub repo: a single place for code — and a stack to be an instance of that code which has a separate configuration. For instance, a single project may have multiple stacks for dev, test, prod, or perhaps for different cloud configurations (e.g., geographic region) or developer environments.

Follow the Getting Started guide, which walks you through creating and deploying your first Pulumi project.

These legacy plans are separate from the current Pro edition. We recommend moving off them to get access to our latest capabilities like Pulumi Deployments, Discovery, and Neo. Contact us to move to a current edition.

Yes, Pulumi has completed the SOC 2 Type 2 compliance process. Pulumi is committed to operational excellence for our customers.

Yes, we offer a self-hosted Pulumi Cloud for companies that have specific data control requirements and want to maintain complete control over hosting Pulumi Cloud. This option is available in the Enterprise edition. You can request a Proof of Concept (PoC) to get started.

Do you want to use Pulumi in your organization, but aren't sure how to bring it up with your boss? We've created a sample email to help you explain its benefits. Feel free to use the full letter or pieces of it. We are always happy to meet to learn more about your needs and explain these benefits in person — just contact us.

Sample Email

Dear {Name},

I'd like to propose that we use Pulumi for our cloud infrastructure needs. I've researched the top infrastructure as code platforms, and Pulumi stands out because of its maturity, strong open source community, support for many clouds, and mix of productivity and enterprise controls, meaning it works great for developers and infrastructure teams alike.

I discovered that Pulumi's community is over 10,000 people and growing, and their customer base includes a diverse array of companies, from startups to some of the largest Fortune 500 and Global 2000 organizations. The top four reasons people are choosing Pulumi are 1) it tames cloud complexity and reduces infrastructure risks, 2) it lets teams use software engineering best practices with infrastructure, 3) it helps teams adopt modern cloud architectures, and 4) it increases collaboration between infrastructure teams, developers, and security engineers.

Here are some examples of their customers to give you an idea of who is using it and why:

• BMW and Fenergo can now release new features faster by empowering their developers to deploy cloud infrastructure easily.
• Snowflake migrated to Kubernetes across multiple clouds in three months.
• Mercedes-Benz Research & Development North America improved collaboration between its infrastructure and application development teams.
• Skai managed a complex public cloud migration project.
• Wiz, Supabase, and Lemonade created innovative engineering cultures.

Pulumi is open source and has a SaaS product that helps organizations like ours manage infrastructure with advanced security and policies. Because it's a SaaS, we can start small and grow as our success with the product grows.

You can learn more on the Pulumi website or view a short introduction video.

I have many ideas on how Pulumi would deliver immediate value to our team. Should I write a more detailed proposal and share it with you or other members of the team for feedback? The Pulumi team has also offered to have a meeting with us to learn more about our use cases, and discuss potential ways we can work together. Should I set that up?

Thanks,

{Your Name}

You can keep track of current usage and upcoming charges by navigating to Settings and then Billing & Usage in the Pulumi Cloud console.

In addition to your monthly up-front fee, you will be billed for the previous month’s on-demand usage on the first day of each month.

Self-service Essentials, Pro, and Enterprise subscriptions use a credit card. Annual contracts are available on Pro and Enterprise only. Contact sales for contract payment options.

For any billing or related issues, please contact us.

If you're not satisfied with Pulumi, we offer a 14-day money-back guarantee, no questions asked. Contact us.

Every edition includes access to the support agent and ticket submission. Essentials, Pro, and Enterprise customers can purchase Standard or Bronze support. Standard is included with Enterprise contracts of at least one year. Self-hosted customers require Platinum support. Compare support plans for prices, coverage, and response objectives.

You may be charged a sales tax in addition to your usage fees in certain jurisdictions. It will be a separate line item on your bill.