Faye

Faye is a self-hosted messaging system for applications that use publish-subscribe communication. It suits teams building in Node.js or Ruby who want control over browser message delivery; teams needing managed hosting or a default multi-server service should look elsewhere.

Its transport choices and extension points offer useful flexibility, but secure access and distributed deployment require deliberate configuration.

Overview

Faye uses the Bayeux protocol and provides servers for Node.js and Ruby, plus clients for servers and major browsers. Browser clients depend on a Faye server to relay messages, so Faye is a component to operate within an application rather than a hosted messaging service. Delivery guarantees are configurable, giving teams control over delivery behavior without making this a turnkey messaging platform.

Adapters support WebSocket, HTTP long-polling, Cross Origin Resource Sharing, and JSON-P callback-polling. That range gives applications alternatives when a preferred transport is unsuitable. After a connection drops, the browser client retries periodically and can redeliver dropped messages, which helps recover from interruptions but does not remove the need to account for delivery behavior in the application.

Key features

• Server and client extensions: Extensions can intercept and modify messages as they enter or leave either side. They can implement subscription authentication, useful for application-specific controls, but access restrictions still need to be designed for the deployment.
• Distributed engines: The default in-process engine cannot serve one Faye service across multiple front-end web servers. Redis and Couchbase engines are documented for distributed deployments, giving teams a path beyond the default while adding infrastructure choices to manage.
• Monitoring API: It can report handshakes, subscriptions, unsubscriptions, publishes, and disconnections. Those events help operators observe messaging activity, though they do not replace application-level monitoring.
• Browser connection planning: Browsers limit connections per host, so Faye advises creating one client per target server. Applications that open many clients to the same server need to account for that constraint.

Pricing

Faye is free open-source software. The Faye plan costs nothing and uses the Apache 2.0 license. It is self-hosted, so teams run the service themselves rather than selecting a hosted tier; the license and price make it suitable when owning deployment and operations is acceptable.

Platforms

Faye supports Linux, macOS, Windows, web, and self-hosted deployment. Its server implementations target Node.js and Ruby, with npm and RubyGems installation paths. Browser support is client-based and requires a Faye server for message delivery.

Who it's for

Faye is a good fit for developers who want Bayeux-based messaging inside an application, especially teams already using Node.js or Ruby and prepared to operate their own server. It is less suitable for teams seeking managed hosting, automatic multi-front-end scaling from the default engine, or messaging that is secure by default: cross-domain access and publishing and subscribing are unrestricted unless the application adds appropriate restrictions.

For transport security, the security guidance recommends HTTPS to protect messages and the HTTP transport from eavesdroppers. That makes deployment configuration part of the security work, not an optional refinement.

Pros and cons

• Pros: Multiple transport adapters, retry and redelivery behavior, and modifiable client and server messages give application teams practical control over delivery and integration.
• Pros: Documented Redis and Couchbase engines provide options for distributed deployments beyond the in-process default.
• Cons: Unrestricted access by default means teams must add application-appropriate publishing, subscription, and cross-domain controls.
• Cons: The default engine cannot run a service across multiple front-end servers, and browser per-host connection limits affect client design.

Alternatives

Message Broker Software is a useful starting point for comparing products across the broader broker category.

• Lightstreamer is worth considering when a freemium option with a demo license capped at 20 concurrent client connections and a free trial better matches evaluation needs.
• EMQX may suit teams looking for a freemium option with a serverless plan and a monthly free quota, with usage-based charges beyond that quota.
• TIBCO FTL is an alternative for readers considering a paid product that also offers a free Community Edition download.
• Apache Artemis is another free, self-hosted broker under Apache License 2.0, with Java 17 or later required.
• Apache RocketMQ is another free open-source option under Apache License 2.0.
• Eclipse Mosquitto is a free on-premises option for teams seeking core MQTT features.
• HiveMQ MQTT Broker is an alternative for readers comparing a freemium MQTT broker with a Lab plan capped at 100 connections and 100 messages per second.
• IronMQ may fit teams wanting a freemium option with a Basic plan that includes 100K API requests per month on a public cluster, with reduced redundancy and limited rates and queues.

Verdict

Choose Faye if you want a free, self-hosted Bayeux messaging system with several transports and extension hooks, and your team can manage security and deployment. Look elsewhere if you need managed service or a default engine that spans multiple front-end servers.