Document protected compute tier pricing and interruption semantics - #301
Merged
Conversation
State the protected tier price (2x the interruptible rate, verified against production billing configuration) in the compute tier docs, the TOML reference, and the cost calculation page. Correct the tier framing: compute_tier sets the interruption guarantee, not spot vs on-demand placement, and interruptible instances can also be relocated by platform capacity consolidation. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
jonoirwinrsa
approved these changes
Jul 22, 2026
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
2 participants
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
The docs described the
protectedcompute tier as "increased cost" without stating the price. This PR states it plainly: protected compute is billed at 2x the interruptible rate, verified against the production billing configuration (the premium is exactly 2x for CPU, memory, and every GPU type on all plans).It also corrects the tier framing while in the area:
compute_tiersets the interruption guarantee, not spot vs on-demand placement. Interruptible instances prefer preemptible capacity but can run on any capacity (billed at the base rate regardless); protected instances run only on capacity that cannot be reclaimed.Changes
scaling/scaling-apps.mdx: Price column in the tier table, new Pricing subsection (2x rate, whole-instance scope, tier fixed at instance start, pricing-page rates are interruptible rates), new Interruptions and Consolidation subsection, corrected section intro.toml-reference/toml-reference.mdx:compute_tierrow now states the interruption-guarantee semantics and the 2x price; example comment updated.calculating-cost.mdx: notes that listed rates are interruptible-tier rates and protected bills at 2x, with a link to the Compute Tier section.🤖 Generated with Claude Code