Home›Catalog›⚙️ DevOps & Infrastructure›EMQX
Screenshot of EMQX website

// screenshot of emqx.com ↗

DEVOPS & INFRASTRUCTURE · PRO TIER

EMQXpro

EMQX is a distributed MQTT broker built in Erlang — millions of concurrent connections, MQTT 5.0 / MQTT 3.1.1 support, clustering, bridges to Kafka / Postgres / etc. The leading OSS MQTT broker for IoT, real-time messaging, edge computing.

Install via WHMCS → Visit emqx.com ↗
⚙️ DevOps & Infrastructure Min 1024 MB RAM Port 18083 (http) Tier pro
// What it is

A closer look.

EMQX is a distributed MQTT broker built in Erlang — millions of concurrent connections, MQTT 5.0 / MQTT 3.1.1 support, clustering, bridges to Kafka / Postgres / etc. The leading OSS MQTT broker for IoT, real-time messaging, edge computing.

For teams running anything from a smart-home server (a few thousand connections) to industrial IoT (millions), EMQX is the industry-standard choice.

// Use cases

What it's for.

Concrete scenarios where teams pick EMQX over the SaaS alternative.

◆

IoT messaging

device-to-cloud telemetry for sensors, smart-home, industrial

◈

Real-time pub/sub

chat, notifications, live updates at scale

◇

Vehicle telematics

connected car platforms

▣

Smart-home hub

central message broker for Home Assistant / OpenHAB

▦

Edge computing

local broker for offline-capable IoT

// Who it's for

Built for these teams.

If your team profile matches one of these, EMQX is a strong fit out of the box.

Profile A

IoT platform engineers

building device telemetry at scale

Profile B

Smart-home enthusiasts

running MQTT broker for Home Assistant / Node-RED

Profile C

Industrial IoT teams

managing thousands of factory sensors

Profile D

Real-time app builders

needing pub/sub message broker

Profile E

Embedded systems devs

developing MQTT-based device fleets

// Differentiators

Why teams pick EMQX.

When evaluating self-hosted options for this category, here are the dimensions on which EMQX consistently lands above the alternatives.

  • ✓Erlang concurrency — handles millions of connections on modest hardware
  • ✓MQTT 5.0 — latest spec with shared subscriptions, request/response
  • ✓Clustering — horizontal scale via clustering, no shared state required
  • ✓Apache 2.0 — fully open
  • ✓Built-in dashboard — admin UI for managing topics, clients, ACL
  • ✓Bridges — Kafka, RabbitMQ, Postgres, Redis bridges built-in
// Integrations

Connects to.

The stack you'll plug EMQX into — services, protocols, and adjacent apps in the BluixApps catalog.

◇
Protocols
MQTT 3.1.1 / 5.0, MQTT over WebSocket, CoAP, LwM2M, STOMP
◈
Auth
built-in users, LDAP, MySQL/Postgres, JWT, OAuth, custom HTTP
◆
ACL
topic-level access control via DB / file
▣
Bridges
Kafka, RabbitMQ, Postgres, Redis, MongoDB sink
▦
Webhooks
fire on client events (connect, disconnect, message)
▩
Prometheus metrics
built-in metrics endpoint
▼
REST API
programmatic broker management
// Adoption & deployment

Notable users & community

  • 14k+ GitHub stars
  • Used by HSBC, VW, Verifone, SAIC Motor for production IoT
  • Backed by EMQ Technologies (CN/SG) — sustainable open-core company
  • Featured in IoT platform architecture guides
  • Active community in MQTT / IoT space

What we ship

  • Docker compose: EMQX single-node (clustering documented for Enterprise tier)
  • Pinned emqx/emqx:5.8 (release-tagged)
  • HTTPS via Let's Encrypt; admin UI with random password
  • MQTT + MQTT-over-WebSocket + dashboard enabled
  • Persistent volume for retained messages + ACL
  • TLS configuration documented in install report
  • Backup hook covers config + retention data
// Tips & operations

Run it properly.

Operational guidance from running this in production — what to do before you scale, what to lock down, what surprises people.

// PERFORMANCE
Set retention policy
retained messages accumulate without expiry; configure cleanup
// SECURITY
Use clustering for HA
single-node broker = single point of failure for IoT platform
// OPERATIONS
Auth + ACL from day one
open broker = vulnerability; always require auth
// RELIABILITY
TLS for all client connections
MQTT supports TLS; never use plain MQTT in production
// DEPLOYMENT
Monitor connection counts
Prometheus metrics + alerts on connection spikes
// SCALING
Mind Erlang memory
EMQX is memory-hungry; size VPS accordingly for millions of connections
1024
// min ram (MB)
5
// min disk (GB)
18083
// access port
http
// protocol
pro
// bluixapps tier
1883:1883 · emqx/emqx:5.8
// docker image

Project resources

Official siteemqx.com ↗
// Alternatives in DevOps & Infrastructure

Compare with

DevOps & Infrastructure
Appsmith
Open page →
DevOps & Infrastructure
Budibase
Open page →
DevOps & Infrastructure
Cachet
Open page →