# vernemq/vernemq

A distributed MQTT message broker based on Erlang/OTP. Built for high quality & Industrial use cases. The VerneMQ mission is active & the project maintained. Thank you for your support!

Repository: https://github.com/vernemq/vernemq
Canonical: https://ross.abutalabs.com/products/vernemq
Homepage: https://vernemq.com
Language: Erlang
License: Apache-2.0
License Family: permissive
Topics: mqtt, m2m, scalable, broker, erlang, distributed, messaging, pubsub, vernemq, iot-middleware, iot, vernemq-users, vernemq-documentation, industrial-iot, industrial-communication, industrial-automation, industry-40, message-queue, manufacturing
Last push: 2026-08-18T20:08:38+00:00

## Health v2 (maintenance only)
Score: 86/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 98, release rhythm 64, longevity 100
- inputs: {"age_days": 4116, "days_push": 15, "days_rel": 24, "gap_med": 237.0, "n_releases_24m": 3}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 3624, forks 429 (observed 2026-08-28T04:08:11.919466+00:00)

## What it is
VerneMQ is a high-performance, distributed MQTT message broker built on Erlang/OTP with master-less clustering for horizontal scalability and fault tolerance. It targets IoT platforms, smart products, and mobile messaging with support for MQTT 5, websockets, plugins, and enterprise-grade operations.

## Use cases
- run a scalable mqtt broker for iot devices
- connect millions of concurrent mqtt clients
- cluster mqtt brokers for high availability
- mobile push messaging with pub/sub
- industrial iot middleware for manufacturing
- bridge mqtt between sites
- monitor and control field devices over mqtt

## When to choose
- you need a battle-tested, horizontally scalable MQTT broker with master-less clustering
- you need MQTT 5, websockets, shared subscriptions, and plugin extensibility (Lua, Erlang, webhooks)
- you run industrial or telecom-grade workloads requiring continuous operation and fault tolerance

## When to avoid
- you need a lightweight single-node broker for a small hobby project
- your team cannot operate Erlang-based systems or prefers brokers in more common languages
- you need Kafka-style persistent log/streaming semantics rather than MQTT pub/sub

## Facets
- artifact type: service
- maturity: stable
- function: message-queue, websocket, auth, monitoring, plugin-system, http-server
- domain: iot, microservices, backend
- platform: self-hosted, cross-platform
- tags: mqtt-broker, pubsub, erlang-otp, clustering, iot-middleware, mqtt5, industrial-iot, messaging, real-time, linux, docker, kubernetes

## Member repositories
- vernemq/vernemq (main) score 86

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:08:11.919466+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-29T18:31:56.573604+00:00, confidence not recorded.
  - readme: https://github.com/vernemq/vernemq (fetched 2026-08-28T04:08:11.919466+00:00, sha 5edd4f46c1f0)
  - homepage: https://vernemq.com (fetched 2026-08-29T09:26:32.316401+00:00, sha 1e0c0d44bca5)
  - site_page: https://docs.vernemq.com (fetched 2026-08-29T09:26:32.326336+00:00, sha f4019c9a6099)
  - site_page: https://vernemq.com/intro/index.html (fetched 2026-08-29T09:26:32.328026+00:00, sha 203e033ff8b8)
- Data as of 2026-08-30T08:39:29.467469+00:00.