Blog: Introducing Pulumi Credits and Neo Tokens

[isaac-pulumi]

Summary

• Adds new blog post announcing Pulumi Bills (unified billing currency) and Neo Tokens (pricing for AI-powered features)
• Effective date: June 1, 2026
• Covers self-serve and invoiced customer transition paths, Neo Token pricing ($3/MTok), usage tracking, and admin controls

Test plan

• Verify frontmatter renders correctly on the blog
• Confirm links (Terms and Conditions, support@pulumi.com) resolve properly
• Add meta.png social share image before publishing
• Confirm author attribution is correct

🤖 Generated with Claude Code

[claude]

Docs Review

Thanks for the announcement! Solid structure overall — the problem framing flows well into the two-part solution, and the transition table at the end is genuinely useful. A few things to address before publishing:

Style guide compliance

H2/H3 heading case (per AGENTS.md: H1 = Title Case, H2+ = sentence case). Multiple H2s currently use Title Case:

• Line 27: ## The Problem We're Solving
• Line 31: ## Pulumi Bills: One Currency for the Whole Platform
• Line 59: ## Neo Tokens: Paying for AI That Does Real Work
• Line 89: ## What You Need to Do
• Line 98: ## Looking Ahead

Suggested fixes (note: keep proper nouns like Pulumi Bills, Neo Tokens capitalized):

## The problem we're solving

## Pulumi Bills: one currency for the whole platform

## Neo Tokens: paying for AI that does real work

## What you need to do

## Looking ahead

Avoid "simple/easy" phrasing — the post title and L100 lean on "simplified"/"maximum flexibility," which the style guide flags. Consider tightening the title to drop "Simplified":

title: \"Introducing Pulumi Bills and Neo Tokens: unified billing for the Pulumi platform\"

(This also gets you closer to the 60-char SEO target — see below.)

SEO and frontmatter

• Line 2 — title is 82 characters. Either shorten it, or add allow_long_title: true to the frontmatter. Shortening is preferred for social previews.

• Line 5 — meta description is 163 characters, just over the 160-char target. Tighten slightly:

  meta_desc: \"Pulumi Bills unifies billing across all Pulumi capabilities, and Neo Tokens bring transparent pricing to AI-powered infrastructure features.\"
  

• Line 14 — social: block is missing the bluesky key. Without it, the post won't auto-post to Bluesky. Add a third entry:

  bluesky: \"...\"

• Line 6 — meta.png is missing from the directory. Already noted in your test plan, just confirming it's still required before merge. Use /blog-meta-image to generate one.

Grammar and copy

• Line 23 — "all of Pulumi capabilities" is ungrammatical. Should be "all of Pulumi's capabilities" or simply "all Pulumi capabilities":

  We're introducing two changes that address this directly: **Pulumi Bills** as a unified billing currency across all Pulumi capabilities, and **Neo Tokens** as the meter for LLM-powered features.
  

• Line 21 — "5 years ago" should be spelled out per Google style for numbers under 10: "five years ago."

• Line 35 — missing Oxford comma and conjunction: "Resource-hours, secret-hours, workflow-minutes, Neo Tokens all draw...":

  Rather than pre-purchasing fixed quantities for each individual feature, customers can pre-purchase a pool of Pulumi Bills and let all usage draw from that pool. Resource-hours, secret-hours, workflow-minutes, and Neo Tokens all draw from the same balance of Pulumi Bills. Once the pool is exhausted, additional usage is billed in arrears.
  

• Line 40 — missing Oxford comma: "Insights and future capabilities":

  - **Start using new features immediately.** IaC, Neo, ESC, Deployments, Insights, and future capabilities all draw from the same pool.
  

• Line 63 — "Million Tokens" is incorrectly capitalized. Standard convention (and your LinkedIn copy on L16) is lowercase:

  **Neo Tokens are priced at $3 per million tokens (MTok).**
  

• Line 67 — "Neo Activity" capitalization is inconsistent. The phrase appears as Title Case in L67 and L69 but is described as a generic "LLM-powered operation," not a proper product term. Recommend lowercasing to "Neo activity" throughout unless this is a defined product noun.

• Line 72 — "Pull Request summaries" should be lowercase "pull request" (matches usage on L75 and aligns with the AGENTS.md rule about lowercase non-proper nouns):

  - **Pull request summaries**: automated summaries on pull requests
  

Content / accuracy

• Line 61 — "More than 3,000 organizations" is a specific factual claim. Worth confirming this number with the Neo team before publishing.

• Line 21 — "consumption-based billing model for Pulumi IaC 5 years ago" — also worth a fact-check on the timeline.

• Line 100 — hedging language: "Pulumi Bills aims to give customers maximum flexibility" — write with confidence and drop the superlative:

  Pulumi Bills gives customers flexibility across the Pulumi portfolio, and Neo Tokens give you a transparent way to track AI-powered infrastructure assistance costs.
  

Nits

• Line 79 — "updated with views for the prior time periods" reads awkwardly. Consider: "with views for prior billing periods" or "with historical views."
• The post has no internal links to existing Pulumi product docs. First mention of each product (ESC, Deployments, Insights, Neo) on line 21 would benefit from links to their respective /docs/ landing pages — both for reader navigation and SEO internal-linking.
• CTA: consider using {{< blog/cta-button >}} shortcode for the closing "contact your Pulumi representative" call, or adding one to the What you need to do section.

