{{ summaryHeading }}
{{ summaryPrimary }}
{{ summaryLine }}
{{ badge.label }}
CLOUD EDGE USERS {{ visualFlowLabel }}
Choose the transfer boundary that most closely matches the bill line you need to estimate.
Enter the baseline monthly transfer before cache, compression, and retry adjustments. Use TB/PB for decimal units or TiB/PiB for binary billing exports.
{{ cache_hit_percent }}%
Set 0 for direct internet egress, or use measured cache-hit/private-path coverage.
{{ payload_reduction_percent }}%
Use observed byte savings; keep 0 when the transfer metric already reflects compressed bytes.
{{ peak_multiplier }}x
Set 1x for steady state; raise it to estimate peak-month budget pressure.
Enter 0 to omit the budget check from the summary.
$ / mo
Provider presets load common public allowances; edit this for your agreement.
GB
First paid block of traffic after the free allowance.
GB @ $
Second paid block of traffic; set 0 when your price card is flat.
GB @ $
Third paid block of traffic; the final tier covers everything above it.
GB @ $
The final tier applies to all remaining billable transfer.
$ / GB
Leave either value at 0 to model bandwidth-only cost.
M req @ $
{{ retry_overhead_percent }}%
Use a small reserve when production telemetry shows retries or duplicated transfer.
MetricValuePlanning noteCopy
{{ row.metric }} {{ row.value }} {{ row.note }}
TierCharged GBRateCostRuleCopy
{{ row.tier }} {{ row.gb }} {{ row.rate }} {{ row.cost }} {{ row.rule }}
LeverModeled changeMonthly savingsOperator noteCopy
{{ row.lever }} {{ row.change }} {{ row.savings }} {{ row.note }}
PresetMonthly costDeltaEffective rateCaveatCopy
{{ row.preset }} {{ row.cost }} {{ row.delta }} {{ row.rate }} {{ row.caveat }}
Tags: Cloud, Devops, Finance
API Gateway Cost Calculator Estimate API Gateway monthly spend across HTTP, REST, Private REST, and WebSocket traffic with request chunks, transfer, cache, and budget checks.
AWS Lambda Cost Calculator Estimate AWS Lambda monthly cost from requests, billed duration, memory, provisioned windows, streaming overage, free tier, and editable rates.
Object Storage Cost Calculator Estimate monthly object storage cost from average capacity, object size, requests, retrieval, egress, lifecycle exposure, and editable rate cards.
Kafka Partition Count Calculator Plan Kafka topic partitions from throughput, event rate, consumer parallelism, replication footprint, broker balance, and keying warnings.
Customize
Advanced
:

Outbound cloud traffic often looks harmless until a launch, media download feature, analytics export, backup restore, or cross-region copy starts moving terabytes away from the service boundary. Egress is that outbound movement. It can be traffic from compute to public users, object storage downloads, API responses, database replication, disaster recovery sync, or data sent from one region to another. Many providers bill those bytes separately from compute and storage, so a workload can be technically healthy and still surprise the budget.

The hard part is not only counting bytes. The billed amount depends on where the traffic leaves, which region or network tier is involved, how much transfer is included, whether a cache or private path avoids the charged boundary, and whether a contract changes the public rate card. A raw 12 TB workload can produce very different bills when some traffic is served from a content delivery network, responses are compressed, retries duplicate failed downloads, or the same data moves across regions instead of to internet users.

Diagram of raw cloud traffic passing through cache and payload savings before reaching a charged internet or cross-region transfer boundary.

Several invoice terms recur across providers. Data transfer out usually means bytes sent away from a service, region, or provider network. Internet egress is traffic sent to public users or external systems. Cross-region transfer covers traffic between provider regions, often for replication, disaster recovery, or analytics. Included transfer is a monthly allowance subtracted before paid tiers. The exact wording varies by provider and service, so the pricing boundary has to match the bill line being estimated.

Workload pattern Why egress changes What to check before budgeting
Media or file downloads Large objects make bytes grow faster than request count. Measure delivered object size after compression and variants.
CDN-backed delivery Cache hits can reduce origin transfer, while misses still bill the origin path. Use the hit rate that actually avoids the modeled charge.
API workloads Repeated JSON responses, pagination choices, and retries can add up. Separate request charges from byte charges and inspect retry overhead.
Backups and migrations One-time bulk transfer can cross several paid tiers in one month. Model steady traffic separately from the peak month.

