Update pricing page content for new billing model

[cnunciato]

Applies the pricing page content updates for the new Credits-based billing model, along with minor casing and consistency cleanup.

[github-actions]

Pre-merge Review — Last updated 2026-06-02T19:24:30Z

Tip

Summary: This PR is a substantial content update to content/pricing/_index.md — a marketing landing page rendered through the pricing layout — that introduces a new billing model (Pulumi credits, monthly up-front fee creating a prepaid pool with in-arrears overage billing) and corresponding Neo token pricing (5M tokens included on Individual, $3 per million on paid tiers). The reader-blocking risk for a pricing page is wrong prices, wrong tier inclusions, or contradictory billing-mechanic prose; the fact-check pass extracted 46 claims and verified 21 against external sources (the rest were either intentional NEW billing-model content not yet on the public pricing page, or could not converge in the time budget). After triage, no blockers remain — the contradicted findings are either (a) the verifier comparing new content against the stale public page (expected; this PR is the change), (b) extractor mis-categorization, or (c) pre-existing content the PR only re-formatted. Hugo build is skipped (content-only PR); no link-integrity, frontmatter, or style findings.

Review confidence:

Dimension	Level	Notes
mechanics	HIGH
facts	MEDIUM	New billing-model copy can't be externally verified against the current public pricing page (the page this PR is updating); reviewer relied on PR-author intent and internal consistency for those passages.

Investigation log

• Cross-sibling reads: not run (not in a templated section)
• External claim verification: 21 of 46 claims verified (16 unverifiable, 9 contradicted) · 4 specialists (numerical, cross-reference, capability, framing); 0 cross-specialist corroborations · routed: 0 inline, 18 Pass 1, 0 Pass 2, 28 Pass 3 (verified 15, contradicted 6, unverifiable 7).
• Cited-claim spot-checks: not run (no cited claims)
• Frontmatter sweep: ran on body + meta_desc
• Temporal-trigger sweep: ran (recency words present in diff; spot-check in-review)
• Code execution: not run (no static/programs/ change)
• Code-examples checks: not run (no fenced code blocks in content files)
• Editorial-balance pass: not run (not under content/blog/)

🚨 Outstanding	⚠️ Low-confidence	💡 Pre-existing	✅ Resolved
0	15	2	0

🔍 Verification trail

46 claims extracted · 21 verified · 16 unverifiable · 9 contradicted

