VerneMQ
At #4 of 13 in our message queue software ranking, VerneMQ is summed up in the catalogue as: MQTT broker on Erlang, clustered, sold as a subscription for production.
On this site vendors can buy visibility, and we say so. Outbound links, including the one to VerneMQ, are marked identically. Read more.
Visit VerneMQ See it in the message queue software ranking
At a glance
| Headquarters | Switzerland |
|---|---|
| Deployment | Unclear from the vendor pages |
| API | VerneMQ mentions an API in the material we reviewed |
| Free plan | No free plan recorded |
| Pricing model | Subscription for production binaries, amounts not listed; binaries tested without charge |
| Best for | Device fleets needing a clustered MQTT broker from a small Swiss maker |
What is VerneMQ?
VerneMQ is a distributed MQTT broker built on Erlang OTP. Its home page says it scales horizontally and vertically on commodity hardware, and that clustering gives high availability, automatic conflict resolution and recovery from netsplits, with the operator tuning the balance between availability and consistency.
The company behind it is Octavo Labs AG, whose address is given as Badenerstrasse 13, 5200 Brugg, Switzerland, with a commercial register number in the Canton of Aarau. The home page calls the software open source without naming the licence, while the downloads page offers subscription-based binaries under an end user licence agreement. The binaries are free to test, and a paid subscription is required for production use. No subscription prices are published.
VerneMQ key features
- Clustered MQTT broker. Nodes form a cluster for availability and scale. The home page mentions automatic conflict resolution and recovery from netsplits, which are the failure cases that matter most when a broker spans several machines.
- Tunable consistency. The operator can adjust the balance between availability and consistency. The pages state the option exists but do not describe the settings, so the practical range has to be read in the documentation.
- Built on Erlang OTP. The broker runs on the Erlang OTP platform and is described as horizontally and vertically scalable on commodity hardware. That is the vendor's account of the design; the pages give no benchmark figures.
- Lua scripting engine. A Lua scripting engine ships with database drivers for PostgreSQL, MySQL, MongoDB, Redis and Memcached. Authentication and hooks can therefore consult a database without a separate plugin written in another language.
- Plugins and webhooks. Webhooks allow custom plugins written in any language, alongside CLI tools and integration APIs. A team can wire VerneMQ to existing services over HTTP rather than compile code into the broker.
- File-based authentication. Built-in file-based authentication and authorisation are listed. They suit small setups, while the Lua engine and plugins are the routes for database-backed or external identity checks.
- Enterprise support. The home page states that enterprise support is available. It gives no response times or support tiers, so those would be settled in the subscription conversation.
Who VerneMQ suits
- A platform team running its own MQTT fleet. Because VerneMQ is software the buyer runs itself, a team that already operates Linux or Docker can place brokers where it likes. Stable packages are offered for several Debian, Ubuntu, Rocky and Amazon Linux versions.
- An IoT backend needing database-aware authentication. The Lua engine with PostgreSQL, MySQL, MongoDB, Redis and Memcached drivers lets device credentials live in a database the team already runs, without extra middleware.
- A Swiss or EU-minded buyer wanting a named vendor. Octavo Labs AG is named with a Swiss address and register number on the home page, so the contracting party is visible before any call.
Getting started with VerneMQ
The documentation site links a Getting Started guide and the downloads page as its entry points for installing VerneMQ. The downloads page lists stable binary packages, version 1.13.0, for Amazon Linux 2, Ubuntu Bionic, Focal and Jammy, Debian Bullseye and Buster, Rocky Linux 8 and 9, and openSUSE 42.3, plus Docker images on Docker Hub.
It also describes building from source through Git with make rel. The binaries are free to test. We did not read the Getting Started guide itself, so the first configuration steps are not described here.
The case for and against VerneMQ
- VerneMQ comes from Octavo Labs AG in Brugg, Switzerland, and is a distributed MQTT broker built on Erlang OTP.
- VerneMQ is tagged Erlang OTP in our records.
- VerneMQ is tagged Clustering in our records.
- Strongest for: Device fleets needing a clustered MQTT broker from a small Swiss maker.
- Marked in our records as MQTT.
- The home page calls the software open source without naming a licence, while the binaries sit under an end user licence agreement.
- Poor match for: Application teams who need queues with JMS or AMQP semantics.
- The downloads page requires a paid subscription for production use but lists no price, currency or billing period.
What we make of VerneMQ
VerneMQ comes from Octavo Labs AG in Brugg, Switzerland, and is a distributed MQTT broker built on Erlang OTP. It clusters with automatic recovery from netsplits and adds Lua scripting and webhooks.
The downloads page says binaries fall under an end user licence, are free to test, and need a paid subscription in production, with no price shown. It speaks MQTT, so it suits devices more than business queues.
The message queue software list places VerneMQ 4 of 13: it follows KubeMQ and comes before HiveMQ. Established names take the places after the first three, in ranked order, and we give no numeric score.
By headquarters, 3 of the 13 are established in Europe, as VerneMQ is in Switzerland.
VerneMQ pros and cons in practice
- The company, address and register number are named on the home page.
- Binaries can be tested without charge before a subscription is needed.
- Lua drivers cover five databases, and webhooks accept plugins in any language.
- Packages exist for several Linux distributions as well as Docker images.
- Subscription prices are not listed, so budgeting needs a conversation with the vendor.
- The home page calls the software open source without naming the licence, while binaries sit under an end user licence agreement.
- No managed or hosted service is named, so operations are the buyer's job.
- Listed stable packages cover version 1.13.0, and some listed operating systems are older releases such as openSUSE 42.3.
Living with VerneMQ: setup and exit
The home page lists CLI tools, integration APIs, file-based authentication and authorisation, and a Lua engine with drivers for PostgreSQL, MySQL, MongoDB, Redis and Memcached.
Stable packages at version 1.13.0 cover Amazon Linux 2, Ubuntu, Debian, Rocky Linux and openSUSE, plus Docker images.
The buyer runs it personally: the home page describes no managed service.
Enterprise support is offered, and the customers named include Microsoft, Volkswagen and Arduino.
VerneMQ pricing
Charging model: Subscription for production binaries, amounts not listed; binaries tested without charge.
The downloads page offers subscription-based binary packages and Docker images and says the binaries are subject to the VerneMQ end user licence agreement. They are free to test, and a paid subscription is required for production use. The page lists no subscription prices, currency or billing period, so the cost is known only after contacting the vendor. Building from source through Git is described separately as open source. Enterprise support is mentioned on the home page without terms. We saw no hosted or managed service named anywhere, so infrastructure costs fall on the buyer.
Source: the pricing material on vernemq.com, as read for Best Message Queue Software in 2026 and last reviewed on 15 November 2026.
VerneMQ: data and security
VerneMQ is software the buyer runs itself, so messages and device data stay on the buyer's infrastructure and the buyer controls their location. The home page lists built-in file-based authentication and authorisation, with Lua and webhook plugins for external checks.
The pages we read name no certification such as ISO 27001 or SOC 2 and no TLS option list. The company is Octavo Labs AG in Switzerland, with a commercial register number given on the home page.
VerneMQ fact sheet
| Product | VerneMQ |
|---|---|
| Vendor website | vernemq.com |
| Catalogue tags | MQTT, Erlang OTP, Clustering |
| Not in our data | user counts and financial results |
| Alternatives page | Not written yet |
| Price visibility | Model recorded, no figure |
| Rank there | #4 of 13 |
| Primary guide | Best Message Queue Software in 2026 |
| Head-to-head pages | Not paired so far |
| Headquarters | Switzerland (Europe) |
Integrations and ecosystem
Integrations the vendor names (12):
- PostgreSQL
- MySQL
- MongoDB
- Redis
- Memcached
- Docker Hub
- Webhooks
- Lua scripts
- Amazon Linux 2
- Ubuntu
- Debian
- Rocky Linux
Also in our records:
- The home page lists CLI tools, integration APIs, file-based authentication and authorisation, and a Lua engine with drivers for PostgreSQL, MySQL, MongoDB, Redis and Memcached.
Close alternatives to VerneMQ
We pick the closest products in the same guide by tags, price model and region.
- KubeMQ (#3 of 13): Broker that presents Kafka clients with a different engine underneath. Watch out: prices appear only through a quote, and infrastructure costs come on top of the licence.
- EMQX (#6 of 13): Suits: IoT and connected-vehicle teams wanting a hosted MQTT broker to start small. (United States)
- Eclipse Mosquitto (#7 of 13): Light MQTT broker from the Eclipse Foundation, for small boards and servers. Watch out: support and business features are sold separately by Cedalo, so the broker alone comes with no vendor service.
- NSQ (#8 of 13): Distributed messaging platform with no central broker, written in Go. Watch out: a crashed node can lose queued messages, since durability is not the default setting.
- Apache RocketMQ (#10 of 13): Aimed at: Java teams wanting ordered messaging they run and tune themselves. (United States)
Also ranked in
| Guide | Position |
|---|---|
| Best Message Queue Software in 2026 | #4 of 13 |
VerneMQ: questions
9 answersWhat does VerneMQ cost?
Our catalogue records VerneMQ’s pricing as: Subscription for production binaries, amounts not listed; binaries tested without charge. On free access, no free tier or free plan is recorded.
Who is VerneMQ best for?
Device fleets needing a clustered MQTT broker from a small Swiss maker. Less suited to: application teams who need queues with JMS or AMQP semantics.
Which country is VerneMQ from?
VerneMQ contracts from Switzerland, so it sits in Europe in our grouping. Headquarters and hosting region are separate questions; this answers the first.
What else should I look at besides VerneMQ?
The closest products in the same guide are KubeMQ, EMQX, Eclipse Mosquitto, NSQ and Apache RocketMQ. They are ranked and described in the same list.
How does VerneMQ rank for message queue software?
VerneMQ is #4 of 13 in our message queue software ranking.
Can I use VerneMQ in production without paying?
The downloads page says binaries are free to test and that a paid subscription is required for production use. Building from source is described separately.
What does a subscription cost?
The pages we read list no prices, currency or billing period.
Is there a hosted VerneMQ?
The home page describes software the buyer runs itself and names no managed service.
Who makes VerneMQ?
Octavo Labs AG, Badenerstrasse 13, 5200 Brugg, Switzerland, according to the home page.
VerneMQ: sources
Read from the vendor’s own pages on 14 November 2026.
- vernemq.com: Architecture, features, company details, support and hosting model
- vernemq.com/downloads/index.html: Binaries, licence terms, subscription requirement, packages and source build
- docs.vernemq.com: Getting Started guide and downloads as entry points
How we rank
The same four questions are asked of every message queue software product: time to value, real cost, the way out and the intended buyer. That puts VerneMQ at #4 of 13. Method and commercial relationships are in our editorial process.