Skip to main content
reference

Serverless Functions Pricing Comparison

Public monthly pricing for AWS Lambda and other serverless functions across two common HTTP workloads.

Pricing verified:

Serverless function pricing changes with request volume, runtime, memory, free allowances, and plan floors. The tables give every provider the same workloads at 1M, 10M, and 100M requests, so those billing differences stay visible.

See Methodology for workload assumptions, product configurations, calculation rules, sources, and exclusions.

Short API requests

Short requests put more weight on request charges, allowances, and plan floors than on execution time.

Duration
100 ms
Active CPU
10 ms
Memory
64 MiB
Request
1 KiB
Response
1 KiB
Short API requests pricing at 1M, 10M, and 100M monthly invocations
AWS Lambda 1 Metered$0.00 On-demand No fixed monthly fee$1.80 On-demand No fixed monthly fee$41.94 On-demand No fixed monthly fee
Deno Deploy 4 Included + overage$0.00 Free Workload included$30.00 Pro $20.00/mo fixed + $10.00 usage$240.02 Pro $20.00/mo fixed + $220.02 usage
Google Cloud Run functions 6 Metered$0.00 Cloud Run functions No fixed monthly fee$3.20 Cloud Run functions No fixed monthly fee$59.54 Cloud Run functions No fixed monthly fee
Fastly Compute 5 Metered$0.00 Public usage pricing No fixed monthly fee$0.00 Public usage pricing No fixed monthly fee$90.00 Public usage pricing No fixed monthly fee
Cloudflare Workers 3 Included + overage$5.00 Paid Standard $5.00/mo fixed · workload included$6.40 Paid Standard $5.00/mo fixed + $1.40 usage$51.40 Paid Standard $5.00/mo fixed + $46.40 usage
Netlify Functions 7 Credits$9.00 Personal $9.00/mo fixed · workload included$33.00 Pro 5,000 credits $33.00/mo fixed · workload included$315.00 Pro 15,000 credits $95.00/mo fixed + $220.00 usage
Vercel Functions 9 Plan + usage$20.00 Pro $20.00/mo fixed · workload included$20.00 Pro $20.00/mo fixed · workload included$154.44 Pro $20.00/mo fixed + $134.44 usage
Supabase Edge Functions 8 Included + overage$30.00 Pro $30.00/mo fixed · workload included$46.00 Pro $30.00/mo fixed + $16.00 usage$226.00 Pro $30.00/mo fixed + $196.00 usage
Azure Flex Consumption 2 Metered Runtime only · Azure Storage not included$10.70 Flex Consumption No fixed monthly fee$131.30 Flex Consumption No fixed monthly fee$1,337.30 Flex Consumption No fixed monthly fee

CPU-intensive functions

Longer runtime and higher memory make execution pricing and product limits matter more.

Duration
1 s
Active CPU
1 s
Memory
512 MiB
Request
1 KiB
Response
1 KiB
CPU-intensive functions pricing at 1M, 10M, and 100M monthly invocations
Netlify Functions 7 Credits$20.00 Pro 3,000 credits $20.00/mo fixed · workload included$195.00 Pro 15,000 credits $95.00/mo fixed + $100.00 usage$1,983.00 Pro 10,000 credits $63.00/mo fixed + $1,920.00 usage
Google Cloud Run functions 6 Metered$20.03 Cloud Run functions No fixed monthly fee$250.48 Cloud Run functions No fixed monthly fee$2,558.98 Cloud Run functions No fixed monthly fee
AWS Lambda 1 Metered$22.13 On-demand No fixed monthly fee$283.06 On-demand No fixed monthly fee$2,892.37 On-demand No fixed monthly fee
Deno Deploy 4 Included + overage$31.89 Pro $20.00/mo fixed + $11.89 usage$185.02 Pro $20.00/mo fixed + $165.02 usage$1,922.22 Pro $20.00/mo fixed + $1,902.22 usage
Vercel Functions 9 Plan + usage$42.04 Pro $20.00/mo fixed + $22.04 usage$420.44 Pro $20.00/mo fixed + $400.44 usage$4,204.44 Pro $20.00/mo fixed + $4,184.44 usage
Azure Flex Consumption 2 Metered Runtime only · Azure Storage not included$49.70 Flex Consumption No fixed monthly fee$521.30 Flex Consumption No fixed monthly fee$5,237.30 Flex Consumption No fixed monthly fee

