Suggestions appear as you type. Use the up and down arrows to choose one and Enter to open it.

This page's audience our own tag's counts — open to see them
–Visits
–Page views
–Clicks to vendors
–Time on page
–Reading now
Clicks to vendors, by tool
  • –
Top countries
  • –
Devices
  • –

– · visits, page views and clicks counted by our own tag, which counts more than our checked analytics; every figure rounded down · how we count

Aedes review

Free#28 of 39 in Message Broker Software

A flexible self-hosted MQTT broker for developers building Node.js messaging systems.

6.5/10Editor score
Aedes6.5 Visit Aedes

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

Aedes is an open-source MQTT broker implemented as a Node.js module. It is intended for developers building embedded, self-hosted MQTT messaging systems and IoT backends. The broker can run on stream servers, inside a Node.js application, or through server and Docker configurations. Its protocol coverage includes MQTT 3.1, MQTT 3.1.1, TCP, TLS, WebSocket, and Bridge Protocol support, giving teams several ways to connect clients and route messages.

The main strength is its combination of broker features and Node.js extensibility. Aedes provides message persistence, offline message buffering, authentication and authorization hooks, clustering, high availability, MQTT bridging, and a programmatic API. Its persistence, emitter, and middleware components are pluggable, while MongoDB, Redis, LevelDB, and NeDB are listed as storage integrations. This makes it suitable for teams that want to shape broker behavior within an application rather than adopt a fixed, separately operated service.

Aedes follows an open-source, self-hosted model, so teams choose and manage their deployment configuration. Delivery guarantees are configurable, and clustering and high availability are available when the surrounding architecture is designed to support them. That flexibility will appeal to Node.js developers who need embedded MQTT capabilities, custom hooks, and selectable persistence options. Teams looking for a managed broker experience or a broader messaging platform should consider alternatives with those operating models or wider protocol coverage.

Aedes pros and cons

  • Where it wins
    • Supports MQTT 3.1 and 3.1.1 over TCP, TLS, and WebSockets
    • Includes persistence, offline buffering, clustering, and high availability
    • Pluggable components with MongoDB, Redis, LevelDB, and NeDB integrations
  • Where it doesn't
    • Requires self-hosted deployment and operational responsibility
    • Focused on MQTT messaging rather than a broad protocol portfolio
    • Configuration is needed for delivery guarantees and high availability

Aedes fact sheet, pricing and score →

Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.

Last updated · How we research and update