Moderate to move
Cloud Functions on Vultr: what it becomes and what it costs.
On Vultr, Cloud Functions becomes containers on Vultr Kubernetes Engine, or long-running services on Vultr Cloud Compute instances. Handlers port to containers; GCP event triggers need re-wiring.
Effort grade
Moderate
Same software, self-hosted: you patch, back up and fix it
Cost after the move, before engineer time
35% of today
$0.0000025 per GB-second is about $6.5 per always-on GB plus invocations; a CX33 replaces a typical fleet, 35% with the one-server floor.
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.
Knative or OpenFaaS on Vultr Kubernetes Engine (VKE)
Keeps the function shape and scale-to-zero on your own cluster; GCP event triggers are still re-wired.
45% of today · Moderate
Cloudflare Workers
Stays serverless at a flat, cheap price; handlers are rewritten for the Workers runtime and GCP triggers are replaced by HTTP and queues.
50% of today · Hard
Your own Cloud Functions line, from your export
Drop one month of your Google Cloud cost export and the report prices every service, Cloud Functions included, on Vultr list prices of 18 Oct 2026, net of the engineer time to run it. In your browser; nothing is uploaded.