Google Cloud Run Takeover & Hackathon!

We teamed up with for a Cloud Run Hackathon October 14th!

To kick things off, we're celebrating on the leaderboard so you can meet the people behind Cloud Run.

They'll be checking out the launches, and hanging out on Product Hunt all week starting today to talk architecture, troubleshoot setups, and cheer you on as you prep for launch day.

How to enter on Oct 14:

Prizes:

  • $500 in Google Cloud credits

  • 1-on-1 chat with Cloud Run engineers

  • Big shoutouts across Google Cloud channels

Participants receive $50 in build credits while supplies last. You must schedule your launch for the Cloud Run Hackathon in order to be eligible to receive the credits.

To receive the credits please schedule a draft or post for October 14th and select "Yes" when asked if you'd like to participate.

To participate in Cloud Run Hackathon, deploy your product on Google Cloud Run and .

3.8K views

Add a comment

Replies

Best

$500.00 in Google Cloud credits? That ain't chump change.

   $50 just for participating isn't bad either.

great!!! you guys are making it interesting day by day!

This is fantastic. It keeps the community engaged and excited. :)

Would it be possible for the design/dev team to add a light/dark mode toggle? I find the text difficult to read on pages with dark backgrounds, such as Vercel Days and the Cloud Run special homepage design.

The dark theme looks great, but the tagline font size is hard to read on an iMac desktop screen. I’ve been using the archive page to read the taglines instead.

Also, I am curious, does the homepage redesign affect the clicks? What does the analytics data say? :)

 noted on the design! Will share the feedback with the team.

On the homepage design the biggest impact is shipping something fun or interesting! Cool products get more clicks :)

 The coolest redesign so far has been Wispr Flow homepage and Hypership. Google Cloud Run above-the-fold box looks neat too. 👏

Excited to see what the community is building with Cloud Run! 🚀 If you're working on an AI application, API, or developer tool, this is a great opportunity to ship something real and share it with the community. What are you building, and what's been the most interesting technical challenge so far?

Hi Omotayo, we’re building an agentic financial wellbeing platform for individuals and small businesses under Lybotech Group. Finwings is our working name while we finalise the branding. We’d love your insights on suitable technology stacks, models and tools as we develop it further. You’re welcome to explore the platform and its Developers area through our launch page.

 Interesting approach to payment orchestration, especially for businesses operating across different payment methods and regions. I'm curious how FinWings handles intelligent payment routing and automatic retries when a provider fails, while avoiding duplicate transactions and maintaining a clear audit trail. Are these capabilities configurable through your API?

 We make Exodus, which moves apps to Cloud Run with the user's coding agent. The most interesting challenge was teaching the scanner where code actually runs. A setInterval in browser JS or a timer in a build script looks exactly like a server-side cron that stalls on Cloud Run. On a corpus of 18 public repos our first version flagged 35 such false breaks; reading where each file runs (static folders, build tools, mobile sources) took that to 0 while keeping the real findings.

 Great work by the team! 🚀 Making Cloud Run migrations easier with coding agents is a really useful idea, especially with the repository checks, cost comparisons, and step-by-step migration plans. I also like the focus on keeping source code local. How does Exodus validate that migrated apps handle state, background jobs, and persistent storage correctly in production? Congrats on the launch! 👏

 Thanks, Omotayo. It checks the code, not production traffic, in four places:

  1. Each plan task (worker to Cloud Tasks, timers to Cloud Scheduler, uploads to Cloud Storage, sessions out of memory) lands as its own commit with a test, and the next audit drops a finding only when the scanner no longer sees the pattern in the code.

  2. `exodus check` runs in CI and fails the build if a pattern comes back: state kept in memory, files written to local disk, timers or loops inside the process.

  3. The data step copies the database and compares it before the domain switch, and the service gets a startup probe on its health route, so a revision that cannot start never takes traffic.

  4. After a month, the agent can read the real bill from the BigQuery billing export and the report shows it next to the estimate, part by part.

It does not load-test the app for you; that part stays with the team.

Thanks for having hackathon this it finally pushed me to migrate the runs for over to Cloud Run Jobs off of the single Cloud Run server. Also, the credit be nice to take a small dent out of my rent sized monthly Google Cloud bill 😂 It's also been nice to identify improvements through folks kicking the tires due to the launch.

look at that! looking forward to seeing what the community will build with Cloud Run

What qualifies as Google Run app? Do firebase deployed apps using Google Run services (such as 2nd gen functions) qualify?

 Hi Marek! Thanks for the question! The app must be deployed directly to Cloud Run.

I am interested

An agent wrote the deploy script for Cloud Run. It reported every migration succeeded and marked the service healthy, while the container was crash-looping on an unset variable. The bug itself was trivial, but chasing down why it claimed everything was fine took half the night.

 Two things helped us with exactly this. Read every required variable at startup and exit if one is missing: the new revision then never becomes Ready and Cloud Run keeps traffic on the old one. And have the agent check the result instead of its own log: gcloud run services describe SERVICE --region REGION --format='value(status.latestReadyRevisionName,status.latestCreatedRevisionName)' should print the same name twice, then a request to the service URL should answer 200. We wrote up startup probes and health checks here (I make Exodus):

very cool - will you accept myappname-uc.a(dot)run(dot)app g cloud run dev urls ...i just chcked submission and url is first thing you are asking for.

 Yes! That is perfectly fine to submit.

123
Next