ntfy vs Synapse (Matrix Homeserver)
| Tagline | Simple HTTP-based push notifications to phone and desktop, no account needed | Reference Matrix homeserver powering decentralized, federated team chat |
| Category | Team Chat & Collaboration | Team Chat & Collaboration |
| Replaces | Slack, Microsoft Teams | Slack, Microsoft Teams, Discord |
| GitHub stars | 32k | 4.5k |
| Language | Go | Python |
| License | Apache-2.0 | AGPL-3.0 |
| Self-host difficulty | 2/5 Easy | 4/5 Involved |
| Deploy options | Docker Docker Compose Manual | Docker Docker Compose Kubernetes Manual |
| Managed hosting | ||
| Last updated | 4 days ago | 2 days ago |
| View repo | View repo |
Where each falls short
The honest trade-offs — what you give up with each, versus the proprietary tools they replace.
ntfy
- No team chat, threading, or message history browsing; designed for one-way push alerts only.
- No rich message formatting, file sharing, or reactions.
- Rate limiting and attachment storage on the free public server are intentionally restrictive.
- iOS push requires routing through ntfy's own APNs proxy unless you self-compile the app.
Synapse (Matrix Homeserver)
- It is a backend only; you must pair it with a client (Element) for a usable product
- Federation and database (PostgreSQL) tuning is required for scale and can be resource-intensive
- Setup involves reverse proxy, TLS, well-known config, and federation ports
- AGPL license and commercial relicensing have caused community friction
Bottom line
Choose ntfy if you want the lower-effort setup; choose ntfy for the larger community and ecosystem. Synapse (Matrix Homeserver) has seen more recent development. Open each guide below for deploy steps and the full feature gap.
Synapse (Matrix Homeserver)
Reference Matrix homeserver powering decentralized, federated team chat