Buzz

MQTT 5 broker with REST and browser-native WebSocket

A standalone MQTT 5 appliance with dynamic user management via REST, native browser WebSocket access, and async database recording.

Try live demo REST API docs Pricing

Docker container
Kubernetes Helm chart
8 database engines
2 queue backends
3 auth methods
8 notification drivers
2 cache engines
4 languages (EN, FR, ES, PT)
REST API + OpenAPI 3.0.3
Realtime WebSocket channels

Buzz eliminates password files and reboots by offering REST-driven credential management for IoT devices. Native MQTT over WebSocket lets browser clients connect directly without a bridge. SQL and NoSQL backends persist traffic alongside your application data. Sensors, mobile apps, and real-time dashboards — Buzz handles TCP, TLS, and WebSocket with MQTT v5 compliance and an operational dashboard.

What it does

Key features

Full MQTT v5 compliance across TCP, TLS, WebSocket, and WSS

Dynamic user management via REST — add/revoke credentials without restarts

Native browser MQTT over WebSocket using the standard subprotocol

Async message recording to SQL (SQLite, Postgres, MySQL, MSSQL) or NoSQL (Redis, Mongo, Elasticsearch)

JWT auth for dashboard and MQTT clients, HMAC for service-to-service

REST publish endpoint for server-side HTTP clients

User banning with optional expiry

Svelte 5 / Tailwind 4 multilingual dashboard (en, fr, es, pt)

Cross-protocol routing — MQTT, WebSocket, and HTTP clients interchange seamlessly

Why it's different

Where it goes beyond the obvious

Native MQTT over WebSocket without a separate bridge service

Dynamic credential management at runtime with no password files or restarts

Unified broker for IoT sensors, browser clients, and HTTP producers

Tech highlights

MQTT v5 (mochi-mqtt) — Paho Interoperability compliant
Transports: TCP :1883, TLS :8883, WS :1882, WSS optional
Backends: SQLite, Postgres, MySQL, MSSQL, Redis, Mongo, Elasticsearch
JWT + HMAC authentication
Svelte 5 + Tailwind 4 dashboard

Built on

mochi-mqtt v2 (MQTT 5)GinGORMCentrifugeAtlas migrations

REST API surface

POST /auth/login JWT token via API key
GET /v1/runtime Connections, memory, traffic
GET /v1/channels List every MQTT topic
POST /v1/channels/publish/{topic} Publish over REST
GET /v1/channels/history/{topic} Recorded messages
POST /v1/users Create an MQTT user at runtime
PUT /v1/users/{username} Rotate password or ban

Full spec at GET /openapi — Swagger UI at /swagger/

Your infrastructure

Backends you can actually pick from.

This service speaks the backends below natively. Swap with a single environment variable.

Databases

SQLite
PostgreSQL
MySQL
SQL Server
MongoDB
Elasticsearch
DynamoDB
Cassandra

Queues

Redis
Valkey

Cache

Redis
Valkey

Notifications

Slack
Discord
Teams
SNS
FCM
APNs
WebPush
Webhooks

Auth

JWT HS256/RS256
LDAP
HMAC

Where it fits

Use cases

IoT and sensor networks needing dynamic device provisioning

Real-time web dashboards requiring browser WebSocket to sensor data

Home automation integrating MQTT devices with web frontends

Message recording and audit trails for compliance-heavy apps

Multi-protocol messaging where HTTP, MQTT and browsers coexist

vs Managed MQTT brokers

Buzz vs AWS IoT Core, HiveMQ Cloud, Mosquitto (OSS)

MQTT, without the Mosquitto cliffs or the per-message invoice

Compare head-to-head

Patterns

Architecture patterns featuring this service

Real-time for IoT and browsers in one broker

Sensors on MQTT, browsers on WebSocket, servers on REST — one Buzz broker handles all three and records every message.

Same family

More in messaging

Switchboard

Messaging

A unified gateway fronting Centrifugo with REST publish/subscribe, message recording, and operational dashboards.

Proxy pass-through for Centrifugo HTTP andShared-secret RESTAsynchronous message recording to Postgres

Ready when you are

Deploy Buzz. Today.

One Docker image. One compose stack. One afternoon to production. Buzz is waiting.

See pricing Browse more services