Managed or Self-Run: Break-Even Fleet

Enter the fleet, the managed premium and the rota it would take to run the service yourself. The calculator returns the annual gap and the fleet size at which self-running starts to pay. Every default is illustrative.

Every default here is illustrative. None comes from a price list or a real estate. Replace all eight with your own figures, in one currency.

The managed service Instances in the fleet Production instances of this one technology Managed premium per instance, per month Managed price less the raw compute and storage underneath it

The rota Engineers on the rota Assumption: six to eight for sustainable round-the-clock cover Loaded cost per engineer, per year Salary plus employment costs, in your currency Share of rota time spent on this service (%) On-call cover and tooling for this technology. Leave out upgrade and incident work, which is counted on the right

Work that scales with the fleet Upgrade days per instance, per year Patching, version upgrades and restore tests Incidents per year, across the fleet At the fleet size entered above Cost per incident Extra cost per incident over the managed service: business impact the provider would have absorbed, plus engineering time outside the rota share

Managed premium, per year 0

Self-run cost, per year 0

Annual gap 0

Break-even fleet 0

Managed premium

Self-run: rota

Self-run: per instance

Break-even fleet is the fixed rota cost divided by the saving on each instance. The saving is the yearly premium less the yearly cost of upgrades and incidents for one instance. A working year is taken as 220 days. The model leaves out migration cost and the risk of a change in the project's licence or editions, both of which count against self-running.

Read the full Managed or Self-Run insight →