Engineering Docs

Cloud Storage, CDN Bandwidth & Egress Cost Calculator

Model monthly infrastructure expenditure across object storage classes, CDN edge cache-hit ratios, and Class A/B API operations.

Workload Reference Profiles:

Workload & Routing Parameters

1 TB 500 TB 1,000+ TB
1 TB 500 TB 1,000+ TB
88% (Standard Production CDN)
0% (Uncached Origin) 85% (Standard) 99% (Immutable)
Active Billing Vectors toggle components
GB-Month Allocation

Includes base storage volume and minimum retention commitments.

Split by Cache-Hit %

Models origin cache-miss fetches plus regional CDN edge delivery.

Millions / mo
Optional
Estimated Monthly Infrastructure Cost
$0
Annual Run-Rate $0
Eff. Egress / GB $0.000
Origin Offload 0.0%
CDN Net Savings $0/mo
Monthly API Ops 0M
Calibrated against October 2026 published cloud & CDN rate cards. View Calculation Equations →

Expenditure Breakdown by Vector

Lowest-Cost Provider Stacks

Ranked by Monthly TCO

How Cloud Storage & Egress TCO Is Calculated

01. Cache-Hit Bandwidth Split

Origin Fills vs. Edge Delivery

When a CDN serves 100 TB of monthly traffic at an 88% cache-hit ratio, 88 TB is billed at the lower CDN edge rate while 12 TB is fetched from origin storage. Adding an Origin Shield PoP collapses duplicate regional misses, reducing origin bandwidth exposure further.

02. Zero-Egress Disruption

Hyperscaler vs. Bandwidth Alliance

Legacy hyperscalers (AWS S3, GCP, Azure) subsidize storage hardware by charging 5x–10x markups on outbound internet egress ($0.085–$0.14/GB). Modern S3-compatible stores like Cloudflare R2 and Backblaze B2 eliminate origin egress fees across peered CDN networks.

03. Request & Retrieval Penalties

Lifecycle Tiering Break-Even Math

Moving data to Infrequent Access or Archive tiers cuts per-GB storage rates by 45%–80%, but introduces per-GB retrieval fees ($0.01–$0.03/GB) and 2x–4x higher API operation costs. Workloads with high read velocity frequently lose money when prematurely tiered down.

Cloud Storage & CDN Engineering Reference

18 technical specifications covering egress mathematics, S3 lifecycle formulas, Origin Shielding, and NAT Gateway avoidance.

View all 18 guides →

Technical Frequently Asked Questions

Most object storage platforms measure capacity in binary gibibytes (1 GiB = 1,073,741,824 bytes) while network interfaces measure transfer in decimal gigabytes (1 GB = 1,000,000,000 bytes). Consequently, 100 TB of decimal files occupies 90.95 TiB of binary storage, creating a 7.37% unit conversion discrepancy on raw invoice line items.
No. AWS waives the S3-to-CloudFront data transfer-out fee ($0.00/GB) for origin cache misses. However, you still pay S3 Class B GET request fees on every origin fetch, CloudFront regional data transfer-out to the internet, and CloudFront per-10,000 HTTPS request charges.
Cloudflare R2 charges $0.015/GB-month for storage and $0.00 for egress. However, for cold archival workloads that rarely egress data, Backblaze B2 ($0.006/GB-month) or AWS S3 Glacier Instant Retrieval ($0.004/GB-month) cost 60% to 73% less per stored terabyte. Additionally, workloads generating billions of small-object PUT or LIST calls must carefully audit Class A operation charges.
No. The Daktan calculation engine runs 100% locally inside your web browser via client-side JavaScript. No infrastructure metrics, storage volumes, or cost estimates are transmitted to or stored in any backend database.