DevOpsKitFinOps & Tools Hub
Cloud FinOpsFree-Tier Factored

Cloud Run vs AWS Lambda Pricing Calculator

Compare serverless compute costs side-by-side. Model request volume, execution latency, memory sizing, and concurrency factors.

Share or export this serverless cost breakdown:

Serverless Workload

Free Tiers Included
⚡ 1-Click Real-World Archetypes
Monthly Invocations10,000,000
Avg Execution Duration200 ms
Cloud Run handles multiple concurrent requests on a single container. AWS Lambda processes 1 request per concurrent instance.

Cost Comparison

Google Cloud Run
$4.88
Includes 2M free requests + 180k vCPU-s
AWS Lambda
$11.80
Includes 1M free requests + 400k GB-s
Most Cost-Effective
Google Cloud Run
Estimated Advantage
$6.92 / mo

Serverless Compute Pricing & Free Tier Rates (2026)

Official compute and memory rates for Google Cloud Run vs AWS Lambda (Tier 1 / us-east-1).

✓ Verified March 2026
PlatformCompute RateMemory RateRequests / 1MMonthly Free TierConcurrency ModelOfficial Docs
Google Cloud Run (Tier 1)$0.00002400 / vCPU-s$0.00000250 / GiB-s$0.402M reqs, 180k vCPU-s, 360k GiB-sMulti-concurrency (up to 1,000 / instance)Cloud Run Docs ↗
AWS Lambda (x86_64)Bundled in GB-s$0.0000166667 / GB-s$0.201M reqs, 400k GB-sSingle-request (1 instance per concurrent req)AWS Lambda Docs ↗
AWS Lambda (Arm / Graviton2)Bundled in GB-s$0.0000133334 / GB-s$0.201M reqs, 400k GB-sSingle-request (1 instance per concurrent req)AWS Lambda Docs ↗

Serverless Concurrency Economics: Cloud Run vs AWS Lambda

When architecting serverless applications, choosing between Google Cloud Run and AWS Lambda has profound financial ramifications. While both abstract away server management and scale to zero, their underlying execution models differ fundamentally in how they handle concurrent traffic.

The Concurrency Multiplier Advantage

In AWS Lambda, the execution concurrency model is strictly 1:1. If 100 requests arrive within the same 200ms window, Lambda initializes and bills for 100 distinct execution instances.

In contrast, Google Cloud Run allows developers to configure multi-request concurrency (up to 1,000 requests per container). If your application spends time awaiting database I/O or external API calls, a single 1-vCPU Cloud Run container can multiplex dozens of requests simultaneously, dramatically reducing billed instance-seconds.

Frequently Asked Questions

Why is Cloud Run often cheaper for high-concurrency web apps?

Cloud Run allows a single container instance to process up to 1,000 concurrent requests simultaneously. AWS Lambda spins up a dedicated execution environment for each concurrent request, multiplying compute bills during traffic spikes.

Do Cloud Run and AWS Lambda have free tiers?

Yes. Google Cloud Run provides 2 million free requests and 180,000 vCPU-seconds monthly. AWS Lambda provides 1 million free requests and 400,000 GB-seconds monthly.

When is AWS Lambda more cost-effective?

AWS Lambda excels for intermittent, event-driven workloads (S3 triggers, SQS queues, cron tasks) where requests arrive sparsely and container startup overhead would be wasted.