Skip to content

Add Neo Code Reviews blog, docs page, pricing updates, Neo enable/disable toggles#19728

Open
kramhuber wants to merge 6 commits into
masterfrom
mhuber/neo-code-reviews
Open

Add Neo Code Reviews blog, docs page, pricing updates, Neo enable/disable toggles#19728
kramhuber wants to merge 6 commits into
masterfrom
mhuber/neo-code-reviews

Conversation

@kramhuber

@kramhuber kramhuber commented Jun 16, 2026 •
edited by cnunciato
Loading

Copy link
Copy Markdown
Contributor

Summary

Ships the Neo Code Reviews launch as one change:

  • Blog: content/blog/neo-code-reviews/, an announcement post with generated feature and meta images. Dated 2026-06-17, so it publishes on its date and is excluded from the production build until then.
  • Docs: new content/docs/ai/code-reviews/ page covering automated and manual reviews, setup (including the individual OAuth step required to trigger a review), governance, and a public-preview callout.
  • GitHub integration page: removed and folded into Code Reviews, with the old URL preserved as an alias. The GitHub App page now notes that triggering a Neo code review requires individual OAuth access, while it stays optional for other Neo tasks.
  • Links: repointed the integrations and pull-requests pages, and the historical neo-github-slack post, to the new page.
  • Pricing: updated the comparison table and plan cards for Neo SKU gating.

@github-actions

github-actions Bot commented Jun 16, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Social Media Review

content/blog/neo-code-reviews/index.md

X — PASS

LinkedIn — PASS

Bluesky — PASS

Suggestions (advisory)

These are stylistic notes — they don't block the post.

X

  • Missing pointer — "We built Neo code reviews to bridge the gap." ends the post with no signal to read the article; add a line that invites the click

LinkedIn

  • Third paragraph explains the full mechanism ("evaluate changes not just in terms of the infra code alone, but also in the context of existing deployed infrastructure, leaving a review on the pull request just as a human teammate would") — withhold at least the "how" so the article still has something to show

Bluesky

  • Missing pointer — identical issue to X; the post ends on "bridge the gap" with no line connecting to the article

Updated for commit 42739d91ab44551f954a779cf08d6ed7dead18d3 (short: 42739d9) at 2026-06-18 23:01 UTC.

@pulumi-bot

pulumi-bot commented Jun 16, 2026 •
edited
Loading

Copy link
Copy Markdown
Collaborator

Your site preview for commit 42739d9 is ready! 🎉

http://www-testing-pulumi-docs-origin-pr-19728-42739d91.s3-website.us-west-2.amazonaws.com

@kramhuber kramhuber marked this pull request as ready for review June 16, 2026 21:37
@kramhuber kramhuber requested a review from cnunciato June 16, 2026 21:38
@github-actions github-actions Bot added the review:triaging Claude Triage is currently classifying the PR label Jun 16, 2026
@github-actions github-actions Bot added domain:website PR touches marketing, pricing, legal, or competitive landing pages domain:docs PR touches technical docs domain:mixed PR touches more than one domain domain:blog PR touches blog posts or customer stories review:in-progress Claude review is currently running and removed review:triaging Claude Triage is currently classifying the PR labels Jun 16, 2026
@github-actions

github-actions Bot commented Jun 16, 2026

Copy link
Copy Markdown
Contributor

Pre-merge Review — Last updated 2026-06-16T21:43:49Z

Tip

Summary: This PR introduces Neo Code Reviews — a new blog post (content/blog/neo-code-reviews/), a new docs page (content/docs/ai/code-reviews/_index.md, which takes over from the now-deleted /docs/ai/integrations/github/ page and parallels the existing /docs/ai/pull-requests/ page), pricing-page feature and comparison-table updates, and internal-link updates pointing existing pages at the new Code Reviews page. For a reader, the blocking kind of wrongness would be an incorrect statement of what Neo Code Reviews requires or how it's billed, or a broken alias on the retired GitHub page. The retired page's URL is correctly preserved as an alias on the new page, the new blog/docs claims check out against the in-PR sources and cross-referenced sibling pages, and the Hugo preflight is clean. One PR-introduced item to confirm sits on the GitHub App page (L119): the new sentence says triggering a Neo code review requires individual access, which couldn't be independently corroborated and reads in tension with the adjacent sentence stating the org-level app handles PR comments and checks regardless of individual access. Almost every pricing-page finding below is on a line this PR did not modify — pre-existing inaccuracies surfaced for awareness, not introduced here. One minor nit on a touched line: the new "Neo Code Reviews" row in the pricing comparison table links to /docs/ai/pull-requests/ rather than the new /docs/ai/code-reviews/ page. Passes run: diff review, external claim verification (172 claims), frontmatter/alias sweep, Hugo preflight, and a cross-sibling consistency spot-check.

Review confidence:

Dimension Level Notes
mechanics HIGH
facts MEDIUM New blog/docs claims verified against in-PR sources; one PR-introduced claim (github-app L119) couldn't be corroborated. The pricing findings are predominantly pre-existing, not introduced by this PR.
cross-sibling consistency MEDIUM Spot-checked the new Code Reviews page against its sibling /docs/ai/ pages and the GitHub App doc — consistent, apart from one minor link-target nit in the pricing comparison table.
Investigation log
  • Cross-sibling reads: 4 of 4 siblings (/docs/ai/pull-requests/, /docs/ai/integrations/, content/docs/integrations/version-control/github-app.md, and the neo-github-slack blog post)
  • External claim verification: 120 of 172 claims verified (28 unverifiable, 16 contradicted) · 4 specialists (numerical, cross-reference, capability, framing); 0 cross-specialist corroborations · routed: 0 inline, 138 Pass 1, 1 Pass 2 (verified 1, contradicted 0, unverifiable 0), 33 Pass 3 (verified 19, contradicted 8, unverifiable 6).
  • Cited-claim spot-checks: 1 of 1 cited claims fetched and compared
  • Frontmatter sweep: ran on body + meta_desc + social.{bluesky, linkedin, twitter}
  • 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: ran (single-subject, N/A)
🚨 Outstanding ⚠️ Low-confidence 💡 Pre-existing ✅ Resolved
1 28 13 0

🔍 Verification trail

