Google Cloud Run
No written verdict yet. Here is what commenters said.
13recommend
1warn against
Nov 3, 2025first mention
Oct 13, 2026latest mention
Why people recommend it
“serverless containers are almost always a better approach since it provides much more flexibility”
invited presenter at Azure Serverless Confon “AWS Lambda Web Functions”
Show 3 more
“I tried to replace what I could with Cloud run”
switched from Google Apps Scripton “Ask HN: Best way to escalate critical GAS bug ignore…”
“Cloud Run makes lots of sense when running lots of small apps”
“moved from Heroku -> App Engine -> Cloud Run, I think you'll appreciate the modern alternatives more”
switched from App Engineon “Heroku Is Not Dead”
Caveats and dissent
“That was an issue for us when we were running on Google's Cloud Run.”
Often compared with
1 moved from Kubernetes to Google Cloud RunFirebase4 comments mention both
1 moved from Google Apps Script to Google Cloud Run
Who recommends it in their own words
Threads where it came up
- AWS Lambda Web Functions 2 mentions
- Why you can need Cloud Run Instances 1 mention
- Alphabet Announces First Quarter 2026 Results 1 mention
- Ask HN: Best way to escalate critical GAS bug ignored by Google 1 mention
- Show HN: Broccoli, one shot coding agent on the cloud 1 mention
- Migrating from Heroku to Magic Containers 1 mention
Also written as Cloud Run. Data: google-cloud-run.json. Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.
All comments 28
“When scale to 0, it only bills when actively serving a request.”
“serverless containers are almost always a better approach since it provides much more flexibility”
“Cheap and easy patterns”
I use Cloud Run a lot. It’s free up to 2M requests per month. It’s also very clean, scalable and very easy to set up.
“I tried to replace what I could with Cloud run”
“That was an issue for us when we were running on Google's Cloud Run.”
“Cloud Run makes lots of sense when running lots of small apps”
“The backend is running on Google Cloud Run”
“Deployed via Cloud Run.”
“moved from Heroku -> App Engine -> Cloud Run, I think you'll appreciate the modern alternatives more”
“google cloud run and build is as easy to setup as railway”
“Backend: Firebase + Google Cloud Run”
“Google cloud run and render.com are both pretty good alternatives”
“a simple api-key injection gateway hosted in google cloud run”
“deployed via Cloud Run”
“Agents run on GCP Cloud Run Jobs (containerized)”
“usually Firebase (+ occasional Cloud Run mixed in)”
“deploy to Cloud Run”
“thanks to Google Cloud Run”
“AIUI, Google Cloud Run is pretty much the same deal”
“product is pretty good in this regard as well”
“The infrastructure runs entirely on Google Cloud Run.”
“why-i-left-kubernetes-for-google-cloud-run”
“I have a similar experience except I use Go+GitHub Actions+Google Cloud Run.”
“Cloud Run does this in seconds”
“hosted on Google Cloud Run and Firebase”
“Running a small thing with essentially no traffic is as close to free as you can get.”
“Decided to see if I could build a cheaper alternative using GCP Cloud Run + Terraform.”