Providers / Google Cloud Run
Google Cloud Run
Serverless containers with the best free tier in the business.
cloud.google.com · Prices checked 2026-08-06
- Type
- Serverless platform
- Starting cost
- Free
- Free tier
- Yes
- Ease of use
- 4/5
Cloud Run is Google Cloud’s serverless container platform, and the reason to consider GCP for a small project: any container scales to zero, the always-free tier (2M requests a month) genuinely covers hobby apps, and deploying is one `gcloud run deploy` from source. We cover Cloud Run rather than Compute Engine because it is the GCP product that competes for indie projects. The risk is the billing model around it: usage-based, no hard spend cap, and a track record of viral surprise-bill stories.
Good to know
- There is no hard spend cap anywhere in Google Cloud — budgets only send alerts. The community horror stories ($4.6k on an idle setup, $18k against a $7 budget) are real.
- Min-instances are the classic trap: a warm instance bills around $10/month, and old revisions can silently keep their own min-instances.
- Egress costs $0.12/GiB after the first free GiB — heavy traffic gets expensive fast.
- Since March 2026 Google can automatically raise your spending-tier quotas, which amplifies leaked-API-key incidents.
Serverless platform
Google Cloud Run
- Best for
- Container apps with spiky or low traffic that want scale-to-zero economics and can manage billing discipline.
- How deploys work
- Run `gcloud run deploy --source .` — buildpacks containerize the app, or push any Docker image; GitHub continuous deployment is built in.
- The tradeoff
- The best free tier and autoscaling here, attached to a billing system with no hard cap and real horror stories.
Why pick it
- The most generous always-free tier of any host here: 2M requests a month, commercial use included.
- True scale to zero — idle apps cost nothing without min-instances.
- Deploy from source with one command, no Dockerfile needed.
- Effortless autoscaling from zero to thousands of instances.
- Excellent EU coverage: Belgium, Netherlands, Frankfurt, Paris, Warsaw, and more.
Why look elsewhere
- No hard spend cap — budget alerts are the only guardrail, and surprise-bill stories keep coming.
- Usage-based pricing across vCPU-seconds, GiB-seconds, requests, and egress is hard to predict.
- Cold starts on scale-to-zero services; keeping one instance warm costs ~$10/month.
- Stateless containers only — no SSH, no persistent disk, WebSockets time-limited.
- The cheapest Cloud SQL instance has no SLA, and a production-grade database costs far more.
Our ratings
What developers say
First-person reports from the past three years, drawn from public discussions and independent write-ups. These are individual experiences, not our ratings; open the original source for its workload and full context. Critical reports include a follow-up check so you can see whether the problem was fixed, partly addressed, remains current, or has no public resolution.
What people like 10 sources
Operators say Cloud Run's autoscaling and request-based billing make it a strong fit for small-business servers and bursty applications when the pricing mode matches the workload.
Google Cloud Run: things you should know before deploying frontendsA new user says they love deploying through Cloud Run and successfully automated tests, image builds, and deployment with a Google Cloud trigger and Terraform.
What is your CI workflow with Cloud Run?A developer moving side projects from Azure reports roughly one-second cold starts and much lower request-based cost; long-term users praise production uptime and simplicity.
Coming from Azure, Cloud Run is amazingOperators report that GitHub Actions or Cloud Build provide reliable, straightforward continuous deployment to Cloud Run without a heavier orchestration platform.
Proper continuous deployment for Cloud RunMultiple operators rank Cloud Run among GCP's best services, citing easy APIs, powerful jobs, scale-to-zero hobby hosting, and successful large production deployments.
Your favorite GCP servicesA developer who moved from AWS after seven years calls GCP easier to set up and Cloud Run dramatically simpler than managed Kubernetes; another describes a startup backend under $100 monthly.
Google Cloud longevityOperators cite Cloud Run as a primary reason to prefer GCP, praising smooth operations, scale-to-zero containers, pricing, and a cleaner developer experience.
Why choose Google Cloud over AWS or Azure?Despite criticizing GCP learning material, experienced cloud practitioners describe Cloud Run as arguably the best service in cloud computing and a strong reason to use the platform.
What is most annoying or cumbersome about Google Cloud?Cloud Run users welcome ephemeral disk, SSH debugging, service bindings, and planned billing caps, while explicitly describing the service as one they love.
What's new for Cloud Run at Next '26An operator uses Cloud Run as part of infrastructure serving millions of users and plans load tests for bursts of 5,000 concurrent visitors, demonstrating confidence in its autoscaling role.
How to do Cloud Run load tests?Critical reports and follow-ups 10 sources
An operator reports recurring outbound network failures in Cloud Run services and jobs after Google marked a NAT issue resolved, causing timeouts and a billing spike.
Cloud Run problems since May 12; GCP says it is solvedMultiple us-central1 operators report Cloud Run environments down while the public status initially appeared healthy; observed downtime ranged from roughly 30 to 60 minutes.
Is Google Cloud Run experiencing an outage?Several us-central1 users observed containers taking twenty minutes or longer to start, while the same service started normally after moving regions.
Cloud Run Flask apps suddenly take a long time to startA WordPress container that was fast on GKE and locally took two to three minutes on Cloud Run when using a mounted Cloud Storage bucket.
WordPress on Cloud Run slow with Cloud StorageA production Flask service stayed sluggish after minimum instances, always-allocated CPU, larger resources, and profiling; Cloud Run alone added variable 400–500 ms latency versus a VM.
Cloud Run and Cloud SQL Flask application has a load of latencyDuring a broad Google Cloud outage, operators received 503 responses and could not restart critical Cloud Run services; status-page acknowledgment lagged the observed failure.
GCP down for anyone else?A low-traffic Streamlit operator paid more than $20 because browser pings kept the application active and prevented the expected scale-to-zero savings.
Streamlit on Cloud Run: tips to save money?An image-processing operator considers Cloud Run expensive at $17 for about 60,000 daily two-second requests, with most spending attributed to CPU.
Any cheaper solution than Cloud Run for image processing tasks?A headless-browser container took about two minutes to launch on Cloud Run even after switching to the official Puppeteer image.
Why is Cloud Run so slow launching headless Puppeteer in Docker?A team measured about 25 seconds of extra cold-start latency in us-central1 versus roughly seven seconds in another region, including with a minimal test container.
Is 20–25 seconds acceptable latency for a cloud provider?Serverless platform
Google Cloud Run
Always free: 2M requests, 180k vCPU-seconds, 360k GiB-seconds per month, plus a $300/90-day new-customer credit.
What you'd realistically pay
| Project stage | Estimate | Based on |
|---|---|---|
| Just starting | Free | Free tier — A scale-to-zero service with hobby traffic typically rounds to $0 — the always-free tier absorbs it. |
| Steady traffic | ≈$10/mo | Pay-as-you-go + 1 warm instance — One min-instance (1 vCPU, 512 MiB at the idle rate) is ~$10/month; request costs on top are usually small. |
| Growing | ≈$58/mo | Always-on + Cloud SQL — ~$50/month for an always-on 1 vCPU / 1 GiB service (instance-based billing) plus ~$7.67 for a db-f1-micro Cloud SQL instance. |
Published prices
| Plan | Price | What you get |
|---|---|---|
| Requests | $0.40/mo | $0.40 per million requests (request-based billing), after 2M free per month. |
| Active compute | Free | $0.000024/vCPU-second and $0.0000025/GiB-second while serving requests; idle time is free without min-instances. |
| Warm min-instance | $10/mo | Roughly $10/month for one 1 vCPU + 512 MiB instance kept warm at the idle rate. |
| Cloud SQL db-f1-micro | $7.67/mo | Cheapest managed PostgreSQL/MySQL: shared core, 0.6 GB RAM, no SLA. Storage billed per GiB extra. |
- Egress: first 1 GiB/month free, then $0.12/GiB to NA/EU/Asia.
- Tier 2 regions cost more; committed-use discounts take ~17% off.
- The $300 new-customer credit runs 90 days and cannot produce a bill — the account closes instead of charging you.
Deploy workflow
| Deploy from Git push Connect a repository and every push deploys automatically. | Yes Built-in continuous deployment from GitHub, or deploy from source with gcloud. |
|---|---|
| Preview deploys Each branch or pull request gets its own temporary URL. | Partial Every deploy creates a tagged revision you can hit directly and split traffic to — but no automatic PR previews. |
| Official CLI A maintained command-line tool for deploys and management. | Yes `gcloud run` covers deploys, revisions, and traffic splits. |
| Instant rollbacks Revert to a previous deploy without rebuilding. | Yes Shift traffic back to any previous revision instantly. |
Platform
| Custom domains + HTTPS Bring your own domain with TLS certificates handled. | Partial Domain mappings exist but Google steers production setups toward a load balancer, which adds cost and setup. |
|---|---|
| Built-in CDN / edge network Static assets served from locations near your visitors. | Partial Cloud CDN is available but requires fronting Cloud Run with a load balancer. |
| Serverless functions Run backend code without managing a server process. | Yes The whole platform is serverless; Cloud Run functions cover event-driven code. |
| Docker containers Deploy your own container image. | Yes Runs any container image — that is the product. |
| SSH / shell access Open a shell on the machine running your app. | No No servers to reach. |
| EU hosting region Run the app itself in a European data center. | Yes A dozen-plus EU regions, four of them at Tier 1 pricing. |
Runtime & operations
| Automatic scaling Capacity grows with traffic without manual resizing. | Yes Scales per request from zero to your max-instances setting. |
|---|---|
| Scale to zero Costs stop (or pause) when nobody is using the app. | Yes Idle services cost nothing unless you set min-instances. |
| Scheduled jobs Run code on a schedule without an external trigger. | Yes Cloud Scheduler triggers services; Cloud Run jobs handle batch work. |
| Managed database A database the provider runs, backs up, and updates. | Yes Cloud SQL from ~$7.67/month (no SLA at that size); Firestore and AlloyDB nearby. |
| Logs & metrics built in See what the app is doing without wiring up third parties. | Yes Cloud Logging, Monitoring, and request traces are built in. |
Every comparison is pre-calculated from the same hand-checked data as this page — prices, ratings, and all 15 features we track, side by side.
Not sure this is the one? Answer four questions and compare it against the alternatives for your project.