IdeaSift

Self-hosters miss urgent alerts or get flooded with noisy ones

People running self-hosted services and small infrastructure setups can miss urgent events when notifications arrive as ordinary messages, and carrier email-to-SMS gateways may drop them. They also want alerts that are easier to understand and controls for templates, planned maintenance, and dependent monitors. Today’s workarounds span chat apps, mail systems, scripts, and manual configuration rather than one dependable alert path.

For self-hosters and small infrastructure operators. Mentioned from Sep 2021 to Aug 2026 on Bluesky, GitHub, Hacker News and Stack Exchange.

13 different people described this problem in 10 separate discussions.

Week of 2026-07-13: 0Week of 2026-07-20: 0Week of 2026-07-27: 1Week of 2026-08-03: 0Week of 2026-08-10: 0Week of 2026-08-17: 0Week of 2026-08-24: 1Week of 2026-08-31: 0Week of 2026-09-07: 0Week of 2026-09-14: 0Week of 2026-09-21: 0Week of 2026-09-28: 0
2 mentions in the last 12 weeks
Indie fit
6.0/10
Pain
5.7/10
Frequency
9.5/10
Willingness to pay
2.8/10
Momentum
4.4/10
Who pays
Businesses
Competition
Medium
Build difficulty
Medium

What people said

Quoted word for word. Follow a link to read the whole discussion.

  1. Previously, I used gotify, then nextcloud chat, where I can post programmatically a new message, but it has such a limitation, I can miss a monitoring event like a service is down (uptime kuma) or a stranger entering a surveilled area (frigate)
    Dankó Dávid on softwarerecs.stackexchange.comApr 2025Asked for a toolHas a workaround
  2. This service by Verizon is simply unreliable. In my testing, I lose about 30% of my alerts because Verizon just drops/ignores messages for whatever reason. I heard ATT is the same. I'm open to either a free SMS service(we're small) or a messaging app like Whatsup
Build brief

See what to build and who will buy it

  • 2 product ideas with the smallest useful version and pricing
  • 5 places to find your first customers
  • 11 more quotes from people who have this problem
  • Current workarounds, existing solutions and risks