---
title: Pricing
description: Pulumi IaC and Pulumi ESC are available in various editions and are free to individuals
url: /pricing/
---
Pulumi IaC and Pulumi ESC are available in various editions and are free to individuals


## Individual

Free forever for individuals.

**$0 forever** (No credit card required)

Includes:
- 1 user
- IaC state management
- Unlimited projects, stacks, and environments
- Unlimited updates and history
- Up to 500 workflow minutes
- Pulumi Neo with 5M free tokens/month

## Team

Everything you need to get started.

**$40 /month base** — **Includes 40 Credits** (Up to 500 resources, additional usage billed on demand)

Everything in **Individual**, plus:
- Up to 10 users
- Secure collaboration and CI/CD
- Neo code reviews and Slack integration
- Resource search
- OIDC and org access tokens
- Webhooks
- Automatic secrets rotation
- Community support

## Enterprise

Security and collaboration for large teams.

**$400 /month base** — **Includes 400 Credits** (Up to 2,000 resources, additional usage billed on demand)

Everything in **Team**, plus:
- Unlimited users
- SAML/SSO and RBAC
- Neo scheduled tasks
- Internal developer platform (IDP)
- Audit logs
- Drift detection and remediation
- Time-to-live stacks
- Customer-managed keys
- Priority feature requests
- 12x5 Enterprise Support available

## Business Critical

Advanced governance, policies, and controls.

**Custom** (Volume discounts and invoicing)

Everything in **Enterprise**, plus:
- [Self-hosting available](/product/self-hosted)
- Built-in compliance (NIST, PCI, and more)
- Automatic group & user sync (SCIM)
- Audit logs export
- Volume pricing and invoicing
- Private Slack and Professional Services
- 24x7 Enterprise Support available

## Edition comparison


### Infrastructure as Code

| | Individual | Team | Enterprise | Business Critical |
|---|---|---|---|---|
| On-demand resource price | Free | $0.00025/hour ($0.1825/month) | Starting at $0.0005/hour ($0.365/month) | Custom |
| Commitment pricing | — | — | ✓ | ✓ |
| Self-hosting | — | — | — | ✓ |
| Updates | Unlimited | Unlimited | Unlimited | Unlimited |
| Concurrent stack updates | 1 | 5 | Unlimited | Unlimited |
| Restore deleted stacks | — | — | ✓ | ✓ |
| Update history | ✓ | ✓ | ✓ | ✓ |
| REST API | ✓ | ✓ | ✓ | ✓ |
| Automation API | ✓ | ✓ | ✓ | ✓ |
| Pulumi-service provider | ✓ | ✓ | ✓ | ✓ |

### Deployments & Workflows

| | Individual | Team | Enterprise | Business Critical |
|---|---|---|---|---|
| CI/CD integrations | Many | Many | Customized for you | Customized for you |
| Drift detection | — | — | ✓ | ✓ |
| Time-to-live stacks | — | — | ✓ | ✓ |
| Scheduled deployments | — | — | ✓ | ✓ |
| GitHub Enterprise Server support | — | — | — | ✓ |
| Webhooks | — | ✓ | ✓ | ✓ |

### Secrets & Configuration

| | Individual | Team | Enterprise | Business Critical |
|---|---|---|---|---|
| On-demand secret price | 25 free | $0.000685/hour ($0.50/month) | $0.001/hour ($0.75/month) | Custom |
| Price per plaintext config | Free | Free | Free | Free |
| Price per 10K API calls | 10K free | $0.10 | $0.10 | $0.10 |
| Commitment pricing | — | — | ✓ | ✓ |
| Self-hosting | — | — | — | Available |
| Max # of secrets | 25 | Unlimited | Unlimited | Unlimited |
| Max # of API calls | 10K / month | Unlimited | Unlimited | Unlimited |
| Version history | — | ✓ | ✓ | ✓ |
| Version tags and import by tags | — | ✓ | ✓ | ✓ |
| Dynamic credentials | ✓ | ✓ | ✓ | ✓ |
| Dynamic secrets | ✓ | ✓ | ✓ | ✓ |
| Rotated secrets | ✓ | ✓ | ✓ | ✓ |
| Database secrets rotation | ✓ | ✓ | ✓ | ✓ |
| Database secrets rotation in private networks | — | — | ✓ | ✓ |
| Customer-managed keys | — | — | ✓ | ✓ |
| Integrations - sync | ✓ | ✓ | ✓ | ✓ |
| Multi-language SDKs | ✓ | ✓ | ✓ | ✓ |

### Insights & Governance

