Pulumi platform teams
Use an agent that understands existing stacks, state, policies, configuration, and organizational permissions.
Independent tool overview
Pulumi AI at a glance
Pulumi AI has evolved into Pulumi Neo, a generally available infrastructure agent that can investigate, generate and review IaC, run previews, propose pull requests, and perform approved cloud work using Pulumi's organizational context and policy controls.
Visit the official Pulumi AI site ↗
- Current product
- Pulumi Neo
- Earlier positioning
- Pulumi AI code generation
- Availability
- Generally available to Pulumi users
- Underlying models
- Anthropic Claude via Amazon Bedrock
- Primary outputs
- Answers, investigations, previews, reviews, and IaC pull requests
- Free allowance
- 5M Neo tokens per month on Individual
- Paid token rate
- $3 per 1M Neo tokens
Overview
What Pulumi AI is
Pulumi's earlier Pulumi AI experience focused on generating infrastructure-as-code from natural-language prompts. The current product is Pulumi Neo, a broader infrastructure agent that can reason over live Pulumi Cloud context and carry work from investigation through a reviewed change.
Neo can answer questions about stacks and resources, diagnose failures, generate Pulumi programs, review infrastructure pull requests, run Pulumi previews, identify policy violations, recommend cost changes, and open a pull request with the proposed code and resource diff.
The agent is powered by Anthropic's Claude family through Amazon Bedrock and includes Pulumi's Agent Skills. Its differentiator is the surrounding context: Pulumi state, stack relationships, discovered resources, policies, permissions, configuration, and connected operational tools.
Neo is available through Pulumi Cloud, the pulumi neo CLI, supported editor agent panels, Slack, pull requests, Pulumi's MCP server, and handoffs from agents such as Claude Code, Codex, and Cursor. External MCP and CLI integrations can add context from services and cloud control planes.
Infrastructure automation has a high blast radius. Neo supports read-only work, Plan Mode, per-task approvals, previews, policy checks, and pull-request review, but organizations still need least-privilege identities, branch protection, staged deployments, independent validation, and incident recovery.
Use cases
Who Pulumi AI is best for
The strongest fit depends on the job you need the product to complete, not the size of its feature list.
Infrastructure investigations
Ask why a deployment failed, what depends on a resource, what changed, or where a policy violation is occurring.
Governed infrastructure changes
Turn a requested outcome into IaC, a preview, policy results, and a pull request that follows normal review controls.
Cloud cost and drift work
Identify underused resources, explain unexpected state, and propose reviewed remediations.
Infrastructure code review
Review pull requests against both the code diff and the context Pulumi Cloud has about real infrastructure.
Scheduled platform operations
Automate repeatable investigations and remediations on eligible Pulumi Cloud plans.
Capabilities
Core Pulumi AI features
Infrastructure-aware answers
Uses Pulumi Cloud state and organizational context to answer questions about resources, stacks, dependencies, failures, and potential changes.
Infrastructure-as-code generation
Creates Pulumi programs in TypeScript, Python, Go, and other supported Pulumi languages from a described outcome.
Pull requests and previews
Can modify IaC, run pulumi preview, summarize affected resources and policy findings, and open a pull request for review.
Policy and compliance context
Works within Pulumi governance and can detect or help remediate misconfigurations and policy violations.
Plan, approval, and read-only modes
Lets teams require an agreed plan, gate selected steps, or remove change capability for investigative use.
Code review
Reviews infrastructure pull requests automatically and accepts targeted requests through the @pulumi-neo mention.
Cost and operational analysis
Surfaces expensive or underused resources and can investigate deployment, configuration, and runtime issues.
Multiple working surfaces
Runs in Pulumi Cloud, the CLI, supported editors through ACP, Slack, pull requests, and other agents through MCP or skills.
External integrations
Can use scoped MCP and CLI connections for systems such as Datadog, PagerDuty, Linear, Atlassian, AWS, Azure, Google Cloud, and Kubernetes.
Scheduled tasks
Eligible plans can run autonomous infrastructure investigations or maintenance on a schedule with organizational controls.
Context graph
Neo uses Pulumi's agent-oriented context layer to connect managed state, stack dependencies, and discovered resources where available.
Process
How the Pulumi AI workflow works
Step 1
Connect the infrastructure context
Confirm the right Pulumi organization, stacks, repositories, cloud accounts, discovery sources, policies, and integrations are visible.
Step 2
Create a least-privilege identity
Give the user and agent only the stack, repository, environment, and cloud permissions required for the intended work.
Step 3
Start read-only
Ask Neo to explain the current state, dependencies, likely failure, cost issue, or policy finding before authorizing changes.
Step 4
Agree on a plan
Use Plan Mode to define scope, affected resources, expected diff, rollback, validation, and approval boundaries.
Step 5
Generate IaC, not console drift
Prefer a reviewed code change that preserves infrastructure history and repeatability over an undocumented manual mutation.
Step 6
Run a preview and policies
Inspect creates, updates, replacements, deletes, provider changes, costs, and mandatory-policy failures before deployment.
Step 7
Review the pull request
Require platform ownership, branch protection, security review, secret scanning, tests, and explicit approval for destructive changes.
Step 8
Deploy progressively
Use lower-risk environments, limited regions or accounts, deployment approvals, monitoring, and a tested rollback path.
Step 9
Audit the outcome
Compare the applied update with the preview, confirm service health and policy state, record the decision, and monitor drift.
Cost
Pulumi AI pricing and free plan
Pulumi Neo is metered within Pulumi Cloud. Individual is free and includes 5 million Neo tokens each month. Paid plans charge $3 per million Neo tokens, alongside the plan's base fee and other Pulumi Cloud resource, secret, discovery, and workflow usage. Team starts at $40 per month, Enterprise at $400, and Business Critical is custom.
Individual
$0
Free Pulumi Cloud plan for one individual with a monthly Neo allowance.
- Five million Neo tokens per month
- One user
- Unlimited projects, stacks, environments, updates, and history
- Up to 500 workflow minutes
Team
$40/month base
Collaboration plan for up to 10 users with 40 included Credits and usage-based overages.
- Neo usage is $3 per million tokens
- Neo code reviews and Slack integration
- Up to 500 resources
- OIDC, organization access tokens, webhooks, and community support
Enterprise
$400/month base
Larger organization plan with 400 included Credits, broader administration, and scheduled Neo tasks.
- Neo usage is $3 per million tokens
- Up to 2,000 resources and unlimited users
- SAML/SSO, RBAC, audit logs, and customer-managed keys
- Drift detection, remediation, and priority features
Business Critical
Custom
Advanced governance, compliance, policy, support, and commercial terms for regulated or high-control environments.
- Volume discounts and invoicing
- Expanded policy packs and enforcement options
- Advanced identity, governance, and support
- Confirm Neo, Context API, and self-hosting requirements with Pulumi
Pricing checked . Check current pricing at the source ↗
Assessment
Pulumi AI strengths and limitations
Where it stands out
- Evolves beyond prompt-to-code by connecting analysis, IaC changes, preview, policy, and pull-request review
- Pulumi state and organizational context can make answers more grounded than a generic coding assistant
- Read-only, Plan Mode, task approvals, RBAC, and branch protections provide multiple control layers
- Works across major clouds, Kubernetes, and the broader Pulumi provider ecosystem
- Multiple access surfaces fit platform teams, developers, incident channels, and existing agent workflows
- IaC-first changes preserve reviewability, repeatability, and a clearer audit trail
- Free Individual allowance makes small-scale evaluation practical
- Transparent $3-per-million-token metering makes Neo usage easier to model
What to consider
- Pulumi AI is no longer just a lightweight prompt-to-IaC generator; the current Neo product assumes or benefits from Pulumi Cloud context and workflows
- Neo can only reason over infrastructure, repositories, integrations, and discovered resources that its identity can see
- Incomplete discovery, stale state, hidden resources, cross-account boundaries, or RBAC trimming can produce an incomplete picture
- Generated IaC can still be wrong, insecure, destructive, expensive, noncompliant, or inconsistent with undocumented organizational conventions
- A successful preview does not prove application health, data safety, capacity, compatibility, or rollback success
- Cloud-provider charges, Pulumi resources, secrets, discovery, workflow minutes, and Neo tokens are separate cost dimensions
- Long investigations, large context graphs, PR annotations, and scheduled tasks can consume substantial tokens
- CLI and MCP integrations can expose powerful credentials and live cloud controls; every connection needs narrow scope and auditability
- Neo inherits the invoking user's permissions, so an overprivileged user creates an overprivileged ceiling even if the agent normally operates with less
- Read-only, Plan Mode, policy checks, and approvals reduce risk but do not replace independent review and tested recovery
- Pulumi's claims about speed, savings, and completeness are vendor claims and may not match a particular estate
- Organizations committed to Terraform or another IaC system should evaluate how much Pulumi Cloud adoption is required for the desired Neo workflow
Compare
Pulumi AI alternatives
The right alternative depends on the specific output, workflow, controls and budget your project requires.
Coding
Claude Code
Choose Claude Code with Pulumi's skills when you want a general terminal agent that can work across infrastructure code and the rest of the repository.
Explore Claude Code →Coding
Codex
Choose Codex with Pulumi's MCP server or handoff skill when OpenAI's agent workflow is primary and infrastructure tasks are one part of broader engineering.
Explore Codex →Coding
Cursor 3
Choose Cursor 3 when an editor-first multi-agent workflow is more important than Pulumi-specific live infrastructure context.
Explore Cursor 3 →Coding
Gemini CLI
Choose Gemini CLI for an open-source terminal agent and bring infrastructure tools into a lower-level, provider-managed workflow.
Explore Gemini CLI →Questions
Pulumi AI FAQs
What happened to Pulumi AI?
Pulumi's AI offering has evolved into Pulumi Neo. The earlier prompt-to-IaC capability remains part of a broader agent that can investigate infrastructure, run previews, review changes, and propose governed pull requests.
What is Pulumi Neo?
Neo is Pulumi's infrastructure agent. It uses Pulumi Cloud context, Claude models through Amazon Bedrock, Pulumi Agent Skills, policies, and user permissions to answer questions and perform approved infrastructure work.
Is Pulumi Neo free?
Pulumi Individual is free and includes 5 million Neo tokens per month. Paid plans meter Neo at $3 per million tokens in addition to plan and other Pulumi Cloud usage.
Can Neo generate infrastructure code?
Yes. Neo can generate Pulumi programs in TypeScript, Python, Go, and other supported languages, then run a preview and propose the change through a pull request.
Can Pulumi Neo deploy infrastructure?
It can execute infrastructure workflows when given permission, but teams can require plans and approvals or keep tasks read-only. Production changes should remain behind normal deployment and review controls.
Does Neo work with Terraform?
Pulumi supports mixed and migration workflows, and Neo can work with infrastructure context beyond only newly generated Pulumi code. Evaluate the exact Terraform workflow and how much Pulumi Cloud context is required before adopting it.
Where can I use Neo?
Neo is available in Pulumi Cloud, the Pulumi CLI, supported editor agent panels, Slack, pull requests, and through Pulumi MCP or skill handoffs from other AI agents.
Which model powers Pulumi Neo?
Pulumi's current documentation says Neo uses Anthropic's Claude family through Amazon Bedrock. The model is only one layer; Pulumi state, skills, policies, permissions, and tools shape the actual result.
Is Pulumi Neo safe for production?
It can be operated with strong controls, but no infrastructure agent is safe by default. Use least privilege, read-only investigation, Plan Mode, previews, mandatory policies, pull-request review, staged deployment, monitoring, and tested rollback.
Bottom line
Our Pulumi AI verdict
Pulumi Neo is one of the clearest examples of an AI feature becoming a real infrastructure workflow rather than a code generator. It is most compelling for teams already using Pulumi Cloud, because live state, policies, permissions, previews, and pull requests provide the context and control a generic agent lacks. Start with read-only investigations and reviewed IaC proposals; expand autonomy only after measuring accuracy, cost, policy behavior, and recovery on real infrastructure.
Visit Pulumi AI website ↗
AI training for the future of work.
Get access to all our AI courses, hundreds of real-world AI use cases, live expert-led workshops, an exclusive network of AI early adopters, and more.
AI Courses
Get unlimited access to all of our current & upcoming industry-specific AI courses for the duration of your subscription.
Daily Guides
To keep up with the rapid pace of AI, our team publishes AI implementation guides daily. Our library contains 300+ practical use cases to automate real-world work.
Workshops
Join weekly, live, interactive sessions with industry leaders who are at the forefront of AI for hands-on implementation guidance and exclusive insights.
Community
Network with an exclusive community of AI-first professionals who are working smarter with AI. Learn how early adopters are using AI in their work and businesses.