Softwr

Cloud · head to head

Azure Functions vs Cortex

Azure Functions logo

Azure Functions

Cloud

Event-driven serverless compute on Azure

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 Azure Functions has a free tier, so it costs nothing to try first.
  • Each has a real cost: Azure Functions consumption plan free grant is capped at 1 million executions and 400,000 GB-seconds of resource consumption per month per subscription, billed per GB-second beyond that; 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.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Azure Functions and Cortex actually diverge.

Attributes where Azure Functions and Cortex differ
AttributeAzure FunctionsCortex
Starting priceFreeOn request
Pricing modelusage-basedquote
Free tierYesNo
PlatformsWebWeb, API
CategoryCloudDeveloper Tools

Identical on both: 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 Azure Functions

Nothing recorded that Cortex does not also cover.

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.

Azure Functions

  • Event-driven computingnot Cortex
  • Serverless application backendnot Cortex
  • Scalable API endpointsnot 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 Azure Functions
  • An organisation where ownership of production services is genuinely unknown after reorganisations or acquisitionsnot Azure Functions
  • Enforcing production readiness standards on new services at creation time rather than at incident reviewnot Azure Functions
  • Replacing a self-hosted Backstage that is consuming a full-time engineer or two just to stay upgradednot Azure Functions

Where each one falls short

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

Azure Functions

  • Consumption plan free grant is capped at 1 million executions and 400,000 GB-seconds of resource consumption per month per subscription, billed per GB-second beyond that
  • The newer Flex Consumption plan's free grant is smaller still, at 250,000 executions and 100,000 GB-seconds per month
  • Premium plan avoids per-execution charges but bills continuously for allocated core seconds and memory regardless of invocation volume
  • Memory is rounded up to the nearest 128 MB and execution time to the nearest 1 ms for billing, so small overages round upward

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

Azure Functions

Free
  • Consumption Plan$null/month
    • 1 million requests free monthly
    • 400,000 GB-seconds free monthly
    • Billed per second and executions
  • Flex Consumption Plan$null/month
    • 250,000 executions free monthly
    • 100,000 GB-seconds free monthly
    • Event-driven scaling
  • Premium Plan$null/month
    • No execution charges
    • At least one instance required
    • Includes automatic scaling and VNET access

Cortex

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

Which should you pick?

Choose Azure Functions if

  • You want to start without paying.
Azure Functions review

Choose Cortex if

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

Questions people ask

Is Azure Functions or Cortex better?
Neither clearly leads. Azure Functions 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, Azure Functions or Cortex?
Azure Functions has a free tier; the other does not. Paid plans start at Free for Azure Functions and On request for Cortex.
Does Azure Functions or Cortex run on more platforms?
Azure Functions runs on Web. Cortex runs on Web, API.
Can I use Azure Functions for free?
Yes. Azure Functions has a free tier, so you can try it without paying. Cortex starts at On request.
What is Azure Functions best used for?
Azure Functions is most often used for event-driven computing, serverless application backend, scalable api endpoints. Of those, event-driven computing and serverless application backend are not what Cortex is typically brought in for.
What can Azure Functions do that Cortex cannot?
Cortex covers Service catalogue, Scorecards, Initiatives, Self-service templates.

Answered from the vendors’ own pages

Azure Functions: Does Azure Functions have a free tier?

Yes, Azure Functions includes a monthly free grant of 1 million requests and 400,000 GB-seconds on the Consumption Plan, or 250,000 executions and 100,000 GB-seconds on Flex Consumption.

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.

Azure Functions: What is Azure Functions' pricing model?

Azure Functions uses usage-based pricing. Consumption plans charge per second of resource consumption and per execution, measured in gigabyte-seconds and rounded to the nearest 128 MB.

Source
Cortex: Is pricing published?

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

Azure Functions: What is the minimum execution time for Azure Functions?

The minimum execution time is 100 milliseconds on Consumption plans. Premium plans charge based on core seconds and allocated memory.

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 Azure Functions

More on Cortex

Keep looking

Other head to heads