Softwr
VerneMQ logo

VerneMQ

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

As of 31 August 2026, VerneMQ is free to use. A distributed MQTT broker built on Erlang/OTP by a small Swiss company, maintained steadily for a decade. Softwr lists it under Databases. VerneMQ is made by Octavo Labs AG, available on Linux, Docker, macOS, Kubernetes.

Overview

What VerneMQ does

VerneMQ is an MQTT broker written in Erlang/OTP that clusters across nodes, supports MQTT 3.1, 3.1.1 and 5.0, and offers a plugin system for authentication, authorisation and message hooks in Erlang, Lua, Python, Java or over WebHooks. It is deliberately narrow: it is a broker with clustering and extensibility, not a data integration platform, and its design goals are predictable memory behaviour and per-session backpressure under load rather than a large feature surface. The fact that changes a decision is the licensing split. The source in the GitHub repository is Apache 2.0, but the binary packages and official Docker images published by Octavo Labs are covered by a separate VerneMQ EULA which requires a yearly subscription contribution for commercial use. Teams that build from source stay under Apache 2.0; teams that docker pull the convenient image are, per those terms, expected to pay. That distinction is not obvious from the repository page and has caught organisations mid-deployment. VerneMQ is developed and maintained by Octavo Labs AG in Zurich, the successor to Erlio GmbH, which is a small company rather than a venture-funded one. Development continues, with 2.x releases through 2026, but the pace and support depth reflect the size of the team. Buyers are industrial and IoT operators who want a stable, unopinionated broker without the feature bloat and licence churn of larger alternatives, and who can accept a narrow support bench.

What people use it for

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

The honest half

Where it falls short

Concrete and checkable, so you can decide whether any of them matter to you. This is the half of a review a vendor will not write about 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.

Cross-shopped

What people choose instead of VerneMQ

Each pairing was judged by two reviewers asking whether a buyer would genuinely weigh the two against each other. The ones that failed were deleted rather than published.

  • VerneMQ logo
    VerneMQ
    vs
    EMQX logo
    EMQX

    EMQX: If you need a rule engine, database bridging and a managed cloud and can accept BSL licence terms

  • VerneMQ logo
    VerneMQ
    vs
    RabbitMQ logo
    RabbitMQ

    RabbitMQ: If your messaging is not device-centric and you want AMQP plus MQTT in one broker

  • VerneMQ logo
    VerneMQ
    vs
    NATS logo
    NATS

    NATS: If you can choose the protocol and want a simpler operational model under Apache 2.0

Pricing

What VerneMQ costs

Taken from the vendor's own pricing page. Prices move, so check before you buy.

Source build

Free

  • Apache 2.0 licensed source from GitHub
  • Full clustering and plugin capability
  • You compile and package it yourself
  • Community support only

Binary packages and Docker images

On request

  • Covered by the VerneMQ EULA, not Apache 2.0
  • Yearly usage subscription expected for commercial use
  • Official builds and Docker images
  • Price not published, arranged with Octavo Labs

Commercial support

On request

  • Evaluation, customisation and operations assistance
  • Custom development
  • Long-term maintenance agreements
  • Quoted per engagement

Capabilities

Features

  • Erlang/OTP clustering

    Nodes join a cluster with shared subscription and session distribution

  • MQTT 5.0 support

    Full MQTT 5 including shared subscriptions and message expiry

  • Plugin system

    Hooks implemented in Erlang, Lua, Python, Java or via HTTP webhooks

  • Backpressure handling

    Per-session flow control that protects the broker under slow consumer load

  • Bridge support

    Broker to broker bridging including to other MQTT implementations

  • Metrics export

    Prometheus and Graphite metrics for cluster and session state

  • MQTT over WebSockets

    Browser clients connecting to the same broker

  • Pluggable auth backends

    Authentication and topic ACLs from files, databases or external services

Answered, with sources

Questions people ask

Each answer names the page it came from, so you can check it rather than take our word for it.

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.

Is the project still maintained?

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

Does it have a managed cloud?

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

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

Keep looking

Where to go from VerneMQ

Best Databases software for

Compare VerneMQ with

Other Databases software

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

    Free, then $234/mo12 researched notes
  • Open-source message broker supporting AMQP and other protocols

    Open source8 researched notes
  • High-performance messaging system for cloud-native applications

    Open source9 researched notes
  • JMS message broker underpinning bank and telecom estates, now maintained rather than expanded

    Pricing on request12 researched notes
  • Industrial process historian with published per-tag pricing and no client licence fees

    From $3,000/yr12 researched notes
  • Multi-protocol event broker sold as software, cloud service or a hardware appliance

    Free plan12 researched notes
  • Time-series database built on PostgreSQL for real-time analytics

    Free plan12 researched notes
  • Cloud-native messaging and streaming with separated storage

    Open source10 researched notes
  • The Meta-lineage distributed SQL query engine, distinct from the Trino fork

    Open source12 researched notes
  • Apache 2.0 MPP analytical database built for joins on open table formats

    Open source12 researched notes
  • Streaming SQL engine built on ClickHouse internals, shipping as one small binary

    Free, then $199/mo12 researched notes
  • The world's most advanced open source relational database

    Free plan11 researched notes
  • Apache 2.0 vector and full-text search engine that runs as an embedded library, a single server or a distributed cloud service.

    Free plan14 researched notes
  • Image and video API for developers

    Free, then $99/mo11 researched notes
  • Reactive backend combining a document database, TypeScript server functions and live queries, source-available under the Functional Source Licence.

    Free plan14 researched notes
  • Apache 2.0 distributed graph database written in Go, maintained by Hypermode, queried through GraphQL or its own DQL language.

    Free plan14 researched notes
  • High-performance Redis-compatible in-memory datastore with 25x better throughput

    Free plan10 researched notes
  • SQL query engine and lakehouse layer over Iceberg tables in object storage

    Free, then $0.2/hour12 researched notes

Softwr does not host reviews and shows no star rating for VerneMQ, because a rating we did not collect is not ours to publish. What is here is the pricing and platform detail from the vendor’s own pages, limitations we could state concretely, and alternatives a reviewer confirmed people weigh against it. Tell us if any of it is wrong.

More on VerneMQ

Best Databases software alternatives

Industrial process historian with published per-tag pricing and no client licence fees

Per tag band per year

NetApp-owned managed service for Cassandra, Kafka, OpenSearch, PostgreSQL and Cadence with a bring-your-own-cloud model

quote

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

Per month by connection and session volume

Attribute-based access control and masking applied inside Snowflake, Databricks and BigQuery

quote

MPP analytical database with a MySQL wire protocol and sub-second aggregation on wide tables

Open source, no licence fee

Streaming database that maintains incremental materialised views in SQL instead of Flink jobs

Per RisingWave Unit hour

Centralised data access governance from the creators of Apache Ranger, now rebranding as Trust3 AI

quote

The Meta-lineage distributed SQL query engine, distinct from the Trino fork

Open source, no licence fee

Compare VerneMQ with alternatives