Softwr

Developer Tools · head to head

Cortex vs EMQX

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
EMQX logo

EMQX

Databases

Erlang MQTT broker for large IoT fleets, relicensed to BSL with production free use limited to one node

From
Free
Free plan
Yes

The short version

  • EMQX starts at $234/mo; Cortex prices on request.
  • Only Cortex lists service catalogue; only EMQX lists erlang clustering.
  • Prices and features on this page were last checked on 31 August 2026.

Where they differ

Only the attributes on which Cortex and EMQX actually diverge.

Attributes where Cortex and EMQX differ
AttributeCortexEMQX
Starting priceOn requestFree
Pricing modelQuotePer month by connection and session volume
Free tierNoYes
PlatformsWeb, APILinux, Self-hosted, Web, macOS
CategoryDeveloper ToolsDatabases

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 Cortex

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

Only in EMQX

  • Erlang clustering
  • MQTT 5.0 and QUIC
  • Rule engine
  • Data integration sinks
  • Session persistence
  • Multi protocol gateways
  • Authentication and authorisation
  • Dashboard and REST API

What people use each for

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

Cortex

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

EMQX

  • A connected vehicle platform needing millions of persistent MQTT sessions with QUIC for handover across mobile networksnot Cortex
  • An industrial operator routing sensor telemetry straight into TimescaleDB or Kafka without writing a consumer servicenot Cortex
  • An IoT product team that has outgrown a single Mosquitto instance and needs clustering and shared subscriptionsnot Cortex
  • A smart building deployment mixing MQTT, CoAP and LwM2M devices on one brokernot Cortex

Where each one falls short

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

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

EMQX

  • The move to Business Source Licence 1.1 at version 5.9 in May 2025 limits free production use to a single node, so the clustering that justifies choosing EMQX now requires a paid subscription from the second node onward
  • The relicensing arrived in a minor release, which caught users who had pinned to 5.x expecting Apache 2.0 terms and forced legal review of existing deployments
  • Running an Erlang/OTP cluster well requires operational knowledge most teams do not have, and diagnosing distribution, mnesia or memory issues means learning a runtime you use for nothing else
  • Enterprise pricing is quoted rather than published for the self-managed edition, so the cost of the clustered configuration you actually need is invisible until you talk to sales
  • The Serverless tier caps at around a thousand connections and shares infrastructure, which makes it a prototyping tier rather than a genuine small production option

Pricing, plan by plan

Cortex

On request
  • CortexOn request
    • Service catalogue and ownership mapping
    • Scorecards and initiatives
    • Self-service templates

EMQX

Free
  • Open Source single nodeFree
    • BSL 1.1 licence since version 5.9
    • Free production use of one node only
    • All former enterprise features visible
  • ServerlessFree
    • Free monthly quota then pay as you go
    • Up to 1,000 connections
    • 8 by 5 support
  • Dedicated Flex$234/mo
    • Single tenant cluster
    • Traffic allowance included
    • 24/7 support
  • Enterprise self-managedOn request
    • Deploy on premises, at the edge or in any cloud
    • Clustering licensed
    • 256 MB maximum message size

Which should you pick?

Choose Cortex if

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

Choose EMQX if

  • You need erlang clustering.
  • You want to start without paying.
  • You work on Linux, Self-hosted, Web, macOS.
  • You also want mqtt 5.0 and quic.

Questions people ask

Is Cortex or EMQX better?
Neither clearly leads. Cortex starts at On request and EMQX at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Cortex or EMQX?
EMQX has a free tier; the other does not. Paid plans start at On request for Cortex and Free for EMQX.
Does Cortex or EMQX run on more platforms?
Cortex runs on Web, API. EMQX runs on Linux, Self-hosted, Web, macOS.
Can I use EMQX for free?
Yes. EMQX has a free tier, so you can try it without paying. Cortex starts at On request.
What is Cortex best used for?
Cortex is most often used for a platform team that needs to prove to leadership how far a kubernetes or framework migration has actually progressed across hundreds of services, an organisation where ownership of production services is genuinely unknown after reorganisations or acquisitions, enforcing production readiness standards on new services at creation time rather than at incident review, replacing a self-hosted backstage that is consuming a full-time engineer or two just to stay upgraded. Of those, a platform team that needs to prove to leadership how far a kubernetes or framework migration has actually progressed across hundreds of services and an organisation where ownership of production services is genuinely unknown after reorganisations or acquisitions are not what EMQX is typically brought in for.
What can Cortex do that EMQX cannot?
Cortex covers Service catalogue, Scorecards, Initiatives, Self-service templates. EMQX covers Erlang clustering, MQTT 5.0 and QUIC, Rule engine, Data integration sinks.

Answered from the vendors’ own pages

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.

EMQX: Is EMQX still open source?

Not in the OSI sense since version 5.9. It is source-available under Business Source Licence 1.1, reverting to Apache 2.0 four years after each release.

Cortex: Is pricing published?

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

EMQX: Can I run a free cluster?

No. The additional use grant permits free production use of one node; clustering requires a commercial licence.

Cortex: Can it self-host?

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

EMQX: What changed for existing users?

Community and enterprise editions merged, so all features are now visible, but the licence terms tightened in the same minor release.

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.

EMQX: Which version is still Apache 2.0?

Releases before 5.9 remain under Apache 2.0, and each BSL release converts to Apache 2.0 four years after publication.

Share

Related pages

Other head to heads