Dendrite vs ntfy
| Tagline | Second-generation Matrix homeserver by the Matrix.org Foundation | Simple HTTP-based push notifications to phone and desktop, no account needed |
| Category | Team Chat & Collaboration | Team Chat & Collaboration |
| Replaces | Slack, Discord, Microsoft Teams | Slack, Microsoft Teams |
| GitHub stars | 5.4k | 31k |
| Language | Go | Go |
| License | Apache-2.0 | Apache-2.0 |
| Self-host difficulty | 3/5 Moderate | 2/5 Easy |
| Deploy options | Docker Docker Compose Manual | Docker Docker Compose Manual |
| Managed hosting | ||
| Last updated | 1 month ago | 6 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.
Dendrite
- Still behind Synapse in feature completeness for some advanced room types
- Performance at scale is less battle-tested than Synapse
- Web client (Element) must be deployed separately
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.
Bottom line
Choose ntfy if you want the lower-effort setup; choose ntfy for the larger community and ecosystem. ntfy has seen more recent development. Open each guide below for deploy steps and the full feature gap.