Egress estimates are planning numbers, not provider quotes. Public prices, destination classes, regional rules, taxes, credits, support programs, and private contracts can change the billed amount. A useful estimate makes the assumptions visible early enough for a team to compare cache, compression, private connectivity, data placement, or provider options before the invoice confirms the wrong architecture.

How to Use This Tool:

Start with the traffic boundary you want to price, then adjust the rate card until it matches the provider page, contract, or billing export you trust.

  1. Choose Pricing preset for a planning starting point, or select Custom editable rate card when you have contract rates or a bill line to mirror.
  2. Enter Monthly data out and choose the unit. Use GB, TB, or PB for decimal values; use TiB or PiB when the source number came from a binary report.
  3. Set Cache or private-path offload, Payload reduction, and Retry overhead. These percentages turn raw transfer into adjusted egress before the included allowance and tiers are applied.
  4. Open Advanced when a preset does not match the price card. Edit included transfer, tier sizes, tier rates, final tier rate, request count, and request price.
  5. Use Peak month multiplier for launches, migrations, disaster recovery tests, seasonal traffic, or cache warmups. Use Monthly budget cap when the summary should flag budget pressure.
  6. Fix any Check egress assumptions message before relying on the result. Negative rates, invalid units, and impossible percentages block the ledger and charts because the model would be charging impossible traffic or prices.

After the first pass, compare Pricing boundary, Source transfer, Adjusted egress volume, and Billable transfer with the same month in your billing export. A mismatch usually means the transfer boundary, unit family, included allowance, destination class, or service-specific fee is different.

Interpreting Results:

Estimated monthly cost is the modeled spend after adjusted transfer passes through included transfer and paid tiers, with any request add-on included. Annualized run rate multiplies that monthly estimate by 12, so it fits steady traffic better than one-time migrations.

Adjusted egress volume is the number to sanity-check first. It starts with source transfer, removes cache or private-path offload, removes payload reduction, and adds retry overhead. If it looks too low, confirm that the offload percentage is traffic that avoids the billed boundary, not traffic that merely hits an application cache inside the same boundary.

Billable transfer is adjusted transfer after the included allowance is subtracted. Tier Ledger shows how many gigabytes land in each paid band and which rate applies. A workload just above the included allowance can move from no bandwidth charge to a small paid charge, while a very large workload may show a lower average rate because later tiers are cheaper.

Budget variance is positive when the estimate is under the entered monthly cap and negative when it is over. Peak-month rows reuse the same rate card and savings assumptions, so a migration that also changes cache behavior, payload size, or retries should be modeled as a separate scenario.

Provider Comparison, Egress Cost Curve, and Provider Cost Map show sensitivity, not final provider truth. Use them to decide which assumptions deserve verification, then check current provider pricing, destination rules, billing exports, taxes, support credits, and contract terms before committing a budget.

Technical Details:

Egress cost is a marginal pricing problem. Unit conversion comes first because decimal terabytes and binary tebibytes do not represent the same number of gigabytes. Traffic adjustment comes next: avoided traffic is removed, smaller payloads reduce the byte count, retry overhead adds duplicated transfer, and the remaining adjusted gigabytes are compared with the included allowance.

Tiered pricing charges paid transfer in order. Each finite tier consumes up to its configured size, and the final tier covers everything left. The effective rate is therefore an average across the adjusted transfer, not the marginal price of the last gigabyte. Request add-ons stay separate from bandwidth cost because they scale with request count rather than transferred bytes.

Formula Core:

The equation below shows the governing monthly calculation. Percent inputs are interpreted as fractions, so 35% cache offload becomes 0.35.

Gadjusted = Graw×(1−c)×(1−p)×(1+r) Gpaid = max(0,Gadjusted−Gincluded) Ctransfer = ∑tiers(Gtier×Rtier) Ctotal = Ctransfer+(q×R) Reffective = CtotalGadjusted
Symbol Meaning Visible input or output
Entered transfer converted to gigabytes. Monthly data out and Source transfer
Traffic avoided by cache, private paths, or same-boundary placement. Cache or private-path offload
Payload reduction from compression, smaller objects, or trimmed responses. Payload reduction
Duplicate transfer from retries or repeated attempts. Retry overhead
Monthly requests in millions and the price per million requests. Request add-on and Request add-on cost

