MQTT broker core
MQTT v3.1.1 support with QoS 0, 1, and 2, retained messages, last will, persistent sessions, and configurable message limits.
Distributed MQTT broker in Rust
YedMQ
Distributed MQTT broker in Rust with tenant isolation, cluster support, and flexible extensions.
Build tenant-aware IoT messaging services around the capabilities teams care about: MQTT v3.1.1, cluster support, and flexible extension points.
Project status: The source repository is still private. YedMQ remains under active development and is not yet recommended for production use.
MQTT v3.1.1Cluster supportTenant isolationFlexible extensions
What ships today
Protocol coverage
MQTT v3.1.1 with QoS 0, 1, and 2, retained messages, last will, and persistent sessions.
Scalable deployment
Run multiple nodes for higher availability and scale-out deployments.
Network listeners
TCP, TLS, WebSocket, WSS, and a REST management API for operations and integration.
Flexible extensions
Use plugins to adapt authentication, authorization, and message flows to your own business needs.
Capabilities aligned with the current codebase
The website now reflects what YedMQ currently implements instead of promising future functionality.
Cluster support
Deploy YedMQ across multiple nodes for scale-out scenarios and more resilient operations.
Tenant isolation
Clients, topics, retained messages, and management operations are scoped by tenant, with public as the default tenant.
Flexible plugin support
Use plugins to connect authentication, authorization, and custom message handling to your own business flows.
REST operations
Management endpoints cover plugins, clients, topics, retained messages, system info, and cluster workflows.
Pick the next document by task
Run a single node
Build YedMQ from source, create a config file, and verify the broker locally.
Plan cluster expansion
Review bootstrap and join modes, node metadata, and REST workflows for scaling out.
Build a plugin
Learn the plugin package layout, protocol handshake, and supported broker hook flows.
Explore the management API
Use the generated OpenAPI reference for endpoint parameters, request bodies, and responses.