Mercure
Mercure Hub is a Helm chart that deploys a Mercure server in Kubernetes to push reliable real-time updates to web browsers and other HTTP clients.
Platform availability
Available on 1 of 10 platforms
- Unraid (not listed)
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
76/100 Good
- Maintained
- 100last commit 17 days ago
- Popular
- 755,358 GitHub stars
- Easy to install
- 251 install platform, install notes
- Light to run
- No data
- Security check
- 81no serious findings, 2 minor, CI, tests, OpenSSF Scorecard 7/10
Based on 4 of 5 factors.
Availability: platform listings confirmed today
- GitHub stars
- 5,358
- Open issues
- 16
- Last commit
- 2026-11-04
- Latest release
- v1.1.6
- License
- AGPL-3.0
- Activity
- declining
Checked 14 days ago - source: GitHub (dunglas/mercure)
Resources & Compatibility
Requirements not published yet.
First-install notes
- Set hub key settings before start If you use RSA keys, set the publisher and subscriber public key files and RS256 (the JWT signing method) in the MERCURE_* variables before starting the hub. Without these settings, the hub cannot verify permission tokens and private updates will be rejected. source
- Create publisher/subscriber tokens Use caddy mercure-token to create permission tokens for publishers and subscribers; for the local quickstart, --dev is enough, while real hubs need the issuer, audience, key, and exact topic grants. Without the right tokens, clients cannot publish to or read the topics they are supposed to access. source
- Advertise the hub URL for discovery If your app supports Mercure discovery, add a Link header that points to the hub's /.well-known/mercure URL and marks it as the Mercure hub. This tells clients where the hub is; without it, automatic discovery may fail and clients will not know which hub to connect to. source
Fetched 40 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
What should I suspect first when Mercure returns 401 or 403 errors?
Most 401 and 403 issues are JWT-shaped.
Which values can be configured in the interactive Senate Docker deployment for Mercure?
You can configure the Mercure version, publisher JWT key, subscriber JWT key, and extra directives.
What support options are mentioned for self-hosted Mercure tiers?
Self-hosted tiers include direct email support from the maintainers, priority next-day support on Business, and full SLAs on Corporate and Elite.
Answers sourced from mercure.rocks, senate.sh
Community
Collected yesterday - public community threads