Skip to content

Show GB-hour billing model on pricing page - #508

Draft
robertjamesprior wants to merge 1 commit into
mainfrom
hypeship/gb-hour-pricing-clarity
Draft

Show GB-hour billing model on pricing page#508
robertjamesprior wants to merge 1 commit into
mainfrom
hypeship/gb-hour-pricing-clarity

Conversation

@robertjamesprior

Copy link
Copy Markdown

Summary

  • Replace the per-browser-type $/sec table with a standard vs. GPU-accelerated $/GB-hour table. Headless/headful/GPU move to a worked-example table underneath instead of looking like separate pricing tiers.
  • Point the Browser Pools section at the same $0.06/GB-hour rate instead of a separate "per GB-second" phrasing.
  • Rework the pricing calculator to compute cost as memory × rate instead of a hardcoded per-browser-type multiplier (the old GPU multiplier of 48 silently encoded "6 GB × 8x the standard rate").

Why

Kernel bills browser usage by memory used × a standard-or-GPU rate. Headless/headful aren't separate pricing tiers — they're fixed memory allocations at the same rate. Confirmed live against Metronome: the browser session uptime (GB-second) product prices by gpu/overage only, and Free, Hobbyist, and Start-Up contracts all resolve to the same rate card — $0.06/GB-hour standard, $0.48/GB-hour GPU (8x). Enterprise GPU pricing is a separate open question and stays out of scope here.

Testing

No test suite for this Mintlify site. Verified the calculator's new derivation against the old hardcoded per-second constants (0.0000166667 / 0.0001333336 / 0.0008000016) — they match exactly. Reviewed the rendered Markdown/JSX by hand; did not run a live mintlify dev preview.

Addresses KERNEL-1959.

Replace the per-browser-type $/sec table with standard/GPU rates per
GB-hour, matching how Metronome actually bills browser usage (GPU
boolean x memory, same rate card across Free/Hobbyist/Start-Up).
Headless/headful/GPU costs move to a worked-example table below. The
calculator and the browser-pools section now derive from the same
memory x rate math instead of a hardcoded per-browser multiplier.
@robertjamesprior
robertjamesprior requested a review from juecd August 18, 2026 21:13
@mintlify

mintlify Bot commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
Kernel 🟢 Ready View Preview Aug 18, 2026, 9:14 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

1 participant