What is included in the Cloud Run free tier?

Cloud Run provides 2 million requests, 360,000 vCPU-seconds, 180,000 GiB-seconds, and 1 GB of outbound data per month free. This is per-account and covers most low-to-moderate traffic services entirely. The free tier makes Cloud Run one of the most cost-effective serverless container platforms for small workloads.

What is the difference between CPU allocation modes?

With 'CPU allocated only during request processing,' you only pay for CPU when handling requests, and CPU is throttled between requests. With 'CPU always allocated,' you pay for CPU as long as the instance is running (including between requests), enabling background processing, WebSocket connections, and consistent performance.

How does concurrency affect cost?

Higher concurrency (up to 1,000) means each instance handles more simultaneous requests, reducing the number of instances needed and total cost. Lower concurrency may be needed for CPU-intensive or memory-intensive request processing. The default concurrency of 80 works well for most web workloads.

GCP Cloud Run Cost Estimator

ComputeGCP

Estimate monthly Cloud Run costs based on requests, CPU, and memory allocation.

Cloud Run Configuration

Requests per Month

Free tier includes 2M requests/month

Average Duration (ms)

CPU Allocation (vCPU)

Memory (MB)

Concurrent Requests per Instance

Max concurrent requests each instance handles (default 80, max 1000)

Minimum Instances

Instances kept warm to avoid cold starts. Set to 0 for scale-to-zero.

CPU Always Allocated ($0.000018/vCPU-sec vs $0.000024/vCPU-sec request-based)

Include Free Tier (180K vCPU-sec + 360K GiB-sec + 2M requests/month)

Raw Output

Output will appear here...

About This Tool

The GCP Cloud Run Cost Estimator calculates monthly costs based on request volume, CPU allocation, memory allocation, and execution time. Cloud Run offers both request-based and instance-based billing models with a generous free tier. The tool factors in CPU throttling settings (allocated only during requests vs. always allocated), minimum instances for cold start mitigation, and concurrency settings.

When to Use This Tool

•Estimating monthly Cloud Run costs for a containerized API with projected request volume and average response time.
•Comparing request-based vs. always-allocated CPU pricing for different traffic patterns.
•Calculating the cost impact of setting minimum instances to eliminate cold starts.
•Modeling free tier coverage for a low-traffic service to determine if Cloud Run is effectively free.

Frequently Asked Questions

What is included in the Cloud Run free tier?: Cloud Run provides 2 million requests, 360,000 vCPU-seconds, 180,000 GiB-seconds, and 1 GB of outbound data per month free. This is per-account and covers most low-to-moderate traffic services entirely. The free tier makes Cloud Run one of the most cost-effective serverless container platforms for small workloads.
What is the difference between CPU allocation modes?: With 'CPU allocated only during request processing,' you only pay for CPU when handling requests, and CPU is throttled between requests. With 'CPU always allocated,' you pay for CPU as long as the instance is running (including between requests), enabling background processing, WebSocket connections, and consistent performance.
How does concurrency affect cost?: Higher concurrency (up to 1,000) means each instance handles more simultaneous requests, reducing the number of instances needed and total cost. Lower concurrency may be needed for CPU-intensive or memory-intensive request processing. The default concurrency of 80 works well for most web workloads.

Related Learning Guides

GKE vs Cloud Run Decision24 min read
Cost Optimization Guide24 min read

Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.