exodus Heroku · Railway · Render · Fly · VPS → Google Cloud Run
Rails to
Cloud Run
Connect Exodus to Claude and point it at your repo. It shows what your app will cost on Cloud Run, rewrites what needs rewriting and moves it. Then you pay only while your app works.
Cloud Run
A copy of your app runs only while someone uses it. Lit = billed.
01 The idea
Your app works minutes a day. Why pay for 24 hours?
Most hosts keep your app running all day and bill all day. Cloud Run starts it when someone visits and stops it when they leave. You pay for the time in between.
02 Why Cloud Run
What your app gets on Cloud Run
Google runs your app the way it runs its own services. You bring the code; the servers, scaling and certificates are Google's job.
Pay only while it works
No visitors, no bill for compute. Every month a free allowance covers small apps entirely.
Grows on its own
A spike of visitors and Cloud Run adds copies of your app in seconds, then removes them when it calms down. No plan to upgrade.
Close to your visitors
Visitors enter Google's own network near where they are, and the request travels on Google's lines to your app, in any of 43 regions.
Releases without fear
Every release is a separate version. Show it to 5 % of visitors first, switch everyone when it looks right, go back in one click.
Nothing to babysit
No servers to patch, no certificates to renew, no process to restart at night. That is Google's job now.
All of Google next door
When the app grows, databases, AI models, queues and analytics are in the same account, one permission away, on the same bill.
03 What it costs
Good things can run for cents
A Rust backend with a web app, a bot, a side project: with a modest audience they fit in Google's free allowance, and the bill is mostly what you store.
Monthly bill
A Rust backend with its web app
- Cloud Runfree
- Traffic out$0.04
- Database, files, secret$0.07
Monthly bill
A Slack bot with a task queue
- Cloud Runfree
- Cloud Tasksfree
- Database, secret$0.07
Monthly bill
A SaaS with a Postgres database
- Cloud Run, API, worker, webfree
- Postgres, smallest$9.40
- Traffic, files, the rest$1.00
Monthly bills of three apps we run on Cloud Run, from Google's billing export, October 2026. A busy app costs more: Exodus tells you how much before you move, and says so when moving is not worth it.
04 How it works
Three steps, and you only press go
Exodus gives Claude the playbook of a move. Claude reads your project, does the work, and shows you each change before it lands.
-
1
Connect
Add the Exodus plugin to Claude Code, or connect it to Antigravity CLI or any MCP client. Open your project and ask to move it.
-
2
Check
Exodus reads the project and answers in plain words: what it costs now and on Cloud Run, what to change, and whether the move is worth it.
-
3
Move
Claude makes the changes, sets up deploys from GitHub and copies your data. You review, then switch the domain. The old host stays as a way back.
05 What's inside
Open tools, one playbook
The playbook comes from moving our own apps to Cloud Run. The tools are open source.
Scanner
A fast tool written in Rust. Reads your project on your machine and finds what to change and what it will cost.
Claude plugin
The playbook your agent follows, step by step, with the scanner and Google's own Cloud Run tools at hand. Works in any MCP client.
Guard
A check in GitHub that keeps the app cheap after the move, so nobody slips an always-on job back in.
Dashboard
Your move as a checklist for the team, and on day 30 the real bill next to the estimate.
Soon06 Early access
Move your first app with us
Exodus is in early access. We move the first apps together with their teams and turn every move into the playbook.