G2

Amar singh C.

Founder

Transportation/Trucking/Railroad

Mid-Market (51-1000 emp.)

7/2/2026

"Cost-Effective Hosting with Fast Deploys and Great Auto-Scaling"

4.5/5

What do you like best about Google Cloud Run?

Google Cloud Run is our main backend hosting service, and we chose it because it’s good and very cost-effective. The automatic instance scaling is also very good, and the pay-as-you-use model works well for us. We don’t have to pay when no instance is running, so during no-traffic times the cost is 0, which is very effective. Even if we set it to publish and don’t stop it every time, the total monthly cost can still get some discounts, which makes it even cheaper.

It also reduces server management, which is very complex with VMs and other setups. The dashboard UI is good, easy to use, and it’s very fast to deploy and upload updates, especially from the Google Cloud CLI. The automatic load balancer is also good, and we don’t have to pay extra for it. The normal 500+ MB RAM is good for a normal backend, especially if it’s in Go.

Our main purpose for choosing Cloud Run is the cost, since it can limit the cost to just a few hundred dollars. One problem is cold starts, but we can overcome that by keeping one instance always live, although we have to pay for it. Still, it’s cheap (around 28 dollars). The logs and metrics are also very good, and the new explain log with Gemini is good too. The direct source code file explorer is also good, etc. Review collected by and hosted on G2.com.

What do you dislike about Google Cloud Run?

Overall, there are many good things about it, and it’s very cost-effective. However, there are a few “hidden” costs to be aware of. For example, for networking, if you use an external IP address, you have to pay for it. It’s not too much, but it is still an extra charge.

Cold starts can also be a problem, though not a big one, because Cloud Run’s cold start time is less than others. We also use AWS Lambda, and it takes about 3x longer than Cloud Run. In my experience, Cloud Run cold starts are usually just a few nanoseconds up to 1 second max.

The UI is good, but many times when I try to update the source code directly from the dashboard, it fails unnecessarily, and then I have to upload it again using the Google CLI. Review collected by and hosted on G2.com.

What problems is Google Cloud Run solving and how is that benefiting you?

The cost is very low, and it’s easy to deploy. The cold start time is lower than others, and it also gives free API calls in the millions. It’s truly pay-as-you-go because we don’t have to pay a fixed minimum amount just to keep the service running.

The auto-scaling is also good, so we don’t have to worry that the backend will crash when the load increases. The load balancer is very good as well, which reduces one of the biggest nightmares in any project: the server crashing when traffic gets too high. Review collected by and hosted on G2.com.