Show GB-hour billing model on pricing page - #508
Closed
robertjamesprior wants to merge 1 commit into
Closed
Conversation
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
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
force-pushed
the
hypeship/gb-hour-pricing-clarity
branch
from
September 3, 2026 02:21
d9a584c to
9e9e2b2
Compare
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Risk assessment: Very Low
Decision: Approve.
This PR touches two files on a Mintlify docs site (info/pricing.mdx, snippets/calculator.jsx; +21/−10). There is no production billing, auth, or infrastructure code in the diff.
What changed
- Pricing copy replaces a per-browser-type
$/sec table with standard vs. GPU-accelerated $ /GB-hour rates, plus a worked-example table for headless / headful / GPU memory allocations. - The in-page calculator now derives per-second cost as memory × rate instead of a hardcoded multiplier. The resulting rates match the previous constants exactly:
- Headless:
1 × 0.0000166667=0.0000166667 - Headful:
8 × 0.0000166667=0.0001333336 - GPU:
6 × 0.0001333336=0.0008000016(same as the old48×multiplier)
- Headless:
Why Very Low
- Documentation and a client-side estimator widget only
- Small, easy-to-verify diff with equivalent calculator outputs
- No shared services, schema, auth, or deploy/infra changes
- No CODEOWNERS file, so codeowner review is not required
No prior approval existed on this PR, so this is the first approval.
Sent by Cursor Automation: Assign PR reviewers
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
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 bygpu/overageonly, 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 devpreview.Addresses KERNEL-1959.