Side by side
Aedes vs Faye
Both stand on message broker software. Which one you can start free with, which one lets you read the code, and what each costs once you pay.
Free plan APISelf-hosted
Aedes offers core MQTT broker features, multiple connection types and a range of persistence options for self-hosted deployments. Its MQTT version limit and authorization behavior are important considerations for a project.
Visit Aedes Free plan Open source APILinuxMac+3
Faye provides protocol-based messaging, multiple transport options, and extension points, with documented engines for distributed deployments. Review its default access settings and browser connection limits when planning an application.
Visit FayeThe facts
| Aedes | Faye | |
|---|---|---|
| Free plan | Yes | Yes |
| Open source | Not published | Yes |
| Runs on | API, Self-hosted | API, Linux, Mac, Self-hosted, Web, Windows |
| Lowest paid plan | Free or on request | Free or on request |
| Plans published | 1 | 1 |
| Maker | Not published | Not published |
| Website | github.com | faye.jcoglan.com |
| On message broker software | #8 of 39 | #4 of 39 |
Aedes: what it does well
- Free under the MIT License
- Supports MQTT 3.1 and 3.1.1
- Offers TCP, SSL/TLS and WebSocket connections
- Persistence plugins cover several storage options
- Includes authentication and authorization support
What to know first
- MQTT 5.0 is not supported
- Clustering requires an on-disk database
- Revoked permissions do not invalidate already authorized messages
Faye: what it does well
- Supports Node.js and Ruby message servers
- Provides clients for major web browsers
- Offers WebSocket and HTTP-based transports
- Extensions can support subscription authentication
- Monitoring reports messaging and connection events
What to know first
- Default engine cannot span multiple front-end servers
- Browser clients need a Faye server for delivery
- Default access permits unrestricted publishing and subscribing
- Browsers impose per-host connection limits