Softwr

Databases · head to head

CosmosDB vs EMQX

CosmosDB logo

CosmosDB

Databases

Globally distributed, multi-model database service from Azure

From
Free
Rated
-
EMQX logo

EMQX

Databases

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

From
Free
Rated
-

The short version

  • Each has a real cost: CosmosDB autoscale provisioned throughput enforces a minimum of 1,000 RU/s, billed hourly whether or not the database is used; 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.
  • They diverge on capability: CosmosDB covers Global Distribution, EMQX covers Erlang clustering.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which CosmosDB and EMQX actually diverge.

Attributes where CosmosDB and EMQX differ
AttributeCosmosDBEMQX
Pricing modelusage-basedPer month by connection and session volume
PlatformsWeb, AzureLinux, Docker, Kubernetes, Cloud, macOS
Founded1975Unknown

Identical on both: starting price (Free), free tier (Yes), user rating (Not yet rated), category (Databases).

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 CosmosDB

  • Global Distribution
  • Multi-model APIs
  • Elastic Scaling
  • Five Consistency Levels
  • SLA-backed Latency
  • Automatic Indexing
  • Serverless
  • Azure Functions

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.

CosmosDB

  • Running a globally distributed multi model database on Azurenot EMQX
  • Serving low latency reads and writes from multiple Azure regionsnot EMQX
  • Storing document, key value and graph data behind a managed servicenot EMQX

EMQX

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

Where each one falls short

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

CosmosDB

  • Autoscale provisioned throughput enforces a minimum of 1,000 RU/s, billed hourly whether or not the database is used
  • Provisioned throughput is charged in every region the account is replicated to, so multi region accounts multiply the RU bill
  • Storage charges cover data, indexes and backups in each replicated region
  • Egress out of Azure and between regions is charged, though ingress is free
  • The free allowance is one account per Azure subscription, limited to 1,000 RU/s and 25 GB
  • RU/s rates vary by region and are only shown through the pricing calculator rather than a flat published rate

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

CosmosDB

Free
  • Free TierFree
    • 1000 RU/s
    • 25GB storage
    • First 12 months
  • ServerlessFree
    • Pay per request
    • Auto-scaling
    • Event-driven workloads

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/month
    • Single tenant cluster
    • Traffic allowance included
    • 24/7 support
  • Enterprise self-managed$undefined/year
    • Deploy on premises, at the edge or in any cloud
    • Clustering licensed
    • 256 MB maximum message size

Which should you pick?

Choose CosmosDB if

  • You need global distribution.
  • You want to start without paying.
  • You work on Web, Azure.
  • You also want multi-model apis.

Choose EMQX if

  • You need erlang clustering.
  • You want to start without paying.
  • You work on Linux, Docker, Kubernetes, Cloud, macOS.
  • You also want mqtt 5.0 and quic.

Questions people ask

Is CosmosDB or EMQX better?
Neither clearly leads. CosmosDB starts at Free and EMQX at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, CosmosDB or EMQX?
CosmosDB starts at Free and EMQX at Free.
Does CosmosDB or EMQX run on more platforms?
CosmosDB runs on Web, Azure. EMQX runs on Linux, Docker, Kubernetes, Cloud, macOS.
Can I use CosmosDB for free?
Both have a free tier, so you can try either at no cost before committing.
What is CosmosDB best used for?
CosmosDB is most often used for running a globally distributed multi model database on azure, serving low latency reads and writes from multiple azure regions, storing document, key value and graph data behind a managed service. Of those, running a globally distributed multi model database on azure and serving low latency reads and writes from multiple azure regions are not what EMQX is typically brought in for.
What can CosmosDB do that EMQX cannot?
CosmosDB covers Global Distribution, Multi-model APIs, Elastic Scaling, Five Consistency Levels. EMQX covers Erlang clustering, MQTT 5.0 and QUIC, Rule engine, Data integration sinks.

Answered from the vendors’ own pages

CosmosDB: Is there a free tier for Azure Cosmos DB?

Yes, Cosmos DB offers a free tier with 1,000 RU/s of throughput and 25 GB of storage per month for the lifetime of the account, available to new accounts.

Source
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.

CosmosDB: How is Cosmos DB priced after the free tier?

Cosmos DB uses three billing models: provisioned throughput billed per request unit per second, vCore pricing for certain APIs, or serverless consumption pricing where you pay only for requests processed. Reserved capacity offers 20% discount for one year or 30% for three years.

Source
EMQX: Can I run a free cluster?

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

CosmosDB: Can I change my pricing model after choosing one?

No. Once you select a compute pricing model and API, they cannot be changed. This choice is permanent for that database.

Source
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.

CosmosDB: Is there a trial period for Cosmos DB beyond the free tier?

Azure offers a 30-day free trial account for all Azure services. Additionally, Azure AI customers may be eligible for a 90-day free Cosmos DB subscription through the Azure AI Advantage program.

Source
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