Moderate to move
Cloud SQL on OVHcloud: what it becomes and what it costs.
On OVHcloud, Cloud SQL becomes PostgreSQL / MySQL on OVHcloud Public Cloud instances (Patroni or replicas, pgBackRest), or an OVHcloud managed database. Same engines. On Hetzner you run it yourself; where the destination sells the managed engine (DigitalOcean, OVHcloud and Scaleway for most of them) it costs roughly twice the bare server, still well under today's price.
Effort grade
Moderate
Same software, self-hosted: you patch, back up and fix it
Cost after the move, before engineer time
40% of today
db-custom-2-8192 is about $0.14/h = $100/mo; a CX33 (4 vCPU, 8 GB) is €8.49; with HA, storage and backups, 40%.
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 PostgreSQL / MySQL at OVHcloud, or an OVHcloud managed database
Where OVHcloud sells the managed engine, backups, failover and patching stay someone else's job. Roughly twice the bare server, still well under today's price.
55% of today · Easy
Hosted Postgres elsewhere (Neon, Supabase, Crunchy Bridge)
A managed Postgres vendor next to OVHcloud: no operations, a modest saving, and cross-provider latency to watch.
80% of today · Easy
Your own Cloud SQL line, from your export
Drop one month of your Google Cloud cost export and the report prices every service, Cloud SQL included, on OVHcloud list prices of 18 Oct 2026, net of the engineer time to run it. In your browser; nothing is uploaded.