ROI calculator
Estimate the cost of moving these reads off the warehouse.
Put in the endpoints you might move: request volume, current warehouse cost, repeat rate, and CDN hit rate. The calculator sizes a small Offloader fleet and compares its cost with what those reads cost today. It is an estimate, not a promise.
Computed entirely in your browser. Your numbers are never sent, stored, or logged.
Estimate
| Repeatable warehouse cost | — |
| Offloader infrastructure | — |
How this is computed
What the estimate assumes
The plain difference
Savings = the repeatable part of your warehouse cost minus the cost of the Offloader fleet. The three scenarios show how much of that spend might actually clear once those reads move.
How the fleet is sized
The calculator converts monthly requests into a
busy-hour rate, assumes traffic can peak at about
4x the average, then sizes enough instances for that
peak. It uses the measured
~2,500 req/s per 4-vCPU instance from
the benchmark, with a minimum of two instances for
availability.
Only the repeatable reads
Offloader serves known endpoint shapes from a snapshot. Ad-hoc queries, internal BI, and one-off reads stay on the warehouse. The saving applies only to the repeatable share of the bill.
Where it won't overclaim
Sizing is an estimate from a benchmark, so confirm it with a pilot. On committed warehouse capacity, savings are only potential until you downsize the tier. The diagnostic separates real savings from savings that need a finance or capacity action.
Ready for the real number?
Book the paid diagnostic.
We use your real traffic and query history to decide what can move, what it costs today, what the Offloader fleet would cost, and which savings finance can actually count.