compare
Mercure vs Sockudo
The same facts for both, read from GitHub every night, and the relation a person reviewed.
| Fact | Mercure | Sockudo |
|---|---|---|
| Language | Go | Rust |
| Licence | AGPL-3.0 | MIT |
| Stars | 5.3k | 819 |
| Latest | v1.0.4 | v5.1.0 |
| Last push | 2026-10-06 | 2026-10-06 |
| Release cadence | about 8 days between releases | about 26 days between releases |
| Active contributors | 5 commit authors on the default branch in the last 90 days | 12 commit authors on the default branch in the last 90 days |
| Flags | none | none |
How they relate
Both replace Pusher Channels. Alternatives to Pusher Channels →
PartialMercureA hub that pushes updates your backend publishes to browsers over Server-Sent Events; no client-to-client messages.
Drop-inSockudoSpeaks the Pusher Channels protocol, so existing Pusher client and server SDKs connect to it.
Mercure
- v1.0.42026-10-05Mercure 1.0.4 fixes a memory regression in 1.0.3. Since Caddy 2.11.7, encode compresses Server-Sent Events responses, a…
- v1.0.32026-10-03Mercure 1.0.3 moves the hub to Caddy 2.11.7, which brings the security fixes and hardening of Caddy 2.11.6: slowloris m…
- v1.0.22026-09-25Mercure 1.0.2 is a security release. After initial reports from Pascal Borreli (@pborreli), Tilia.coop did a full audit…
- v1.0.02026-09-16Mercure 1.0 is final. When the protocol was drafted in 2018, the web standards covering its needs did not exist, so Mer…
- v1.0.0-beta.12026-09-14Mercure 1.0 beta 1. The 1.0 protocol is settling. Since alpha 3 the subscription endpoint now enforces the HTTP semanti…pre-release
Mercure
unsigned The latest release, v1.0.4, carries no signature GitHub could verify.
Loading the security report
Sockudo
unsigned The latest release, v5.1.0, carries no signature GitHub could verify.
Loading the security report