Softwr

Databases · head to head

EMQX vs Valkey

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
-
Full reviewWebsite
Valkey logo

Valkey

Databases

Open-source in-memory data store forked from Redis

From
Free
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: 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.; Valkey younger project, so its track record is short even though the codebase is not
  • They diverge on capability: EMQX covers Erlang clustering, Valkey covers Redis-compatible.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which EMQX and Valkey actually diverge.

Attributes where EMQX and Valkey differ
AttributeEMQXValkey
Pricing modelPer month by connection and session volumeOpen source, no licence fee; managed cloud billed separately
PlatformsLinux, Docker, Kubernetes, Cloud, macOSLinux, macOS, Docker, Self-hosted

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

Only in Valkey

  • Redis-compatible
  • BSD licensed
  • Rich data structures
  • Replication and persistence

What people use each for

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

EMQX

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

Valkey

  • Continuing on a permissively licensed in-memory store after the Redis licence changenot EMQX
  • Caching and session storage where a foundation-governed project is a procurement requirementnot EMQX
  • Migrating from Redis without rewriting application codenot EMQX

Where each one falls short

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

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.

Valkey

  • Younger project, so its track record is short even though the codebase is not
  • Divergence from Redis grows over time, so compatibility is strongest near the fork point and weakens as both evolve
  • Ecosystem tooling and documentation still frequently assume Redis, leaving translation work

Pricing, plan by plan

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

Valkey

Free
  • ValkeyFree
    • Full functionality
    • Self-hosted
    • No usage limits

Which should you pick?

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.
EMQX review

Choose Valkey if

  • You need redis-compatible.
  • You want to start without paying.
  • You work on Linux, macOS, Docker, Self-hosted.
  • You also want bsd licensed.
Valkey review

Questions people ask

Is EMQX or Valkey better?
Neither clearly leads. EMQX starts at Free and Valkey at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, EMQX or Valkey?
EMQX starts at Free and Valkey at Free.
Does EMQX or Valkey run on more platforms?
EMQX runs on Linux, Docker, Kubernetes, Cloud, macOS. Valkey runs on Linux, macOS, Docker, Self-hosted.
Can I use EMQX for free?
Both have a free tier, so you can try either at no cost before committing.
What is EMQX best used for?
EMQX is most often used for a connected vehicle platform needing millions of persistent mqtt sessions with quic for handover across mobile networks, an industrial operator routing sensor telemetry straight into timescaledb or kafka without writing a consumer service, an iot product team that has outgrown a single mosquitto instance and needs clustering and shared subscriptions, a smart building deployment mixing mqtt, coap and lwm2m devices on one broker. Of those, a connected vehicle platform needing millions of persistent mqtt sessions with quic for handover across mobile networks and an industrial operator routing sensor telemetry straight into timescaledb or kafka without writing a consumer service are not what Valkey is typically brought in for.
What can EMQX do that Valkey cannot?
EMQX covers Erlang clustering, MQTT 5.0 and QUIC, Rule engine, Data integration sinks. Valkey covers Redis-compatible, BSD licensed, Rich data structures, Replication and persistence.

Answered from the vendors’ own pages

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.

Valkey: Is Valkey free?

Yes, BSD-licensed open source under the Linux Foundation.

EMQX: Can I run a free cluster?

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

Valkey: Why does Valkey exist?

Redis changed its licence away from BSD in 2024. Valkey is the community fork continuing under permissive terms, backed by AWS, Google Cloud and Oracle among others.

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.

Valkey: Can I switch from Redis to Valkey?

At the fork point it is drop-in compatible with existing clients and data. The further both projects move from that point, the more you should verify the specific features you use.

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

More on EMQX

More on Valkey

Keep looking

Other head to heads