Softwr

Cloud & Infrastructure · head to head

Heroku vs Lambda (AWS Serverless)

Heroku logo

Heroku

Cloud & Infrastructure

Cloud Application Platform

From
$7/month
Rated
-
Lambda (AWS Serverless) logo

Lambda (AWS Serverless)

Cloud & Infrastructure

Run code without thinking about servers

From
Free
Rated
-

The short version

  • Only Lambda (AWS Serverless) has a free tier, so it costs nothing to try first.
  • Each has a real cost: Heroku there is no free dyno tier; the cheapest Eco dyno is $5 per month; 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
  • They diverge on capability: Heroku covers Git-based deployment, Lambda (AWS Serverless) covers Function-as-a-Service.

Where they differ

Only the attributes on which Heroku and Lambda (AWS Serverless) actually diverge.

Attributes where Heroku and Lambda (AWS Serverless) differ
AttributeHerokuLambda (AWS Serverless)
Starting price$7/monthFree
Pricing modelsubscriptionusage-based
Free tierNoYes
PlatformsWeb, Api, WorkersWeb, Api
Founded20072014

Identical on both: user rating (Not yet rated), category (Cloud & Infrastructure).

What each one covers

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 Heroku

  • Git-based deployment
  • Buildpacks
  • Dynos (containers)
  • Add-ons marketplace
  • Postgres database
  • Logging
  • API
  • GitHub

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

Both cover

  • Environment variables
  • Cloud deployment
  • Web support

What people use each for

The jobs each tool is most often brought in to do.

Heroku

  • Deploying and scaling web applications with git push and no server administrationnot Lambda (AWS Serverless)
  • Running managed Postgres, Redis and Kafka as attached data servicesnot Lambda (AWS Serverless)
  • Isolated production environments in a Private Space for regulated workloadsnot Lambda (AWS Serverless)

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

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

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

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

Pricing, plan by plan

Heroku

$7/month
  • Hobby$7/month
    • 512MB RAM
    • Shared CPU
    • 1 web dyno
  • Standard$50/month
    • 512MB RAM
    • Dedicated CPU
    • Automatic scaling

Lambda (AWS Serverless)

Free
  • Free TierFree
    • 1M free requests/month
    • 400,000 GB-seconds/month
    • Always free

Which should you pick?

Choose Heroku if

  • You need git-based deployment.
  • You work on Web, Api, Workers.
  • You also want buildpacks.

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.

Questions people ask

Is Heroku or Lambda (AWS Serverless) better?
Neither clearly leads. Heroku starts at $7/month and Lambda (AWS Serverless) at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Heroku or Lambda (AWS Serverless)?
Lambda (AWS Serverless) has a free tier; the other does not. Paid plans start at $7/month for Heroku and Free for Lambda (AWS Serverless).
Does Heroku or Lambda (AWS Serverless) run on more platforms?
Heroku runs on Web, Api, Workers. Lambda (AWS Serverless) runs on Web, Api.
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 $7/month.
What is Heroku best used for?
Heroku is most often used for deploying and scaling web applications with git push and no server administration, running managed postgres, redis and kafka as attached data services, isolated production environments in a private space for regulated workloads. Of those, deploying and scaling web applications with git push and no server administration and running managed postgres, redis and kafka as attached data services are not what Lambda (AWS Serverless) is typically brought in for.
What can Heroku do that Lambda (AWS Serverless) cannot?
Heroku covers Git-based deployment, Buildpacks, Dynos (containers), Add-ons marketplace. Lambda (AWS Serverless) covers Function-as-a-Service, Event-driven execution, Auto-scaling, Pay-per-use. Both handle Environment variables, Cloud deployment, Web support.

Related pages

Other head to heads