| | Individual | Team | Enterprise | Business Critical |
|---|---|---|---|---|
| On-demand resource price | Free | $0.000025/hour ($0.0185/month) | Starting at $0.00005/hour ($0.0365/month) | Custom |
| Workflow cost per minute / included per month | 500 free | $0.01 | $0.01 / Custom | $0.01 / Custom |
| Resource search | — | ✓ | ✓ | ✓ |
| Primary accounts | 1 | 1 | 10 / Custom | Custom |
| Data export | — | — | ✓ | ✓ |
| Property search | — | ✓ | ✓ | ✓ |
| Policy enforcement | Manual | [Organization-managed](/docs/insights/policy/#pulumi-cloud-integration) | [Organization-managed](/docs/insights/policy/get-started/#enforcing-a-policy-pack) | [Organization-managed](/docs/insights/policy/get-started/#enforcing-a-policy-pack) |
| Preventative policies | Manual | ✓ | ✓ | ✓ |
| Audit policies | — | ✓ | ✓ | ✓ |
| Pre-built policy packs | — | Pulumi Best Practices | Pulumi Best Practices | Pulumi Best Practices, CIS, NIST, HITRUST, PCI DSS |
| Custom policy packs | — | Up to 25 policies (1 pack limit) | Up to 100 policies (3 pack limit) | Unlimited |
| Enforcement Modes | — | Advisory & Mandatory | Advisory & Mandatory | Advisory, Mandatory & Remediation |

### Internal Developer Platform

| | Individual | Team | Enterprise | Business Critical |
|---|---|---|---|---|
| Developer portal | Host public templates | Host public templates | Host private templates | Host private templates |

### Infrastructure AI

| | Individual | Team | Enterprise | Business Critical |
|---|---|---|---|---|
| Pulumi Neo | 5M tokens/month (free) | $3/M tokens | $3/M tokens | $3/M tokens |
| Neo in the CLI | ✓ | ✓ | ✓ | ✓ |
| MCP & CLI Integrations | ✓ | ✓ | ✓ | ✓ |
| Neo code reviews | — | ✓ | ✓ | ✓ |
| Slack integration | — | ✓ | ✓ | ✓ |
| Scheduled tasks | — | — | ✓ | ✓ |

### Administration

| | Individual | Team | Enterprise | Business Critical |
|---|---|---|---|---|
| Members | 1 | Up to 10 | Unlimited | Unlimited |
| Admins | — | 1 | Unlimited | Unlimited |
| Organizations | — | 1 | Multiple supported | Multiple supported |
| Identity providers | GitHub, GitLab, Atlassian | GitHub, GitLab, Atlassian | GitHub, GitLab, Atlassian, SAML/SSO | GitHub, GitLab, Atlassian, SAML/SSO |
| SAML/SSO | — | — | Many | Many |
| SCIM integration | — | — | — | ✓ |
| OIDC support | ✓ | ✓ | ✓ | ✓ |
| Create and manage teams | — | — | ✓ | ✓ |
| Role-based access control (RBAC) | — | — | ✓ | ✓ |
| Custom roles | — | — | Up to 25 | Unlimited |
| Tag-based access control | — | — | ✓ | ✓ |
| Assign custom roles to users and teams | — | — | ✓ | ✓ |
| Organization and team access tokens | — | ✓ | ✓ | ✓ |
| Audit logs | — | — | ✓ | ✓ |
| Automated log export to S3 | — | — | — | ✓ |

### Support

| | Individual | Team | Enterprise | Business Critical |
|---|---|---|---|---|
| Support | — | — | Available, 12x5 / 24x7 support | Available, 12x5 / 24x7 support |
| Normal ticket SLA | — | — | Available, 1 or 5 business days | Available, 1 or 5 business days |
| Urgent ticket SLA | — | — | Available, 4 hours to 2 business days | Available, 4 hours to 2 business days |
| Private Slack channel | — | — | Available | Available |
| Community Slack | ✓ | ✓ | ✓ | ✓ |
| Professional services | — | — | Available | Available |
| Onboarding and training | — | — | Available | Available |
| Terraform Migration | — | — | Available | Available |
| SLA | — | — | Available | Available |

## Frequently asked questions

### Pricing

**Do I pay as I go, or prepaid up-front?**

If you self-serve by entering 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. If your usage exceeds your Pulumi Credit pool, you will be billed in arrears for your usage at the end of the monthly term.

If you prefer to pay annually, you can [contact sales](/contact/?form=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.

**What are Pulumi Credits?**

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 either through a monthly up-front fee or 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.

**How are IaC resources billed?**

IaC resources are billed hourly at the rate of $0.00025 for Team ($0.1825 per resource per month) and starting at $0.0005 for Enterprise ($0.365 per resource per month). This is the cost of managing an IaC resource for a full hour.

Enterprise plans receive volume discounts, so that the more resources you consume, the lower the incremental rate. This is true of self-serve pay-as-you-go plans, although prepaid plans offer more considerable discounts.

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](/docs/concepts/resources) (e.g., an Amazon S3 bucket), [component resources](/docs/iac/concepts/components) which are groupings of resources (e.g., an Amazon EKS cluster), and [stacks](/docs/iac/concepts/stacks) which contain resources (e.g., dev, test, prod stacks).

**What can I do with 500 IaC resources per month?**

The Team 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 Enterprise plan includes up to 2,000 resources.

**How do I find out how many IaC resources I have?**

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

- <u>If you are using Pulumi Cloud</u>: Navigate to the dashboard and review the resource graph titled “Resource Count over Time.”

- <u>If using Pulumi with a DIY backend</u>: 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.

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

**What are some examples of how many IaC resources are needed for my use case?**

[**Serverless API with Amazon API Gateway and AWS Lambda**](https://github.com/pulumi/examples/tree/master/aws-ts-apigatewayv2-http-api)
(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**](https://github.com/pulumi/examples/tree/master/aws-py-eks)
(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**](https://github.com/pulumi/examples/tree/master/aws-py-wordpress-fargate-rds)
(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.

**How are ESC secrets billed?**

ESC secrets are billed hourly at the rate of $0.000685 for Team ($0.50 per secret per month) and $0.001 for Enterprise ($0.75 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 Pulumi Cloud Team 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.

**How are ESC secrets API calls metered?**

You pay $0 for the first free 10K API calls / month to the [ReadOpen API](/docs/pulumi-cloud/reference/environments/#read-open-environment) endpoint. Once you hit 10,000 API calls, you are metered at $0.1 for 10K API calls. If you use 5K API calls you will be billed $0.05.

API usage includes any calls from the [CLI](/docs/iac/cli/commands/pulumi_env/), [SDK](/docs/esc/development/languages-sdks/), [Pulumi-service provider](/registry/packages/pulumiservice/api-docs/environment/), direct [REST API](/docs/pulumi-cloud/reference/environments/) call that hits the ReadOpen API endpoint

**What are workflow minutes?**

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

**Can I prepay for resources, secrets, and secrets API calls?**

Yes, you can! Please contact us to discuss the Enterprise and Business Critical editions, which include volume pricing for paying in advance.

**What are Neo tokens?**

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.

**Can I manage Neo usage for my organization?**

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.

### Product

**What are Pulumi open source and Pulumi Cloud?**

Pulumi's Infrastructure as Code CLI and SDK are an open-source project that is supported by an active community. [Pulumi Cloud](/product/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.

**Can I use Pulumi for free?**

Yes! There are three ways to use Pulumi for free.

First, Pulumi Cloud is free to use, now and forever, for individuals. You get all of the convenience of automatic state management, unlimited updates, and many other great features without needing to pay anything at all for it.

Second, Pulumi is an [open-source project](https://github.com/pulumi/pulumi). You can [run Pulumi entirely offline](/docs/iac/concepts/state-and-backends#using-a-diy-backend) 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.

Finally, we offer a 14-day free trial for the Business Critical edition. Once the trial is over, you can continue to use the Business Critical Edition by chatting with sales or changing to Team or Enterprise Edition. After your trial expires, no data will be lost, and there is a grace period.

**What is an organization? What are projects and stacks?**

The Individual 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 Team Edition is designed for teams to collaborate on shared infrastructure projects. The Enterprise Edition offers more sophisticated organization management facilities, including RBAC for advanced policy controls.

Pulumi [projects](/docs/concepts/projects/) and [stacks](/docs/concepts/stack/) 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.

**How do I get started?**

Follow the [Getting Started guide](/docs/quickstart/), which walks you through creating and deploying your first Pulumi project.

**How do I move from Starter or Pro to the new Team Edition?**

We recommend moving from the old SKUs to get access to our latest capabilities like Pulumi Deployments, Insights and Neo. [Contact us](/contact/?form=sales) to move to the new Team Edition.

**Is Pulumi SOC 2 compliant?**

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

**Can I host Pulumi Cloud in my cloud or datacenter?**

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 Business Critical Edition. You can [request a Proof of Concept (PoC)](/product/self-hosted/#self-hosted-trial) to get started.

**How do I convince my boss?**

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](/contact/?form=sales).

**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](/case-studies/bmw/) and Fenergo can now release new features faster by empowering their developers to deploy cloud infrastructure easily.
>- [Snowflake migrated to](/case-studies/snowflake/) Kubernetes across multiple clouds in three months.
>- [Mercedes-Benz](/case-studies/mercedes-benz/) Research & Development North America improved collaboration between its infrastructure and application development teams.
>- [Skai](/blog/kenshoo-migrates-to-aws-with-pulumi/) managed a complex public cloud migration project.
>- [Wiz](/case-studies/wiz/), [Supabase](/case-studies/supabase/), and [Lemonade](/case-studies/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}

### Billing and Support

**How can I keep track of my usage?**

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

**When will I be billed for using Team or Enterprise Edition?**

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.

**What payment options do you accept?**

For the Pulumi Team Edition, you can pay with a credit card (we use Stripe for processing). Pulumi Enterprise Edition offers additional payment options. Please [contact us](/contact/?form=sales) for those options.

**What if I have billing or account issues?**

For any billing or related issues, please [contact us](/contact/).

**What if I am not satisfied with my Pulumi purchase?**

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

**How do I get support for Pulumi?**

12 x 5, 24 x 7 support, professional and advising services, and private Slack channel are available to purchase in the Enterprise and Business Critical editions of Pulumi Cloud. [Contact us](/contact/?form=sales) if you need help or have any questions.

**Does Pulumi charge sales tax?**

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.