PricingNest

Bandwidth Cost Calculator

Estimate egress/bandwidth cost and a recommended price using your own per-GB costs, fixed overhead, and target gross margin.

Inputs

Scenarios

Applies to the selected input only; adjust other inputs manually if needed.

Results

Estimated monthly cost
-
-
Recommended monthly price
-
-
Effective price per GB
-
-
Gross margin
-
-

Insights

Updated from your current assumptions.
Adjust inputs to see recommendations.

Compare

Save a baseline to see deltas for every output.
Estimated monthly cost
Baseline -
Delta -
Recommended monthly price
Baseline -
Delta -
Effective price per GB
Baseline -
Delta -
Gross margin
Baseline -
Delta -

Sensitivity

Adjust the input to see how outputs respond to small changes.
Estimated monthly cost
Low -
Base -
High -
Recommended monthly price
Low -
Base -
High -
Effective price per GB
Low -
Base -
High -
Gross margin
Low -
Base -
High -

Guide

Use this page to test assumptions, compare scenarios, and document the reasoning behind a pricing decision. Start with the example setup below, then adapt the inputs to match your own product, costs, and packaging.

Example Inputs Outputs How it works Modeling tips Validation checks Common mistakes Interpretation Use cases Mini walkthroughs Scenarios Edge cases FAQ

Example (defaults)

Example inputs: GB egress per month = 2000, Cost per GB = 0.03, Monthly fixed cost = 300

Estimated monthly cost
$360.00
Recommended monthly price
$1,800.00
Effective price per GB
$0.90
Gross margin
80%

Inputs explained

Input Default Notes
Currency USD Adjust to match your product assumptions.
GB egress per month 2000 Adjust to match your product assumptions.
Cost per GB 0.03 Adjust to match your product assumptions.
Monthly fixed cost 300 Adjust to match your product assumptions.
Target gross margin (%) 80 Adjust to match your product assumptions.

Outputs explained

Output What it means
Estimated monthly cost A money value based on your selected currency.
Recommended monthly price A money value based on your selected currency.
Effective price per GB A money value based on your selected currency.
Gross margin A percentage value derived from the inputs.

How it works

  • Bandwidth variable cost = GB per month x cost per GB.
  • Monthly cost = bandwidth variable cost + fixed overhead.
  • Recommended price = monthly cost / (1 - target margin).

Modeling tips

  • Use a blended egress cost per GB across regions and CDNs.
  • Model average monthly GB, not peak traffic spikes.
  • Include CDN request costs in fixed overhead if they are material.
  • Apply commitment discounts by lowering the blended cost per GB.
  • Test a high-traffic scenario to confirm margins hold at scale.
  • If you have free transfer, subtract it before entering GB.

Validation checks

  • Effective price per GB should exceed cost per GB at your target margin.
  • Recommended price should be greater than or equal to monthly cost.
  • If fixed cost is zero, confirm you are not missing support overhead.
  • Monthly cost should equal GB per month x cost per GB plus fixed overhead.

Common mistakes

  • Using list egress pricing instead of blended rates.
  • Mixing internal transfer with billable egress.
  • Ignoring regional cost differences.
  • Forgetting free transfer allowances or CDN credits.
  • Leaving out request fees that are material.

Interpretation

  • Treat effective price per GB as the margin-safe floor for the traffic mix you modeled.
  • If bandwidth cost is volatile or externally billed, test a separate bandwidth line item or pass-through threshold instead of hiding it inside a bundled plan price.
  • If CDN or origin-driven costs differ materially across cohorts, compare blended and high-traffic scenarios before publishing one public rate.
  • If regional egress cost varies materially, use regional pricing guardrails or enterprise exceptions instead of forcing one global GB price.
  • If fixed overhead is meaningful relative to usage, pair bandwidth pricing with a base fee or minimum commitment.

Use cases

CDN pricing
Estimate margin-safe bandwidth pricing for content delivery.
High-traffic tiers
Model pricing for customers with large monthly egress.

Mini walkthroughs

Egress pricing baseline
  1. Enter monthly GB and blended cost per GB.
  2. Add fixed overhead and margin target.
  3. Review effective price per GB.
Cost sensitivity
  1. Increase cost per GB for a high-cost region.
  2. Check the recommended price impact.
  3. Decide if regional pricing is needed.

Scenarios

Low egress plan
500 GB per month to model a starter plan with low traffic.
High egress plan
2 TB per month to test pricing for bandwidth-heavy customers.
Multi-region traffic
Increase cost per GB to reflect higher-cost regions or CDN mix.
CDN offload
Lower cost per GB to model improved cache hit rates.

Edge cases

  • If GB per month is 0, the model only reflects fixed overhead.
  • If cost per GB is 0, confirm CDN or egress pricing is not missing.
  • If target margin is too high, price may exceed market benchmarks.
  • If cost per GB spikes in a region, consider region-specific pricing.

FAQ

How do I turn blended egress cost into a bandwidth price floor?
Add variable egress cost and fixed overhead into monthly cost, divide by expected GB, then apply your target gross-margin buffer to set a defendable floor.
When should bandwidth be priced as a separate line item?
Break bandwidth out when usage varies widely across accounts or when bundling it would force low-usage customers to subsidize heavy ones.
When should CDN costs be passed through separately?
Use a separate pass-through or surcharge when CDN-heavy traffic materially changes margin and a single blended rate would either underprice heavy cohorts or overprice everyone else.
How should I handle regional egress differences in pricing?
Use weighted regional averages for standard plans, then add regional guardrails, enterprise carve-outs, or separate rate cards when one region is materially more expensive.
When does bandwidth overhead require a base fee or minimum commitment?
Add a base fee or minimum commit when support, monitoring, and traffic overhead are too large to recover reliably from per-GB pricing alone.
Should I use peak or average monthly GB when pricing bandwidth?
Use average monthly GB for your baseline, then stress-test traffic spikes or p90 months before publishing public rates.
How do I test whether margin still holds for traffic spikes or heavy accounts?
Run a heavier traffic scenario with higher GB, weaker cache performance, or a costlier regional mix and confirm gross margin still clears your target.
Can I combine bandwidth with storage or compute in one plan?
Yes, but model each cost driver separately first so you know whether a blended plan hides bandwidth risk or needs an explicit overage component.