Launching today
Exodus for Google Cloud Run
Upgrade any app to Cloud Run, with your coding agent
51 followers
Upgrade any app to Cloud Run, with your coding agent
51 followers
Cloud Run is Google's managed platform: no servers to look after, new copies in seconds under load, a bill only while your code works. Exodus takes your app there with your coding agent (Claude Code, Codex, Cursor): it checks the app on your machine, shows what you pay today and on Cloud Run and what to change, by 50+ playbooks from real moves. Then the agent makes the move, task by task, or designs a new app for Cloud Run. Free and open source. Try it on your repo today.
Hey Product Hunt! I'm Abdugafur, co-founder of elim.io, here with Alex.
Google Cloud Run is one of the best places to run an app: it scales to zero, bills only while your code works, and runs on Google's own network. Getting in is the hard part. It has its own rules, and many common architectures break on them quietly: a cron inside the process fires late or twice, a worker waiting on a queue stalls, uploads on local disk vanish, sessions in memory sign people out. So most teams stay on a PaaS and keep paying for hours their app sleeps, because the path there isn't clear.
We moved our own apps this year and wrote down every step. Exodus turns that into a path your coding agent follows, to upgrade any app to Cloud Run:
→ Is your app ready? One line to your agent installs our open-source CLI and checks the repository on your machine: processes, data, settings and every pattern that breaks or bills while idle.
→ What will it cost? Today's bill against Cloud Run at Google's list prices, with your traffic, 16 regions and a 12-month forecast.
→ How should it be built? Your app drawn on Google Cloud, rebuilt by our 50+ playbooks: each change with the reason, the replacement and the order.
→ Then move. Your agent works the plan, a commit per task, and the report ticks itself. exodus check in CI keeps it that way.
→ Starting from zero? Describe the idea and Exodus designs it for Cloud Run block by block: services, database, stack, and the bill at launch and in a year.
Your code never leaves your machine, we run no AI of our own, and we never sign in to your Google Cloud. For the Cloud Run team: Exodus runs on Cloud Run itself, one Rust service with Firestore, scaling 0 to 3.
Free, no paid tier, and the CLI is open source. A real report, no sign-up: https://exodus.elim.io/demo
What keeps your app off Cloud Run today? We're here all day.
A bit more on how Exodus works.
The audit
→ Processes: web, workers, scheduled jobs, release steps
→ Data: databases, caches, files on disk, outside services
→ Settings: env variable names, Dockerfile, CI, domains
→ Every pattern that behaves differently on Cloud Run
The questions
Only what the repo can't answer: traffic, where your users are, what you pay today. Your agent checks first and asks you the rest.
The report
→ A verdict with its reason
→ Cost per part of your app, today vs Cloud Run
→ The target architecture
→ Changes in order, each with its effort
Share it by link or download as Markdown / JSON.
The move
→ One task, one commit, one test
→ Data copied and compared before the switch
→ Steps only you can do (sign-in, billing, DNS) come to you with instructions
After a month
Your agent reads the real Google bill and the report sets it against the estimate, part by part.
Your data
Findings go to the cabinet. Code, secrets, and env values stay on your machine.
When it says "stay"
Heavy 24/7 load or a persistent disk usually fit Cloud Run poorly. The report tells you.
Works with Claude Code, Codex, Cursor and others · macOS and Linux
Lovely products. Congrats on launch & best wishes ahead to the team. @alexeynovikov 😄