Moderate to move
Memorystore on Vultr: what it becomes and what it costs.
On Vultr, Memorystore becomes Valkey on Vultr Cloud Compute instances, or a Vultr Managed Database. Protocol-compatible. 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
35% of today
A 5 GB basic instance is $0.049/h = $36/mo; a CX23 (4 GB) is €5.49, 35% with persistence and a replica.
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 Valkey / Redis at Vultr, or a Vultr Managed Database
Where Vultr sells a managed cache, persistence and failover stay someone else's job; about twice the bare server.
60% of today · Easy
Hosted Redis elsewhere (Upstash, Redis Cloud)
A cache vendor next to Vultr: no operations, little saving, and cross-provider latency on every call.
90% of today · Easy
Your own Memorystore line, from your export
Drop one month of your Google Cloud cost export and the report prices every service, Memorystore included, on Vultr list prices of 18 Oct 2026, net of the engineer time to run it. In your browser; nothing is uploaded.