ntfy sends push notifications to your phone or desktop with a single curl command: publish a message to any topic and every subscriber receives it instantly, no signup or API key required. Over 31,000 GitHub stars and 106 releases since 2021 back a server supporting five priority levels mapped to distinct notification sounds and vibration patterns, emoji tags for visual classification, click actions that open URLs when tapped, and up to three action buttons per notification for view, HTTP callback, broadcast, or clipboard copy operations. File attachments push images from surveillance cameras, documents, or any binary payload directly to mobile devices. Subscriptions work through JSON streams, Server-Sent Events, WebSockets, or raw text, with server-side filtering by priority, tags, and message ID. Authentication enforces topic-level access control through Basic Auth, Bearer tokens, or query parameters, with a built-in user and ACL management system. UnifiedPush compatibility lets ntfy serve as a push distributor for Mastodon, Matrix, and other federated services. Web Push via VAPID keys delivers browser notifications without the mobile app. The server ships as a single statically linked Go binary or Docker image supporting amd64, armv7, and arm64 architectures, consuming 30-50 MB RAM at idle with SQLite-backed message caching. Integrations include Grafana, Prometheus Alertmanager, Uptime Kuma, Home Assistant, and Ansible Semaphore. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache 2.0 / GPLv2 dual-licensed.

Real-time alerts from your own infrastructure to your phone, with no Firebase, Pushover, or third-party push service in the path: Gotify is a simple, self-hosted notification server written in Go. The model is deliberately minimal: senders push messages with a single HTTP POST to the REST API, receivers subscribe over a WebSocket stream, and a clean React web UI manages the pieces. Senders are namespaced as "applications," each with its own token, so your backup script, Uptime Kuma, CI pipeline, and cron jobs each get an identity, an icon, and independently revocable credentials - centralized alerting from many services with per-source management. Messages carry a title, body, and priority level that maps to notification importance on the client. The official Android app (on both F-Droid and Google Play, notable for working entirely without Google Play Services) shows push notifications for new messages; the web UI itself supports Web Push in the browser; and gotify/cli pushes messages from shell scripts with one command. A server-side plugin system adds custom behavior, and the whole thing runs as a single small binary with SQLite by default - near-zero resource footprint. Because dozens of tools (and Apprise) speak Gotify natively, it slots in as the notification hub for an entire homelab or ops stack.

One REST call, 130+ notification services: Apprise API wraps the well-known Apprise library in a lightweight Django/Gunicorn microservice, so "send an alert" works the same whether it goes to Slack, Discord, Telegram, Teams, email, SMS, Pushover, or PagerDuty - each addressed by a simple URL scheme. It solves the credential-sprawl problem cleanly: instead of embedding provider tokens in every app, cron job, and CI pipeline, you centralize them here and everything else just POSTs a body and title. Two modes cover every workflow. Stateless calls to /notify carry target URLs in the payload (or fall back to a default set via APPRISE_STATELESS_URLS); stateful mode stores named configurations server-side under keys, so /notify/{KEY} fans out to everything registered - with tag-based routing (comma for OR, space for AND) selecting which endpoints fire per message. Messages take info, success, warning, or failure types in text, Markdown, or HTML, with attachments up to a configurable size. A built-in web UI manages and tests configurations, APPRISE_CONFIG_LOCK makes the store read-only, service allow/deny lists restrict which schemes work, webhook remapping adapts third-party payloads, and a Prometheus /metrics endpoint watches the gateway itself.