For the default 12 TB scenario, decimal unit conversion gives 12,000 GB of source transfer. With 35% cache or private-path offload, 12% payload reduction, and 3% retry overhead, adjusted transfer is 7,069.92 GB. After 100 GB of included transfer, 6,969.92 GB remains billable. At $0.09 per GB in the first paid tier and no request add-on, the monthly transfer cost is $627.29 and the effective rate is about $0.0887 per adjusted GB.

Boundary and Precision Rules:

Rule Applied behavior Why it matters
Decimal and binary units 1 TB is 1,000 GB; 1 TiB is 1,024 GB; 1 PB is 1,000,000 GB; 1 PiB is 1,048,576 GB. Billing exports and storage dashboards may not use the same unit family.
Included transfer Included GB is subtracted after traffic adjustments and cannot exceed adjusted transfer. The paid transfer can be zero even when source transfer is not zero.
Finite tiers Tier 1, Tier 2, and Tier 3 charge only up to their configured size; size 0 skips that tier. Removing a tier changes which rate the remaining transfer reaches.
Final tier The final rate is open-ended for all paid transfer above the finite tiers. Very large months need a credible final rate or a provider quote.
Displayed precision Currency is rounded for display, while chart and JSON values keep numeric detail where useful. Small rounding differences can appear when reconciling against invoice line items.

The provider-style presets are editable worksheets. AWS, Azure, and Google Cloud price data can vary by region, service, destination, network tier, support program, and billing agreement. A correct model for one boundary can be wrong for another boundary even when the transfer volume is identical.

Accuracy and Privacy Notes:

Provider pricing pages, contract terms, and billing exports are the source of truth for live commitments. The calculation does not ask for provider credentials, does not connect to a billing account, and cannot detect taxes, credits, marketplace discounts, support charges, NAT processing, load balancer processing, CDN cache-fill rules, or service-specific exceptions.

Use conservative assumptions for procurement, architecture approval, or migration planning. If a provider asks customers to contact sales above a traffic level, treat the last tier as a placeholder until the account team confirms the rate and any aggregation rules.

Worked Examples:

Typical monthly workload. With the default AWS planning preset, 12 TB of Monthly data out, 35% cache or private-path offload, 12% payload reduction, 3% retry overhead, and a $900 budget cap, the result shows Adjusted egress volume of 7,069.92 GB and Billable transfer of 6,969.92 GB. Estimated monthly cost is $627.29, leaving Budget variance $272.71 under the cap.

Included-transfer edge. Set source traffic to 100 GB, set offload, payload reduction, and retry overhead to 0%, and keep included transfer at 100 GB. Billable transfer is 0 GB and the bandwidth charge is $0. Raise source traffic to 101 GB and the first paid gigabyte reaches Tier 1, so the same rate card produces a small bandwidth charge instead of a fully included month.

Troubleshooting path. If Check egress assumptions appears, review the field named in the message before using the tables. Cache offload above 99%, payload reduction above 90%, negative request values, or negative tier rates prevent a meaningful Tier Ledger.

FAQ:

Why does the same transfer volume cost different amounts?

The transfer boundary changes the rate card. Internet egress, cross-region replication, CDN delivery, private connectivity, provider network tiers, and contract discounts can each have different prices and included allowances.

Should I enter CDN cache hit rate directly?

Only enter the percentage that reduces the billed transfer being modeled. A high edge cache hit rate helps this estimate only when it prevents origin or provider egress from crossing the charged boundary.

Why do TB and TiB change the result?

TB is decimal and converts to 1,000 GB. TiB is binary and converts to 1,024 GB. The selected unit changes Source transfer before the pricing tiers are applied.

Why is Provider Comparison not a final provider decision?

The comparison uses editable planning presets against the same traffic assumptions. Provider selection also depends on storage price, compute price, latency, regions, compliance, support, discounts, and service fit.

What should I do when the estimate and invoice disagree?

Match the invoice month, service, region, destination class, included transfer, and unit first. Then edit the tier sizes and rates until Pricing boundary and Tier Ledger reflect the actual bill line.

Glossary:

Egress
Outbound data leaving a cloud service, region, network boundary, or provider environment.
Data transfer out
The billable outbound traffic category used by many cloud pricing pages and invoices.
Included transfer
A transfer allowance subtracted from adjusted egress volume before paid tiers are charged.
Effective rate
The total modeled cost divided by adjusted egress volume, useful for comparing tiered and flat-rate assumptions.
Retry overhead
Extra transfer caused by repeated downloads, failed attempts, replayed jobs, or duplicated replication.
Peak month multiplier
A traffic multiplier for a launch, migration, campaign, or other month that is larger than steady state.

References: