Cloud Exit Cost Calculator

Work out cloud exit cost instantly with clear inputs, formula shown and shareable results.

About Cloud Exit Cost Calculator

Exit cost is dominated by re-engineering, not by egress. Extracting 300 TB costs about 27,000 in transfer, while replacing fourteen managed services with self-hosted equivalents costs 840,000 in engineering. That asymmetry is the real lock-in: proprietary managed services, not the data transfer bill that gets the attention.

Formula

Exit cost

egress = TB x 1000 x per-GB rate; engineering = managed services x per-service replacement cost

Worked example

With the default values below, Cloud Exit Cost Calculator returns Total exit cost of $867,000. Change any input above and every figure here is recalculated in your browser.

Inputs used

Data to extractminimum 0 TB: 300 TB
Egress price per GBminimum 0: 0.09
Managed services to replaceminimum 0: 14
Engineering cost per service replacedminimum 0: 60,000

Results

Total exit cost: $867,000
Data egress: $27,000
Re-engineering managed services: $840,000
Share of cost from engineering: 96.9%

Step by step

1Values used
2Exit cost
3Total exit cost= 867,000
4Data egress= 27,000
5Re-engineering managed services= 840,000
6Share of cost from engineering= 96.9

Assumptions and limits

The result is derived only from the 4 inputs listed above. Anything not among them is not part of the calculation.
In particular, this calculator does not take inflation, tax or compounding frequency into account.
Figures are rounded for display to 1 decimal place, so totals built from several rounded parts can differ slightly from the unrounded arithmetic.

How these calculators are built and tested is described on the Methodology page. If a figure looks wrong, please report it.

Frequently Asked Questions

Do providers waive egress for leaving?

Following European regulatory pressure, the major providers now offer free egress for customers fully leaving, subject to conditions. It does not apply to partial or ongoing transfers.

How is lock-in reduced?

Prefer open standards and portable runtimes where the cost is reasonable — containers, PostgreSQL, S3-compatible APIs, Kubernetes. Accept lock-in deliberately where the managed service saves enough to justify it.