172 claims extracted · 120 verified · 28 unverifiable · 16 contradicted
  • L3 in content/blog/neo-code-reviews/index.md "date: 2026-06-17T08:00:00-07:00" → ➖ not-a-claim (evidence: This is a blog post frontmatter date field — a publication timestamp set by the PR author for their own content. It is not a falsifiable third-party assertion; it is metadata describing when the author intends the post to be published.; source: repo:content/blog/neo-code-reviews/index.md L3)
  • L19 in content/blog/neo-code-reviews/index.md "Neo Code Reviews analyzes pull request changes in conjunction with what Pulumi Cloud knows about your running infrastructure, providing both high-level and cod…" (also L27, L31, L34) → ✅ verified (evidence: The blog post at content/blog/neo-code-reviews/index.md contains the exact sentence: "Neo Code Reviews analyzes pull request changes in conjunction with what Pulumi Cloud knows about your running infrastructure, providing both high-level…; source: repo:content/blog/neo-code-reviews/index.md)
  • L23 in content/blog/neo-code-reviews/index.md "A database property that cannot be changed in place will cause Pulumi to replace the database — destroying the running instance and creating a new one with a n…" (also L25) → ✅ verified (evidence: The blog file's LinkedIn social copy states verbatim: "That property can't be changed in place, so Pulumi will replace the database: destroy the running instance, create a new one with a new endpoint. The diff never showed it." — which exa…; source: repo:content/blog/neo-code-reviews/index.md (LinkedIn social block, lines ~23-32))
  • L27 in content/blog/neo-code-reviews/index.md "Pulumi Neo Code Reviews reads the preview output and leaves its feedback right on the pull request, down to the line. Now in public preview on GitHub." → ✅ verified (evidence: The exact claim text appears verbatim in the LinkedIn social copy of the blog post's front matter: "Pulumi Neo Code Reviews reads the preview output and leaves its feedback right on the pull request, down to the line. Now in public preview…; source: repo:content/blog/neo-code-reviews/index.md)
  • L34 in content/blog/neo-code-reviews/index.md "Neo Code Reviews analyzes pull request changes in conjunction with what Pulumi Cloud knows about your running infrastructure." → ✅ verified (framing: strengthened — claim uses "pull request changes in conjunction with" while source says "pull requests against"; both convey the same relationship and the sourc…; evidence: The /docs/ai/code-reviews/ page states: "Neo Code Reviews analyzes pull requests against what Pulumi Cloud knows about your running infrastructure and leaves its feedback in the pull request." The blog's phrasing ("analyzes pull request…; source: content/docs/ai/code-reviews/_index.md)
  • L38 in content/blog/neo-code-reviews/index.md "Neo Code Reviews has access to the entirety of a user's other cloud context, such as stack relationships and dependencies." → ✅ verified (evidence: The blog post states: "Neo not only has access to both of those, but also to the entirety of your other cloud context, such as stack relationships and dependencies." This directly confirms the claim.; source: repo:content/blog/neo-code-reviews/index.md)
  • L42 in content/blog/neo-code-reviews/index.md "Neo Code Reviews skips draft pull requests and those opened by bots by default." → ✅ verified (evidence: The blog post at content/blog/neo-code-reviews/index.md states verbatim: "Either way, it skips draft pull requests and those opened by bots by default." This directly confirms the claim.; source: repo:content/blog/neo-code-reviews/index.md)
  • L42 in content/blog/neo-code-reviews/index.md "Neo can review every pull request automatically, or only when someone mentions @pulumi-neo." → ✅ verified (evidence: The blog post at content/blog/neo-code-reviews/index.md line 42 states verbatim: "Neo can review every pull request automatically, or only when someone mentions @pulumi-neo."; source: repo:content/blog/neo-code-reviews/index.md)
  • L44 in content/blog/neo-code-reviews/index.md "Neo Code Reviews runs inside the same governance as every other Neo task, with RBAC, guardrails, and audit logging." → ➖ not-a-claim (evidence: The line at L44 reads: "Neo Code Reviews runs inside the same governance as every other Neo task, with the RBAC, guardrails, and audit logging your organization has set." This is the PR author's own description of their own product feature…; source: repo:content/blog/neo-code-reviews/index.md)
  • L48 in content/blog/neo-code-reviews/index.md "If Neo already posts preview summaries on pull requests, Code Reviews is automatically on, and its review takes the place of those summaries." → ➖ not-a-claim (evidence: The text at L48 of the blog post itself reads: "If Neo already posts preview summaries on your pull requests, Code Reviews is on, and its review takes the place of those summaries." This is the PR author's own description of their own feat…; source: repo:content/blog/neo-code-reviews/index.md)
  • L50 in content/blog/neo-code-reviews/index.md "After general availability on July 1, 2026, Neo Code Reviews reviews begin counting toward an organization's Neo token usage at the same per-token rate as any…" → 🤷 unverifiable (evidence: No public source confirms that Neo Code Reviews reach GA on July 1, 2026, or that they count toward Neo token usage at the same per-token rate as other Neo tasks. The Pulumi pricing page returned only a single sentence fragment, and no sea…; source: WebSearch ran query "Pulumi Neo Code Reviews token usage pricing GA July 2026"; top results didn't address the claim. https://www.pulumi.com/pricing/ returned only a fragment with no relevant detail.; intuition: July 1, 2026 is a suspiciously precise future GA date (15 days from today); the per-token rate parity claim is a specif…)
  • L54 in content/blog/neo-code-reviews/index.md "The Pulumi Community Slack is accessible at https://slack.pulumi.com/." → ✅ verified (evidence: The URL https://slack.pulumi.com/ returns HTTP 200 with body: "Join the Pulumi Community on Slack! ... Join the Pulumi Community on Slack where you can ask questions or share ideas about infrastructure as code."; source: https://slack.pulumi.com/)
  • L4 in content/blog/neo-github-slack/index.md "lastmod: 2026-06-16T08:00:00-07:00" → ➖ not-a-claim (evidence: This is a lastmod front-matter metadata field in a blog post file, recording the last-modified timestamp of the PR author's own document. It is not a falsifiable assertion about a third-party fact — it is git/diff metadata embedded in th…; source: repo:content/blog/neo-github-slack/index.md L4)
  • L18 in content/blog/neo-github-slack/index.md "Every engineer with a linked Pulumi Cloud identity can mention Neo from GitHub or Slack threads." (also L30, L33, L75) → ✅ verified (framing: strengthened — claim narrows "the threads they already work in" to "GitHub or Slack threads"; the source's broader form proves the claim as a subset given the…; evidence: The blog post at content/blog/neo-github-slack/index.md states verbatim: "every engineer with a linked Pulumi Cloud identity can mention Neo from the threads they already work in," in the context of GitHub and Slack integrations — directly…; source: repo:content/blog/neo-github-slack/index.md)
  • L33 in content/blog/neo-github-slack/index.md "Pulumi Neo already runs Pulumi tasks from the Cloud console and the terminal before this GitHub and Slack integration." → ✅ verified (evidence: The blog post at line 33 states: "The agent that already runs Pulumi tasks from the Cloud console and the terminal now participates in the threads where your team discusses changes." The referenced Neo CLI post con…; source: repo:content/blog/neo-github-slack/index.md (L33) and repo:content/blog/pulumi-neo-cli/index.md)
  • L35 in content/blog/neo-github-slack/index.md "Mentioning @Neo in a Slack channel causes Neo to start a task and continue the conversation as the user replies." → ✅ verified (evidence: Line 35 of the blog post states: "Mention @Neo in a Slack channel and Neo starts a task, continuing the conversation as you reply." This directly matches the claim.; source: repo:content/blog/neo-github-slack/index.md)
  • L41 in content/blog/neo-github-slack/index.md "When mentioned in a GitHub PR or issue, Neo sees the diff, the stacks linked to the repository, and their current state." → ✅ verified (evidence: The blog post at L41 states: "Neo sees the diff, the stacks linked to the repository, and their current state." This is an exact match to the claim.; source: repo:content/blog/neo-github-slack/index.md)
  • L41 in content/blog/neo-github-slack/index.md "Neo can identify resources that change in stacks the PR doesn't touch directly." → ➖ not-a-claim (evidence: The claim is a faithful description of Neo's behavior as authored in this very PR's blog post (line 41: "including resources that change in stacks the PR doesn't touch directly"). This is the PR author describing their own product feature,…; source: repo:content/blog/neo-github-slack/index.md)
  • L41 in content/blog/neo-github-slack/index.md "Neo's responses in GitHub land in the same thread as the mention, making the analysis part of the review record." → ✅ verified (evidence: The blog post states: "Responses land in the same thread, so the analysis becomes part of the review record and any follow-up stays with it." This directly confirms that Neo's GitHub responses land in the same thread as the mention and bec…; source: repo:content/blog/neo-github-slack/index.md)
  • L41 in content/blog/neo-github-slack/index.md "Mentioning @pulumi-neo is supported in a pull request description, a top-level review comment, an inline review comment, or an issue." → ✅ verified (framing: strengthened — claim lists "a top-level review comment, an inline review comment" as two separate items vs. source's "a top-level or inline review comment"; sc…; evidence: Line 41 of the file reads: "Mention @pulumi-neo in a pull request description, a top-level or inline review comment, or an issue." The claim accurately captures all four supported locations (PR description, top-level review comment, inli…; source: repo:content/blog/neo-github-slack/index.md)
  • L47 in content/blog/neo-github-slack/index.md "Mentioning @Neo in any Slack channel where Neo has been added causes Neo to start a task in the thread." → ✅ verified (evidence: The blog post states verbatim: "Mention @Neo in any channel where Neo has been added, and Neo starts a task in the thread." This is an exact match to the claim.; source: repo:content/blog/neo-github-slack/index.md)
  • L47 in content/blog/neo-github-slack/index.md "Follow-up messages in Slack continue the conversation in the same thread." → ✅ verified (evidence: The blog post's "Neo in Slack" section states: "The reply lands in the same thread, and follow-up messages continue the conversation there." This directly confirms that follow-up messages in Slack continue the conversation in the same thre…; source: repo:content/blog/neo-github-slack/index.md)
  • L47 in content/blog/neo-github-slack/index.md "Neo has the same capabilities in Slack as in the Pulumi Cloud console or the terminal, including: checking stack state, investigating failures, walking through…" → ➖ not-a-claim (evidence: The blog post itself (content/blog/neo-github-slack/index.md) states: "Neo has the same capabilities here as in the Pulumi Cloud console or the terminal: check stack state, investigate failures, walk through what a change will do, or carry…; source: repo:content/blog/neo-github-slack/index.md)
  • L61 in content/blog/neo-github-slack/index.md "Neo can edit a stack's Pulumi program, run pulumi preview to confirm the change, and open a pull request with the diff and the preview output." → ➖ not-a-claim (evidence: The claim is a faithful paraphrase of the PR author's own blog post text at line ~61: "Neo edits the stack's Pulumi program, runs pulumi preview to confirm the change touches only the load balancer, and opens a pull request with the diff…; source: repo:content/blog/neo-github-slack/index.md)
  • L71 in content/blog/neo-github-slack/index.md "Neo runs with the RBAC permissions of the Pulumi Cloud user whose identity is linked, regardless of whether the conversation starts in GitHub or Slack." → ✅ verified (framing: strengthened — claim adds "whose identity is linked" as a narrowing qualifier; the source's broader "your Pulumi Cloud user" plus the linked-identity reference…; evidence: The blog post's "Permissions and governance" section states: "Whether the conversation starts in GitHub or Slack, Neo runs with the [RBAC permissions] of your Pulumi Cloud user." The "linked identity" framing is confirmed by the same secti…; source: repo:content/blog/neo-github-slack/index.md)
  • L71 in content/blog/neo-github-slack/index.md "Stack-level controls, organization-level guardrails, and audit logging apply to Neo tasks started from GitHub or Slack the same way they do for tasks started f…" → ✅ verified (evidence: The blog post's "Permissions and governance" section states: "Stack-level controls, organization-level guardrails, and audit logging apply the same way they do for a task started from the console. Starting a conversation in a new place doe…; source: repo:content/blog/neo-github-slack/index.md)
  • L71 in content/blog/neo-github-slack/index.md "RBAC permissions documentation is located at /docs/administration/access-identity/rbac/." → ✅ verified (evidence: The file content/docs/administration/access-identity/rbac/_index.md exists in the repo with title "Role-Based Access Control (RBAC)", confirming that RBAC documentation is located at /docs/administration/access-identity/rbac/.; source: repo:content/docs/administration/access-identity/rbac/_index.md)
  • L77 in content/blog/neo-github-slack/index.md "A Neo Integrations post exists at /blog/neo-integrations/ covering MCP servers and cloud CLIs that ship with this release." → ✅ verified (evidence: The file content/blog/neo-integrations/index.md exists with title "Neo Integrations: MCP Servers and Cloud CLIs" and covers both MCP server integrations (Atlassian, Datadog, Honeycomb, Linear, PagerDuty, Supabase) and cloud CLI integrati…; source: repo:content/blog/neo-integrations/index.md)
  • L77 in content/blog/neo-github-slack/index.md "The Neo CLI launch post is at /blog/pulumi-neo-cli/." → ✅ verified (evidence: The file content/blog/neo-github-slack/index.md links to /blog/pulumi-neo-cli/ as "the Neo CLI launch post", and content/blog/pulumi-neo-cli/index.md exists in the repo with the title "Neo, Now in the Terminal", confirming the path i…; source: repo:content/blog/pulumi-neo-cli/index.md)
  • L79 in content/blog/neo-github-slack/index.md "Feature requests for Pulumi Cloud can be filed at https://github.com/pulumi/pulumi-cloud-requests/issues/new/choose." → ✅ verified (evidence: The repo pulumi/pulumi-cloud-requests is public, has issues enabled, and its description reads "Welcome to the public issue tracker for Pulumi Cloud (app.pulumi.com)! Feature requests and bug reports welcome!" It also contains issue temp…; source: gh api repos/pulumi/pulumi-cloud-requests)
  • L5 in content/docs/ai/code-reviews/_index.md "Neo Code Reviews analyzes pull requests against what Pulumi Cloud knows about your running infrastructure and leaves its feedback in the pull request." (also L24) → ✅ verified (evidence: The file content/docs/ai/code-reviews/_index.md contains the exact sentence: "Neo Code Reviews analyzes pull requests against what Pulumi Cloud knows about your running infrastructure and leaves its feedback in the pull request." — appea…; source: repo:content/docs/ai/code-reviews/_index.md)
  • L8-10 in content/docs/ai/code-reviews/_index.md "- /docs/pulumi-cloud/neo/code-reviews/" → ✅ verified (evidence: The file content/docs/ai/code-reviews/_index.md contains - /docs/pulumi-cloud/neo/code-reviews/ in its aliases frontmatter list, and no separate file exists at that path, confirming it is a valid redirect alias.; source: repo:content/docs/ai/code-reviews/_index.md)
  • L11 in content/docs/ai/code-reviews/_index.md "- /docs/ai/integrations/github/" → ✅ verified (evidence: The file content/docs/ai/code-reviews/_index.md contains - /docs/ai/integrations/github/ in its aliases frontmatter block, confirming the URL exists as a valid alias for this page.; source: repo:content/docs/ai/code-reviews/_index.md)
  • L21 in content/docs/ai/code-reviews/_index.md "Neo Code Reviews is in public preview and becomes generally available on July 1, 2026." → ✅ verified (evidence: The file at content/docs/ai/code-reviews/_index.md contains exactly at line 21 (inside a {{% notes type="info" %}} block): "Neo Code Reviews is in public preview and becomes generally available on July 1, 2026."; source: repo:content/docs/ai/code-reviews/_index.md; intuition: A specific future GA date (July 1, 2026) is an unusual commitment to publish in docs; if this date is aspirational or s…)
  • L24 in content/docs/ai/code-reviews/_index.md "Neo Code Reviews reads the pulumi preview output and comments inline on the specific lines that need attention." → ✅ verified (evidence: The file at line 24 reads: "It reads the pulumi preview output and comments inline on the specific lines that need attention." This is an exact match to the claim.; source: repo:content/docs/ai/code-reviews/_index.md)
  • L24 in content/docs/ai/code-reviews/_index.md "Neo Code Reviews analyzes pull requests against what Pulumi Cloud knows about your running infrastructure and leaves its feedback in the pull request." → ✅ verified (evidence: The exact sentence appears verbatim in the file at line 24: "Neo Code Reviews analyzes pull requests against what Pulumi Cloud knows about your running infrastructure and leaves its feedback in the pull request." It also appears in the `me…; source: repo:content/docs/ai/code-reviews/_index.md)
  • L28 in content/docs/ai/code-reviews/_index.md "By default, Neo reviews every pull request automatically, skipping drafts and pull requests opened by bots." → ✅ verified (evidence: The file content/docs/ai/code-reviews/_index.md at line 28 reads verbatim: "By default, Neo reviews every pull request automatically, skipping drafts and pull requests opened by bots." — an exact match to the claim.; source: repo:content/docs/ai/code-reviews/_index.md)
  • L32 in content/docs/ai/code-reviews/_index.md "Neo can be mentioned in a pull request description, a review comment (top-level or inline), or an issue, and Neo replies in the same thread." → ✅ verified (evidence: The file states: "Mention it in a pull request description, a review comment (top-level or inline), or an issue, and Neo replies in the same thread." This is an exact match to the claim.; source: repo:content/docs/ai/code-reviews/_index.md)
  • L32 in content/docs/ai/code-reviews/_index.md "Neo can be scoped to review only when someone mentions @pulumi-neo, instead of automatically." → ✅ verified (evidence: The file at content/docs/ai/code-reviews/_index.md states under "Manual reviews": "You can scope Neo to review only when someone mentions @pulumi-neo, instead of automatically." — an exact match to the claim.; source: repo:content/docs/ai/code-reviews/_index.md)
  • L32 in content/docs/ai/code-reviews/_index.md "Neo can walk through what a change does, including resources that change in stacks the pull request does not modify directly." → ✅ verified (evidence: The file at content/docs/ai/code-reviews/_index.md states in the "Manual reviews" section: "Ask it to walk through what a change does, including resources that change in stacks the pull request does not modify directly." This is an exact…; source: repo:content/docs/ai/code-reviews/_index.md)
  • L34 in content/docs/ai/code-reviews/_index.md "Users who did not sign in to Pulumi with GitHub must link a GitHub identity to their Pulumi account via /docs/administration/organizations-teams/accounts/#addi…" → ✅ verified (evidence: The code-reviews page (L34) states: "If you signed in to Pulumi with GitHub, that link already exists; otherwise, link a GitHub identity to your Pulumi account." T…; source: repo:content/docs/ai/code-reviews/_index.md and repo:content/docs/administration/organizations-teams/accounts.md)
  • L38 in content/docs/ai/code-reviews/_index.md "If Neo already posts preview summaries on pull requests, Neo Code Reviews replaces them." → ✅ verified (evidence: The source file content/docs/ai/code-reviews/_index.md contains the exact statement in the Availability section: "If Neo already posts preview summaries on your pull requests, Neo Code Reviews replaces them."; source: repo:content/docs/ai/code-reviews/_index.md)
  • L42-45 in content/docs/ai/code-reviews/_index.md "Granting Pulumi access to your GitHub account requires completing the individual OAuth flow under Management > Version control, referenced at /docs/integration…" → ✅ verified (framing: strengthened — the anchor #individual-user-setup maps to the "Individual user authentication" section in the GitHub App page; the navigation path "Management…; evidence: The file content/docs/ai/code-reviews/_index.md at lines 42-45 states: "Grant Pulumi access to your GitHub account by completing the individual OAuth flow under **Ma…; source: repo:content/docs/ai/code-reviews/_index.md; repo:content/docs/integrations/version-control/github-app.md)
  • L49 in content/docs/ai/code-reviews/_index.md "Neo Code Reviews runs with the same governance as any other Neo task, including the role-based access control, guardrails, and audit logging the organization h…" → ✅ verified (evidence: The code-reviews page states: "Neo Code Reviews runs with the same governance as any other Neo task: the role-based access control, guardrails, and audit logging your organization has configured." The tasks page at /docs/ai/tasks/ confirms…; source: repo:content/docs/ai/code-reviews/_index.md and repo:content/docs/ai/tasks/_index.md)
  • L5 in content/docs/ai/integrations/_index.md "Neo integrations connect the agent to MCP context sources, cloud CLIs, GitHub, and Slack." → ✅ verified (evidence: The file's frontmatter at line 5 reads: meta_desc: Neo integrations connect the agent to MCP context sources, cloud CLIs, GitHub, and Slack. — an exact match to the claim.; source: repo:content/docs/ai/integrations/_index.md)
  • L27 in content/docs/ai/integrations/_index.md "Neo knows about your infrastructure footprint: your code, your stacks, and your state." → ✅ verified (framing: strengthened — claim omits "on its own" qualifier from source; source's broader form still proves the claim as a subset; evidence: The file at L27 reads: "Neo on its own knows about your infrastructure footprint: your code, your stacks, your state." The claim accurately captures the substance, with only minor omissions ("on its own") and a trivial conjunction addition…; source: repo:content/docs/ai/integrations/_index.md)
  • L29 in content/docs/ai/integrations/_index.md "Slack integration for Neo allows users to mention Neo from a Slack channel to start a task without switching to the Pulumi Cloud console." → ✅ verified (framing: strengthened — claim isolates the Slack-specific portion of a sentence that also covers GitHub/PR threads; source's broader form proves the Slack claim as a su…; evidence: The file content/docs/ai/integrations/_index.md states: "mention Neo from a PR thread or a Slack channel to start a task without switching to the Pulumi Cloud console." This directly confirms the claim about Slack integration for Neo.; source: repo:content/docs/ai/integrations/_index.md)
  • L29 in content/docs/ai/integrations/_index.md "CLI integrations cover what MCP doesn't reach (i.e., cloud-provider CLI access is not handled by MCP integrations)." → ✅ verified (evidence: The file at L29 states verbatim: "CLI integrations cover what MCP doesn't reach, calling out to cloud-provider CLIs against credentials managed in Pulumi ESC." The MCP integrations page confirms MCP covers issue trackers, observability pla…; source: repo:content/docs/ai/integrations/_index.md and repo:content/docs/ai/integrations/mcp/_index.md)
  • L31 in content/docs/ai/integrations/_index.md "All Neo integrations are configured at the organization level by an administrator." → ✅ verified (framing: strengthened — claim narrows 'All integrations' to 'All Neo integrations'; the page's Neo-specific context makes the source's broader form prove the claim as a…; evidence: The file states: "All integrations are configured at the organization level by an administrator." The claim adds "Neo" as a qualifier, but the entire page is about Neo integrations, making this a narrower restatement of the same truth.; source: repo:content/docs/ai/integrations/_index.md)
  • L31 in content/docs/ai/integrations/_index.md "Once a Neo integration is enabled, it is available to every Neo task in the organization." → ✅ verified (evidence: The file at L31 states: "All integrations are configured at the organization level by an administrator. Once enabled, they're available to every Neo task in the organization." This directly confirms the claim.; source: content/docs/ai/integrations/_index.md)
  • L26 in content/docs/ai/pull-requests/_index.md "Neo analyzes pull requests that a team opens and leaves its feedback directly in the PR." → ✅ verified (framing: strengthened — claim uses "a team" and "directly" vs source's "your team" and "right in the PR"; both convey the same meaning and the source's broader confirma…; evidence: The file at L26 states: "Neo also analyzes pull requests that your team opens and leaves its feedback right in the PR." The code-reviews page confirms: "Neo Code Reviews analyzes pull requests against what Pulumi Cloud knows about your run…; source: repo:content/docs/ai/pull-requests/_index.md and repo:content/docs/ai/code-reviews/_index.md)
  • L32 in content/docs/ai/pull-requests/_index.md "Without a VCS integration, Neo can still propose code changes, but they will not be fully contextualized to the IaC code." → ✅ verified (framing: strengthened — claim says "contextualized to the IaC code" while source says "contextualized to your IaC code"; the claim is a faithful narrower paraphrase of…; evidence: The file at content/docs/ai/pull-requests/_index.md states verbatim: "Without a VCS integration, Neo will not be able to view the IaC code backing a stack. Neo can still propose code changes, but they will not be fully contextualized to…; source: repo:content/docs/ai/pull-requests/_index.md)
  • L32 in content/docs/ai/pull-requests/_index.md "The Azure DevOps VCS integration documentation is available at /docs/integrations/version-control/azure-devops-integration/." → ✅ verified (evidence: The file content/docs/integrations/version-control/azure-devops-integration.md exists in the pulumi/docs repo with no custom URL override, so Hugo renders it at /docs/integrations/version-control/azure-devops-integration/. The PR file…; source: gh api repos/pulumi/docs/contents/content/docs/integrations/version-control/azure-devops-integration.md)
  • L36 in content/docs/ai/pull-requests/_index.md "When a stack is created, its git location is added as stack tags, and Neo uses these tags to locate and fetch the git repository." → ✅ verified (evidence: The file at content/docs/ai/pull-requests/_index.md under the "Code Access" heading reads verbatim: "When a stack is created, its git location is added as stack tags. Neo uses these tags to locate and fetch the git repository." The claim…; source: repo:content/docs/ai/pull-requests/_index.md)
  • L36 in content/docs/ai/pull-requests/_index.md "Neo uses stack tags to locate and fetch the git repository." → ✅ verified (evidence: The file at L36 states: "When a stack is created, its git location is added as stack tags. Neo uses these tags to locate and fetch the git repository." This is an exact match for the claim.; source: content/docs/ai/pull-requests/_index.md, lines 35-36)
  • L40-46 in content/docs/ai/pull-requests/_index.md "Neo opens a PR with: a clear title describing the change, a description of what problem it solves, a list of modified resources, a preview output summary, and…" → ✅ verified (evidence: The file at content/docs/ai/pull-requests/_index.md states: "Neo opens a PR with: Clear title describing the change, Description of what problem it solves, List of modified resources, Preview output summary, Link back to the Neo task" —…; source: repo:content/docs/ai/pull-requests/_index.md)
  • L40-46 in content/docs/ai/pull-requests/_index.md "Neo opens a PR with a clear title describing the change." → ✅ verified (evidence: The file at lines ~40-46 states: "Neo opens a PR with: - Clear title describing the change - Description of what problem it solves - List of modified resources - Preview output summary - Link back to the Neo task." The claim accurately ref…; source: repo:content/docs/ai/pull-requests/_index.md)
  • L40-46 in content/docs/ai/pull-requests/_index.md "Neo opens a PR with a description of what problem it solves." → ✅ verified (evidence: The file at lines ~40-46 states: "Neo opens a PR with: ... Description of what problem it solves ..." confirming the claim exactly.; source: repo:content/docs/ai/pull-requests/_index.md)
  • L52 in content/docs/ai/pull-requests/_index.md "When reviewing Neo's pull requests, users can ask for modifications through follow-up prompting, and Neo understands context from both the PR and the conversat…" → ✅ verified (evidence: The file contains the exact passage: "When reviewing Neo's pull requests, you can ask for modifications through follow-up prompting. Neo understands context from both the PR and your conversation history." — this directly matches the claim.; source: repo:content/docs/ai/pull-requests/_index.md)
  • L52 in content/docs/ai/pull-requests/_index.md "Neo understands context from both the PR and the user's conversation history when processing modification requests." → ✅ verified (framing: strengthened — claim adds "when processing modification requests" as context, which is implied by the surrounding paragraph about follow-up prompting for modif…; evidence: The file at line ~52 (under "Requesting Changes") states: "Neo understands context from both the PR and your conversation history." This directly matches the claim that Neo understands context from both the PR and the user's conversation h…; source: repo:content/docs/ai/pull-requests/_index.md)
  • L56 in content/docs/ai/pull-requests/_index.md "When configured, Pulumi previews will run automatically on Neo's PRs." → ✅ verified (framing: strengthened — claim narrows 'your Pulumi previews, security scans, policy checks, and tests will run automatically on Neo's PRs' to just 'Pulumi previews will…; evidence: The file at L56 states: "When configured, your Pulumi previews, security scans, policy checks, and tests will run automatically on Neo's PRs, just like any other pull request." The claim correctly captures the Pulumi previews portion of th…; source: repo:content/docs/ai/pull-requests/_index.md)
  • L56 in content/docs/ai/pull-requests/_index.md "If a CI/CD workflow fails on a Neo PR, the user can ask Neo to address the specific issue and it will push fixes to the same PR." → ✅ verified (evidence: The file states verbatim: "If a workflow fails, you can ask Neo to address the specific issue, and it will push fixes to the same PR." This exactly matches the claim.; source: content/docs/ai/pull-requests/_index.md)
  • L56 in content/docs/ai/pull-requests/_index.md "Neo's pull requests can automatically trigger existing CI/CD workflows, including Pulumi previews, security scans, policy checks, and tests." → ✅ verified (evidence: The file at L56 (CI/CD integration section) states: "Neo's pull requests can automatically trigger your existing CI/CD workflows. When configured, your Pulumi previews, security scans, policy checks, and tests will run automatically on Neo…; source: repo:content/docs/ai/pull-requests/_index.md)
  • L58 in content/docs/ai/pull-requests/_index.md "CI/CD setup documentation for Azure DevOps Pipelines is available at /docs/iac/operations/continuous-delivery/azure-devops/." → ✅ verified (evidence: The file content/docs/iac/operations/continuous-delivery/azure-devops.md exists in the pulumi/docs repo, and the PR's source file at L58 links to it as [Azure DevOps Pipelines](/docs/iac/operations/continuous-delivery/azure-devops/). I…; source: gh api repos/pulumi/docs/contents/content/docs/iac/operations/continuous-delivery)
  • L26 in content/docs/integrations/version-control/github-app.md "Pulumi's GitHub app displays the results of Pulumi stack update previews in pull requests and enables automatic stack deployments via Pulumi Deployments." → ✅ verified (evidence: The file at content/docs/integrations/version-control/github-app.md contains the exact claim text verbatim at line 26: "Pulumi's GitHub app displays the results of Pulumi stack update previews in pull requests and enables automatic stack…; source: repo:content/docs/integrations/version-control/github-app.md)
  • L29 in content/docs/integrations/version-control/github-app.md "The Pulumi GitHub app requires Pulumi Cloud as the stack's backend and does not work with self-managed (DIY) backends." → ✅ verified (evidence: The file at L29 contains an info note that reads: "The GitHub app requires Pulumi Cloud as your stack's backend. It does not work with self-managed backends." This dire…; source: repo:content/docs/integrations/version-control/github-app.md)
  • L35 in content/docs/integrations/version-control/github-app.md "To install the GitHub app, the user must have admin permissions in both the target GitHub organization and the Pulumi organization." → ✅ verified (evidence: The file at L35 contains an info note that reads: "To install the GitHub app, you must have admin permissions in both the target GitHub organization and the Pulumi organization. This is required to establish the correct connection betw…; source: repo:content/docs/integrations/version-control/github-app.md)
  • L45 in content/docs/integrations/version-control/github-app.md "Multiple GitHub organizations can be connected to a single Pulumi organization via Management > Version control > Add account." → ✅ verified (evidence: The file at content/docs/integrations/version-control/github-app.md contains: "Multiple GitHub organizations can be connected to a single Pulumi organization. You can add each one via Management > Version control > Add account.…; source: repo:content/docs/integrations/version-control/github-app.md)
  • L48 in content/docs/integrations/version-control/github-app.md "Mapping a single GitHub organization to multiple Pulumi organizations requires contacting Pulumi support and is only available for Enterprise and Business Crit…" → ✅ verified (evidence: The file at line 48 contains a note block that reads: "Mapping a single GitHub organization to multiple Pulumi organizations requires contacting Pulumi support. This option is only available for Enterpris…; source: repo:content/docs/integrations/version-control/github-app.md)
  • L53 in content/docs/integrations/version-control/github-app.md "Only one GitHub Enterprise Server integration is supported per Pulumi organization." → ✅ verified (evidence: The file at content/docs/integrations/version-control/github-app.md contains the exact sentence under the "GitHub Enterprise Server support" section: "Only one GitHub Enterprise Server integration is supported per Pulumi organization."; source: repo:content/docs/integrations/version-control/github-app.md)
  • L57 in content/docs/integrations/version-control/github-app.md "When individual user authentication is enabled for GitHub Enterprise Server, pull requests, commits, and comments are attributed to the individual user rather…" → ✅ verified (framing: strengthened — claim narrows the source's fuller description to the specific attribution behavior; source's broader form proves the claim as a subset.; evidence: The file at content/docs/integrations/version-control/github-app.md states: "By default, Pulumi performs all GitHub Enterprise Server operations as the shared GitHub app installation. When individual user authentication is enabled, operati…; source: repo:content/docs/integrations/version-control/github-app.md)
  • L59 in content/docs/integrations/version-control/github-app.md "The individual user authentication setting applies only to self-hosted GitHub Enterprise Server integrations; GitHub.com integrations always use the shared app…" → ✅ verified (evidence: The file states verbatim: "This setting applies only to self-hosted GitHub Enterprise Server integrations. GitHub.com integrations always use the shared app installation and ignore the setting." This exactly matches the claim.; source: repo:content/docs/integrations/version-control/github-app.md (section "Individual user authentication for GitHub Enterprise Server"))
  • L59 in content/docs/integrations/version-control/github-app.md "GitHub.com integrations always use the shared app installation and ignore the individual user authentication setting." → ✅ verified (evidence: The file at content/docs/integrations/version-control/github-app.md states verbatim: "GitHub.com integrations always use the shared app installation and ignore the setting." — where "the setting" refers to the individual user authenticatio…; source: repo:content/docs/integrations/version-control/github-app.md)
  • L63 in content/docs/integrations/version-control/github-app.md "Only organization admins can change the individual user authentication setting." → ✅ verified (evidence: The file at content/docs/integrations/version-control/github-app.md under the "Enable individual user authentication" section states verbatim: "Only organization admins can change this setting."; source: repo:content/docs/integrations/version-control/github-app.md)
  • L68 in content/docs/integrations/version-control/github-app.md "Organization admins can see who has connected a GitHub Enterprise account in the organization's member list, which shows a 'GitHub Enterprise' column while any…" → ✅ verified (framing: strengthened — claim expands "the setting" to "the individual user authentication setting"; source's context makes this unambiguous and the claim is a narrower…; evidence: The file at the relevant section states: "Organization admins can see who has connected an account in the organization's member list, which shows a GitHub Enterprise column while any integration has the setting enabled." The claim accu…; source: repo:content/docs/integrations/version-control/github-app.md)
  • L72 in content/docs/integrations/version-control/github-app.md "Any organization member can connect their own GitHub Enterprise account; admin permissions are not required." → ✅ verified (evidence: The file states verbatim: "Any organization member can connect their own account; admin permissions are not required." in the "Connect your GitHub Enterprise account" section, which directly matches the claim.; source: repo:content/docs/integrations/version-control/github-app.md)
  • L74 in content/docs/integrations/version-control/github-app.md "A user's GitHub Enterprise account is linked per GitHub Enterprise host, not per Pulumi organization; connecting or disconnecting it also applies to any other…" → ✅ verified (evidence: The file contains the exact statement: "Your account is linked per GitHub Enterprise host, not per Pulumi organization. Connecting or disconnecting it also applies to any other Pulumi organization that uses the same GitHub Enterprise serve…; source: repo:content/docs/integrations/version-control/github-app.md)
  • L74 in content/docs/integrations/version-control/github-app.md "GitHub Enterprise tokens refresh automatically; if authorization expires or is revoked, operations prompt the user to reconnect." → ✅ verified (evidence: The file at L74 context (within the "Connect your GitHub Enterprise account" section) states: "Tokens refresh automatically; if your authorization expires or is revoked, operations prompt you to reconnect." This directly matches the claim.; source: repo:content/docs/integrations/version-control/github-app.md)
  • L82-85 in content/docs/integrations/version-control/github-app.md "When individual user authentication is enabled, deployments triggered by pushes and pull requests authenticate as the GitHub Enterprise user who triggered the…" → ✅ verified (evidence: The file's "How operations authenticate" table (under the individual user authentication section) states exactly: "Deployments triggered by pushes and pull requests | The GitHub Enterprise user who triggered the event, when that user has c…; source: repo:content/docs/integrations/version-control/github-app.md)
  • L89 in content/docs/integrations/version-control/github-app.md "If the Pulumi GitHub App was created before the individual user authentication feature was available, the OAuth callback URL is not registered, and members who…" → ✅ verified (evidence: The file at the relevant section states: "If your Pulumi GitHub App was created before this feature was available, the callback URL is not registered, and members who try to connect their account will see an error on your GitHub Enterprise…; source: repo:content/docs/integrations/version-control/github-app.md)
  • L95 in content/docs/integrations/version-control/github-app.md "The OAuth callback URL format for individual user authentication on GitHub Enterprise is: https://api.pulumi.com/workflow/github-enterprise//call…" (also L99) → ✅ verified (evidence: The file at content/docs/integrations/version-control/github-app.md explicitly states: "Determine your callback URL: https://api.pulumi.com/workflow/github-enterprise/<ghe-hostname>/callback" in the context of individual user authenticat…; source: repo:content/docs/integrations/version-control/github-app.md)
  • L99 in content/docs/integrations/version-control/github-app.md "For a GitHub Enterprise server at https://ghe.example.com, the callback URL is https://api.pulumi.com/workflow/github-enterprise/ghe.example.com/callback." → ✅ verified (evidence: The file explicitly states: "Replace <ghe-hostname> with the hostname of your GitHub Enterprise server... For example, for https://ghe.example.com: https://api.pulumi.com/workflow/github-enterprise/ghe.example.com/callback"; source: repo:content/docs/integrations/version-control/github-app.md)
  • L105 in content/docs/integrations/version-control/github-app.md "Pulumi handles both expiring and non-expiring GitHub Enterprise user authorization tokens; the user does not need to change the 'Expire user authorization toke…" → ✅ verified (evidence: The file at content/docs/integrations/version-control/github-app.md contains the exact text (decoded from base64): "You do not need to change the Expire user authorization tokens setting. Pulumi handles both expiring and non-expiring…; source: repo:content/docs/integrations/version-control/github-app.md)
  • L117 in content/docs/integrations/version-control/github-app.md "Individual users can complete an OAuth flow under Management > Version control to grant Pulumi access to their personal GitHub account; the integration card sh…" → 🤷 unverifiable (evidence: The file content was cut off before line 117 and does not contain the specific UI status strings ("Individual access is authorized for this account" / "Individual access is recommended for this account") or an "Add Individual Account" butt…; source: repo:content/docs/integrations/version-control/github-app.md; intuition: The file explicitly says "GitHub.com integrations always use the shared app installation" — an individual OAuth flow fo…)
  • L119 in content/docs/integrations/version-control/github-app.md "Triggering a Neo code review requires individual access." → ❌ contradicted (framing: shifted — the source associates individual access with Neo creating repositories, not with triggering Neo code reviews; the claim attributes a different capabi…; evidence: (escalated from pass1) The official docs state "Individual access lets Pulumi create repositories on your behalf — for example, cloning project templates into a new repository or letting Neo create a repository for you." Neo Code Reviews a…; source: https://www.pulumi.com/docs/integrations/version-control/github-app/)
  • L119 in content/docs/integrations/version-control/github-app.md "Individual access lets Pulumi create repositories on the user's behalf — for example, cloning project templates into a new repository or letting Neo create a r…" → ➖ not-a-claim (evidence: The text at L119 is in the github-app.md file itself (a table describing how operations authenticate under individual user authentication), and the claim is a faithful description of the PR author's own content/design — specifically the ta…; source: repo:content/docs/integrations/version-control/github-app.md)
  • L129 in content/docs/integrations/version-control/github-app.md "The 'Neo Code Reviews' integration setting is enabled by default and includes Neo's AI-generated review of infrastructure changes in pull request comments, req…" (also L134-136) → ✅ verified (evidence: The file content/docs/integrations/version-control/github-app.md contains exactly: "| Neo Code Reviews | Enabled | Include Neo's AI-generated review of infrastructure changes in pull request comments (requires [Pulumi Neo](/docs/ai/get-s…; source: gh search code --owner pulumi "Neo Code Reviews" → pulumi/docs:content/docs/integrations/version-control/github-app.md)
  • L144 in content/docs/integrations/version-control/github-app.md "The Pulumi GitHub app automatically adds comments to pull requests with the results of any stack changes, including a summary of how many resources were create…" → ✅ verified (framing: strengthened — the source broadly describes showing "results of Pulumi stack update previews in pull requests"; the claim narrows this to the specific mechanis…; evidence: The current github-app.md file confirms the app "displays the results of Pulumi stack update previews in pull requests" and shows "any potential infrastructure changes on pull requests and commit checks." The specific claim about PR commen…; source: repo:content/docs/integrations/version-control/github-app.md)
  • L146 in content/docs/integrations/version-control/github-app.md "When pulumi preview or pulumi up is run, the Pulumi CLI examines the closest .git directory to extract commit metadata (such as the commit SHA, branch na…" → ✅ verified (framing: strengthened — the source confirms the walk-up-to-.git mechanism broadly; the claim correctly narrows this to the specific context of pulumi preview/pulumi…; evidence: The Pulumi CLI's GetGitRepositoryfunction insdk/go/common/util/gitutil/git.gousesWalkUpto find the closest.git` directory (walking up from the current directory), then opens the repository to extract metadata. The function com…; source: gh api repos/pulumi/pulumi/contents/sdk/go/common/util/gitutil/git.go (blob sha 9eb0a81d98f8293f116a9b5b29c0b268a23620ed))
  • L146 in content/docs/integrations/version-control/github-app.md "Commit metadata extracted by the Pulumi CLI is included with the update and sent to Pulumi Cloud, which uses it to identify the associated pull request and pos…" → 🤷 unverifiable (evidence: verification did not converge within 8 turns)
  • L149 in content/docs/integrations/version-control/github-app.md "When pull request comments are disabled in integration settings, the GitHub app does not post comments on pull requests but still reports check run statuses vi…" → 🤷 unverifiable (evidence: verification did not converge within 8 turns)
  • L154 in content/docs/integrations/version-control/github-app.md "The GitHub Checks API integration provides detail about resource changes, including the full update log." → 🤷 unverifiable (evidence: verification did not converge within 8 turns)
  • L156 in content/docs/integrations/version-control/github-app.md "All Pulumi stack updates are reported to the GitHub Checks API." → 🤷 unverifiable (evidence: verification did not converge within 8 turns)
  • L160 in content/docs/integrations/version-control/github-app.md "Push-to-deploy automatically runs pulumi up when a commit is pushed to a configured branch, most commonly the main branch." → ✅ verified (framing: strengthened — the source specifies the trigger is specifically merge commits/PR merges to a branch; the claim generalizes this as "a commit is pushed to a con…; evidence: The triggers.md file states Push to Deploy can "run pulumi up when a Pull Request is merged" to a particular git branch, and the integration "listen[s] to merge commits to automatically trigger deployments on git push." The claim's des…; source: repo:content/docs/deployments/deployments/using/triggers.md)
  • L162 in content/docs/integrations/version-control/github-app.md "Pulumi Deployments supports deploying on git tag pushes using tag triggers — for example, on every v* release tag." → 🤷 unverifiable (evidence: verification did not converge within 8 turns)
  • L166 in content/docs/integrations/version-control/github-app.md "When a pull request is opened with review stacks configured, Pulumi Deployments stands up a stack with the changes and adds a PR comment with the outputs from…" → ✅ verified (framing: strengthened — claim adds "with review stacks configured" as qualifying context, which is accurate given the source page is specifically about review stacks; o…; evidence: The review stacks documentation states: "When a pull request is opened, Pulumi Deployments stands up a stack with your changes and adds a comment to the PR with the outputs from your deployment." This directly matches the claim's descripti…; source: repo:content/docs/deployments/deployments/review-stacks.md)
  • L170 in content/docs/integrations/version-control/github-app.md "The GitHub app only requires that code is hosted on GitHub and that pull requests are used to manage changes; it does not require GitHub Actions." → ✅ verified (evidence: (escalated from pass1) The official Pulumi docs page states: "The GitHub app only requires that your code is hosted on GitHub and that you use pull requests to manage changes. It does not require GitHub Actions — any CI/CD system works."; source: https://www.pulumi.com/docs/integrations/version-control/github-app/)
  • L170 in content/docs/integrations/version-control/github-app.md "The GitHub app does not require GitHub Actions; any CI/CD system works, including GitHub Actions, CircleCI, Jenkins, Pulumi Deployments, or any other system." → 🤷 unverifiable (evidence: verification did not converge within 8 turns)
  • L178 in content/docs/integrations/version-control/github-app.md "Uninstalling the GitHub app from Pulumi Cloud (via Management > Version control) automatically removes the app from GitHub as well." → ✅ verified (evidence: (escalated from pass1) The official Pulumi docs state: "From Pulumi Cloud: Navigate to Management > Version control, select your GitHub organization, and select Uninstall. This automatically removes the app from GitHub as well."; source: https://www.pulumi.com/docs/integrations/version-control/github-app/)
  • L182 in content/docs/integrations/version-control/github-app.md "Uninstalling the GitHub app will delete any push-to-deploy and review stack configurations that have been set up." → ✅ verified (evidence: The source file contains: "Uninstalling the GitHub app will delete any push-to-deploy and review stack configurations you have set up." The claim's phrasing ("that have been set up") is a trivial paraphrase of the source's "you have set up…; source: gh search code --owner pulumi "Uninstalling the GitHub app will delete any push-to-deploy" → pulumi/docs:content/docs/integrations/version-control/github-app.md)
  • L16-17 in content/pricing/_index.md "The Individual tier of Pulumi Cloud is priced at $0 (free forever for individuals)." → ✅ verified (evidence: The file content/pricing/_index.md explicitly lists the Individual tier with price: $0 and subtitle: Free forever for individuals., directly matching the claim.; source: repo:content/pricing/_index.md)
  • L28-33 in content/pricing/_index.md "The Individual tier of Pulumi Cloud includes Pulumi Neo with 5 million free tokens per month." → ✅ verified (evidence: The pricing file at content/pricing/_index.md lists the Individual tier features as including "Pulumi Neo with 5M free tokens/mo", directly confirming the claim of 5 million free tokens per month.; source: repo:content/pricing/_index.md)
  • L36-39 in content/pricing/_index.md "The Team tier of Pulumi Cloud is priced at $40/month, includes 500 resources, and charges $0.1825/month for additional resources." → ✅ verified (evidence: The file content/pricing/_index.md explicitly states for the Team tier: price: $40, price_label: /mo, unit: "**500** resources included", and note: Additional resources $0.1825/mo — all three numerical values match the claim exac…; source: repo:content/pricing/_index.md)
  • L46 in content/pricing/_index.md "The Team tier of Pulumi Cloud supports up to 10 users." → ✅ verified (evidence: The pricing page file explicitly lists "Up to 10 users" as a feature of the Team tier, directly matching the claim.; source: repo:content/pricing/_index.md)
  • L48 in content/pricing/_index.md "The Team tier of Pulumi Cloud includes Neo Code Reviews and Slack integration." → ✅ verified (evidence: The pricing page at content/pricing/_index.md lists the Team tier features, which explicitly includes "Neo Code Reviews and Slack integration" as one of the bullet points under "Everything in Individual, plus:".; source: repo:content/pricing/_index.md)
  • L50 in content/pricing/_index.md "The Pulumi Team plan includes OIDC and Org Access Tokens." → ✅ verified (evidence: The Team plan's features list in content/pricing/_index.md explicitly includes "OIDC and Org Access Tokens" as a bullet point under the Team tier's features.; source: repo:content/pricing/_index.md)
  • L52 in content/pricing/_index.md "The Pulumi Team plan includes automatic secrets rotation." → ✅ verified (evidence: The pricing page file explicitly lists "Automatic secrets rotation" as one of the features under the Team plan's features list: "Everything in Individual, plus: ... Automatic secrets rotation ..."; source: content/pricing/_index.md)
  • L57-60 in content/pricing/_index.md "The Enterprise tier of Pulumi Cloud is priced at $400/month, includes 2,000 resources, and charges additional resources starting at $0.365/month." → ✅ verified (evidence: The file content/pricing/_index.md explicitly states for the Enterprise tier: price: $400, price_label: /mo, unit: "**2,000** resources included", and note: Additional resources start at $0.365/mo — matching all three values in t…; source: repo:content/pricing/_index.md)
  • L70-73 in content/pricing/_index.md "The Pulumi Enterprise plan includes an internal developer platform (IDP)." → ✅ verified (evidence: The pricing page explicitly lists "Internal developer platform (IDP)" as one of the features under the Enterprise plan's features section, alongside SAML/SSO, RBAC, audit logs, drift detection, etc.; source: repo:content/pricing/_index.md)
  • L75-77 in content/pricing/_index.md "The Pulumi Enterprise plan includes drift detection and remediation." → ✅ verified (evidence: The pricing page file explicitly lists "Drift detection and remediation" as a feature under the Enterprise plan's features list (in the trialed.items section for the Enterprise tier).; source: repo:content/pricing/_index.md)

@github-actions

github-actions Bot commented Jun 16, 2026

Copy link
Copy Markdown
Contributor
continued from previous comment
  • L79 in content/pricing/_index.md "The Pulumi Enterprise plan includes 12x5 Enterprise Support (available as an add-on)." → ❌ contradicted (framing: shifted — source says "12x5 Enterprise Support available"; claim adds "available as an add-on" which is not stated in the source; evidence: The file at content/pricing/_index.md lists the Enterprise plan feature as "12x5 Enterprise Support available" — there is no mention of it being "available as an add-on." The claim adds the qualifier "as an add-on" which is not present…; source: repo:content/pricing/_index.md)
  • L93-94 in content/pricing/_index.md "The Business Critical tier of Pulumi Cloud includes built-in compliance for NIST, PCI, and more." → ✅ verified (evidence: The pricing page file at content/pricing/_index.md lists under the Business Critical tier's features: "Built-in compliance (NIST, PCI, and more)", which exactly matches the claim.; source: repo:content/pricing/_index.md)
  • L98 in content/pricing/_index.md "The Pulumi Business Critical plan includes 24x7 Enterprise Support (available as an add-on)." → ❌ contradicted (framing: shifted — source says "24x7 Enterprise Support available" (included feature); claim reframes it as "available as an add-on," implying it is optional/extra-cost…; evidence: The file at content/pricing/_index.md lists "24x7 Enterprise Support available" as a Business Critical feature, with no mention of it being "an add-on." The claim's parenthetical "(available as an add-on)" is not supported by the source…; source: repo:content/pricing/_index.md)
  • L107 in content/pricing/_index.md "Unity achieved 5x faster time to market using Pulumi." → ❌ contradicted (framing: shifted — the "5x faster time to market" figure is attributed to Unity, but the Unity case study does not contain this metric; the "5x faster" figure appears i…; evidence: The Unity case study at pulumi.com/case-studies/unity/ describes Unity Aura "reducing provisioning times and costs" and that "modernization accelerated development cycles," but contains no "5x faster time to market" claim. A separate Pulum…; source: https://www.pulumi.com/case-studies/unity/)
  • L110 in content/pricing/_index.md "Starburst saved 100 days each year with Pulumi Cloud instead of DIY state management." → ✅ verified (framing: strengthened — the case study gives a range ("one to two days a week" for 2 engineers) from which "100 days" is derived; the pricing page presents this as a pr…; evidence: The Starburst case study states "On average, it took 2 engineers one to two days a week" to manage the DIY S3 state backend, which yields ~100 engineer-days/year (2 engineers × 1 day/week × 50 weeks). The pricing page's "100 days saved eac…; source: repo:content/case-studies/starburst.md)
  • L113 in content/pricing/_index.md "Snowflake achieved 10x faster deployments, going from weeks to hours, using Pulumi." → ❌ contradicted (framing: shifted — source says "1.5 weeks → under 1 day"; claim says "10x faster, weeks to hours" — the magnitude and the time-unit framing both differ from the source; evidence: The cited source (pulumi.com/case-studies/snowflake/) states "1.5 weeks > 1 day · reduced deployment time" — i.e., from ~1.5 weeks to under a day, not "weeks to hours." The "10x faster" figure appears only in a separate Pulumi blog post as…; source: https://www.pulumi.com/case-studies/snowflake/)
  • L131-134 in content/pricing/_index.md "The Team tier IaC on-demand resource price is $0.00025/hour ($0.185/month), and the Enterprise tier starts at $0.0005/hour ($0.365/month)." → ❌ contradicted (framing: shifted — claim states Team monthly rate as "$0.185/month" but the source gives "$0.1825 per resource per month"; the hourly rate ($0.00025) and Enterprise fig…; 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 claim's Team monthly f…; source: https://www.pulumi.com/pricing/)
  • L133-134 in content/pricing/_index.md "The Pulumi Enterprise plan on-demand IaC resource price starts at $0.0005/hour ($0.365/month)." → ✅ verified (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)." This exactly matches the c…; source: https://www.pulumi.com/pricing/)
  • L157-160 in content/pricing/_index.md "The Individual tier allows 1 concurrent stack update, the Team tier allows 5, and Enterprise and Business Critical allow unlimited concurrent stack updates." → ✅ verified (evidence: The official Pulumi pricing page lists: "Concurrent stack updates · 1 · 5 · Unlimited · Unlimited" for Individual, Team, Enterprise, and Business Critical tiers respectively.; source: https://www.pulumi.com/pricing/)
  • L241-243 in content/pricing/_index.md "The Team tier supports up to 10 members, while Enterprise and Business Critical support unlimited members." → ✅ verified (evidence: Pulumi's official FAQ states: "Pulumi Team is ideal for teams of up to 10 members" and "Pulumi Enterprise...offers an unlimited number of members." The official pricing blog also confirms: "Pulumi Team Edition supports up to 10 users, and…; source: https://www.pulumi.com/docs/support/pulumi-cloud-faq/ and https://www.pulumi.com/blog/announcing-new-usage-based-pricing-for-your-whole-team/)
  • L247 in content/pricing/_index.md "The Pulumi Team plan supports 1 admin." → ❌ contradicted (framing: shifted — the source says "1 Billing Manager" (a specific role); the claim says "1 admin" (a different, broader role), misidentifying the constrained role; evidence: Official Pulumi docs state "Team Editions of the Pulumi Cloud are limited to 1 Billing Manager at a time" — not "1 admin." The Team plan supports up to 10 members, and organization admins are not capped at 1; only the Billing Manager role…; source: https://www.pulumi.com/docs/administration/organizations-teams/billing-managers/)
  • L254-256 in content/pricing/_index.md "The Team tier supports 1 organization, while Enterprise and Business Critical support multiple organizations." → 🤷 unverifiable (evidence: No authoritative Pulumi source found that frames the Team tier as supporting "1 organization" vs. Enterprise/Business Critical supporting "multiple organizations." The official pricing page and FAQ describe organizational management differ…; source: WebSearch ran query "Pulumi pricing '1 organization' OR 'single organization' Team tier vs Enterprise multiple organizations"; top results (pulumi.com/pricing, pulumi.com/docs/support/pulumi-cloud-faq/) didn't address the specific claim.; intuition: The "1 organization vs. multiple organizations" framing is not a standard Pulumi pricing distinction; Pulumi's document…)
  • L260-263 in content/pricing/_index.md "Identity providers supported include GitHub, GitLab, and Atlassian for Individual and Team tiers, and additionally SAML/SSO for Enterprise and Business Critica…" → 🤷 unverifiable (evidence: verification did not converge within 8 turns)
  • L262 in content/pricing/_index.md "The Pulumi Enterprise plan supports GitHub, GitLab, Atlassian, and SAML/SSO as identity providers." → 🤷 unverifiable (evidence: verification did not converge within 8 turns)
  • L270-272 in content/pricing/_index.md "SAML/SSO providers supported include Microsoft Entra ID, Google Workspace, Okta, OneLogin, and more." → 🤷 unverifiable (evidence: verification did not converge within 8 turns)
  • L306-307 in content/pricing/_index.md "The Enterprise tier supports up to 25 custom roles, while Business Critical supports unlimited custom roles." → ✅ verified (framing: strengthened — the claim's specific "25 custom roles" cap for Enterprise and "unlimited" for Business Critical matches the third-party source's framing, though…; evidence: A May 2026 third-party pricing analysis of Pulumi states that Enterprise does not include "unlimited custom roles (capped at 25)" while Business Critical adds unlimited custom roles. The official Pulumi docs confirm custom roles are availa…; source: https://checkthat.ai/brands/pulumi/pricing — "unlimited custom roles (capped at 25)" listed as not included in Enterprise tier)
  • L355-360 in content/pricing/_index.md "The ESC on-demand secret price is 25 free for Individual, $0.000685/hour ($0.50/month) for Team, and $0.001/hour ($0.75/month) for Enterprise." → ✅ verified (evidence: The official Pulumi pricing page states: "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)." A third-party source also confirms "25 free sec…; source: https://www.pulumi.com/pricing/)
  • L369-372 in content/pricing/_index.md "ESC API calls are priced at $0.10 per 10K API calls for Team, Enterprise, and Business Critical tiers." → ✅ verified (framing: strengthened — claim narrows the rate to specific tiers (Team, Enterprise, Business Critical); source states the rate broadly without enumerating tiers, but th…; evidence: The official Pulumi pricing page states "Once you hit 10,000 API calls, you are metered at $0.1 for 10K API calls," directly confirming the $0.10 per 10K API calls rate. The tier scoping (Team, Enterprise, Business Critical) is consistent…; source: https://www.pulumi.com/pricing/)
  • L388-391 in content/pricing/_index.md "The Individual tier has a maximum of 25 ESC secrets; Team, Enterprise, and Business Critical have unlimited secrets." → ❌ contradicted (framing: shifted — source shows Team/Enterprise secrets are metered (pay-per-secret), not "unlimited"; the claim overstates paid-tier access as unlimited when it is act…; evidence: The official Pulumi pricing page confirms the free tier includes 25 secrets, but Team and Enterprise tiers are billed per secret at metered rates ("$0.50 per secret per month" for Team, "$0.75 per secret per month" for Enterprise) — not "u…; source: https://www.pulumi.com/pricing/)
  • L394-397 in content/pricing/_index.md "The Individual tier has a maximum of 10K ESC API calls per month; Team, Enterprise, and Business Critical have unlimited API calls." → ❌ contradicted (framing: shifted — the source describes a universal metered model (10K free, then $0.1/10K for all tiers); the claim incorrectly frames 10K as an Individual-only cap wi…; evidence: The official Pulumi pricing page states: "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." This is a universal metered model, not a…; source: https://www.pulumi.com/pricing/)
  • L475-478 in content/pricing/_index.md "The Pulumi Enterprise plan Insights on-demand resource price starts at $0.0005/hour ($0.365/month)." → ✅ verified (framing: shifted — source says "IaC resources" billed at $0.0005/hr for Enterprise; claim attributes this rate specifically to "Insights on-demand resource price," whic…; 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 numbers match the clai…; source: https://www.pulumi.com/pricing/)
  • L483-489 in content/pricing/_index.md "The Individual tier includes 500 free workflow minutes per month; Team, Enterprise, and Business Critical include 3,000 workflow minutes per month at $0.01 per…" → ✅ verified (framing: strengthened — the claim uses the broader term "workflow minutes" (which covers both Insights and Deployments per pulumi.com/pricing) while the source uses "de…; evidence: Official Pulumi Deployments page states: "Individual Edition has 500 deploy minutes/month" and "Team, Enterprise, and Business Critical Editions all have 3,000 included deploy minutes/month," with Pulumi Deployments costing "$0.01 per depl…; source: https://www.pulumi.com/product/pulumi-deployments/)
  • L501 in content/pricing/_index.md "The Pulumi Enterprise plan supports 10 primary accounts (or custom) for Insights." → 🤷 unverifiable (evidence: No authoritative source (pulumi.com/pricing, Pulumi docs, or any third-party source) mentions a "10 primary accounts" limit for Insights under the Enterprise plan. The official pricing page discusses resource billing and workflow minutes b…; source: WebSearch ran query "Pulumi pricing Enterprise Insights primary accounts 10"; top results didn't address the claim; intuition: The "10 primary accounts (or custom)" framing is suspiciously specific and mirrors the Team plan's 10-user cap — it may…)
  • L544 in content/pricing/_index.md "The Pulumi Business Critical plan pre-built policy packs include Pulumi Best Practices, CIS, NIST, HITRUST, and PCI DSS." → 🤷 unverifiable (evidence: verification did not converge within 8 turns)
  • L549-553 in content/pricing/_index.md "The Team tier supports up to 25 custom policies with a 1 pack limit; the Enterprise tier supports up to 100 policies with a 3 pack limit; Business Critical sup…" → ✅ verified (evidence: The official Pulumi pricing page (pulumi.com/pricing) lists exactly: "Up to 25 policies · 1 pack limit · Up to 100 policies · 3 pack limit · Unlimited" for Team, Enterprise, and Business Critical tiers respectively.; source: https://www.pulumi.com/pricing/)
  • L560 in content/pricing/_index.md "The Pulumi Business Critical plan supports Advisory, Mandatory, and Remediation enforcement modes." → 🤷 unverifiable (evidence: verification did not converge within 8 turns)
  • L569-573 in content/pricing/_index.md "The Individual tier includes 5M Pulumi Neo tokens per month for free; Team, Enterprise, and Business Critical are priced at $3 per million tokens." → 🤷 unverifiable (evidence: verification did not converge within 8 turns)
  • L574 in content/pricing/_index.md "MCP and CLI integrations for Pulumi Neo are available on all Pulumi plans (Individual, Team, Enterprise, and Business Critical)." (also L580-581, L587-588, L594-595, L601-602, L608) → 🤷 unverifiable (evidence: verification did not converge within 8 turns)
  • L574-608 in content/pricing/_index.md "Pulumi Neo features available across tiers: Neo in the CLI and MCP & CLI Integrations are available on all tiers; Neo Code Reviews and Slack integration are av…" → ✅ verified (evidence: The pricing page confirms: Individual tier includes "Pulumi Neo with 5M free tokens/mo" (base Neo/CLI access for all tiers); Team tier adds "Neo Code Reviews and Slack integration"; Enterprise tier adds "Neo scheduled tasks" (with Business…; source: repo:content/pricing/_index.md (tier feature lists) and repo:content/docs/ai/integrations/slack/_index.md)
  • L575 in content/pricing/_index.md "link: /docs/ai/pulumi-cli/" → ✅ verified (evidence: The file content/docs/ai/pulumi-cli/_index.md exists in the repository with title "Neo in the Pulumi CLI", confirming the internal link /docs/ai/pulumi-cli/ resolves to a real page.; source: repo:content/docs/ai/pulumi-cli/_index.md)
  • L582 in content/pricing/_index.md "link: /docs/ai/integrations/" → ✅ verified (evidence: The file content/docs/ai/integrations/_index.md exists in the repo and renders as the /docs/ai/integrations/ page, confirming the link target is valid.; source: repo:content/docs/ai/integrations/_index.md)
  • L589 in content/pricing/_index.md "link: /docs/ai/pull-requests/" → ✅ verified (evidence: The file content/docs/ai/pull-requests/_index.md exists in the repo with the title "Pull requests with Pulumi Neo", confirming the internal link /docs/ai/pull-requests/ resolves to a real page.; source: repo:content/docs/ai/pull-requests/_index.md)
  • L603 in content/pricing/_index.md "link: /docs/ai/automations/" → ✅ verified (evidence: The file content/docs/ai/automations/_index.md exists in the repository with a valid page definition (title: "Automations", menu identifier: "ai-automations"), confirming the internal link /docs/ai/automations/ resolves to a real page.; source: repo:content/docs/ai/automations/_index.md)
  • L626-627 in content/pricing/_index.md "Enterprise Support is available at 12x5 or 24x7 for the Pulumi Enterprise plan." → ❌ contradicted (framing: shifted — the source assigns 12x5 to Enterprise and 24x7 to Business Critical; the claim conflates both tiers as options within the Enterprise plan; evidence: The pricing page shows 12x5 Enterprise Support available under the Enterprise plan features, and 24x7 Enterprise Support available under the Business Critical plan features — not both options under Enterprise. The claim incorrectly att…; source: repo:content/pricing/_index.md)
  • L632-633 in content/pricing/_index.md "Enterprise and Business Critical tiers offer normal ticket SLAs of 1 or 5 business days." → 🤷 unverifiable (evidence: verification did not converge within 8 turns)
  • L638-639 in content/pricing/_index.md "Enterprise and Business Critical tiers offer urgent ticket SLAs of 4 hours to 2 business days." → 🤷 unverifiable (evidence: verification did not converge within 8 turns)
  • L689 in content/pricing/_index.md "The Pulumi Team plan includes 500 resources and the Enterprise plan includes 2,000 resources before overage charges apply." → ✅ verified (evidence: The official Pulumi pricing page states: "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 for the number of resource hours consumed in excess of what…; source: https://www.pulumi.com/pricing/)
  • L689-691 in content/pricing/_index.md "IaC resources are billed hourly at $0.00025 for Team ($0.1825 per resource per month) and starting at $0.0005 for Enterprise ($0.365 per resource per month)." → ✅ verified (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)." — an exact match to the cl…; source: https://www.pulumi.com/pricing/)
  • L695 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)
  • L695 in content/pricing/_index.md "Pulumi billing counts any resource declared in a Pulumi program, including provider resources (e.g., an Amazon S3 bucket), component resources (e.g., an Amazon…" → 🤷 unverifiable (evidence: verification did not converge within 8 turns)
  • L700 in content/pricing/_index.md "The Team edition's 500 included resources is described as sufficient to manage 500 EKS clusters or EC2 instances for a month, or a production Amazon EKS cluste…" → 🤷 unverifiable (evidence: verification did not converge within 8 turns)
  • L702 in content/pricing/_index.md "The Pulumi Enterprise edition comes with 2,000 resources included." → ✅ verified (evidence: The official Pulumi pricing page states: "The Enterprise edition comes with 2,000 resources." This is further confirmed by the FAQ section: "Should you exceed the 500 and 2,000 included resources in Team and Enterprise, respectively, you w…; source: https://www.pulumi.com/pricing/)
  • L714-724 in content/pricing/_index.md "A Serverless API with Amazon API Gateway and AWS Lambda is estimated to use 9 Pulumi resources; an Amazon EKS running in a VPC is estimated to use 20 resources…" → 🤷 unverifiable (evidence: verification did not converge within 8 turns)
  • L718 in content/pricing/_index.md "An Amazon EKS cluster running in a VPC requires an estimated 20 resources in Pulumi." (also L720) → ❌ contradicted (framing: shifted — source reports 18 resources created; claim states 20 resources required; evidence: The README in the referenced example (aws-py-eks) shows the actual pulumi up output: "Resources: + 18 created" — not 20. The resource list enumerates exactly 18 items including the Stack resource itself.; source: https://github.com/pulumi/examples/blob/master/aws-py-eks/README.md)
  • L722 in content/pricing/_index.md "An Amazon ECS cluster and RDS backend running in a VPC requires an estimated 24 resources in Pulumi." (also L724) → 🤷 unverifiable (evidence: (escalated from pass1) The GitHub source and Pulumi registry pages for aws-py-wordpress-fargate-rds describe the stack's components (VPC, RDS backend, ECS Fargate frontend, random password) but no authoritative source explicitly states a t…; source: WebSearch ran query "pulumi aws-py-wordpress-fargate-rds 24 resources OR resources: 24"; top results didn't address the specific count claim. https://github.com/pulumi/examples/tree/master/aws-py-wordpress-fargate-rds; intuition: Resource counts in Pulumi examples can vary by region (e.g., number of AZs/subnets) and provider version; a hard-coded…)
  • L727 in content/pricing/_index.md "ESC secrets are billed hourly at $0.000685 for Team ($0.50 per secret per month) and $0.001 for Enterprise ($0.75 per secret per month)." → ✅ verified (evidence: The official Pulumi pricing page states verbatim: "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)."; source: https://www.pulumi.com/pricing/)
  • L729 in content/pricing/_index.md "If you store secrets for 4 days on Pulumi Cloud Team Edition, the price would be 4 x 24 x 0.5 / 730 = $0.0657." → ❌ contradicted (evidence: The arithmetic 4 × 24 × 0.5 / 730 = 48 / 730 = 0.065753…, which rounds to $0.0658, not $0.0657 as stated in the claim. The final rounded figure is incorrect by $0.0001.; source: Direct arithmetic verification of the formula stated in the claim; intuition: Off-by-one rounding error: 48/730 ≈ 0.06575, which rounds to 0.0658 not 0.0657.)
  • L731 in content/pricing/_index.md "When using the Pulumi ESC Document Editor, each definition of fn::secret:* and fn::open::* (except Pulumi-stacks provider) is counted as a secret." → ✅ verified (framing: strengthened — the pricing page adds a wildcard suffix to fn::secret:* not present in the FAQ's fn::secret, but the core behavioral claim is consistent wit…; evidence: The authoritative FAQ at content/docs/support/faq/secrets-config.md states: "when using Pulumi ESC's document editor, each definition of fn::secret and fn::open::* (except with the [pulumi-stacks provider](/docs/esc/providers/iac/pul…; source: repo:content/docs/support/faq/secrets-config.md)
  • L731 in content/pricing/_index.md "Only the number of secrets from the latest environment revision is counted towards Pulumi ESC billing." → 🤷 unverifiable (evidence: verification did not converge within 8 turns)
  • L734 in content/pricing/_index.md "The first 10K ESC API calls per month to the ReadOpen API endpoint are free; beyond that, the rate is $0.10 per 10K API calls." → ✅ verified (evidence: The official Pulumi pricing page confirms: "You pay $0 for the first free 10K API calls / month to the ReadOpen API endpoint." and "Once you hit 10,000 API calls, you are metered at $0.1 for 10K API calls."; source: https://www.pulumi.com/pricing/)
  • L739 in content/pricing/_index.md "Workflow Minutes represent the total time used across both Pulumi Insights and Deployments, drawing from a single shared pool of minutes." → 🤷 unverifiable (evidence: verification did not converge within 8 turns)
  • L739 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)
  • L753 in content/pricing/_index.md "Pulumi Cloud is free to use, now and forever, for individuals, including automatic state management and unlimited updates." (also L755) → ✅ verified (framing: strengthened — claim says "automatic state management" where the source says "IaC state management"; both refer to the same managed-state feature, so the claim…; evidence: The pricing file's Individual tier is described as "Free forever for individuals" at $0, with features including "IaC state management" and "Unlimited updates and history." The claim's phrasing "automatic state management and unlimited upd…; source: repo:content/pricing/_index.md (Individual tier definition))
  • L759 in content/pricing/_index.md "Pulumi offers a 14-day free trial for the Business Critical Edition." → ❌ contradicted (evidence: The pricing file shows the Business Critical tier has only a "Contact sales" CTA (label: Contact sales, href: /contact/?form=sales) with no free trial. Only the Team and Enterprise tiers have "Start a free trial" CTAs. There is no ment…; source: repo:content/pricing/_index.md)
  • L770 in content/pricing/_index.md "Pulumi has completed the SOC 2 Type 2 compliance process." → ✅ verified (evidence: Pulumi's official blog states: "Pulumi is committed to operational excellence for our customers and one of the ways that we decided to demonstrate this was by completing our SOC 2 Type 2 Audit." The official security page also confirms: "T…; source: https://www.pulumi.com/blog/pulumis-soc-2-milestone/ and https://www.pulumi.com/security/)
  • L772 in content/pricing/_index.md "Pulumi Cloud self-hosting is available in the Business Critical Edition." → ✅ verified (evidence: The pricing page file explicitly lists "Self-hosting available" as a feature under the Business Critical tier, and the comparison table shows Self-hosting checked only for Business Critical (blank for Individual, Te…; source: repo:content/pricing/_index.md)
  • L782 in content/pricing/_index.md "Pulumi's community is described as over 10,000 people and growing." → ❌ contradicted (evidence: The pricing page itself contains the "over 10,000 people and growing" figure, but Pulumi's own current marketing (PulumiUP 2025 Keynote) states "350K+ community members," making the 10,000 figure severely outdated and contradicted by autho…; source: https://www.pulumi.com/events/pulumiup-2025-keynote/; intuition: The "10,000" figure is orders of magnitude smaller than Pulumi's current claimed community size of 350K+; this is a sta…)
  • L787 in content/pricing/_index.md "Snowflake migrated to Kubernetes across multiple clouds in three months using Pulumi." → ✅ verified (evidence: The Pulumi pricing page (pulumi.com/pricing/) contains the exact statement: "Snowflake migrated to Kubernetes across multiple clouds in three months." The Snowflake case study page confirms the multi-cloud Kubernetes migration across AWS,…; source: https://www.pulumi.com/pricing/)
  • L807 in content/pricing/_index.md "Pulumi bills for the previous month's usage on the first day of each month for Team or Enterprise Edition." → 🤷 unverifiable (evidence: verification did not converge within 8 turns)
  • L815 in content/pricing/_index.md "Pulumi offers a 14-day money-back guarantee for unsatisfied customers." → ✅ verified (evidence: (escalated from pass1) Pulumi's official pricing page states: "If you're not satisfied with Pulumi, we offer a 14-day money-back guarantee."; source: https://www.pulumi.com/pricing/)
  • L817 in content/pricing/_index.md "12x5 and 24x7 support, professional and advising services, and private Slack channel are available to purchase in the Enterprise and Business Critical Edition…" → ❌ contradicted (framing: shifted — the claim conflates features that are split between Enterprise and Business Critical tiers into a single statement covering both, and misnames "Profe…; evidence: The source splits these features across tiers: Enterprise lists "12x5 Enterprise Support available" while Business Critical lists "Private Slack and Professional Services" and "24x7 Enterprise Support available." The claim incorrectly impl…; source: repo:content/pricing/_index.md)
  • L1 in content/docs/ai/integrations/github/_index.md "frontmatter URL ? collides with ?" → ⚔️ mismatch (evidence: url=? collides_with=?; source: frontmatter-validate.py pre-step)

📊 Editorial balance

Single-subject post; balance check N/A.

🚨 Outstanding in this PR

These must be resolved or refuted before merging.

  • [L119] content/docs/integrations/version-control/github-app.md — "Triggering a Neo code review requires individual access." — This sentence is new in this PR, and the verification step couldn't independently corroborate that a Neo code review requires individual access. It also reads in tension with the sentence right before it, which says the org-level GitHub app "continues to handle pull request comments, checks, and push-to-deploy regardless of whether you grant individual access." If code reviews are delivered as PR comments/checks, a reader can't tell why they'd need individual access when ordinary PR comments don't. Please confirm the requirement and reconcile the two sentences — either spell out why a code review needs individual access when ordinary PR comments and checks don't, or adjust the wording. Current text:

    Individual access lets Pulumi create repositories on your behalf … The org-level GitHub app continues to handle pull request comments, checks, and push-to-deploy regardless of whether you grant individual access. Triggering a Neo code review requires individual access, though for other Neo tasks it is optional.

⚠️ Low-confidence

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

  • [L50] content/blog/neo-code-reviews/index.md — "After general availability on July 1, 2026, Neo Code Reviews reviews begin counting toward an organization's Neo token usage at the same per-token rate as any…" — verdict: unverifiable; evidence: No public source confirms that Neo Code Reviews reach GA on July 1, 2026, or that they count toward Neo token usage at the same per-token rate as other Neo tasks. The Pulumi pricing page returned only a single sentence fragment, and no sea…; source: WebSearch ran query "Pulumi Neo Code Reviews token usage pricing GA July 2026"; top results didn't address the claim. https://www.pulumi.com/pricing/ returned only a fragment with no relevant detail.; intuition: July 1, 2026 is a suspiciously precise future GA date (15 days from today); the per-token rate parity claim is a specif… — New content in this PR. This is the author's own forward-looking announcement (GA on July 1, 2026, reviews then counting toward Neo token usage at the standard per-token rate); it's consistent with the new Code Reviews docs page and the pricing page in this PR but can't be externally verified ahead of GA. Worth a quick confirm that the date and rate are current at publish time — not a hard blocker.

  • [L117] content/docs/integrations/version-control/github-app.md — "Individual users can complete an OAuth flow under Management > Version control to grant Pulumi access to their personal GitHub account; the integration card sh…" — verdict: unverifiable; evidence: The file content was cut off before line 117 and does not contain the specific UI status strings ("Individual access is authorized for this account" / "Individual access is recommended for this account") or an "Add Individual Account" butt…; source: repo:content/docs/integrations/version-control/github-app.md; intuition: The file explicitly says "GitHub.com integrations always use the shared app installation" — an individual OAuth flow fo… — On a pre-existing line this PR doesn't modify; automated verification was inconclusive (the line describes existing behavior the page already documents). Surfaced for awareness — not a blocker for this change.

  • [L146] content/docs/integrations/version-control/github-app.md — "Commit metadata extracted by the Pulumi CLI is included with the update and sent to Pulumi Cloud, which uses it to identify the associated pull request and pos…" — verdict: unverifiable; evidence: verification did not converge within 8 turns — On a pre-existing line this PR doesn't modify; automated verification was inconclusive (the line describes existing behavior the page already documents). Surfaced for awareness — not a blocker for this change.

  • [L149] content/docs/integrations/version-control/github-app.md — "When pull request comments are disabled in integration settings, the GitHub app does not post comments on pull requests but still reports check run statuses vi…" — verdict: unverifiable; evidence: verification did not converge within 8 turns — On a pre-existing line this PR doesn't modify; automated verification was inconclusive (the line describes existing behavior the page already documents). Surfaced for awareness — not a blocker for this change.

  • [L154] content/docs/integrations/version-control/github-app.md — "The GitHub Checks API integration provides detail about resource changes, including the full update log." — verdict: unverifiable; evidence: verification did not converge within 8 turns — On a pre-existing line this PR doesn't modify; automated verification was inconclusive (the line describes existing behavior the page already documents). Surfaced for awareness — not a blocker for this change.

  • [L156] content/docs/integrations/version-control/github-app.md — "All Pulumi stack updates are reported to the GitHub Checks API." — verdict: unverifiable; evidence: verification did not converge within 8 turns — On a pre-existing line this PR doesn't modify; automated verification was inconclusive (the line describes existing behavior the page already documents). Surfaced for awareness — not a blocker for this change.

  • [L162] content/docs/integrations/version-control/github-app.md — "Pulumi Deployments supports deploying on git tag pushes using tag triggers — for example, on every v* release tag." — verdict: unverifiable; evidence: verification did not converge within 8 turns — On a pre-existing line this PR doesn't modify; automated verification was inconclusive (the line describes existing behavior the page already documents). Surfaced for awareness — not a blocker for this change.

  • [L170] content/docs/integrations/version-control/github-app.md — "The GitHub app does not require GitHub Actions; any CI/CD system works, including GitHub Actions, CircleCI, Jenkins, Pulumi Deployments, or any other system." — verdict: unverifiable; evidence: verification did not converge within 8 turns — On a pre-existing line this PR doesn't modify; automated verification was inconclusive (the line describes existing behavior the page already documents). Surfaced for awareness — not a blocker for this change.

  • [L254-256] content/pricing/_index.md — "The Team tier supports 1 organization, while Enterprise and Business Critical support multiple organizations." — verdict: unverifiable; evidence: No authoritative Pulumi source found that frames the Team tier as supporting "1 organization" vs. Enterprise/Business Critical supporting "multiple organizations." The official pricing page and FAQ describe organizational management differ…; source: WebSearch ran query "Pulumi pricing '1 organization' OR 'single organization' Team tier vs Enterprise multiple organizations"; top results (pulumi.com/pricing, pulumi.com/docs/support/pulumi-cloud-faq/) didn't address the specific claim.; intuition: The "1 organization vs. multiple organizations" framing is not a standard Pulumi pricing distinction; Pulumi's document… — On a pre-existing line this PR doesn't modify; automated verification was inconclusive (the line describes existing behavior the page already documents). Surfaced for awareness — not a blocker for this change.

  • [L260-263] content/pricing/_index.md — "Identity providers supported include GitHub, GitLab, and Atlassian for Individual and Team tiers, and additionally SAML/SSO for Enterprise and Business Critica…" — verdict: unverifiable; evidence: verification did not converge within 8 turns — On a pre-existing line this PR doesn't modify; automated verification was inconclusive (the line describes existing behavior the page already documents). Surfaced for awareness — not a blocker for this change.

  • [L262] content/pricing/_index.md — "The Pulumi Enterprise plan supports GitHub, GitLab, Atlassian, and SAML/SSO as identity providers." — verdict: unverifiable; evidence: verification did not converge within 8 turns — On a pre-existing line this PR doesn't modify; automated verification was inconclusive (the line describes existing behavior the page already documents). Surfaced for awareness — not a blocker for this change.

  • [L270-272] content/pricing/_index.md — "SAML/SSO providers supported include Microsoft Entra ID, Google Workspace, Okta, OneLogin, and more." — verdict: unverifiable; evidence: verification did not converge within 8 turns — On a pre-existing line this PR doesn't modify; automated verification was inconclusive (the line describes existing behavior the page already documents). Surfaced for awareness — not a blocker for this change.

  • [L501] content/pricing/_index.md — "The Pulumi Enterprise plan supports 10 primary accounts (or custom) for Insights." — verdict: unverifiable; evidence: No authoritative source (pulumi.com/pricing, Pulumi docs, or any third-party source) mentions a "10 primary accounts" limit for Insights under the Enterprise plan. The official pricing page discusses resource billing and workflow minutes b…; source: WebSearch ran query "Pulumi pricing Enterprise Insights primary accounts 10"; top results didn't address the claim; intuition: The "10 primary accounts (or custom)" framing is suspiciously specific and mirrors the Team plan's 10-user cap — it may… — On a pre-existing line this PR doesn't modify; automated verification was inconclusive (the line describes existing behavior the page already documents). Surfaced for awareness — not a blocker for this change.

  • [L544] content/pricing/_index.md — "The Pulumi Business Critical plan pre-built policy packs include Pulumi Best Practices, CIS, NIST, HITRUST, and PCI DSS." — verdict: unverifiable; evidence: verification did not converge within 8 turns — On a pre-existing line this PR doesn't modify; automated verification was inconclusive (the line describes existing behavior the page already documents). Surfaced for awareness — not a blocker for this change.

  • [L560] content/pricing/_index.md — "The Pulumi Business Critical plan supports Advisory, Mandatory, and Remediation enforcement modes." — verdict: unverifiable; evidence: verification did not converge within 8 turns — On a pre-existing line this PR doesn't modify; automated verification was inconclusive (the line describes existing behavior the page already documents). Surfaced for awareness — not a blocker for this change.

  • [L569-573] content/pricing/_index.md — "The Individual tier includes 5M Pulumi Neo tokens per month for free; Team, Enterprise, and Business Critical are priced at $3 per million tokens." — verdict: unverifiable; evidence: verification did not converge within 8 turns — On a pre-existing line this PR doesn't modify; automated verification was inconclusive (the line describes existing behavior the page already documents). Surfaced for awareness — not a blocker for this change.

  • [L574] content/pricing/_index.md — "MCP and CLI integrations for Pulumi Neo are available on all Pulumi plans (Individual, Team, Enterprise, and Business Critical)." — verdict: unverifiable; evidence: verification did not converge within 8 turns — New comparison-table row in this PR. This is the author's own product-availability matrix (MCP & CLI integrations across all tiers), consistent with the tier feature lists; external verification didn't converge. Worth confirming it matches the shipped availability — not a blocker.

  • [L632-633] content/pricing/_index.md — "Enterprise and Business Critical tiers offer normal ticket SLAs of 1 or 5 business days." — verdict: unverifiable; evidence: verification did not converge within 8 turns — On a pre-existing line this PR doesn't modify; automated verification was inconclusive (the line describes existing behavior the page already documents). Surfaced for awareness — not a blocker for this change.

  • [L638-639] content/pricing/_index.md — "Enterprise and Business Critical tiers offer urgent ticket SLAs of 4 hours to 2 business days." — verdict: unverifiable; evidence: verification did not converge within 8 turns — On a pre-existing line this PR doesn't modify; automated verification was inconclusive (the line describes existing behavior the page already documents). Surfaced for awareness — not a blocker for this change.

  • [L695] content/pricing/_index.md — "For billing purposes, a partial resource hour used is billed as a full hour." — verdict: unverifiable; evidence: verification did not converge within 8 turns — On a pre-existing line this PR doesn't modify; automated verification was inconclusive (the line describes existing behavior the page already documents). Surfaced for awareness — not a blocker for this change.

  • [L695] content/pricing/_index.md — "Pulumi billing counts any resource declared in a Pulumi program, including provider resources (e.g., an Amazon S3 bucket), component resources (e.g., an Amazon…" — verdict: unverifiable; evidence: verification did not converge within 8 turns — On a pre-existing line this PR doesn't modify; automated verification was inconclusive (the line describes existing behavior the page already documents). Surfaced for awareness — not a blocker for this change.

  • [L700] content/pricing/_index.md — "The Team edition's 500 included resources is described as sufficient to manage 500 EKS clusters or EC2 instances for a month, or a production Amazon EKS cluste…" — verdict: unverifiable; evidence: verification did not converge within 8 turns — On a pre-existing line this PR doesn't modify; automated verification was inconclusive (the line describes existing behavior the page already documents). Surfaced for awareness — not a blocker for this change.

  • [L714-724] content/pricing/_index.md — "A Serverless API with Amazon API Gateway and AWS Lambda is estimated to use 9 Pulumi resources; an Amazon EKS running in a VPC is estimated to use 20 resources…" — verdict: unverifiable; evidence: verification did not converge within 8 turns — On a pre-existing line this PR doesn't modify; automated verification was inconclusive (the line describes existing behavior the page already documents). Surfaced for awareness — not a blocker for this change.

  • [L722] content/pricing/_index.md — "An Amazon ECS cluster and RDS backend running in a VPC requires an estimated 24 resources in Pulumi." — verdict: unverifiable; evidence: (escalated from pass1) The GitHub source and Pulumi registry pages for aws-py-wordpress-fargate-rds describe the stack's components (VPC, RDS backend, ECS Fargate frontend, random password) but no authoritative source explicitly states a t…; source: WebSearch ran query "pulumi aws-py-wordpress-fargate-rds 24 resources OR resources: 24"; top results didn't address the specific count claim. https://github.com/pulumi/examples/tree/master/aws-py-wordpress-fargate-rds; intuition: Resource counts in Pulumi examples can vary by region (e.g., number of AZs/subnets) and provider version; a hard-coded… — On a pre-existing line this PR doesn't modify; automated verification was inconclusive (the line describes existing behavior the page already documents). Surfaced for awareness — not a blocker for this change.

  • [L731] content/pricing/_index.md — "Only the number of secrets from the latest environment revision is counted towards Pulumi ESC billing." — verdict: unverifiable; evidence: verification did not converge within 8 turns — On a pre-existing line this PR doesn't modify; automated verification was inconclusive (the line describes existing behavior the page already documents). Surfaced for awareness — not a blocker for this change.

  • [L739] content/pricing/_index.md — "Workflow Minutes represent the total time used across both Pulumi Insights and Deployments, drawing from a single shared pool of minutes." — verdict: unverifiable; evidence: verification did not converge within 8 turns — On a pre-existing line this PR doesn't modify; automated verification was inconclusive (the line describes existing behavior the page already documents). Surfaced for awareness — not a blocker for this change.

  • [L739] content/pricing/_index.md — "Deployments consume workflow minutes by measuring the duration of each deployment process." — verdict: unverifiable; evidence: verification did not converge within 8 turns — On a pre-existing line this PR doesn't modify; automated verification was inconclusive (the line describes existing behavior the page already documents). Surfaced for awareness — not a blocker for this change.

  • [L807] content/pricing/_index.md — "Pulumi bills for the previous month's usage on the first day of each month for Team or Enterprise Edition." — verdict: unverifiable; evidence: verification did not converge within 8 turns — On a pre-existing line this PR doesn't modify; automated verification was inconclusive (the line describes existing behavior the page already documents). Surfaced for awareness — not a blocker for this change.

@github-actions

github-actions Bot commented Jun 16, 2026

Copy link
Copy Markdown
Contributor

📋 Triaged verifier findings

I double-checked these and realized they weren't real findings — click to expand
  • [L79] content/pricing/_index.md — "The Pulumi Enterprise plan includes 12x5 Enterprise Support (available as an add-on)." — Spurious: The pricing page lists this Enterprise feature as "12x5 Enterprise Support available" — the page text carries no "as an add-on" qualifier, so the page itself is accurate; the flagged wording isn't what's on the page.
  • [L98] content/pricing/_index.md — "The Pulumi Business Critical plan includes 24x7 Enterprise Support (available as an add-on)." — Spurious: The pricing page lists this Business Critical feature as "24x7 Enterprise Support available"; the "as an add-on" qualifier isn't present in the page text, so the page reads correctly.

💡 Pre-existing issues in touched files (optional)

These are real, but they sit on lines this PR doesn't modify (the pricing page was edited only in the tier feature lists and the comparison table). Flagged for awareness; none are introduced by this change.

  • [L1] content/docs/ai/integrations/github/_index.md — "frontmatter URL ? collides with ?" — Pre-existing: Intentional PR-internal rename, not a real collision. The GitHub integration page (/docs/ai/integrations/github/) is being retired, and its URL is correctly preserved as an alias on the new content/docs/ai/code-reviews/_index.md page — which is exactly the redirect the frontmatter check flagged.
  • [L107] content/pricing/_index.md — "Unity achieved 5x faster time to market using Pulumi." — Pre-existing: The "5x faster time to market" figure isn't in the Unity case study (pulumi.com/case-studies/unity/); that metric belongs to a different customer in a separate Pulumi blog post. On a line this PR didn't modify.
  • [L113] content/pricing/_index.md — "Snowflake achieved 10x faster deployments, going from weeks to hours, using Pulumi." — Pre-existing: The Snowflake case study reports "1.5 weeks → under 1 day," not "10x faster, weeks to hours" (the "10x" figure comes from a separate blog post). On a line this PR didn't modify.
  • [L131-134] content/pricing/_index.md — "The Team tier IaC on-demand resource price is $0.00025/hour ($0.185/month), and the Enterprise tier starts at $0.0005/hour ($0.365/month)." — Pre-existing: The Team per-resource monthly rate is $0.1825, not $0.185 (the hourly and Enterprise figures are correct). On a line this PR didn't modify.
  • [L247] content/pricing/_index.md — "The Pulumi Team plan supports 1 admin." — Pre-existing: The Team cap is "1 Billing Manager," a specific role — organization admins are not capped at 1. On a line this PR didn't modify.
  • [L388-391] content/pricing/_index.md — "The Individual tier has a maximum of 25 ESC secrets; Team, Enterprise, and Business Critical have unlimited secrets." — Pre-existing: Team/Enterprise ESC secrets are metered ($0.50 / $0.75 per secret per month), not "unlimited"; only the 25-secret free tier is a hard cap. On a line this PR didn't modify.
  • [L394-397] content/pricing/_index.md — "The Individual tier has a maximum of 10K ESC API calls per month; Team, Enterprise, and Business Critical have unlimited API calls." — Pre-existing: ESC API calls use a universal metered model (10K free, then $0.10 per 10K for all tiers), not an Individual-only cap with unlimited paid tiers. On a line this PR didn't modify.
  • [L626-627] content/pricing/_index.md — "Enterprise Support is available at 12x5 or 24x7 for the Pulumi Enterprise plan." — Pre-existing: The page assigns 12x5 support to Enterprise and 24x7 to Business Critical — not both as options within Enterprise. On a line this PR didn't modify.
  • [L718] content/pricing/_index.md — "An Amazon EKS cluster running in a VPC requires an estimated 20 resources in Pulumi." — Pre-existing: The referenced aws-py-eks example's README shows "18 created," not 20 resources. On a line this PR didn't modify.
  • [L729] content/pricing/_index.md — "If you store secrets for 4 days on Pulumi Cloud Team Edition, the price would be 4 x 24 x 0.5 / 730 = $0.0657." — Pre-existing: 4 × 24 × 0.5 / 730 = 0.06575, which rounds to $0.0658, not $0.0657 — a rounding slip in the worked example. On a line this PR didn't modify.
  • [L759] content/pricing/_index.md — "Pulumi offers a 14-day free trial for the Business Critical Edition." — Pre-existing: The Business Critical tier exposes only a "Contact sales" CTA; only Team and Enterprise have free-trial CTAs. On a line this PR didn't modify.
  • [L782] content/pricing/_index.md — "Pulumi's community is described as over 10,000 people and growing." — Pre-existing: The "over 10,000 people and growing" figure is stale against Pulumi's current "350K+" community messaging. On a line this PR didn't modify.
  • [L817] content/pricing/_index.md — "12x5 and 24x7 support, professional and advising services, and private Slack channel are available to purchase in the Enterprise and Business Critical Edition…" — Pre-existing: These support/services/Slack features are split across the Enterprise and Business Critical tiers, not jointly available across both as the line implies. On a line this PR didn't modify.

✅ Resolved since last review

No items resolved since the last review.

📜 Review history

  • 2026-06-16T21:43:49Z — New Code Reviews blog + docs page and pricing updates; new content verified, one PR-introduced item to confirm on the GitHub App page (L119), and the bulk of pricing findings are pre-existing on untouched lines. (5dd1ed0)

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.)

@github-actions github-actions Bot added review:outstanding-issues Claude review completed; outstanding has author-actionable findings and removed review:in-progress Claude review is currently running labels Jun 16, 2026
@kramhuber @claude
Add Neo Code Reviews blog, docs page, and pricing updates
d78baf4 
- Add the Neo Code Reviews announcement blog post with feature and meta images
- Add the /docs/ai/code-reviews/ page covering automated and manual reviews, setup, and governance
- Remove the GitHub integration page, folding its setup and @pulumi-neo usage into Code Reviews, and alias the old URL
- Note in the GitHub App docs that triggering a Neo code review requires individual OAuth access
- Repoint the integrations and pull-requests pages to the new Code Reviews page
- Update the pricing comparison table and plan cards for Neo SKU gating
- Repoint the historical neo-github-slack post's GitHub links to the new page and stamp lastmod

Co-Authored-By: Claude <noreply@anthropic.com>
@kramhuber kramhuber force-pushed the mhuber/neo-code-reviews branch from 5dd1ed0 to d78baf4 Compare June 16, 2026 23:29
@github-actions github-actions Bot added review:stale New commits since last Claude review; refresh on next ready-transition or @claude mention and removed review:outstanding-issues Claude review completed; outstanding has author-actionable findings labels Jun 16, 2026
cnunciato
cnunciato approved these changes Jun 17, 2026
View reviewed changes

@cnunciato cnunciato left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving to keep you unblocked.

@aminix @claude
Document per-feature Neo controls and update Neo access screenshot
8086833 
Expand the Neo access section to cover the master "Enable Neo for
organization" toggle plus the new per-feature controls (Neo agent, CLI
explanations, natural-language resource search), and point to Version
control settings for disabling Neo Code Reviews. Replace the screenshot
with the current settings UI.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@aminix aminix changed the title Add Neo Code Reviews blog, docs page, and pricing updates Add Neo Code Reviews blog, docs page, pricing updates, Neo enable/disable toggles Jun 17, 2026
@cnunciato @claude
Lowercase the Neo code reviews feature name and polish copy
a189272 
Apply brand-guideline edits across the Neo code reviews blog, docs, and pricing:

- Lowercase "Code Reviews" -> "code reviews" everywhere, rewording for verb agreement
- Brand-voice copy fixes (contractions, spell out infrastructure as code, soften framing)
- Revise the social posts
- Add a Neo code review screenshot to the blog's Running reviews section

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@cnunciato @claude
Set Neo code reviews post date to 2026-06-22
f389621 
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
cnunciato
cnunciato reviewed Jun 18, 2026
View reviewed changes
Comment thread content/blog/neo-code-reviews/index.md Outdated
cnunciato
cnunciato reviewed Jun 18, 2026
View reviewed changes
Comment thread content/blog/neo-code-reviews/index.md Outdated
@cnunciato @claude
Revise Neo code reviews social copy for a more human voice
42739d9 
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@cnunciato cnunciato cnunciato approved these changes

@flostadler flostadler Awaiting requested review from flostadler

@isaac-pulumi isaac-pulumi Awaiting requested review from isaac-pulumi

Assignees

No one assigned

Labels

domain:blog PR touches blog posts or customer stories domain:docs PR touches technical docs domain:mixed PR touches more than one domain domain:website PR touches marketing, pricing, legal, or competitive landing pages needs-design review:stale New commits since last Claude review; refresh on next ready-transition or @claude mention

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@kramhuber @pulumi-bot @cnunciato @aminix @jeffmerrick