Benchmarked at one million concurrent WebSocket connections and 30 million delivered messages per minute on a single server, Centrifugo is a self-hosted real-time messaging server that integrates with any backend language — Node.js, Python, Go, Ruby, PHP, Java — without requiring architectural changes to your existing application. It handles persistent connections over WebSocket, HTTP-streaming, Server-Sent Events, gRPC, and experimental WebTransport, routing messages through a channel-based PUB/SUB model with automatic reconnection recovery that replays missed messages from hot channel history. Built-in horizontal scaling operates through Redis (including Redis Cluster, AWS ElastiCache, Valkey, KeyDB, and DragonflyDB), NATS, or PostgreSQL brokers, allowing multi-node deployments without external message queues. The server provides JWT-based authentication using HMAC or RSA keys, granular channel permissions, online presence tracking showing who is currently subscribed to a channel, and an RPC proxy that forwards client calls to your backend over HTTP or gRPC. The embedded ReactJS admin web interface displays real-time connection statistics, node information, and provides an interactive API console for publishing messages, managing subscriptions, and inspecting channel history. Official client SDKs are available for JavaScript, Dart, Go, Swift, and Java, with unidirectional transports requiring no SDK at all. Centrifugo also supports delta updates to minimize bandwidth, connection event proxying, and Prometheus-compatible metrics for Grafana monitoring. 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.

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.

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.

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.

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.

An entire backend in a single Go executable: PocketBase embeds SQLite with realtime subscriptions, authentication and user management, file storage, and an admin dashboard, all behind a REST-ish API. SQLite runs in WAL mode, which outperforms client-server databases for the read-heavy workloads typical of small and mid-sized apps. Authentication supports email/password, one-time passwords, and 15+ OAuth2 providers including Google, Apple, and GitHub, with stateless tokens. Clients subscribe to record changes over server-sent events, and official JavaScript and Dart SDKs cover web, mobile, and Flutter frontends. Collections, rules, and API access permissions are managed visually in the admin UI. When you need custom logic, extend it with JavaScript hooks running in the embedded JS VM of the prebuilt binary, or import PocketBase as a Go library and compile custom business logic into your own single-file backend. File storage attaches uploads to records with thumbnail generation for images and optional S3-compatible external storage. All state lives in one pb_data directory, so backup is a directory copy and upgrade is replacing a binary - one of the lowest-maintenance backends you can run. The contrast with Firebase is the point: where usage-based pricing scales with reads, writes, and bandwidth, PocketBase runs the entire backend at flat hosting cost, and the data is a plain SQLite file you can copy anywhere. MIT-licensed.

A PostgreSQL database becomes a production-grade GraphQL API the moment Hasura GraphQL Engine points at it: track tables and relationships - existing schemas included - and full query, mutation, and subscription types appear with where, order_by, limit, offset, and on_conflict arguments, no resolvers or boilerplate written. Its Haskell core compiles GraphQL to efficient SQL, and any query becomes a real-time live query with a single keyword, powering dashboards and collaborative UIs over standard GraphQL subscriptions. Authorization is where Hasura earns its enterprise reputation: role-based access control with row- and column-level permission policies driven by session variables from JWTs, auth webhooks, or headers - each role effectively sees its own GraphQL schema containing only what it may touch, integrating cleanly with Auth0, Firebase, or homegrown auth. Event triggers fire webhooks on inserts, updates, and deletes for asynchronous business logic; Actions extend the schema with custom REST handlers; remote schema stitching merges external GraphQL services into one endpoint; and auto-generated REST endpoints serve clients that skip GraphQL. A browser console handles data modeling and API exploration, the CLI manages migrations and metadata as code, and deployment is a single stateless Docker container beside Postgres.

Kuzzle ships a production-ready backend from day one: data storage with Elasticsearch search, real-time pub/sub notifications, user authentication, role-based permissions, and a multi-protocol API serving HTTP, WebSocket, and MQTT simultaneously on port 7512. Rather than rebuilding these standard features from scratch for each project, you get a ready-made backend that accepts connections from web applications, mobile clients, and IoT devices through one unified API surface. Elasticsearch provides persistent document storage with full-text search, geospatial queries, and aggregation pipelines, while Redis handles internal caching and memory storage operations. The Koncorde real-time engine powers pub/sub messaging and database notifications, enabling clients to subscribe to document changes with filter conditions that trigger instant updates when matching data is created, modified, or deleted. User management includes JWT-based authentication, role-based access control with granular permissions at the controller and action level, and pluggable authentication strategies via Passport.js. The extensible plugin framework allows developing custom business logic, additional authentication providers, storage connectors, and protocol handlers. Client SDKs for JavaScript, Dart, Kotlin, and C++ accelerate frontend development, while the Kourou CLI provides command-line API access and project scaffolding. The Vue.js Admin Console offers a web interface for managing indexes, collections, documents, users, profiles, and roles. Horizontal scaling through masterless cluster mode targets 99.99% uptime without single points of failure. 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.

With over 20,000 GitHub stars and adoption by companies building everything from telehealth platforms to AI voice agents, LiveKit is the most widely deployed open-source real-time communication server available. The Go-based Selective Forwarding Unit handles hundreds of concurrent participants per node with adaptive bitrate streaming, simulcast layers, SVC codec support for VP9 and AV1, and end-to-end encryption. Client SDKs span JavaScript, Swift, Kotlin, Flutter, React Native, Rust, Python, Unity, and ESP32 embedded devices, while server-side APIs cover Node.js, Go, Ruby, Java, Python, Rust, PHP, and .NET. The Agents framework enables building AI-powered voice and video applications — real-time speech-to-text, LLM-driven conversations, and computer vision pipelines — running as server-side participants in any room. Egress records sessions to S3-compatible storage or streams to RTMP endpoints, while Ingress pulls external feeds from OBS via RTMP, WHIP, or SRT into LiveKit rooms. The SIP bridge connects traditional telephony to WebRTC rooms for hybrid conferencing. JWT-based authentication, webhook notifications, room-level moderation APIs, and selective subscription give operators granular control. Deploy as a single binary for development, Docker Compose for production single-node, or Kubernetes with the official Helm chart for distributed multi-region clusters using Redis for state coordination. 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.

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.