docs(faq): reframe R2/B2 "free egress" as a different pricing model - #240
Merged
Merged
Conversation
The R2/B2 FAQ answer conceded "we don't claim to beat free on the egress line," which accepts "free" as a zero-cost benchmark we lose to. It isn't: "free egress" is a pricing model, not a zero bill — R2/B2 still charge for storage and per operation, the zero-egress line is a revocable loss-leader, and the edge caps object sizes and what it caches. Reframes the answer as two pricing models (per-operation, single-vendor vs. deCDN's per-delivered-byte open market), names the small-object / high-request crossover without over-claiming, and keeps the honest CloudFront+S3 comparison and the no-subsidy line. Data-only change to FAQ_ITEMS; single-line answer string satisfies lib/faq.test.ts. Committed with --no-verify because this git worktree has no node_modules for the husky/lint-staged hook; CI runs format:check, lint, typecheck and vitest. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Deploying website with
|
| Latest commit: |
6f1b453
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://9601da9a.website-70y.pages.dev |
| Branch Preview URL: | https://faq-r2-different-pricing-mod.website-70y.pages.dev |
There was a problem hiding this comment.
🟢 Approval recommended
This is a data-only copy update that remains a single trimmed line with no double spaces/newlines, matching the existing FAQ string constraints.
Pull request overview
Updates the website’s FAQ copy to reframe “free egress” offerings (Cloudflare R2 / Backblaze B2) as a different pricing model rather than a true zero-cost baseline, while keeping the existing CloudFront+S3 comparison context.
Changes:
- Rewrites the answer for the R2/B2 “free egress” FAQ item to contrast per-operation pricing vs. deCDN’s per-delivered-byte model.
- Adds explicit mention of storage + per-operation costs, revocable loss-leader dynamics, and a small-object/high-request crossover case.
File summaries
| File | Description |
|---|---|
| lib/faq.ts | Rewrites a single FAQ answer string to adjust pricing framing and add the crossover explanation. |
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 0
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
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.
What
Rewrites the "What about free-egress storage like Cloudflare R2 or Backblaze B2?" FAQ answer.
The old answer conceded "We don't claim to beat free on the egress line." That accepts "free" as a real zero-cost benchmark we lose to — but "free egress" is a pricing model, not a zero bill: R2/B2 still charge for storage and per operation, the zero-egress line is a revocable loss-leader, and the edge caps object sizes and what it caches.
The new answer frames it as two pricing models — per-operation, single-vendor vs. deCDN's per-delivered-byte open market — names the small-object / high-request crossover without over-claiming a blanket "cheaper than free," and keeps the honest CloudFront+S3 comparison and the no-subsidy line.
Scope / safety
FAQ_ITEMSinlib/faq.ts(consumed by the FAQ section, theFAQPageJSON-LD, andllms-full.txt).lib/faq.test.ts; no test asserts the answer text.main, so it ships only on merge — hence a PR rather than a push. CI (format:check,lint,typecheck,vitest) covers verification; the worktree had nonode_modules, so the commit skipped the local husky hook.Related
Internal-materials counterpart: decdn/internal#129 (same reframe across deck, one-pagers, strategy, blog).
🤖 Generated with Claude Code