ntfy vs Slack
Thinking of swapping Slack for the open-source ntfy? Here’s the honest trade-off.
31k Go Apache-2.0 3 days ago
What you give up vs Slack
- 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.
What you gain
- • Full data ownership — self-host ntfy on your own infrastructure.
- • No per-seat SaaS bill (Slack: per-seat pricing and a capped message history).
- • Open-source code you can audit and extend (Apache-2.0).