Skip to the content
Know your tech before you buy it. Makers: get listed from $49/mo

Faye

faye.jcoglan.com

  • Free plan
  • Open source
  • Windows
  • macOS
  • Linux
  • Web
  • API
  • Self-hosted
8.3 Club score Visit faye.jcoglan.com

What Faye is

Faye is a publish-subscribe messaging system based on the Bayeux protocol. It provides message servers for Node.js and Ruby, as well as clients for servers and major web browsers. Browser clients need a Faye server to relay messages, and can retry after a lost connection and redeliver messages that were dropped. Transport adapters support WebSocket, HTTP long-polling, Cross Origin Resource Sharing, and JSON-P callback-polling. The default in-process engine cannot run one Faye service across multiple front-end web servers; Redis and Couchbase engines are documented for distributed deployments. Server and client extensions can intercept or change messages, including to implement subscription authentication. The monitoring API reports handshakes, subscriptions, unsubscriptions, publishes, and disconnections. Faye is free under the Apache 2.0 license. Node.js installation uses npm, while Ruby installation uses RubyGems. The documentation advises using one browser client per target server because of per-host connection limits. It also notes that cross-domain access and unrestricted publishing and subscribing are enabled by default, and recommends application-specific restrictions and HTTPS.

Who it suits

Faye suits developers building publish-subscribe messaging into Node.js or Ruby services and browser clients. Teams deploying across multiple front-end servers should consider its documented Redis or Couchbase engines.

Good to know, and what to watch

  • Supports Bayeux messaging
  • Offers Node.js and Ruby servers
  • Browser client can retry and redeliver dropped messages
  • Extensions can support subscription authentication
  • Monitoring API reports messaging events
  • Default engine cannot span multiple front-end servers
  • Cross-domain access and unrestricted publishing are default
  • Browsers impose per-host connection limits

Faye

Free

Open source

Getting started

  1. Install the Node.js server through npm or the Ruby server through RubyGems
  2. Deploy Faye on Linux, macOS or Windows, or self-host it
  3. Run a Faye server for browser clients
  4. Connect clients using a supported transport
  5. Add server or client extensions for message handling or subscription authentication
  6. Apply application-appropriate access restrictions and use HTTPS

Limits to check

Its default in-process engine cannot serve one Faye service across multiple front-end web servers, and browser clients face per-host connection limits.

The verdict

Faye provides server and browser clients with several transport options and documented paths for distributed deployments. Add application-appropriate access restrictions and use HTTPS to protect messages.

Questions people ask

Is Faye free and open source?

Yes. The listed Faye plan is free, and the software uses the Apache 2.0 license.

Which languages and platforms are supported?

Faye provides servers for Node.js and Ruby and runs on Linux, macOS and Windows. It also offers server and browser clients and supports self-hosting.

How do I install Faye?

The download instructions provide npm installation for Node.js and RubyGems installation for Ruby.

Can Faye run across multiple front-end servers?

The default in-process engine cannot. Redis and Couchbase engines are documented for distributed deployments.

What transports does Faye support?

Its adapters support WebSocket, HTTP long-polling, Cross Origin Resource Sharing and JSON-P callback-polling.

Are publishing and subscribing restricted by default?

No. Cross-domain access and unrestricted publishing and subscribing are enabled by default, so the documentation advises adding application-appropriate restrictions.

What the maker publishes

Additional backends
The engine documentation lists separate faye-redis, faye-redis-sharded and faye-couchbase backends. source
Browser connection model
Browser documentation recommends one Faye client per target server because browsers limit connections per host. source
Browser requirement
Browser clients require a Faye server to handle message delivery between clients. source
Channel subscriptions
Subscriptions support wildcard channel patterns and return cancellable subscription promises. source
Client recovery
The browser client periodically retries after a lost connection and can redeliver dropped messages. source
Client support
Clients can run on servers and in major web browsers. source
Clustering tradeoff
Redis-backed clustering enables scaling across front ends but adds external I/O and is slower than in-process storage. source
Credential handling
The security guide says server extensions should remove authorization credentials before messages are forwarded to subscribers. source
Cross-domain support
Faye clients and servers support cross-domain communication without extra configuration. source
Extensibility
User-written client and server extensions can intercept, modify or reject messages. source
Extensions
Server and client extensions can intercept and modify incoming or outgoing messages, including to implement subscription authentication. source
Independent activity limit
Ruby Toolbox rates faye-websocket 0.88 and flags low commit activity and no release in over a year. source
Independent maintenance limit
Snyk's analyzed snapshot labels maintenance inactive, with no commits in six months, 19 open issues, four open pull requests and one maintainer. source
Independent popularity
Snyk reports about 1.7 million weekly npm downloads and roughly 4,385 GitHub stars for Faye. source
Independent repository scale
GitHub shows the Faye organization repository with about 4.4k stars and 367 forks, plus separate Ruby and Node WebSocket repositories. source
Independent security status
Snyk reports no known security issues for the package version it analyzed, while recording four historical vulnerabilities in older versions. source
Integrations
The download instructions provide installation through npm for Node.js and RubyGems for Ruby. source
Latest release
The download page lists version 1.4.3, released 27 September 2026. source
License
Faye is open-source software released under the Apache 2.0 license. source
License and release
The site lists version 1.4.2, released 14 September 2026, under the Apache 2.0 license. source
Limit: complexity and state
The same Stack Overflow discussion describes Faye as more complex than Juggernaut and notes that its then-current state was held in memory. source
Limit: historical TLS vulnerability
A Singapore government SingCERT bulletin says older faye-websocket and Faye Ruby clients lacked TLS certificate validation, with fixes released in faye-websocket 0.11.0 and Faye 1.4.0. source
Limit: scope
A separate Stack Overflow discussion characterizes Faye as a web pub-sub layer rather than a general Redis-style storage system. source
Maker
The site credits James Coglan as Faye’s maker. source

Checked against the maker's pages on 15 Oct 2026.