Pulumi review

Pulumi is an infrastructure-as-code (IaC) platform for defining and managing cloud infrastructure. Its main distinction is that teams can write infrastructure in familiar programming languages rather than only in a purpose-built configuration language. The product material lists TypeScript, Python, Go, .NET, Java, YAML, and HCL as supported options.

That flexibility can support reusable infrastructure components. Teams can package and share components through package managers such as npm, PyPI, and NuGet. Pulumi’s platform also covers secrets and configuration, policy and compliance, audit trails, and self-service infrastructure. The product material describes Pulumi Neo as an AI infrastructure agent that uses code and organizational context for workflows. It also lists resource discovery through natural-language queries for managed and unmanaged cloud resources.

Pulumi is therefore more than a language choice: it combines infrastructure authoring with governance and management features. YAML is supported, so teams do not have to standardize on a general-purpose programming language to use it.

Pulumi makes the strongest case when infrastructure needs logic that is awkward to express in a declarative configuration format. Teams can use familiar programming-language features and build reusable components, rather than forcing every use case into a fixed configuration pattern. One commenter on Reddit said adopting Pulumi improved productivity for both infrastructure and application developers; other commenters preferred its software-development approach to DSL configuration.

The platform also brings several management features into the same product. The listed capabilities include central secrets management, connections to external secret stores, short-lived credentials through OIDC, policy as code, audit trails, and compliance tracking. Pulumi Neo and natural-language resource discovery extend that scope beyond authoring infrastructure, although the product material does not quantify their results.

There is a free plan for individuals and open-source projects. The pricing page lists unlimited projects, stacks, and environments on that plan, alongside 1 user, up to 500 workflow minutes, 25 secrets, and 10,000 API calls per month. For a small project within those caps, that gives a team a way to start without a paid subscription.

Programmability comes with trade-offs. Reddit commenters warn that infrastructure written in a general-purpose language can be over-engineered, harder for the next hire to maintain, and subject to the security risks of a larger dependency tree. Others argue that a simpler declarative tool is easier to standardize. That is not proof Pulumi will cause those problems, but it is a real adoption cost to weigh against the flexibility.

The paid plans also have firm resource limits. According to the pricing page, Essentials is $40 per month and includes 40 Pulumi Credits, up to 500 managed resources, 5 concurrent stack updates, and 1 primary cloud account. Pro is $400 per month, with 400 credits, up to 2,000 managed resources, and 10 primary cloud accounts. Additional usage draws from credits at $1 per credit; excess usage is billed in arrears. Managed resources cost $0.00025 per hour on Essentials and start at $0.0005 per hour on Pro. Workflow minutes cost $0.01 each on both plans. Essentials and Pro bill monthly in advance; annual commitments are available only for Pro and Enterprise, with contract pricing. Enterprise pricing is not published.

Pulumi’s Free plan costs $0 and includes one user, up to 500 workflow minutes, 25 secrets, 10,000 API calls per month, and unlimited projects, stacks, and environments. Essentials is $40 per month; Pro is $400 per month—a tenfold jump. Essentials includes 40 Pulumi Credits, up to 500 managed resources, and one primary cloud account. Pro includes 400 credits, up to 2,000 managed resources, and 10 primary cloud accounts. Both paid plans bill monthly in advance. Annual commitments are available only for Pro and Enterprise, with contract pricing; Enterprise pricing is not published.

Watch the usage charges: additional usage draws from credits at $1 per credit, with excess billed in arrears. Workflow minutes cost $0.01 each on Essentials and Pro. Managed resources, secrets, discovered resources, and Pulumi Neo tokens also have separate charges. Support is extra: Standard is $625 per month, and Bronze is $1,250 per month; higher tiers require contacting sales. Check expected usage before comparing the $40 and $400 sticker prices.

Switching to Pulumi means defining infrastructure with one of its supported languages—such as TypeScript, Python, Go, .NET, Java, or YAML—or HCL. That flexibility can suit teams with dynamic infrastructure needs, but it is a poor fit if you want simple declarative IaC or a common IaC standard. Budget time to map existing definitions and workflows before committing; the published materials do not publish migration steps, import limits, or state-export details.

The product information describes managed infrastructure, secrets, policies, and audit trails, but does not specify how to export state or move those functions to another platform. Ask Pulumi about portability and test your exit path before putting production workflows behind the platform. Reddit reports about why customers leave were not included in the published material, so we can’t attribute a list of reasons to users. The clearest switching risk in the available information is cost: usage-based charges can sit on top of plan fees, and Essentials and Pro bill monthly in advance.