Exodus got the Cloud Run Superfan Award at the Product Hunt x Google Cloud Run Hackathon. It is one of three Editors' Picks that the Google Cloud team gave on October 16, 2026, next to the main prize, which went to Inferock. The other two picks went to Rambox and CraveLens. More than 130 products launched in the hackathon on October 14.
The card is a frame of the video in Product Hunt's post on X.
In short
- The award is an Editors' Pick from the Google Cloud team, announced by Product Hunt on X and in its newsletter on October 16, 2026.
- The hackathon's main prize, $500 in Google Cloud credits, a spotlight on Google Cloud's channels and a 1:1 with the Cloud Run team, went to Inferock.
- Exodus runs on Cloud Run itself: one Rust service with Firestore in europe-west1.
- On launch day a member of the Cloud Run team asked whether Exodus helps with budgets. It did not; the same evening the plan got a "Budget and alerts" step, released in v0.2.10.
The award
Product Hunt announced the picks in a post on X, and the next post in the thread reads "The Cloud Run Superfan Award goes to Exodus for Cloud Run". The picks came from the Google Cloud team, not from the vote. On the day's vote Exodus finished ninth.
What Exodus is
Exodus takes an app to Google Cloud Run with the coding agent you already use. The agent checks the app on your machine, Exodus shows what it costs today and on Cloud Run and which changes it needs, and the agent works the plan a commit at a time. Your code stays on your machine, and Exodus never signs in to your Google Cloud.
The product runs on Cloud Run too. The API and the web cabinet are one Rust service on axum, with Firestore for reports, deployed from a container in europe-west1. The CLI is open source. More on what Cloud Run is, what breaks on the way there and running Rust on it.
What a judge asked, and what shipped that evening
During the launch Sara Ford of the Cloud Run team asked four questions on the launch page: what Exodus scans for, whether it looks for state, whether it helps with budgets and spend caps, and how it knows today's bill. The first, second and fourth had answers in the product. The third did not: Exodus never touched billing, and budgets lived only in a guide.
That evening the plan got a "Budget and alerts" step. It sets a Cloud Billing budget on the project at the report's Cloud Run estimate, rounded up, at least $5, with email alerts at 50%, 90% and 100% of spend and on the forecast. The agent shows the gcloud billing budgets create command and runs it with your own gcloud once you approve. It shipped in v0.2.10. The same day v0.2.9 added Windows: irm https://exodus.elim.io/install.ps1 | iex in PowerShell. How budgets work: budget alerts and the billing export.
Try it
A sample report needs no sign-up. To check your own app, sign up, install the CLI once, and give the prompt from the cabinet to your agent.
Sources
5
- x.comProduct Hunt on X, the Editors' Picks of the Google Cloud Run Hackathon
- x.comProduct Hunt on X, "The Cloud Run Superfan Award goes to Exodus for Cloud Run"
- producthunt.comGoogle Cloud Run Hackathon, Product Hunt
- producthunt.comExodus for Google Cloud Run, the launch on Product Hunt
- github.comExodus releases v0.2.9