Quick answer
AWS Lambda is cheaper than Google Cloud Run at all three usage levels Playxoft priced. For 50 million requests a month at 200 ms, 512 MB and 10 ms of CPU each in US East, it costs $86.47 a month against $106.40, and it is cheaper in all 12 regions covered. Playxoft's comparison uses official list prices checked October 14, 2026, with the always-free allowances applied.
- Official list prices
- 3 usage levels
- 12 regions
- Feature comparison
- Free calculator
How to compare AWS Lambda and Google Cloud Run costs
- 1Pick a usage level (5M requests, 50M requests, 500M requests), then change the numbers or add more items with the + buttons.
- 2Choose the Region where your users are. Prices differ by region.
- 3Adjust the numbers in each card. Every field has an i tip explaining it.
- 4Compare the two monthly totals, then open Cost breakdown to see exactly how AWS Lambda and Google Cloud Run bill each line.
Which is cheaper, AWS Lambda or Google Cloud Run?
Monthly list prices in US East with the always-free allowances applied:
| Usage per month | AWS Lambda | Google Cloud Run | Cheaper |
|---|---|---|---|
| 5M requests: 100 ms, 256 MB, 10 ms CPU each | $0.80 | $1.20 | AWS Lambda by $0.40 |
| 50M requests: 200 ms, 512 MB, 10 ms CPU each | $86.47 | $106.40 | AWS Lambda by $19.93 |
| 500M requests: 200 ms, 1 GB, 20 ms CPU each | $1,759.80 | $1,843.18 | AWS Lambda by $83.38 |
AWS Lambda is cheaper for 50M requests a month in all 12 regions the calculator covers. Cloud Run is priced with one request per instance at a time; serving several requests on one instance lowers its cost.
What are the Lambda and Cloud Run unit prices?
List prices in AWS us-east-1 (N. Virginia) and Google Cloud us-east1 (South Carolina), read on October 14, 2026:
| Price (US East, on-demand) | AWS | Google Cloud |
|---|---|---|
| Serverless, per million requests | $0.20 | $0.40 |
| Serverless compute | $0.0000166667 per GB-s | $0.000024 per vCPU-s + $0.0000025 per GiB-s |
Is AWS Lambda or Google Cloud Run cheaper in your region?
50 million requests a month at 200 ms, 512 MB and 10 ms of CPU each, priced in each of the 12 regions the calculator covers:
| Region | AWS Lambda | Google Cloud Run | Cheaper |
|---|---|---|---|
| US East | $86.47 | $106.40 | Lambda |
| US West | $86.47 | $106.40 | Lambda |
| Canada | $86.47 | $143.37 | Lambda |
| Brazil (São Paulo) | $86.47 | $143.37 | Lambda |
| Ireland | $86.47 | $106.40 | Lambda |
| UK (London) | $86.47 | $143.37 | Lambda |
| Germany (Frankfurt) | $86.47 | $143.37 | Lambda |
| India | $86.47 | $106.40 | Lambda |
| Singapore | $86.47 | $143.37 | Lambda |
| Japan (Tokyo) | $86.47 | $106.40 | Lambda |
| South Korea (Seoul) | $86.47 | $143.37 | Lambda |
| Australia (Sydney) | $86.47 | $143.37 | Lambda |
How do AWS Lambda and Google Cloud Run compare on features?
| AWS Lambda | Google Cloud Run | |
|---|---|---|
| Billing | Requests + duration × memory, per 1 ms | Requests + vCPU and memory time, rounded up to 100 ms |
| Maximum run time | 15 minutes | 60 minutes (HTTP), 9 minutes (events) |
| Memory | 128 MB to 10,240 MB | From 128 MiB to several GiB |
| Free tier | 1M requests + 400,000 GB-s a month | 2M requests + 180,000 vCPU-s + 360,000 GiB-s a month |
| Requests per instance | 1 at a time | Up to 1,000 (default 80) |
| Where code runs | One AWS region | One Google Cloud region |
| Languages | Node.js, Python, Java, .NET, Ruby | Node.js, Python, Go, Java, Ruby, PHP, .NET |
Facts from each provider's own documentation, checked October 14, 2026.
What are the key differences between AWS Lambda and Google Cloud Run?
- Billing unit. Lambda bills memory × duration per millisecond. Cloud Run bills CPU and memory separately for instance time, rounded up to 100 ms.
- Free tier. Cloud Run includes 2 million requests, 180,000 vCPU-seconds and 360,000 GiB-seconds a month; Lambda 1 million requests and 400,000 GB-seconds.
- Concurrency. A Lambda execution environment handles one request at a time; a Cloud Run instance can handle up to 1,000.
- Limits. Lambda runs up to 15 minutes with up to 10,240 MB of memory; Cloud Run functions run up to 60 minutes per HTTP request.
Should you choose AWS Lambda or Google Cloud Run?
Choose AWS Lambda if
- your functions are short and per-millisecond billing matters
- you build on DynamoDB, S3 and other AWS events
- you want one request per environment with no tuning
Choose Google Cloud Run if
- your functions can serve many requests at once per instance
- you need runs longer than 15 minutes
- you want the larger free tier
More comparisons: AWS vs Google Cloud · Amazon EC2 vs Compute Engine · AWS Lambda vs Cloudflare Workers · AWS Lambda vs Azure Functions · Google Cloud Run vs Cloudflare Workers · Amazon S3 vs Google Cloud Storage · Amazon RDS vs Google Cloud SQL · Amazon DynamoDB vs Firestore.
Where do these prices come from?
Both sides use the provider's own published price list, read on October 14, 2026, for the same region, with the always-free allowances applied.
- AWS: AWS Lambda pricing
- Google Cloud: Cloud Run pricing
Prices are in US dollars, on-demand, for Linux, with no commitments. Every figure on this page is generated from the same price snapshot as the calculator, and automated tests check each claim whenever the prices change. A month is 730 hours and 1 TB is 1,024 GB. Providers change prices from time to time, so for a purchase decision confirm the final figure in the provider's console.
Moving between AWS Lambda and Google Cloud Run?
Playxoft builds and runs production backends on AWS, Google Cloud, Azure and Cloudflare, and plans migrations between them with no surprise downtime, including white-label work for agencies. Send us your architecture or last month's invoice and we will tell you, free, which side is cheaper for your real usage. Get a free cloud cost review.
Frequently asked questions
Last updated by the Playxoft engineering team.