• L32-33 in content/pricing/_index.md "The Individual/Free tier of Pulumi Cloud includes Neo, described as Pulumi's infrastructure agent." → ✅ verified (evidence: The pricing page at content/pricing/_index.md lists under the Individual (Free) tier features: "Neo, our infrastructure agent". Multiple other docs pages (e.g., content/releases/agentic-infrastructure-era.md) also confirm: "Neo, our in…; source: repo:content/pricing/_index.md)
• L36 in content/pricing/_index.md "The Team edition of Pulumi Cloud starts at $40 per month." → ✅ verified (evidence: The pricing file explicitly lists the Team tier with price: Starts at $40 and price_label: /mo, confirming the claim that the Team edition starts at $40 per month.; source: repo:content/pricing/_index.md)
• L38-39 in content/pricing/_index.md "The Team edition of Pulumi Cloud covers up to 500 resources, with additional usage billed on demand." → ✅ verified (evidence: The Team tier in content/pricing/_index.md has note: Up to 500 resources, additional usage billed on demand, which directly confirms the claim.; source: repo:content/pricing/_index.md)
• L46 in content/pricing/_index.md "The Team plan supports up to 10 users." → ✅ verified (evidence: The official Pulumi blog (February 2026) states: "Pulumi Team Edition supports up to 10 users, and Pulumi Enterprise Edition supports unlimited users." A third-party analysis also confirms "The Team tier has a hard cap of 10 users."; source: https://www.pulumi.com/blog/announcing-new-usage-based-pricing-for-your-whole-team/)
• L56 in content/pricing/_index.md "The Enterprise edition of Pulumi Cloud costs $400 per month." → ✅ verified (evidence: The pricing file explicitly lists the Enterprise tier with price: $400 and price_label: /mo, confirming the claim that the Enterprise edition costs $400 per month.; source: repo:content/pricing/_index.md)
• L58-59 in content/pricing/_index.md "The Enterprise edition of Pulumi Cloud covers up to 2,000 resources, with additional usage billed on demand." → ✅ verified (evidence: The file content/pricing/_index.md contains the Enterprise tier note: "Up to 2,000 resources, additional usage billed on demand", which directly matches the claim.; source: repo:content/pricing/_index.md)
• L475-476 in content/pricing/_index.md "The ESC resource cost starts at $0.0005/hour ($0.365/month) for Enterprise plans." → ❌ contradicted (framing: shifted — the claim attributes the $0.0005/hour ($0.365/month) rate to "ESC resources" but the source assigns this rate to "IaC resources"; ESC secrets have a…; evidence: The official Pulumi pricing page states: "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)." The $0.0005/hour ($0.365/m…; source: https://www.pulumi.com/pricing/)
• L481 in content/pricing/_index.md "The Individual/Free tier includes 500 free workflow minutes per month." → ✅ verified (framing: strengthened — claim uses Pulumi's broader "workflow minutes" label (per the pricing page's own terminology) for what the Deployments page calls "deploy minute…; evidence: The official Pulumi Deployments product page states "Individual Edition has 500 deploy minutes/month," and the Pulumi pricing page defines "Workflow Minutes" as the umbrella term covering both Insights and Deployments minutes drawn from a…; source: https://www.pulumi.com/product/pulumi-deployments/)
• L482 in content/pricing/_index.md "The workflow cost per minute is $0.01 for Team, Enterprise, and Business Critical plans." (also L484) → ✅ verified (framing: strengthened — the source uses "deployment minute" while the PR uses "workflow minute" (the current Pulumi pricing page umbrella term); the $0.01/min rate and…; evidence: The official Pulumi Deployments product page states "Pulumi Deployments costs $0.01 per deployment minute" and confirms "Team, Enterprise, and Business Critical Editions all have 3,000 included deploy minutes/month," with the same per-minu…; source: https://www.pulumi.com/product/pulumi-deployments/)
• L529 in content/pricing/_index.md "Audit policies are not available on the Individual/Free tier of Pulumi Cloud but are available on Team, Enterprise, and Business Critical plans." (also L532) → 🤷 unverifiable (evidence: verification did not converge within 8 turns)
• L539 in content/pricing/_index.md "Pre-built policy packs available on the Business Critical plan include Pulumi Best Practices, CIS, NIST, HITRUST, and PCI DSS." (also L543) → 🤷 unverifiable (evidence: verification did not converge within 8 turns)
• L564 in content/pricing/_index.md "The Individual/Free tier of Pulumi Cloud includes up to 5 million Neo tokens." → 🤷 unverifiable (evidence: (escalated from pass1) The official Pulumi pricing page (pulumi.com/pricing) lists various Individual tier limits (deployment minutes, secrets, API calls) but contains no mention of a "5 million Neo tokens" allocation. Neo tokens are confi…; source: WebSearch ran query "Pulumi Cloud pricing Individual Free tier Neo tokens"; top results didn't address the specific 5 million token claim. https://www.pulumi.com/pricing/; intuition: The "5 million" figure is suspiciously round and may be a newly introduced or not-yet-published pricing detail; the off…)
• L565 in content/pricing/_index.md "Neo (Pulumi's infrastructure agent) is available (checked) on Team, Enterprise, and Business Critical plans." (also L567-568, L573) → ❌ contradicted (framing: narrowed — claim broadens the source by omitting Individual; the source shows Neo is available on all four tiers (Individual, Team, Enterprise, Business Critic…; evidence: The file shows "Neo, our infrastructure agent" is listed as a feature of the Individual (free) plan, and each higher tier inherits everything from the previous tier ("Everything in Individual, plus:", etc.). Neo is therefore availa…; source: repo:content/pricing/_index.md (Individual plan features list))
• L571-573 in content/pricing/_index.md "- content: $3" → 🤷 unverifiable (evidence: The official Pulumi pricing page lists per-resource rates of $0.1825/month (Team) and $0.365/month (Enterprise); no $3 figure appears in any current pricing source. Without the full file context (e.g., what product/tier the $3 refers to),…; source: WebSearch ran query "Pulumi pricing per resource month 2024 2025"; top result: https://www.pulumi.com/pricing/; intuition: $3 does not match any known Pulumi per-resource or per-secret rate; likely a plan-level or add-on price, but context is…)
• L571 in content/pricing/_index.md "The activity cost for Neo is $3 per million tokens on Team, Enterprise, and Business Critical plans." (also L573) → 🤷 unverifiable (evidence: The official Pulumi pricing page (pulumi.com/pricing) covers IaC resource billing, ESC secrets, and deployment minutes but contains no mention of Neo token pricing. The Pulumi Neo REST API docs confirm "Neo tokens are the priced unit used…; source: WebSearch ran query "Pulumi Neo activity cost pricing per million tokens"; top results didn't address the claim. Also searched "Pulumi Neo '$3 per million tokens' pricing" — pulumi.com/pricing returned but contained no Neo token price.; intuition: $3/million tokens is a plausible AI pricing figure (matches Claude 3.5 Sonnet input rate), but Pulumi's public pricing…)
• L651 in content/pricing/_index.md "Self-serve Pulumi Cloud customers are charged an up-front fee at the beginning of each monthly term, which creates a pool of Pulumi credits; usage exceeding th…" → ❌ contradicted (framing: shifted — claim describes self-serve customers as paying up-front to create a credit pool, but the source says self-serve customers are billed in-arrears; the…; evidence: (escalated from pass1) The official Pulumi pricing page states: "If you self-serve by entering a credit card, you will be billed in-arrears every month for your usage." The up-front/credit-pool model requires contacting sales and is not th…; source: https://www.pulumi.com/pricing/)
• L653 in content/pricing/_index.md "Customers who prefer to pay annually can contact sales to receive a discount for a committed amount of usage paid up-front; if they consume all up-front purcha…" → ✅ verified (framing: shifted — claim says "prefer to pay annually" while source says "prefer to pay up-front"; the annual framing is an added specificity not present in the source,…; evidence: The official Pulumi pricing page states: "If you prefer to pay up-front, you can contact sales and receive a discount for a committed amount of usage paid up-front. If you subsequently consume all up-front purchased usage, you will be bill…; source: https://www.pulumi.com/pricing/)
• L656 in content/pricing/_index.md "All usage of Pulumi services draws from a pool of Pulumi credits; once the pool is exhausted, customers are billed in arrears for additional use." → ❌ contradicted (framing: narrowed — claim broadens the "pool" concept from "workflow minutes" (source) to "all usage of Pulumi services" (claim); source supports only the narrower form…; evidence: The official Pulumi pricing page states "All usage draws from a single, shared pool of minutes" only in the context of Workflow Minutes (Insights + Deployments), not all Pulumi services. IaC resources, ESC secrets, and API calls are billed…; source: https://www.pulumi.com/pricing/)
• L659 in content/pricing/_index.md "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 p…" → ✅ verified (evidence: The official Pulumi pricing page states verbatim: "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)." — an exact match…; source: https://www.pulumi.com/pricing/)
• L661 in content/pricing/_index.md "Enterprise plans receive volume discounts on IaC resources, so that the more resources consumed, the lower the incremental rate; prepaid plans offer more consi…" → 🤷 unverifiable (framing: shifted — the source confirms volume/prepaid discounts exist for Enterprise, but does not confirm the specific tiered-rate structure (lower incremental rate at…; evidence: (escalated from pass1) Pulumi's official pricing page confirms Enterprise plans have volume pricing and prepaid options with bulk discounts ("Enterprise Edition…is also now available with usage-based pricing, including prepaid options with…; source: https://www.pulumi.com/blog/announcing-new-usage-based-pricing-for-your-whole-team/ (result 5-4); https://www.pulumi.com/pricing/ (result 1-13) (WebSearch dispatched but verification did not converge within the turn budget))
• L663 in content/pricing/_index.md "For billing purposes, a partial resource hour used is billed as a full hour." → 🤷 unverifiable (evidence: verification did not converge within 8 turns)
• L663 in content/pricing/_index.md "Pulumi counts any resource declared in a Pulumi program for billing purposes, including provider resources (e.g., an Amazon S3 bucket), component resources (e.…" → 🤷 unverifiable (evidence: verification did not converge within 8 turns)
• L666 in content/pricing/_index.md "The Team edition includes up to 500 IaC resources to get started with." → ✅ verified (evidence: The official Pulumi pricing page states: "The Team edition includes 500 IaC resources to get started with." This is an exact match to the claim.; source: https://www.pulumi.com/pricing/)
• L668 in content/pricing/_index.md "500 IaC resources is enough to manage 500 EKS clusters or EC2 instances for a month." → ✅ verified (evidence: The official Pulumi pricing page states: "You could manage 500 EKS clusters or EC2 instances for a month using this amount," directly matching the claim about 500 IaC resources being sufficient for 500 EKS clusters or EC2 instances for a m…; source: https://www.pulumi.com/pricing/)
• L670 in content/pricing/_index.md "The Enterprise plan includes up to 2,000 IaC resources." → ✅ verified (evidence: Pulumi's official pricing page states: "The Enterprise edition comes with 2,000 resources" and "Should you exceed the 500 and 2,000 included resources in Team and Enterprise, respectively, you will be charged at the end of the month."; source: https://www.pulumi.com/pricing/)
• L683 in content/pricing/_index.md "A Serverless API with Amazon API Gateway and AWS Lambda (the linked example) uses an estimated 9 resources." → ✅ verified (evidence: The README.md for the linked example explicitly shows in its pulumi up output: "Resources: + 9 created" — listing 8 AWS resources (apigatewayv2:Api, iam:Role, lambda:Function, iam:RolePolicyAttachment, lambda:Permission, apigatewayv2:Int…; source: https://github.com/pulumi/examples/blob/master/aws-ts-apigatewayv2-http-api/README.md)
• L688 in content/pricing/_index.md "An Amazon EKS running in a VPC (the linked example) uses an estimated 20 resources." → ❌ contradicted (evidence: The README in the linked example (aws-py-eks) shows the actual pulumi up output: "Resources: + 18 created", not 20. The claim asserts 20 resources, but the source shows 18.; source: https://github.com/pulumi/examples/blob/master/aws-py-eks/README.md)
• L693 in content/pricing/_index.md "An Amazon ECS cluster and RDS backend running in a VPC (the linked example) uses an estimated 24 resources." → 🤷 unverifiable (evidence: (escalated from pass1) The resource tree in the GitHub README and Pulumi Registry page for aws-py-wordpress-fargate-rds is truncated and no source explicitly states a total resource count. The visible tree shows ~20 named resources but is…; source: WebSearch ran query "pulumi aws-py-wordpress-fargate-rds 24 resources OR resources created"; https://github.com/pulumi/examples/tree/master/aws-py-wordpress-fargate-rds; intuition: The number 24 is plausible given the partial tree (~20 visible resources plus truncated Frontend section), but cannot b…)
• L710 in content/pricing/_index.md "Workflow Minutes represent the total time used across both Pulumi Insights and Deployments, drawing from a single shared pool; for Insights, workflow minutes m…" → 🤷 unverifiable (evidence: verification did not converge within 8 turns)
• L710 in content/pricing/_index.md "Deployments consume workflow minutes by measuring the duration of each deployment process." → 🤷 unverifiable (evidence: verification did not converge within 8 turns)
• L716 in content/pricing/_index.md "Neo tokens are the metering method for Neo-powered features including Neo tasks, pull-request annotations, and natural-language search, and cost $3 per million…" → 🤷 unverifiable (evidence: Pulumi's REST API docs confirm "Neo tokens are the priced unit used for billing," but no public Pulumi pricing page or authoritative source found in searches discloses the $3/million tokens rate or the specific feature list (pull-request a…; source: WebSearch ran query "Pulumi Neo tokens pricing per million" and "Pulumi Neo tokens "$3" million pricing pull-request annotations natural-language search"; top results didn't address the specific price claim.; intuition: $3/million tokens is a plausible LLM-era price point, but the Pulumi public pricing page (pulumi.com/pricing/) returned…)
• L720 in content/pricing/_index.md "Neo features can be managed in the Pulumi Cloud dashboard under Settings → Neo Settings, and Neo integration with version control systems is located under Mana…" → 🤷 unverifiable (evidence: verification did not converge within 8 turns)
• L727 in content/pricing/_index.md "Pulumi Cloud is described as a managed service for the open-source CLI and SDK that tracks infrastructure state, coordinates updates with the CLI, manages secr…" → ✅ verified (evidence: (escalated from pass1) The Pulumi pricing page states: "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... It also manages secrets, supports SAML…; source: https://www.pulumi.com/pricing/)
• L738 in content/pricing/_index.md "After the Business Critical trial expires, no data will be lost, and there is a grace period." → 🤷 unverifiable (evidence: verification did not converge within 8 turns)
• L743 in content/pricing/_index.md "Pulumi projects and stacks are a way to organize Pulumi code. You can consider a Pulumi project to be anal…" → 🤷 unverifiable (evidence: verification did not converge within 8 turns)
• L747 in content/pricing/_index.md "Moving from Starter or Pro to the new Team Edition gives access to Pulumi Deployments, Insights, and Neo." → 🤷 unverifiable (evidence: (escalated from pass1) The Pulumi pricing page confirms the FAQ heading "How do I move from Starter or Pro to the new Team Edition?" exists, and separate pages confirm Team Edition includes Deployments and that Neo is available to all user…; source: WebSearch ran query "Pulumi 'Starter' OR 'Pro' to 'Team Edition' upgrade migration 2025"; https://www.pulumi.com/pricing/; intuition: The claim bundles three distinct products (Deployments, Insights, Neo) as migration benefits — Neo is described as avai…)
• L749 in content/pricing/_index.md "Pulumi has completed the SOC 2 Type 2 compliance process." → ✅ verified (evidence: Pulumi's official security page states "The Pulumi platform employs industry best practices for security and is SOC 2 Type II certified." The official blog also confirms: "completing our SOC 2 Type 2 Audit."; source: https://www.pulumi.com/security/)
• L762 in content/pricing/_index.md "The sample email states that Pulumi's customer base includes companies from startups to some of the largest Fortune 500 and Global 2000 organizations." → ✅ verified (evidence: The live Pulumi pricing page contains the exact sample email text: "their customer base includes a diverse array of companies, from startups to some of the largest Fortune 500 and Global 2000 organizations."; source: https://www.pulumi.com/pricing/)
• L766-770 in content/pricing/_index.md "The sample email states that Mercedes-Benz Research & Development North America improved collaboration between its infrastructure and application development t…" → ❌ contradicted (framing: shifted — the attribution of the Mercedes-Benz MBRDNA collaboration claim to /case-studies/bmw/ is wrong; the correct source is /case-studies/mercedes-benz/; evidence: The Pulumi case study about Mercedes-Benz Research & Development North America improving collaboration between infrastructure and application teams exists at pulumi.com/case-studies/mercedes-benz/, not /case-studies/bmw/ as the source_hint…; source: https://www.pulumi.com/case-studies/mercedes-benz/)
• L767 in content/pricing/_index.md "Snowflake migrated to Kubernetes across multiple clouds in three months using Pulumi." → ✅ verified (evidence: The Pulumi case study page confirms Snowflake moved "all their deployments, on multiple cloud vendors, to that platform, all in three months" using a Kubernetes-based architecture, and "Snowflake switched to Pulumi and met all their goals."; source: https://www.pulumi.com/case-studies/snowflake/)
• L768 in content/pricing/_index.md "Mercedes-Benz Research & Development North America improved collaboration between its infrastructure and application development teams using Pulumi." → ✅ verified (framing: strengthened — claim narrows the source's "bring their application and infrastructure teams closer together" to "improved collaboration between its infrastruct…; evidence: The Pulumi case study page confirms: "Learn how Mercedes-Benz Research and Development worked with Pulumi to bring their application and infrastructure teams closer together." The page also identifies the subject as "Mercedes-Benz Research…; source: https://www.pulumi.com/case-studies/mercedes-benz/)
• L769 in content/pricing/_index.md "Skai managed a complex public cloud migration project using Pulumi." → ✅ verified (framing: strengthened — claim narrows the source's detailed migration story to "managed a complex public cloud migration project using Pulumi"; source's broader account…; evidence: The Pulumi blog post at /blog/kenshoo-migrates-to-aws-with-pulumi/ (titled "Skai Migrates to AWS with Pulumi") confirms Skai used Pulumi to migrate its private cloud infrastructure to AWS, describing a complex migration involving hundreds…; source: https://www.pulumi.com/blog/kenshoo-migrates-to-aws-with-pulumi/)
• L770 in content/pricing/_index.md "Wiz, Supabase, and Lemonade created innovative engineering cultures using Pulumi." → ❌ contradicted (framing: shifted — source names "Cockroach Labs, Sourcegraph, and Lemonade" but the claim substitutes "Wiz, Supabase, and Lemonade"; different companies are attributed…; evidence: The Pulumi pricing page (pulumi.com/pricing) states: "Cockroach Labs, Sourcegraph, and Lemonade created innovative engineering cultures." The PR claim replaces Cockroach Labs and Sourcegraph with Wiz and Supabase, which are not the compani…; source: https://www.pulumi.com/pricing/)
• L788 in content/pricing/_index.md "In addition to a monthly up-front fee, Pulumi bills for the previous month's on-demand usage on the first day of each month for Team or Enterprise Edition cust…" → ❌ contradicted (framing: narrowed — claim adds "In addition to a monthly up-front fee" which the source does not state; the source describes only in-arrears billing on the first of eac…; evidence: (escalated from pass1) The official Pulumi pricing page states only: "You will be billed for the previous month's usage on the first day of each month" — with no mention of a separate monthly up-front fee billed alongside on-demand usage.…; source: https://www.pulumi.com/pricing/)
• L796 in content/pricing/_index.md "Pulumi offers a 14-day money-back guarantee for unsatisfied customers." → ✅ verified (evidence: Pulumi's official pricing page states: "If you're not satisfied with Pulumi, we offer a 14-day money-back guarantee." This directly confirms the claim.; source: https://www.pulumi.com/pricing/)
• L798 in content/pricing/_index.md "12x5 and 24x7 support, professional and advising services, and a private Slack channel are available to purchase in the Enterprise and Business Critical editio…" → ❌ contradicted (framing: shifted — the claim bundles features across tiers and introduces "advising services" not present in the source; the source distributes 12x5 to Enterprise and P…; evidence: The pricing page shows: Enterprise includes "12x5 Enterprise Support available" and Business Critical includes "Private Slack and Professional Services" and "24x7 Enterprise Support available." The claim incorrectly states "advising servic…; source: repo:content/pricing/_index.md)

🚨 Outstanding in this PR

These must be resolved or refuted before merging.

No outstanding blockers.

⚠️ Low-confidence

Review each and resolve as appropriate — these don't block the PR.

• [L529] content/pricing/_index.md — "Audit policies are not available on the Individual/Free tier of Pulumi Cloud but are available on Team, Enterprise, and Business Critical plans." — verdict: unverifiable (verifier did not converge in 8 turns). The claim is internally consistent with the comparison table in this same file (Audit policies row at L526-532: Individual _blank, Team/Enterprise/BC _check), so no author action is required.

• [L539] content/pricing/_index.md — "Pre-built policy packs available on the Business Critical plan include Pulumi Best Practices, CIS, NIST, HITRUST, and PCI DSS." — verdict: unverifiable (verifier did not converge in 8 turns). The claim is internally consistent with the comparison-table row at L533-539 of this file. Author question: is this list (CIS, NIST, HITRUST, PCI DSS) still current for Business Critical, or have packs been added/removed?

• [L564] content/pricing/_index.md — "The Individual/Free tier of Pulumi Cloud includes up to 5 million Neo tokens." — verdict: unverifiable (no public source found; verifier flagged "5 million" as suspiciously round). This is new pricing-model copy this PR is introducing, so absence from the live pricing page is expected. Author question: please confirm the 5M-token Individual allocation matches what billing/PM has committed to publish.

• [L571] content/pricing/_index.md — "The activity cost for Neo is $3 per million tokens on Team, Enterprise, and Business Critical plans." — verdict: unverifiable (no public Pulumi source confirms the rate). This is new pricing-model copy this PR is introducing. Author question: please confirm the $3/million-tokens rate has been signed off by billing/PM.

• [L661] content/pricing/_index.md — "Enterprise plans receive volume discounts on IaC resources, so that the more resources consumed, the lower the incremental rate; prepaid plans offer more consi…" — verdict: unverifiable at the specific tiered-rate level (verifier confirmed volume/prepaid discounts exist; the precise "lower incremental rate at higher volumes" structure is not publicly documented). Not a blocker — the prose is general enough to be accurate even if rate-card details are private. Author question: is there a public landing page or doc you'd like to link for the volume-discount mechanics?

• [L663] content/pricing/_index.md — "For billing purposes, a partial resource hour used is billed as a full hour." — verdict: unverifiable (verifier did not converge in 8 turns). This is a long-standing FAQ assertion (also present pre-PR). No author action required unless billing has changed the round-up behavior.

• [L663] content/pricing/_index.md — "Pulumi counts any resource declared in a Pulumi program for billing purposes, including provider resources (e.g., an Amazon S3 bucket), component resources (e.…" — verdict: unverifiable (verifier did not converge in 8 turns). Pre-existing FAQ wording; consistent with the linked concept docs. No author action required.

• [L693] content/pricing/_index.md — "An Amazon ECS cluster and RDS backend running in a VPC (the linked example) uses an estimated 24 resources." — verdict: unverifiable (the linked example's README does not show a final pulumi up resource count; verifier could see ~20 named resources in a truncated tree). This number existed in the pre-PR copy (PR only re-formatted the surrounding text). Author question: if you have a recent pulumi up count for aws-py-wordpress-fargate-rds, it would be worth syncing — but not a blocker for this PR.

• [L710] content/pricing/_index.md — "Workflow Minutes represent the total time used across both Pulumi Insights and Deployments, drawing from a single shared pool; for Insights, workflow minutes m…" — verdict: unverifiable (verifier did not converge in 8 turns). The "shared pool of workflow minutes" model is mentioned on the public pricing page; the detailed split between Insights (discovery + policy) and Deployments (deployment duration) is reasonable but not separately citable.

• [L710] content/pricing/_index.md — "Deployments consume workflow minutes by measuring the duration of each deployment process." — verdict: unverifiable (verifier did not converge in 8 turns). Consistent with the Deployments product page's per-minute billing model.

• [L716] content/pricing/_index.md — "Neo tokens are the metering method for Neo-powered features including Neo tasks, pull-request annotations, and natural-language search, and cost $3 per million…" — verdict: unverifiable (no public source for the $3/million rate or the feature list). This is new pricing-model copy this PR is introducing. Author question: please confirm the Neo-features list (tasks, PR annotations, natural-language search) is the complete and final set, and the $3/M rate is signed off.

• [L720] content/pricing/_index.md — "Neo features can be managed in the Pulumi Cloud dashboard under Settings → Neo Settings, and Neo integration with version control systems is located under Mana…" — verdict: unverifiable (verifier did not converge in 8 turns; UI nav paths aren't externally checkable without a logged-in session). Author question: please double-check the exact menu paths in the current Pulumi Cloud UI (Settings → Neo Settings; Management → Version Control) since UI menus drift quickly.

• [L738] content/pricing/_index.md — "After the Business Critical trial expires, no data will be lost, and there is a grace period." — verdict: unverifiable (verifier did not converge in 8 turns). Pre-existing FAQ wording unchanged by this PR. Author question: if the grace-period length has a fixed value (e.g., 30 days), consider naming it; otherwise no action.

• [L743] content/pricing/_index.md — "Pulumi projects and stacks are a way to organize Pulumi code. You can consider a Pulumi project to be anal…" — verdict: unverifiable (descriptive analogy; verifier did not converge). Note: both linked anchors (/docs/concepts/projects/ and /docs/concepts/stack/) are non-canonical; canonical paths under /docs/iac/concepts/. Per AGENTS.md, links inside /content/docs/ should use the full canonical path. This page is /content/pricing/, so the rule is advisory here — but consider /docs/iac/concepts/projects/ and /docs/iac/concepts/stacks/ for future-proofing.

• [L747] content/pricing/_index.md — "Moving from Starter or Pro to the new Team Edition gives access to Pulumi Deployments, Insights, and Neo." — verdict: unverifiable (verifier confirmed Team Edition includes Deployments and Neo is broadly available; the specific Starter-Pro → Team upgrade-benefit bundle isn't separately documented). Author question: confirm Insights is in fact a net-new capability for migrating Starter/Pro users (the row implies it is).

📋 Triaged verifier findings

I double-checked these and realized they weren't real findings — click to expand

• [L571-573] content/pricing/_index.md — "- content: $3" — Spurious: the extractor grabbed a raw YAML literal (content: $3) as a standalone "claim"; it is not a sentence-level assertion. The substantive claim is covered by the L571 entry in ⚠️ Low-confidence.

• [L475-476] content/pricing/_index.md — "The ESC resource cost starts at $0.0005/hour ($0.365/month) for Enterprise plans." — Spurious: the claim extractor mis-categorized this row. Lines 475-476 sit inside the ## Pulumi Insights Table section (header "Insights & Governance"), row On-demand resource price — these are IaC resource rates ($0.00025/$0.0005 per hour), not ESC. The verifier correctly identified the rate as IaC's, but the underlying file content does not assert "ESC"; the misattribution is in the extracted claim text only.

• [L565] content/pricing/_index.md — "Neo (Pulumi's infrastructure agent) is available (checked) on Team, Enterprise, and Business Critical plans." — Spurious: the verifier read the _check marks across Team/Enterprise/BC as "Neo limited to those three tiers," but the Individual column for the same row (L564) carries Up to 5M tokens — i.e., Neo is available on Individual, just with a token allowance instead of an unmetered check. The table conveys availability across all four tiers; the claim text mis-reads the markers.

• [L651] content/pricing/_index.md — "Self-serve Pulumi Cloud customers are charged an up-front fee at the beginning of each monthly term, which creates a pool of Pulumi credits; usage exceeding th…" — Spurious: the verifier compared against pulumi.com/pricing's current copy ("billed in-arrears every month"), but the PR's stated purpose (per title and diff scope) is to replace that model with the Pulumi-credits + up-front-fee model. This contradiction is intentional — the public page hasn't been updated yet.

• [L656] content/pricing/_index.md — "All usage of Pulumi services draws from a pool of Pulumi credits; once the pool is exhausted, customers are billed in arrears for additional use." — Spurious: same as L651. The "credits pool" concept is the new billing model this PR introduces. The verifier correctly noted the live page only mentions the pool concept for Workflow Minutes; the PR is broadening the model to all services.

• [L766-770] content/pricing/_index.md — "The sample email states that Mercedes-Benz Research & Development North America improved collaboration between its infrastructure and application development t…" — Spurious: the verifier's source_hint was /case-studies/bmw/ (extractor confusion across adjacent bulleted lines), but the actual content at L768 correctly links to /case-studies/mercedes-benz/. The Mercedes-Benz attribution in the file is correct; only the extractor's source_hint was off.

• [L770] content/pricing/_index.md — "Wiz, Supabase, and Lemonade created innovative engineering cultures using Pulumi." — Spurious: the verifier flagged this as a substitution against the live page's "Cockroach Labs, Sourcegraph, and Lemonade." The diff confirms the change is intentional — Wiz and Supabase replace Cockroach Labs and Sourcegraph in the sample-email customer list. Both /case-studies/wiz/ and /case-studies/supabase/ are valid internal links. No author action needed beyond confirming this is the marketing-approved customer trio.

• [L788] content/pricing/_index.md — "In addition to a monthly up-front fee, Pulumi bills for the previous month's on-demand usage on the first day of each month for Team or Enterprise Edition cust…" — Spurious: same as L651/L656. The "monthly up-front fee" is the new billing model this PR introduces; the verifier's contradiction is against the stale public page.

💡 Pre-existing issues in touched files (optional)

• [L688] content/pricing/_index.md — "An Amazon EKS running in a VPC (the linked example) uses an estimated 20 resources." — verdict: contradicted (linked README's pulumi up shows Resources: + 18 created). Pre-existing: the number 20 was carried over from the prior copy; this PR only reformatted the surrounding HTML (<b>20</b><br> → (Estimated resources: 20)). Suggested follow-up (not blocking this PR): update to 18 to match the example's current resource count.

• [L798] content/pricing/_index.md — "12x5 and 24x7 support, professional and advising services, and a private Slack channel are available to purchase in the Enterprise and Business Critical editio…" — verdict: contradicted (12x5 is Enterprise-only; 24x7 and Private Slack are Business Critical-only per the comparison table at L77, L96, L591-610). Pre-existing: the bundled wording (and the inclusion of "advising services") predates this PR; the diff only normalized punctuation and re-cased "private Slack channel." Suggested follow-up (not blocking this PR): rewrite the FAQ answer to distinguish which support tier appears at which edition, matching the comparison table.

✅ Resolved since last review

No items resolved since the last review.

📜 Review history

• 2026-06-02T19:24:30Z — Triaged 7 verifier contradictions as spurious (new billing-model copy vs. stale public page, or extractor mis-reads); moved 2 to pre-existing; 16 low-confidence items flagged for author confirmation. No blockers. (05eb8fa)

---

Need a re-review? Want to dispute a finding? Mention @claude and include #update-review.
(For ad-hoc questions or fixes, just @claude — no hashtag.)

[pulumi-bot]

Your site preview for commit e02a2c2 is ready! 🎉

http://www-testing-pulumi-docs-origin-pr-19481-e02a2c2f.s3-website.us-west-2.amazonaws.com

[isaac-pulumi]

@cnunciato my only major nit here is that Pulumi Credits is defined in the customer's agreement (on the order form) and defined terms tend to be capitalized. I see in this draft we've used "Pulumi credits" -- can we bring back title case?

[cnunciato]

@isaac-pulumi Done!

[isaac-pulumi]

@cnunciato Can we do anything to fix the wrapping on the price for Team edition? It looks like "Starts at/mo" on my end:

[isaac-pulumi]

Odd wrapping here. See comment in PR thread

[isaac-pulumi]

See request to fix wrapping on Team price

[cnunciato]

@isaac-pulumi Something I didn't notice until now: It looks like both Team and Enterprise have base rates, but only Team was labeled "starts at". Is there a reason Enterprise wasn't? Shouldn't they both be presented similarly?

That said, since "Starts at" doesn't fit in that spot, I went ahead and removed it from the Team plan and instead appended "base" to both. Let me know what you think. I know this isn't exactly what you asked for; it's just that these slots in the layout are currently pretty constrained. If we do need to use "Starts at", I'd probably suggest we make a slight tweak to position it differently — maybe above the number somehow (in which case I'd probably tag @jeffmerrick in).

[pulumi-bot]

Lighthouse Performance Report

Commit: e02a2c2 | Metric definitions

Page	Device	Score	FCP	LCP	TBT	CLS	SI
Homepage	Mobile	🔴 30	3.6s	11.9s	3943ms	0.012	9.2s
Homepage	Desktop	🟡 71	0.8s	1.1s	299ms	0.245	1.6s
Install Pulumi	Mobile	🟡 51	5.3s	7.8s	322ms	0.029	8.1s
Install Pulumi	Desktop	🟡 81	1.3s	1.9s	21ms	0.013	3.0s
AWS Get Started	Mobile	🟡 53	5.1s	7.7s	278ms	0.066	7.8s
AWS Get Started	Desktop	🟡 82	1.3s	1.8s	22ms	0.023	3.0s