Softwr

Cloud · head to head

Lambda (AWS Serverless) vs Cortex

Lambda (AWS Serverless) logo

Lambda (AWS Serverless)

Cloud

Run code without thinking about servers

From
Free
Free plan
Yes
Full reviewWebsite
Cortex logo

Cortex

Developer Tools

Internal developer portal that scores service ownership and maturity rather than just cataloguing services

From
On request
Free plan
No
Full reviewWebsite

The short version

  • Only Lambda (AWS Serverless) has a free tier, so it costs nothing to try first.
  • Each has a real cost: 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; Cortex pricing is quote only, so a platform team cannot build a business case or compare against the true cost of self-hosted Backstage without entering a sales cycle first.
  • They diverge on capability: Lambda (AWS Serverless) covers Function-as-a-Service, Cortex covers Service catalogue.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

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

Attributes where Lambda (AWS Serverless) and Cortex differ
AttributeLambda (AWS Serverless)Cortex
Starting priceFreeOn request
Pricing modelusage-basedquote
Free tierYesNo
CategoryCloudDeveloper Tools
Founded2014Unknown

Identical on both: platforms (Web, Api), user rating (Not yet rated).

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 Lambda (AWS Serverless)

  • Function-as-a-Service
  • Event-driven execution
  • Auto-scaling
  • Pay-per-use
  • Multiple languages
  • Concurrency limits
  • Dead Letter Queues
  • Environment variables

Only in Cortex

  • Service catalogue
  • Scorecards
  • Initiatives
  • Self-service templates
  • Query language
  • Eng intelligence
  • Integrations layer
  • On-call and ownership mapping

What people use each for

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

Lambda (AWS Serverless)

  • Event-driven functions without managing serversnot Cortex
  • API backends behind API Gatewaynot Cortex
  • Processing S3, DynamoDB, SQS and Kinesis eventsnot Cortex
  • Scheduled jobs without a always-on instancenot Cortex
  • Edge compute through Lambda@Edgenot Cortex

Cortex

  • A platform team that needs to prove to leadership how far a Kubernetes or framework migration has actually progressed across hundreds of servicesnot Lambda (AWS Serverless)
  • An organisation where ownership of production services is genuinely unknown after reorganisations or acquisitionsnot Lambda (AWS Serverless)
  • Enforcing production readiness standards on new services at creation time rather than at incident reviewnot Lambda (AWS Serverless)
  • Replacing a self-hosted Backstage that is consuming a full-time engineer or two just to stay upgradednot Lambda (AWS Serverless)

Where each one falls short

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

Cortex

  • Pricing is quote only, so a platform team cannot build a business case or compare against the true cost of self-hosted Backstage without entering a sales cycle first.
  • The catalogue is only as accurate as the metadata you supply, so an organisation with inconsistent repository conventions spends its first quarter cleaning data before any scorecard means anything.
  • Scorecards create political friction: publishing a per-team grade turns an engineering standard into a performance metric, and teams will game the rules rather than fix the underlying issue.
  • It is closed source and hosted, so organisations with strict data residency or air-gap requirements have limited options compared with running Backstage themselves.
  • Value scales with organisation size, so a company with fifty engineers and thirty services will find the catalogue tells them nothing they did not already know while still paying an enterprise contract.

Pricing, plan by plan

Lambda (AWS Serverless)

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

Cortex

On request
  • Cortex$undefined/year
    • Service catalogue and ownership mapping
    • Scorecards and initiatives
    • Self-service templates

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.
Lambda (AWS Serverless) review

Choose Cortex if

  • You need service catalogue.
  • You work on Web, API.
  • You also want scorecards.
Cortex review

Questions people ask

Is Lambda (AWS Serverless) or Cortex better?
Neither clearly leads. Lambda (AWS Serverless) starts at Free and Cortex at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Lambda (AWS Serverless) or Cortex?
Lambda (AWS Serverless) has a free tier; the other does not. Paid plans start at Free for Lambda (AWS Serverless) and On request for Cortex.
Does Lambda (AWS Serverless) or Cortex run on more platforms?
Lambda (AWS Serverless) runs on Web, Api. Cortex 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. Cortex starts at On request.
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 Cortex is typically brought in for.
What can Lambda (AWS Serverless) do that Cortex cannot?
Lambda (AWS Serverless) covers Function-as-a-Service, Event-driven execution, Auto-scaling, Pay-per-use. Cortex covers Service catalogue, Scorecards, Initiatives, Self-service templates.

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.

Source
Cortex: How is Cortex different from Backstage?

Backstage is an open source framework you build and staff. Cortex is a hosted product with scorecards and initiatives out of the box and no platform team required to keep it running.

Lambda (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.

Source
Cortex: Is pricing published?

No. Cortex requires a sales conversation and prepares a custom proposal.

Lambda (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).

Source
Cortex: Can it self-host?

It is offered as a hosted product; on-premise arrangements are handled through sales rather than published.

Cortex: What is the main adoption risk?

Bad or missing service metadata. The catalogue and every scorecard on top of it inherit whatever quality your repositories already have.

Share

Related pages

More on Lambda (AWS Serverless)

More on Cortex

Keep looking

Other head to heads