Exodus for Google Cloud Run

This is an interesting concept. I've been in situations where I've wanted to move an app or system out from another cloud onto GCP, so this sort of a migration service is helpful.How does this handle large, no-downtime data migrations?

Hi Exodus team! I have a few questions: Can you tell me more about what Exodus scans for? Based on the video, it seems to be looking for dependencies, like what database the app is using, etc? Does Exodus assume the app is already running in a serverless architecture, or does it scan for statefulness as well?Does Exodus help setup spend caps, budgets, etc related to billing?And lastly, how does Exodus know what the user is paying for currently? Does the user provide that information directly? Good luck with today's launch!

Lovely products. Congrats on launch & best wishes ahead to the team. @alexeynovikov 😄

How did you use Cloud Run for this launch?

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/demoWhat keeps your app off Cloud Run today? We're here all day.