Additional costs

Some charges sit outside the headline estimates. This table shows whether each listed cost is included, plus any published allowance or rate. Superscript numbers match the provider markers above.

ProviderAdditional costIncludedAllowanceRate
AWS Lambda ¹Internet data transferNo100 GB/month$0.09/GB
Azure Flex Consumption ²Required Storage
Internet egress
No (required)
No

100 GB/month
Variable
$0.087/GB
Cloudflare Workers ³EgressNo separate charge
Deno Deploy ⁴EgressYes200 GB$0.50/GB
Fastly Compute ⁵Delivery bandwidth
Delivery requests
No
No
100 GB
1M requests
$0.12/GB
$1/M requests
Google Cloud Run functions ⁶Internet data transferNo1 GiB/month$0.12/GiB
Netlify Functions ⁷BandwidthNoPlan credit pool20 credits/GB
Supabase Edge Functions ⁸EgressNo250 GB$0.09/GB uncached
$0.03/GB cached
Vercel Functions ⁹Edge Requests
Fast Data Transfer
No
No
10M requests
1 TB
$2/M requests
$0.15/GB

Rates are current public self-serve rates for the reference region or plan where a comparable rate is available. Allowances are account- or plan-scoped and may be shared with other usage.

Key takeaways

  • At 1M short requests, AWS Lambda, Deno Deploy, Google Cloud Run functions, and Fastly Compute remain at $0 under the modeled allowances. Fastly is also $0 at 10M. Cloudflare Workers starts at its $5 paid-plan floor.
  • Longer CPU use and higher memory make the 100M CPU-intensive workload much more expensive than the short API workload.
  • Vercel’s included Pro credit covers the modeled usage at 10M short requests, so the headline total remains the $20 monthly plan price.

How to read these prices

These estimates use public USD pricing or the lowest eligible public self-serve plan. Monthly allowances and credits are assumed fully available to the modeled workload. Taxes, negotiated discounts, enterprise contracts, and unrelated services are excluded.

We show a price only when the reviewed public terms support an exact estimate for that workload. Azure Flex is runtime only because the workload defines no Azure Storage usage. Cloudflare Workers, Supabase Edge Functions, and Fastly Compute have no CPU-intensive estimate because the 512 MiB workload exceeds their reviewed memory limits.

See Methodology for workload assumptions, product configurations, calculation rules, sources, and exclusions.

FAQ

What are the hidden costs of serverless functions?
The headline function estimate can exclude data transfer, required storage, databases, queues, observability, and other adjacent services. The comparison lists published transfer and required-service charges where they are part of the reviewed public terms, while optional services remain outside the modeled function workload.
When do serverless functions become expensive?
Serverless functions become more expensive as request volume, execution time, and memory or CPU allocation rise, and some providers add paid plan floors before usage charges. The CPU-intensive workload shows how longer runtime and higher memory can change the bill even at the same request volume.
Are serverless functions cheaper than servers or containers?
Not necessarily, and this reference does not compare those infrastructure models directly. A fair comparison would need equivalent capacity, idle time, supporting services, and operational scope, so the function tables should not be read as proof that serverless is cheaper than servers or containers.
Does a free tier mean my serverless application will be free?
No. Included function usage can make modeled execution cost $0 while required plans, data transfer, storage, or other services still add cost. Allowances may also be account- or plan-scoped and shared with other usage.
What actually determines the cost of a serverless function?
Request count is only one input. Providers can meter requests, executions, CPU time, memory over duration, wall duration, packages, fixed plans, and credits, so the same workload can produce different bills.