Serverless cost calculator

What a workload costs a month on Cloud Run, Cloud Run functions, Lambda, Azure Functions, Container Apps and Fargate: the number of requests, how long each takes and the vCPU and memory it needs, in the cheapest region anywhere or in a zone.

Prices checked 25 October 2026, 16:05 UTC, from each provider's own price data. List prices in USD; a GB is 1,024 MB on every cloud here.

ServiceRegionA month
Fargateus-west-2$36.04
Cloud Run, instance-basedus-central1$52.60
Lambdaap-southeast-7$55.62
Cloud Runus-central1$55.98
Cloud Run functionseurope-north1$55.98
Container Appsuaenorth$76.64
Azure Functionseastus$138

10 million requests of 200 ms at 1 vCPU and 2 GiB, one at a time, free tiers taken off.

Every service side by side for any size, how busy and where, with the cheapest VM beside them: the serverless prices table. Prices per region: Cloud Run, Cloud Run functions, Lambda, Fargate, Azure Functions, Container Apps. When a VM is cheaper: VM vs serverless.

Questions

What does the calculator assume?

Requests spread evenly over the month, the given number at once on an instance. Lambda bills each request to the millisecond. Cloud Run, Azure Functions and Container Apps bill the time an instance is busy, rounded up (to 100 ms, at least a second on Azure Functions, to the second on Container Apps): with steady traffic that is the busy time, with sparse traffic each request is rounded up on its own, never more than the instances the load needs running all month. Fargate and instance-based Cloud Run run enough instances for the load all month, at least one. No cold starts, data transfer or storage.

How is memory chosen on Lambda and Azure Functions?

Lambda gets the memory that gives at least the vCPUs you ask for (1,769 MB per vCPU) and at least the memory, up to 10,240 MB and 6 vCPU. Azure Functions gets the smallest Flex Consumption instance that fits: 512 MB with 0.25 vCPU, 2,048 MB with 1 or 4,096 MB with 2.