Powering notification delivery for thousands of organizations with over 39,000 GitHub stars, Novu is the open-source communication infrastructure that eliminates the need to build separate integrations for every messaging channel. The TypeScript-based platform provides a single API endpoint that routes notifications across In-App Inbox, Email via SendGrid, Mailgun, AWS SES, and Postmark, SMS through Twilio, Vonage, and Plivo, Push via Firebase Cloud Messaging, Expo, and APNS, and Chat through Slack, Discord, Microsoft Teams, and WhatsApp. The embeddable React Inbox component delivers real-time WebSocket-powered notifications with read/unread states, action buttons, and user-controlled preferences directly inside your application. The workflow engine orchestrates complex multi-channel delivery with conditional branching, time delays, digest batching to reduce notification fatigue, throttle controls, and per-step channel fallbacks. Novu Connect introduces Agent Communication Infrastructure enabling AI agents built with LangChain, Claude, or custom frameworks to hold threaded two-way conversations with humans across any supported channel through a single conversation model with identity resolution and credential management. The backend runs on Node.js with NestJS, MongoDB for notification storage, Redis with BullMQ for job queuing, and Socket.io for real-time delivery. Self-hosting deploys via Docker Compose with the dashboard accessible at port 4200. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

One notify() call is all your product needs to reach users on push, email, SMS, chat, and webhooks, with NotifKit deciding how and when each message travels. List the channels in the order you prefer and NotifKit tries each in turn, so a failed push quietly becomes an SMS or an email instead of a lost message. Per-user preferences, consent, and quiet hours in each user's own timezone hold non-urgent sends until morning, while critical messages such as one-time passwords travel their own lane immediately. Templates, multi-step workflows that wait days or block on events, scheduling, throttling, and deduplication all run behind that single call, defined in TypeScript and kept in your repository. Delivery logs record every attempt, and the admin dashboard shows a live activity feed, queue depth per priority lane, workflow runs step by step, and a replayable dead-letter queue. Several products can share one deployment as separate projects with their own API keys, rate limits, and data, and any service can call the REST API without the TypeScript SDK. Ask an AI assistant why a password reset never arrived by connecting the built-in MCP server to Claude Code, Cursor, or another MCP client. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Unlike a calendar alert that rings on one phone, a MIND reminder reaches any of 100+ services, including email, Pushbullet, BlueSky, Cisco Webex Teams, and SMS gateways, from a self-hosted reminder app that you control. Normal reminders fire with second precision once or repeat every few days, once a year, on chosen weekdays, or on a custom cron schedule, while static reminders wait for a button press, so a single tap can tell the family that you are running late. Templates store colour, title, services, and text for fast creation, and the colour-coded library can be searched and sorted, with each reminder enabled, disabled, or tested on demand. Time zone changes, including daylight saving shifts, are accounted for, and sends that fail on a connection error are retried every two minutes until they succeed. Several users can share one instance: the admin panel handles accounts and registration, login lifetime, reverse-proxy URL prefix, debug logs, and scheduled database backups that can be exported and imported, and sign-in supports two-factor authentication. A documented REST API covers reminders, templates, notification services, and static triggers, and the web interface adapts to phone screens. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. GPL-3.0 licensed.

With 21,400 GitHub stars, 500+ contributors, and battle-tested since its 2016 open-source release after powering Facebook's mobile backend infrastructure, Parse Server delivers production-grade Backend-as-a-Service that eliminates months of custom API development. The platform generates REST and GraphQL endpoints automatically from your data schema with class-level permissions and object-level ACLs providing granular access control. Cloud Code enables server-side JavaScript execution for triggers (beforeSave, afterSave, beforeDelete, afterDelete), custom functions, and scheduled jobs — all deployable without restarting the server. Live Queries push realtime data changes to subscribed clients via WebSockets, powering chat applications, collaborative editors, and live dashboards. Push notification support spans APNs for iOS, FCM for Android, and web push for browsers with audience segmentation, scheduling, and delivery analytics. The Parse Dashboard provides a comprehensive admin interface with a data browser featuring configurable info panels, graph visualization, custom canvas builder with draggable elements, AI agent integration via OpenAI, data import/export, and multi-factor authentication. Database flexibility supports MongoDB 6-8 and PostgreSQL 13-18 with PostGIS for geospatial queries. Native SDKs cover JavaScript, iOS (Swift/Objective-C), Android, Flutter/Dart, .NET/Xamarin, Unity, PHP, and Arduino for IoT devices. Deploy via npm, Docker, or the official Express template with automatic schema migration. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache 2.0 licensed.

