Skip to content

Update network volume pricing to $0.09/GB/month flat (STO-813) - #904

Open
jenocram-Runpod wants to merge 1 commit into
mainfrom
sto-813-network-volume-price
Open

jenocram-Runpod wants to merge 1 commit into
mainfrom
sto-813-network-volume-price

Conversation

@jenocram-Runpod

Copy link
Copy Markdown

What

Updates the docs for the standard (MooseFS) network volume price change in STO-813.

Tier Old New
Under 1 TB $0.07/GB/month $0.09/GB/month
1 TB and up $0.05/GB/month $0.09/GB/month

The 1 TB discount goes away, so every page now shows one flat rate and the tier rows and wording are removed. High-performance storage, Global Volumes, container disk, and volume disk prices are unchanged.

Pages changed

  • pods/pricing.mdx
  • pods/storage/types.mdx
  • storage/network-volumes.mdx
  • storage/s3-api.mdx
  • serverless/pricing.mdx
  • serverless/storage/overview.mdx
  • accounts-billing/billing.mdx

Do not merge yet

This must not merge until the go-live date is set and the billing change (RunPod repo) has shipped. Customers get about 2 weeks' notice before go-live, and the docs should change on the same day the new price takes effect.

🤖 Generated with Claude Code

Standard network volumes move from $0.07/GB/month (under 1 TB) and
$0.05/GB/month (1 TB and up) to a flat $0.09/GB/month. The 1 TB
discount is removed. High-performance storage is unchanged. (STO-813)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@mintlify

mintlify Bot commented Oct 15, 2026 •

Copy link
Copy Markdown
Contributor

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

Project Status Preview Updated
runpod-docs 🟢 Ready View Preview Oct 15, 2026, 4:59 PM

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

This branch was successfully deployed

1 active deployment
staging — e2fb6419 Deployed Oct 15, 2026 by mintlify[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants