Free · works with the coding agent you already use

Stairway to Cloud Run

Exodus and your coding agent audit your repository, show what your app costs today and on Google Cloud Run, then move it there step by step. Your code never leaves your machine.

exodus · acme-api
From Heroku, Railway, Render, FlyTo Google Cloud Run

Six steps, one at a time.

Exodus gives your coding agent the tools, the knowledge and the plan. The agent writes the code, and you approve every change.

Sign in to Exodus
Continue with Google

No access to your repositories, ever.

Sign in with Google. One click. Exodus never asks for GitHub or for your code.

Run this in your repository
curl -fsSL exodus.elim.io/i | sh -s 7F3K-QX9PCopy

One-time code, expires in 15 minutes.

Paste one line. It installs the CLI, links it to your account and prepares the repository for your agent.

Audit
webNode 20, Express
workerBullMQ
cron3 schedules
postgres180 MB
2 will break, 1 bills idle

Your agent audits the project. Web, API, workers, schedules, migrations, data, and every pattern that breaks on Cloud Run.

A few questions
Visits a day?about 5,000
Where are your users?Europe, US
Your bill today?$48 a month
Live connections?No

Answer what code can't tell. The CLI hands your agent a short questionnaire, and you answer in your own language.

Move after 4 changes
$48 → $11

a month on Cloud Run

Checklist: 0 of 9

Read the report. Cost today and on Cloud Run, what to change and in what order. Share it with a link.

Plan: 5 of 6 done
Worker → Cloud Tasks
Cron → Cloud Scheduler
Uploads → a bucket
Deploys from GitHub
Data copied and compared
Switch the domain

Move, step by step. The report becomes a queue. Your agent works through it, a commit and a test per task.

The report, a document you can send.

Every audit becomes a report in your account: a snapshot of one repository at one moment, with its own link. Download it as Markdown or JSON, or pull it back into the repository to start the move.

exodus.elim.io/r/acme-api/3

acme-api

Report 3 · 10 October 2026 · from Railway

Verdict
Move after 4 changes

A web process, a queue worker, three schedules and Postgres: a good fit for Cloud Run once the worker, the schedules, the uploads and the live updates are rewritten.

Monthly cost
Today, Railway$48.00
On Cloud Run$11.12

Most of the new bill is the database. The app itself fits in Google's free allowance.

Now and after
web: node dist/server.js→Cloud Run service worker: BullMQ→Cloud Tasks cron: 3 schedules→Cloud Scheduler Postgres 180 MB→Cloud SQL Redis→not needed uploads/ on disk→Cloud Storage bucket

An example report. In a real one every number comes from your audit and Google's prices, never from a guess.

Your agent, our knowledge, your code.

Any coding agent

Exodus is a command-line tool, not a plugin for one assistant. It installs instructions for whichever agent works in your repository, and the agent does the thinking.

Claude CodeCodexCursorGemini CLIWindsurfGitHub Copilot

Knowledge, not guesses

Your agent asks Exodus instead of guessing, with commands like exodus ask.

  • Cloud Run's documentation, digested and kept current
  • Google's live prices for every region
  • A tested replacement for every pattern
  • Lessons from real moves, anonymized

Your code stays yours

The audit runs on your machine. Exodus receives findings, never source code.

  • Sign in with Google, no access to GitHub
  • .exodus/ stays out of git
  • Your key lives in your own config, not in the repository
  • Delete a project and its reports with one click

Cloud Run is Google's way to run your app.

You give it your code; Google runs it. Copies of your app start on Google's machines when requests arrive, as many as the traffic needs, and none when nobody is there.

You pay for the seconds it works. Not for the hours it waits. A small app fits inside the free monthly allowance of 2 million requests.

It is backed in writing. Every service gets a 99.95% monthly uptime commitment, Google's network in front of it and the rest of Google Cloud one permission away.

Cloud Run next to where you are now.

What changes for your app when it leaves a hosting platform for Google's.

Cloud Run Heroku Railway Render Fly.io A VPS
You pay forSeconds your app is workingEvery hour a dyno is upCPU and memory used, plus a plan feeEvery hour an instance is upSeconds a machine runsThe whole month
Stops when nobody uses itOn every serviceEco dynos onlyOptional sleep modeFree tier onlyAuto-stopNo
Adds copies under load by itselfEvery service, up to 1,000 requests per copyPerformance dynos onlyCopies set by handPro workspaces and upStarts machines you createdOnly with extra setup
Front door near your usersGoogle's edge, 200+ points of presenceThe app's region28 edge locationsCloudflareAnycastThe server
Regions to deploy in43124517Depends on the provider
Uptime commitment99.95% on every serviceNot publishedEnterprise onlyEnterprise only99.9% on Enterprise, from $2,500/month99.9-99.99% for the machine
Try a release on part of the trafficAny percentage, roll back in one clickNot documentedNot documentedNot documentedCanary and blue-green deploysYou build it
Free every month2M requests, 180k vCPU-secondsNoneTrial, then $1 credit750 hours, sleeps when idleNoneNone

From each platform's own documentation and pricing pages, read 9 October 2026. Monograms stand in for the platforms' logos.

Measured by others, not by us.

An independent university study ran 38 million requests across eight serverless platforms over three months. Its data is public. No public study has measured Heroku, Railway or Render the same way.

The same computation, run over and over for three months. The bar is the slow end, the time within which 95% of runs finished, relative to Cloud Run. Shorter means your app's speed does not wobble. Cloud Run is the steadiest of the seven that could be timed.

Cloud Run1×fastest slow end
Fastly Compute3.2×
Fly.io3.6×
AWS Lambda x863.8×
Oracle Functions x864.0×
Oracle Functions ARM4.2×
AWS Lambda ARM5.6×

Schirmer et al., TU Berlin, "New Kids: An Architecture and Performance Investigation of Second-Generation Serverless Platforms", 2026. 38 million calls, November 2025 to January 2026; data and notebooks. Google's platform in the study is Cloud Run functions, which runs on Cloud Run.

What your app gets on Cloud Run.

00:00billed only here24:00

Pays only while it works. No visitors, no bill for compute. The free allowance covers small apps entirely.

0 copies120

Grows on its own. A spike and Cloud Run adds copies in seconds, each taking up to 1,000 requests at once, then removes them.

Close to your visitors. They enter Google's network near where they are, and the request rides Google's own lines to your app.

HTTPS certificates
Server and OS updates
Restarts after a crash
Load balancing, scaling
Logs and metrics

Nothing to babysit. No server to log into, no certificate that expires on a Sunday. Deploy, and the rest is Google's job.

Releases without fear. Every release is a version. Show it to 5% of visitors, switch everyone, go back in one click.

All of Google next door. Databases, files, queues, AI models and analytics in the same account, on the same bill.

Good things run for cents.

Real monthly bills of apps we run on Cloud Run. With a modest audience they fit in Google's free allowance, and the bill is mostly what you store.

A Rust backend with its web app

  • Cloud Runfree
  • Traffic out$0.04
  • Database, files, secret$0.07
a month$0.11

A Slack bot with a task queue

  • Cloud Runfree
  • Cloud Tasksfree
  • Database, secret$0.07
a month$0.07

A full SaaS with Postgres

  • Cloud Run: API, worker, webfree
  • Postgres, smallest$9.40
  • Traffic, files, the rest$1.00
a month$10.40

Free. All of it.

No card, no trial, no paid tier.

  • The CLI and every command
  • Audits and reports, as many as you need
  • The plan and the move
  • The knowledge base
  • The check that keeps your app cheap afterwards

Moving something big?

Many services, a large database, no room for downtime. Our engineers have moved production apps to Cloud Run and will plan and run the move with your team.

Consult an expert

Take the first step.

Sign in, paste one line, and see what your app costs on Cloud Run before you change a line of it.