Moderate to move
MySQL HeatWave on OVHcloud: what it becomes and what it costs.
On OVHcloud, MySQL HeatWave becomes MySQL on OVHcloud Public Cloud instances (replicas, Orchestrator, XtraBackup), or an OVHcloud managed database. Same engine. HeatWave's in-memory analytics has no drop-in equivalent; the OLTP part moves as MySQL.
Effort grade
Moderate
Same software, self-hosted: you patch, back up and fix it
Cost after the move, before engineer time
40% of today
Open-source replacement exists but someone has to run it; residual is servers plus the engineer time counted separately.
Engineer time
6 h a month
To run the replacement: patching, backups, on-call. Plus about 5 engineer days for the move itself.
Other ways to replace it
The report lets you pick any of these per service; the figure and the grade follow.
Managed MySQL at OVHcloud, or an OVHcloud managed database
Where OVHcloud sells managed MySQL, backups and failover stay someone else's job.
55% of today · Easy
Your own MySQL HeatWave line, from your export
Drop one month of your Oracle Cloud cost export and the report prices every service, MySQL HeatWave included, on OVHcloud list prices of 18 Oct 2026, net of the engineer time to run it. In your browser; nothing is uploaded.