Publishing readiness checklist

• social: block present with copy for twitter, linkedin — missing bluesky
• meta_image set, not empty, not the default placeholder — meta.png file is missing from the directory
• meta_image uses current Pulumi logos (pending file creation)
• <!--more--> break present after intro (line 25)
• Author profile exists with avatar (data/team/team/meagan-cojocar.toml, static/images/team/meagan-cojocar.jpg)
• All links resolve (Terms & Conditions, support email)
• No code examples to verify
• No animated GIFs
• No images requiring alt text (yet — once meta.png lands, ensure it's non-animated)
• Title ≤60 chars or allow_long_title: true set — currently 82 chars, neither condition met

---

Mention @claude if you'd like me to take another pass after revisions, or have me draft replacement copy for any of the flagged spots.

[github-actions]

Social Media Review

content/blog/pulumi-bills-neo-tokens/index.md

X — FAIL

• Single paragraph; X requires at least 2 paragraphs separated by a blank line

LinkedIn — FAIL

• Dense single block of text; LinkedIn requires multiple short paragraphs

Bluesky — missing

No copy provided. Suggested copy drafted below.

---

Suggested copy

X (202/255 chars) — paragraph break inserted after first sentence; no other changes:

Introducing Pulumi Bills and Neo Tokens: one unified billing currency for IaC, ESC, Deployments, Insights, and Neo.

1 Pulumi Bill = $1 USD. Neo Tokens priced at $3/MTok. Changes effective June 1, 2026.

LinkedIn (435/2950 chars) — split into short paragraphs at natural sentence boundaries; no words changed:

We're simplifying how Pulumi billing works. Pulumi Bills gives you one unified currency across the entire platform — IaC, ESC, Deployments, Insights, and Neo all draw from the same pool.

No more guessing fixed allocations per product or separate procurement for each new capability.

Neo Tokens bring transparent, predictable pricing to AI-powered infrastructure features at $3 per million tokens.

Changes are effective June 1, 2026.

Bluesky (271/300 chars) — drafted from the article:

Pulumi Bills replaces separate resource-hour, secret-hour, and workflow-minute buckets with a single pool. All products — IaC, ESC, Deployments, Insights, and Neo — draw from the same balance.

Neo Tokens price AI-powered features at $3/MTok. Both changes go live June 1.

---

To apply these suggestions, comment: @claude please update the social posts in the frontmatter with the suggested copy from the social media review above

To re-run the social media review after updates, comment: /social-review

Updated for commit 9d25dd31d6799883e60d1c44eda9350e1a1992f2 (short: 9d25dd3) at 2026-05-08 20:26 UTC.

[isaac-pulumi]

@claude please replace all usage of "Pulumi Bills" with "Pulumi Credits" in the blog and social copy.
change the URL slug to pulumi-credits-neo-tokens

[pulumi-bot]

Claude finished @isaac-pulumi's task in 1m 56s —— View job

---

Pulumi Bills → Pulumi Credits — done

• Replaced "Pulumi Bills" → "Pulumi Credits" (and singular "Pulumi Bill" → "Pulumi Credit") throughout the blog body, frontmatter title, meta_desc, and social.twitter / social.linkedin copy
• Renamed directory content/blog/pulumi-bills-neo-tokens/ → content/blog/pulumi-credits-neo-tokens/ (git detected as a rename, history preserved)
• Added aliases: [/blog/pulumi-bills-neo-tokens/] so the old URL still resolves
• Committed and pushed to blog/pulumi-bills-neo-tokens

Notes / things I did not touch:

• The branch name still contains pulumi-bills — renaming branches is outside what I can do here, and the PR title is already updated. Safe to leave.
• "credit card" references (e.g., "self-serve credit card customers") were left as-is — that's the payment method, not the product term.
• Style-guide items from my earlier review (H2 sentence case, the title length, the missing bluesky social key, missing meta.png, etc.) are still open. Let me know if you'd like me to apply those in a follow-up commit.
  · branch: blog/pulumi-bills-neo-tokens

[isaac-pulumi]

@claude fix the error preventing the preview from generating

[pulumi-bot]

Claude finished @isaac-pulumi's task in 3m 17s —— View job

---

Fixing preview build error — done

• Investigate the preview build error
• Remove broken meta_image reference from frontmatter
• Commit and push the fix

Root cause

The frontmatter on line 6 declared meta_image: meta.png, but meta.png did not exist in content/blog/pulumi-credits-neo-tokens/. In layouts/partials/head.html:80-85, the blog branch resolves the field via .Resources.GetMatch .Params.meta_image and immediately calls .RelPermalink on the result — when the resource is missing, that's a nil-pointer call and Hugo panics, which prevents the preview from rendering.

Fix

Removed the meta_image: meta.png line so the build falls back to the default OG image (/logos/brand/og-default.png) until a real meta.png is added. I attempted to generate the image via the /blog-meta-image skill but couldn't install uv / cairosvg / pillow in this CI environment (sandboxed pip and curl). When you're ready to add the real social card, run /blog-meta-image locally — the Rocket template would be a natural fit since this is an announcement of new features.

Other items from the earlier docs-review pass (H2 sentence case, the 82-char title, missing bluesky social key, grammar nits) are still open — happy to tackle any of those if you'd like. Mention @claude with the ones you want applied.

Commit: 35d4b81 on blog/pulumi-bills-neo-tokens ·