Softwr

Databases · head to head

Valkey vs VerneMQ

Valkey logo

Valkey

Databases

Open-source in-memory data store forked from Redis

From
Free
Rated
-
Full reviewWebsite
VerneMQ logo

VerneMQ

Databases

Erlang MQTT broker whose source is Apache 2.0 but whose official binaries need a paid subscription

From
Free
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: Valkey younger project, so its track record is short even though the codebase is not; VerneMQ the official binaries and Docker images are not Apache 2.0 but sit under a EULA requiring a yearly commercial subscription, a distinction easy to miss and awkward to discover during a licence audit.
  • They diverge on capability: Valkey covers Redis-compatible, VerneMQ covers Erlang/OTP clustering.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Valkey and VerneMQ actually diverge.

Attributes where Valkey and VerneMQ differ
AttributeValkeyVerneMQ
Pricing modelOpen source, no licence fee; managed cloud billed separatelyquote
PlatformsLinux, macOS, Docker, Self-hostedLinux, Docker, macOS, Kubernetes

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 Valkey

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

Only in VerneMQ

  • Erlang/OTP clustering
  • MQTT 5.0 support
  • Plugin system
  • Backpressure handling
  • Bridge support
  • Metrics export
  • MQTT over WebSockets
  • Pluggable auth backends

What people use each for

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

Valkey

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

VerneMQ

  • An industrial operator that wants an MQTT broker with predictable memory behaviour and no data integration features it will not usenot Valkey
  • A team building from source to stay strictly under Apache 2.0 terms with no vendor licence entanglementnot Valkey
  • A deployment needing custom authentication logic implemented as a plugin in Lua or over a webhooknot Valkey
  • An organisation that wants a broker maintained by a small European company rather than by a vendor that keeps changing licencesnot Valkey

Where each one falls short

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

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

VerneMQ

  • The official binaries and Docker images are not Apache 2.0 but sit under a EULA requiring a yearly commercial subscription, a distinction easy to miss and awkward to discover during a licence audit.
  • Octavo Labs is a very small company, so support depth, response times and the bus factor on the codebase are materially thinner than at HiveMQ or EMQ.
  • There is no data integration or rule engine layer, so routing messages into a database means writing and operating your own consumer service.
  • Operating an Erlang cluster requires runtime knowledge that most teams do not have and will use for nothing else in their stack.
  • There is no vendor-managed cloud offering, so every deployment is self-operated with the infrastructure and on-call cost that implies.

Pricing, plan by plan

Valkey

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

VerneMQ

Free
  • Source buildFree
    • Apache 2.0 licensed source from GitHub
    • Full clustering and plugin capability
    • You compile and package it yourself
  • Binary packages and Docker images$undefined/year
    • Covered by the VerneMQ EULA, not Apache 2.0
    • Yearly usage subscription expected for commercial use
    • Official builds and Docker images
  • Commercial support$undefined/year
    • Evaluation, customisation and operations assistance
    • Custom development
    • Long-term maintenance agreements

Which should you pick?

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

Choose VerneMQ if

  • You need erlang/otp clustering.
  • You want to start without paying.
  • You work on Linux, Docker, macOS, Kubernetes.
  • You also want mqtt 5.0 support.
VerneMQ review

Questions people ask

Is Valkey or VerneMQ better?
Neither clearly leads. Valkey starts at Free and VerneMQ at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Valkey or VerneMQ?
Valkey starts at Free and VerneMQ at Free.
Does Valkey or VerneMQ run on more platforms?
Valkey runs on Linux, macOS, Docker, Self-hosted. VerneMQ runs on Linux, Docker, macOS, Kubernetes.
Can I use Valkey for free?
Both have a free tier, so you can try either at no cost before committing.
What is Valkey best used for?
Valkey is most often used for continuing on a permissively licensed in-memory store after the redis licence change, caching and session storage where a foundation-governed project is a procurement requirement, migrating from redis without rewriting application code. Of those, continuing on a permissively licensed in-memory store after the redis licence change and caching and session storage where a foundation-governed project is a procurement requirement are not what VerneMQ is typically brought in for.
What can Valkey do that VerneMQ cannot?
Valkey covers Redis-compatible, BSD licensed, Rich data structures, Replication and persistence. VerneMQ covers Erlang/OTP clustering, MQTT 5.0 support, Plugin system, Backpressure handling.

Answered from the vendors’ own pages

Valkey: Is Valkey free?

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

VerneMQ: Is VerneMQ free?

The source is Apache 2.0 and free. The official binary packages and Docker images are covered by a separate EULA that expects a yearly fee for commercial use.

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.

VerneMQ: Is the project still maintained?

Yes. Octavo Labs AG in Zurich continues to publish 2.x releases, most recently in 2026.

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.

VerneMQ: Does it have a managed cloud?

No. Every deployment is self-hosted, with commercial support available from Octavo Labs.

VerneMQ: How does it compare to EMQX?

Narrower in features and without a rule engine, but with a simpler licence story for source builds after EMQX moved to BSL.

Share

Related pages

More on Valkey

More on VerneMQ

Keep looking

Other head to heads