Worked example · Oracle Cloud
An Oracle Cloud tenancy on E4 shapes and Autonomous Database.
OCPU and memory hours pooled per shape family, an Autonomous Database billed in ECPUs, MySQL HeatWave, block and object storage, and the 10 TB of free egress. Read through the way the calculator reads it: the bill, what it becomes on Hetzner, the verdict, and what would change it.
The bill
$2,582 a month across 11 services after setting aside marketplace. The six largest lines:
| Service | Grade | Today | On Hetzner | Change |
|---|---|---|---|---|
| Oracle Database | Hard | $1,976 | $149 | saves $1,827 |
| Compute | Easy | $204 | $336 | adds $132 |
| Object Storage | Easy | $128 | $38 | saves $90 |
| MySQL HeatWave | Moderate | $125 | ~$50 | saves $75 |
| Container Engine for Kubernetes | Easy | $72 | ~$22 | saves $50 |
| Block Volume | Easy | $43 | $75 | adds $33 |
~ marks a rule-of-thumb ratio; the rest is priced from usage in the file.
What it becomes on Hetzner
- 5 servers: 1× AX102-1, 1× CX53, 2× CX53, 1× CX53
- $696/mo for servers, storage and traffic
- 40 h/mo of engineer time, $3,000
- $16,800 one-off, no payback at this net
Extra cost per year
$13,367
Not worth moving at this size. Hetzner costs more once someone is paid 40 hours a month to run it.
Grow first: at this size the hours decide, not the hardware. 9 of your 11 services move easily; 1 is hard. 85% of the Hetzner figure is priced from your usage; the rest is ratio-priced services and engineer time, which is where the range comes from.
Likely range $4,242 more to $504 less a month. Hetzner list prices of 17 Oct 2026, default assumptions.
The same file on nine destinations
Net per year after engineer time, best first. No destination pays for this account; Hetzner loses least.
| Hetzner | −$13,367 over |
| Scaleway | −$20,660 over |
| OVHcloud | −$21,165 over |
| UpCloud | −$22,012 over |
| Vultr | −$23,687 over |
| Hetzner (US) | −$24,429 over |
| DigitalOcean | −$24,680 over |
| Akamai (Linode) | −$25,229 over |
| Exoscale | −$37,736 over |
What would change the answer
- Engineer time. 40 hours a month at $75/h is $3,000, 81% of the destination figure. Halve the rate or fold the work into an existing team and the verdict moves first.
- Scale. Engineer time grows slowly with the number of servers; hardware grows with the bill. The same mix at three times the size usually flips a marginal answer.
- Moving only part of it. The first wave (foundation: storage, traffic, edge) is Object Storage, Block Volume, Outbound Data Transfer, Load Balancer: $79/mo for about 2 engineer days, with the databases left where they are.
- The hard services. Oracle Database has no equivalent at the destination; keeping them on Oracle Cloud removes their engineer time and their risk from the plan.
Every one of these is a setting in the report. Open the example and change them.