TextBee turns an Android phone with a SIM card into an SMS gateway your applications can call, so one-time codes, alerts, reminders, and two-way conversations go out as ordinary texts from a real number. Pair a phone by scanning a QR code in the dashboard, then send messages from the REST API, the dashboard, or the JavaScript SDK. Bulk campaigns load from a CSV file and are paced to stay within carrier limits, and any message can be scheduled up to 72 hours ahead. With several phones or SIM cards attached, each message can name the device and SIM it should use. Every message moves through pending, dispatched, sent, delivered, or failed, and the history view lists all devices together. Incoming texts appear in the dashboard and the API, and webhooks push received messages and delivery reports to your server with an HMAC-SHA256 signature you can verify. An official MCP server lets AI assistants send texts and read replies. API keys, devices, usage, and webhook subscriptions are all managed from one web interface. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Mercure is a realtime hub that pushes updates from your backend straight to browsers over Server-Sent Events, so live dashboards, chat rooms, and activity feeds refresh the moment data changes. Subscribers connect through the browser's built-in EventSource API and choose topics with exact matchers for single resources or URL Pattern matchers for whole families such as /books/:id. Publishers send one form-encoded POST to the hub endpoint, and Mercure fans each update out to every matching connection instantly. JWT access tokens grant publish and subscribe rights topic by topic, so private updates reach only entitled clients while public topics can stay open to anonymous subscribers. If a connection drops, the client reconnects with its last event ID and Mercure replays the updates it missed from stored history. Subscription events announce every arrival and departure, so your application gets live presence and a current list of who is connected. A built-in debug UI shows messages flowing through the hub alongside active subscriptions, turning realtime bugs into something you can watch happen. Optional end-to-end encryption protects sensitive payloads, and any backend able to send an HTTP POST can publish, whatever language it runs. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.

Operational watches your product for the moments that matter, signups, payments, failed webhooks and cron jobs, and pushes the important ones to your phone as they happen. Your code sends structured events with a name and a JSON payload through a simple API, using the official Node.js or PHP SDKs or the WordPress plugin, and every event lands in a searchable feed organized by project and category. Mark an event notify and it becomes a push notification on your phone through the installable web app, while everything else waits quietly in the feed for when you actually want to look. Related events nest inside each other as contexts, so a failed checkout can carry its payment attempt, gateway response and retry history in one expandable bundle instead of forty scattered log lines. Events can carry action buttons that trigger your webhooks, letting you approve a refund, restart a job or retry a delivery from the notification itself. Teammates share projects with their own accounts, a test mode lets you rehearse integrations without polluting the real feed, and a built-in MCP server exposes your events to AI tools. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.

Sixty-thousand-plus GitHub stars make Uptime Kuma the most popular self-hosted monitoring tool - MIT-licensed, Node.js, and the standard replacement for UptimeRobot, Pingdom, and Freshping. It watches a dozen monitor types: HTTP(S) endpoints with keyword and JSON-query content validation, TCP ports, ICMP ping, DNS records, WebSockets, Docker containers via the socket, Steam game servers, MQTT brokers, gRPC services, and push-based heartbeats for cron jobs and internal workers. Checks run at intervals as tight as 20 seconds - versus UptimeRobot's 5-minute free tier - with unlimited monitors and unlimited data retention. When something fails, alerts fan out through 90+ notification channels: Slack, Discord, Telegram, email with LiquidJS templating, PagerDuty, OpsGenie, ntfy, Gotify, Matrix, and dozens more via native providers plus the Apprise library. Unlimited public or password-protected status pages - mappable to specific domains and organized into monitor groups - communicate health to customers, with maintenance windows that suppress alerts during planned work. The reactive dashboard graphs response times, tracks SSL certificate expiry with advance warnings, supports proxies and 2FA, and ships in dozens of languages. One Docker container with a SQLite volume covers an entire infrastructure.