A Pager: High-priority notification service that beeps until acknowledged.

What it does

UDP-7777 is a local notification system that sends persistent alerts to a desktop application until the user acknowledges them. It listens on UDP port 7777 and works without cloud servers or account setup. Users can send notifications to machines on their local network, Tailscale mesh networks, or localhost. The application includes a retro "signal codes" system for common message types like emergency alerts, queries, and food notifications.

Who it is for

Developers and technical users who want alert functionality without cloud dependency. Teams using local networks or mesh VPN setups (Tailscale, WireGuard) can integrate it without external infrastructure. Anyone frustrated with notification overload from modern communication platforms may find the persistent beep-until-acknowledged model useful for genuinely important alerts.

Pricing

Not shown.

How it stands out

The service eliminates cloud infrastructure by running entirely on the recipient's machine. No accounts, no authentication servers, and no data transmission outside the network stack. It uses simple UDP broadcasting rather than establishing persistent connections. The capcode system maps IP addresses to retro 10-digit identifiers, creating a minimal addressing scheme. The software is digitally signed and available for Windows, macOS, and Linux. The design philosophy prioritizes simplicity: no headers, no handshakes, no message history.

What a founder should check

First, verify actual reliability advantages over modern notification systems. The pager comparison emphasizes signal strength during disasters, but that claim needs validation for 2025 mesh networks and local UDP versus tested alternatives. Does persistent beeping actually reduce missed critical alerts, or do users habituate and tune it out like other notification systems?

Second, assess switching costs and network lock-in. If users build workflows around UDP-7777's local-only model, how easily can they migrate to competitors if infrastructure needs change? The lack of cloud logging might be a feature for privacy but could become a limitation if audit trails or alert analytics become necessary.

Third, examine the moat against simpler alternatives. A local notification system with UDP is technically straightforward to replicate. Competitive pressure could come from teams implementing similar functionality in-house, existing monitoring tools adding UDP support, or mesh VPN platforms bundling native alerting. The minimal feature set means differentiation is difficult to defend.

Thinking of building something like this?

Every launch here is a competitor to somebody's idea. If yours is close, check it against the market before you build: the Full Check names the rivals, the prices and the gaps.