Google Cloud Run makes it easy to deploy and scale containerized applications without managing servers or infrastructure. The deployment process is straightforward, startup times are fast, and automatic scaling helps applications handle changing traffic efficiently. It integrates seamlessly with other Google Cloud services, fits well into CI/CD workflows, and provides a cost-effective way to run production workloads while allowing developers to focus on building applications instead of maintaining infrastructure. Review collected by and hosted on G2.com.

Google Cloud Run has been reliable overall, but debugging production issues can sometimes be challenging because logs and monitoring data are spread across multiple Google Cloud services. Cold starts may also be noticeable for infrequently used services, and configuring advanced networking or security settings can be more complex than expected. More built-in optimization guidance, clearer cost visibility, and enhanced monitoring tools would make the platform even easier to manage at scale. Review collected by and hosted on G2.com.

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.

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.

Google Cloud Run as a serverless container product from google cloud is fully managed serverless meaning, no clusters ad nodes, just deploy your container and let google handle scaling. Cloud Run also facilitates automatic scaling from zero and ensures container based flexibility and last but not least cloud run has pay per use pricing mechanism Review collected by and hosted on G2.com.

Cold starts on cloud run can be slow for traffic that is infrequent. Cloud Run has no native GPU support and has a limited to 60 minute request timeout. VPC access on cloud run has complexities as well Review collected by and hosted on G2.com.

Google Cloud Run is an incredibly flexible and powerful but in some sense also very simple product that allows us to create serverless services in a super easy way. We've got it in some instances with a min_instance=1 (so not serverless) and then other internal serverless APIs. The cost is for our mostly internal services basically negligent - which is great because having a dedicated VM would for these services make things both much more complicated and expensive. Review collected by and hosted on G2.com.

Google Cloud Run is great in many instances, but the limited timeouts and service shutdowns paired with no option for spot VMs makes it not a good fit for certain workloads in our company. For these we use Kubernetes. Review collected by and hosted on G2.com.

I use Google Cloud Run to run frontend and backend services for internal apps like a seat booking app for my Data Analyst team. It helps me deploy solutions quickly and solves the pain of managing many infrastructure headaches, with scaling being handled well. I like the concurrency support, which allows a single instance container to handle multiple requests simultaneously. The startup CPU boost is a powerful feature that resolves the cold start problem, maximizing efficiency and saving costs. Review collected by and hosted on G2.com.

Despite CPU boost for heavy apps, there is still a delay. Connecting to my organization's Private VPC was a headache. I believe integrating with organization networking should be made easy, and connecting with legacy systems needs to be improved. Review collected by and hosted on G2.com.

I love how Google Cloud Run makes everything just easy. I don't have to think about what region my site is running on or if it can scale to handle more customers. I don't even have to think about the infrastructure that's created when I deploy an app to Cloud Run. I just know that it's done, and I know that it works. Review collected by and hosted on G2.com.

The difference between Google Cloud Run and Firebase hosting should be more clear. I use both but in some instances, I'm not sure which one I should be using. So I feel like Cloud Run could be more clear as to what scenarios it's best used for. Review collected by and hosted on G2.com.

I really like how easy it is to use Google Cloud Run. Deploying a containerized app is very easy, and I don't have to manage servers or clusters. It's easy and fast to implement; I was able to get the API up and running in minutes without any complicated setup.

Google Cloud's docs and community customer support are very helpful, and when I need help, I usually get answers quickly. I use Cloud Run regularly for small to medium-sized apps, especially when I need a fast and scalable deployment.

It has the features I need, such as auto-scaling, logging, and concurrency control, and its integration with other Google Cloud products like Cloud Build, IAM, and monitoring tools is also very smooth.

Overall, Cloud Run saves me time and reduces the burden of management. It's easy to get started with and flexible enough for production workloads. Review collected by and hosted on G2.com.

One thing I noticed is that debugging can be a bit more complicated than with a traditional server. Since it's completely serverless, you don't have direct access to the underlying environment, which can sometimes make troubleshooting more difficult.

Another drawback is its price for consistently high-traffic workloads; if your services are always running at high volumes, it can become more expensive than a fixed server setup.

Finally, while it integrates well with other Google Cloud services, setting up cross-platform integration can take extra effort if you use multiple clouds or older systems.

Overall, these are minor issues compared to the benefits and scalability it provides, but they're worth keeping in mind depending on your workload. Review collected by and hosted on G2.com.

The 'Scale to Zero' capability and the effortless developer experience. At Alborda Games, we can deploy microservices without managing any underlying infrastructure. The integration with Google Cloud Build means we have a seamless GitOps workflow where every push to our repository automatically updates our staging or production environments. It handles SSL, load balancing, and scaling automatically, which saves our team dozens of hours of DevOps work Review collected by and hosted on G2.com.

Cold starts can still be a minor hurdle for latency-sensitive applications, though 'min-instances' helps mitigate this. I also find the IAM (Identity and Access Management) configuration to be quite steep for beginners; setting up service accounts with the exact 'least-privilege' permissions can be a bit of a trial-and-error process. Additionally, the web console UI can occasionally feel cluttered when managing a large number of revisions Review collected by and hosted on G2.com.

I like the simplicity of deployments and automatic scaling with Google Cloud Run. It’s easy to run containerized services without managing servers, and integration with GCP logging monitoring is very convenient. I also like how fast deployments are and how easy it is to integrate Cloud Run with CI/CD pipelines and other GCP services. It makes development and maintenance much more efficient. Review collected by and hosted on G2.com.

Sometimes debugging can be harder than expected, especially when logs or environment configs aren't set up correctly. Cold starts can also be noticeable for some workloads. Review collected by and hosted on G2.com.

I like Google Cloud Run because it's very simple and flexible. It helps me deploy containerized applications quickly without worrying about scalability, network, and availability issues. This simplicity allows me to focus entirely on building my applications. I find it very good for accessing various services like Google Map API and the translation API, which makes it easy to integrate different applications. I also appreciate how easy it is to set up and use, making my work more straightforward. Review collected by and hosted on G2.com.

I find debugging somehow an issue, and sometimes, when there are many applications loaded, it feels difficult to get back to where I was. It would be better if there was a trace back option to easily navigate back to the beginning, as I often get lost in the middle of using it. Review collected by and hosted on G2.com.