[batuhan]

Brings Pricing & Limits in line with what billing actually charges:

• Compute is $0.1188 per CPU-hour ($0.000033 per CPU-second), the rate billing uses. It was rounded to $0.119, which would have read as a small price rise.
• MySQL compute and storage are complimentary for now, with the price that applies once they're measured (marked †). Nothing records either today, and we don't charge for what we can't measure.
• Example bills recomputed: the studio uses $4.75 of $15, the busy app $8.47 of $15.

🤖 Generated with Claude Code

---

^{Open in [code]smith · Need help on this PR? Tag @codesmith-bot with what you need.}

Summary by CodeRabbit

• Pricing Updates
  • MySQL compute is temporarily free, then priced at $0.1188 per CPU-hour.
  • Storage is temporarily free, then priced at $0.10 per GB-month after the first 1 GB per Space. Storage charges are based on daily measurements averaged over the month.
  • The CPU-hour rate is now $0.1188.
  • Updated example bills reflect the temporary free periods and revised charges.

[indent]

Issues

All clear! No issues remaining. 🎉

2 issues already resolved

• The recomputed Pro examples ("Uses $4.75 of $15", "Uses $8.47") only verify the compute rate against billing. On monorepo main, RETAIL_RATE_CARD has no per-plan inclusions for builds, uncached traffic, cached traffic or dynamic requests, so billing would charge far more than the examples show, and "publish exactly what we bill" is still untrue for these rows.
  _{Found by Indent Review Agent}
• Storage cells now say "Free now; ...†", but the row tip and the Fine print Storage row in content/(account)/pricing.mdx still say only that the first 1 GB per Space "isn't counted for now", and the first two examples still say "Under the 1 GB not counted" while the Pro examples say "Free for now". MySQL compute's tip was updated and Storage's wasn't. (fixed by commit 72afd61)
  _{Found by Indent Review Agent}

CI Checks

All required checks passed on 40036cb. The non-required Spacefast Builds check failed again with "The runtime API hit a fatal error." CodeRabbit is still running.

Spacefast Builds

• Not a required check. It failed with the same message on all three heads (b04107f, 72afd61, 40036cb), with no annotations and no readable log. Failing identically on every commit points to a platform problem rather than the pricing changes. Check the build on the Spacefast dashboard.

Review agents

Select any unchecked box below to run or rerun that agent.

Passed (1)

• Indent Review Agent · No issues found

Full results

Indent Review Agent

• Summary: No issues found
• Last ran on commit: 40036cb7
• Latest result

  {
    "summary": "No issues found",
    "findings": []
  }

[coderabbitai]

No actionable comments were generated in the recent review.

Walkthrough

Pricing terms and plan values now show temporary-free MySQL compute and storage, followed by stated rates. Business overrides and example bills reflect the updated terms. The pricing page’s fine print also describes temporary-free storage.

Changes: Pricing Updates

Layer / File(s)	Summary
Pricing terms and rates content/(account)/pricing.mdx, scripts/pricing-next.mjs	The fine print and plan values state that storage and MySQL compute are free temporarily, then show their later rates. Business overrides match these terms. The CPU-hour rate changes from $0.119 to $0.1188.
Example bills scripts/pricing-next.mjs	Example bills label storage and MySQL compute as free for now and update displayed costs and included-usage totals.

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Other

Possibly related PRs

• spacefast/docs#122: This PR also changes Business pricing overrides and the pricing page’s fine print.
• spacefast/docs#115: This PR introduced the pricing page and data model that this PR updates.

Merge Risk: Minimal · up to 40036

The page describes temporary waivers and updated example totals. No material merge-readiness risk was established.

Pre-merge checks: 5

Check name	Status	Explanation
Description Check		Check skipped - CodeRabbit’s high-level summary is enabled.
Title check		The title clearly and concisely describes the main change: updating published pricing to match actual billing.
Docstring Coverage		No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 1 files. (1 skipped: 1 unsupported.)

Finishing Touches

Generate docstrings

• Commit to this branch
• Create a new PR

Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Recent review info

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: 4a6099fa-7bb1-4182-b7c2-765d59936488

Commits

Reviewing files that changed from the base of the PR and between bd61ed5 and 40036cb.

Files selected for processing: 2

• content/(account)/pricing.mdx
• scripts/pricing-next.mjs

Included review availability: This review used your included allowance. 0 included reviews remain after this review. Your included PR review attempts over the past 7 days set your current allowance at 1 review per hour.

[chatgpt-codex-connector]

Codex Review Summary: ❌ Failed

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	❌ Failed 2026-11-09T14:02:00.143787Z We couldn’t complete this review. Comment @codex review to try again.	b04107f	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.