Cloud · head to head
Lambda (AWS Serverless) vs Heroku

Lambda (AWS Serverless)
Cloud
Run code without thinking about servers
- From
- Free
- Free plan
- Yes
The short version
- Heroku is a cloud platform as a service.
- Lambda (AWS Serverless) is free; Heroku starts at $5/mo.
- Only Lambda (AWS Serverless) lists event-driven execution; only Heroku lists dynos (containers).
- Where Lambda (AWS Serverless) falls short: provisioned concurrency, used to avoid cold starts, is charged separately at $0.0000041667 per GB-second whether or not the function runs.
- Where Heroku falls short: there is no free dyno tier; the cheapest Eco dyno is $5 per month.
- Prices and features on this page were last checked on 13 November 2026.
How do Lambda (AWS Serverless) and Heroku differ?
Lambda (AWS Serverless) and Heroku differ on starting price (Free against $5/month), pricing model (Usage-based against Subscription) and free tier (Yes against No). Only the attributes on which Lambda (AWS Serverless) and Heroku actually diverge.
| Attribute | Lambda (AWS Serverless) | Heroku |
|---|---|---|
| Starting price | Free | $5/month |
| Pricing model | Usage-based | Subscription |
| Free tier | Yes | No |
| Platforms | Web, API | Web, API, Workers |
| Founded | 2014 | 2007 |
Identical on both: category (Cloud).
Which features does each one have?
They share 3 listed features; 17 appear only for Lambda (AWS Serverless) and 17 only for Heroku. Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.
Only in Lambda (AWS Serverless)
- Function-as-a-Service
- Event-driven execution
- Auto-scaling
- Pay-per-use
- Multiple languages
- Concurrency limits
- Dead Letter Queues
- API Gateway
Only in Heroku
- Git-based deployment
- Buildpacks
- Dynos (containers)
- Add-ons marketplace
- Postgres database
- Logging
- API
- GitHub
Both cover
- Environment variables
- Cloud deployment
- Web support
What is each one used for?
Lambda (AWS Serverless) is most often brought in for event-driven functions without managing servers; Heroku for application hosting. The jobs each tool is most often brought in to do.
Lambda (AWS Serverless)
- Event-driven functions without managing serversnot Heroku
- API backends behind API Gatewaynot Heroku
- Processing S3, DynamoDB, SQS and Kinesis eventsnot Heroku
- Scheduled jobs without a always-on instancenot Heroku
- Edge compute through Lambda@Edgenot Heroku
Heroku
- Application hostingnot Lambda (AWS Serverless)
- Database as a servicenot Lambda (AWS Serverless)
- CI/CD pipelinesnot Lambda (AWS Serverless)
- API deploymentnot Lambda (AWS Serverless)
Where do Lambda (AWS Serverless) and Heroku fall short?
Lambda (AWS Serverless)'s most cited limit: ephemeral storage beyond the included 512 MB is metered. Heroku's: there is no free dyno tier; the cheapest Eco dyno is $5 per month. Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Lambda (AWS Serverless)
- Billed on two axes at once, $0.20 per million requests plus $0.0000166667 per GB-second of duration, so memory settings change the bill as much as traffic does
- Provisioned concurrency, used to avoid cold starts, is charged separately at $0.0000041667 per GB-second whether or not the function runs
- Ephemeral storage beyond the included 512 MB is metered
- Lambda@Edge costs $0.60 per million requests, three times the standard request rate
- VPC use and cross-region data transfer carry EC2 charges on top
Heroku
- There is no free dyno tier; the cheapest Eco dyno is $5 per month
- Eco dynos sleep after 30 minutes of inactivity, are restricted to personal accounts and allow only 2 process types
- Free SSL and 10 process types start at the Basic dyno at $7 per month
- Private and Shield dyno types require a Private Space, which is billed on top of the dynos
- Private Space dynos start at $250 per month for Private-M and $500 per month for Private-L
- Dyno prices are per dyno per month, so an app with several process types multiplies the bill
How much do Lambda (AWS Serverless) and Heroku cost?
Lambda (AWS Serverless) is free to use; Heroku starts at $5/mo. Plan by plan below, from each vendor's own pricing page.
Lambda (AWS Serverless)
Free- Free TierFree
- 1M free requests/month
- 400,000 GB-seconds/month
- Always free
Heroku
$5/month- Eco Dyno$5/mo
- 0.5 GB RAM
- Git/Docker deploy
- Custom domains
- Basic Dyno$7/mo
- 0.5 GB RAM
- Always-on
- Free SSL
- Standard-1X Dyno$25/mo
- 0.5 GB RAM
- Horizontal scaling
- App metrics
- Standard-2X Dyno$50/mo
- 1 GB RAM
- Horizontal scaling
- App metrics
Which should you pick?
Choose Lambda (AWS Serverless) if
- You need function-as-a-service.
- You want to start without paying.
- You work on Web, API.
- You also want event-driven execution.
Choose Heroku if
- You need git-based deployment.
- You work on Web, API, Workers.
- You also want buildpacks.
Questions people ask
- Is Lambda (AWS Serverless) or Heroku better?
- Neither clearly leads. Lambda (AWS Serverless) starts at Free and Heroku at $5/month, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Lambda (AWS Serverless) or Heroku?
- Lambda (AWS Serverless) has a free tier; the other does not. Paid plans start at Free for Lambda (AWS Serverless) and $5/month for Heroku.
- Does Lambda (AWS Serverless) or Heroku run on more platforms?
- Lambda (AWS Serverless) runs on Web, API. Heroku runs on Web, API, Workers.
- Can I use Lambda (AWS Serverless) for free?
- Yes. Lambda (AWS Serverless) has a free tier, so you can try it without paying. Heroku starts at $5/month.
- What is Lambda (AWS Serverless) best used for?
- Lambda (AWS Serverless) is most often used for event-driven functions without managing servers, api backends behind api gateway, processing s3, dynamodb, sqs and kinesis events, scheduled jobs without a always-on instance. Of those, event-driven functions without managing servers and api backends behind api gateway are not what Heroku is typically brought in for.
- What can Lambda (AWS Serverless) do that Heroku cannot?
- Lambda (AWS Serverless) covers Function-as-a-Service, Event-driven execution, Auto-scaling, Pay-per-use. Heroku covers Git-based deployment, Buildpacks, Dynos (containers), Add-ons marketplace. Both handle Environment variables, Cloud deployment, Web support.
Answered from the vendors’ own pages
Lambda (AWS Serverless): Is there a free tier for AWS Lambda?
Yes. AWS Lambda offers a free tier including 1 million requests per month, 400,000 GB-seconds per month, and 100 GB monthly response streaming.
SourceHeroku: How much does Heroku cost?
Heroku dyno pricing starts at $5 per month USD for the Eco tier (with 30-minute inactivity sleep), $7 per month for Basic (always-on), and scales up to $1,500 per month for Performance-2XL with 126 GB RAM.
SourceLambda (AWS Serverless): How is AWS Lambda charged?
Lambda charges $0.20 per million requests. Duration charges are $0.0000166667 per GB-second for x86 (up to 6 billion GB-seconds/month in US East Ohio with tiered pricing). Ephemeral storage over the included 512 MB costs $0.0000000309 per GB-second. Provisioned Concurrency costs $0.0000041667 per GB-second with a 5-minute minimum.
SourceHeroku: What is the cheapest always-on Heroku plan?
The Basic Dyno at $7 per month USD is Heroku's cheapest always-on container option. It provides 0.5 GB RAM, free SSL, and support for 10 process types.
SourceLambda (AWS Serverless): What are Lambda Durable Functions pricing?
Lambda Durable Functions include operations at $8.00 per million (start execution, steps, waits). Data written costs $0.25 per GB. Data retention is $0.15 per GB-month with configurable 1-90 day retention (default 14 days).
SourceHeroku: How is Heroku Postgres priced?
Heroku Postgres Essential tier (shared resources) starts at $5-$20 per month for 1-32 GB disk. Standard tier (dedicated) ranges $50-$12,000 per month. Premium, Private, Shield, and Advanced tiers offer higher performance at corresponding prices.
SourceRelated pages
More on Lambda (AWS Serverless)
Other head to heads
- Lambda (AWS Serverless) vs Deno Deploy
- Lambda (AWS Serverless) vs Cerebrium
- Lambda (AWS Serverless) vs Serverless Framework
- Lambda (AWS Serverless) vs Neon
- Lambda (AWS Serverless) vs Beam Cloud
- Lambda (AWS Serverless) vs Upstash
- Lambda (AWS Serverless) vs Koyeb
- Lambda (AWS Serverless) vs Azure Functions
- Lambda (AWS Serverless) vs Lambda
- Lambda (AWS Serverless) vs Porter
- Lambda (AWS Serverless) vs Terragrunt
- Lambda (AWS Serverless) vs HAProxy
- Lambda (AWS Serverless) vs K3s
- Lambda (AWS Serverless) vs Proxmox VE
- Lambda (AWS Serverless) vs Buildah
- Lambda (AWS Serverless) vs CloudAMQP
- Lambda (AWS Serverless) vs Rancher
- Lambda (AWS Serverless) vs Coolify
- Lambda (AWS Serverless) vs Dokku
- Lambda (AWS Serverless) vs DigitalOcean
- Lambda (AWS Serverless) vs AWS (Amazon Web Services)
- Lambda (AWS Serverless) vs Render
- Lambda (AWS Serverless) vs SST
- Lambda (AWS Serverless) vs Encore
- Lambda (AWS Serverless) vs Zeabur
- Lambda (AWS Serverless) vs Railway
- Lambda (AWS Serverless) vs Linode
- Lambda (AWS Serverless) vs Go
- Lambda (AWS Serverless) vs Hetzner Cloud
- Lambda (AWS Serverless) vs Infracost
- Lambda (AWS Serverless) vs Jaeger
- Lambda (AWS Serverless) vs Longhorn
- Heroku vs Deno Deploy
- Heroku vs Cerebrium
- Heroku vs Serverless Framework
- Heroku vs Neon
- Heroku vs Beam Cloud
- Heroku vs Upstash
- Heroku vs Koyeb
- Heroku vs Azure Functions
- Heroku vs Lambda
- Heroku vs Porter
- Heroku vs Terragrunt
- Heroku vs HAProxy
- Heroku vs K3s
- Heroku vs Proxmox VE
- Heroku vs Buildah
- Heroku vs CloudAMQP
- Heroku vs Rancher
- Heroku vs Coolify
- Heroku vs Dokku
- Heroku vs DigitalOcean
- Heroku vs AWS (Amazon Web Services)
- Heroku vs Render
- Heroku vs SST
- Heroku vs Encore
- Heroku vs Zeabur
- Heroku vs Railway
- Heroku vs Linode
- Heroku vs Go
- Heroku vs Hetzner Cloud
- Heroku vs Infracost
- Heroku vs Jaeger
- Heroku vs Longhorn

