Friendica connects to more federation protocols than any other single platform: ActivityPub reaches Mastodon, Pleroma, Misskey, Lemmy, Pixelfed, and PeerTube; the Diaspora protocol bridges that network; and OStatus provides legacy compatibility. But protocol reach is just the foundation. Where most fediverse platforms stop at microblogging, Friendica offers long-form posts, photo albums, event calendars with RSVP, group discussions, and rich multimedia content. BlueSky and Tumblr connectors extend your reach into non-federated networks, while RSS import pulls content from any blog or news source into your timeline. Privacy controls let you scope each post to specific contacts, groups, or public visibility with per-post granularity rather than account-wide settings. Multiple themes customize the interface from Facebook-like layouts to minimal designs, and Fedilab provides native mobile access. Under the hood, the PHP application with MariaDB runs as either an Apache or FPM Docker image with Redis caching and background cron workers handling federation delivery, media processing, and notification dispatch. One of the oldest fediverse projects (1,650+ stars, 160+ contributors since 2010), Friendica has weathered every protocol evolution and platform migration the decentralized web has thrown at it, making it one of the most battle-tested social networking platforms available.

Movie night should not depend on everyone pressing play at the same second; SyncWatch runs your own watch-party server so friends in different places watch the same frame together. The host controls play, pause, seeking, and playback speed for the whole room, and late joiners or drifting clients are corrected back to the shared position automatically. You build the program from uploads or direct HTTPS media links, with subtitles, audio, images, and documents handled in the same library. Rooms can be permanent or temporary, protected by passwords and member limits, with host, admin, and permission-group control over who may operate playback. Between scenes, people talk through public and private chat, on-screen danmaku comments, emoji, voice messages, or full-room voice. Anyone can share a browser tab, window, desktop, or phone screen into the room, so a clip, a game, or a presentation becomes the shared screen. The server also keeps friends, notifications, online presence, bans, registration approvals, and an operations log, so a private community can run itself without a platform account. Uploaded media is analyzed and thumbnailed automatically, with browser-compatible versions generated for awkward formats. Backups, data export, a recycle bin, mail verification, and network diagnostics round out the admin side. 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 Janus installation can host a video meeting in one session, stream a camera feed in another, and bridge a browser call into a telephone network in a third, because Janus is a general-purpose WebRTC server whose work is done by interchangeable plugins. The VideoRoom plugin publishes each participant's streams to everyone else in the room with simulcast and viewport selection, so a class or team call adapts quality per viewer instead of forcing one bitrate on all. Streaming mounts live or prerecorded sources, including RTSP cameras and RTP feeds, and hands them to any number of WebRTC viewers, while AudioBridge mixes voices into conference rooms with recording and signed-token access. SIP and NoSIP plugins register with existing VoIP infrastructure and place or receive calls, translating between WebRTC media and telephone audio so a web page can ring a desk phone. Record&Play captures publisher streams to files you can replay through the same server, TextRoom adds data-channel chat rooms, and Lua or JavaScript plugins let you script custom media logic without recompiling the core. Applications talk to Janus over HTTP or WebSocket APIs, with RabbitMQ, MQTT, and NATS transports for bus-driven deployments, and event handlers report session activity to your monitoring stack. 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.

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.

Companies with privacy and security concerns about piping customer conversations through Intercom or Zendesk run Papercups - open-source live customer chat. The stack is a deliberate strength: an Elixir/Phoenix API over PostgreSQL, with real-time messaging powered by Phoenix Channels and Presence - the same BEAM foundation trusted by Discord and PagerDuty for fault-tolerant, low-latency messaging. Customers see a customizable chat widget that embeds in any site as an HTML snippet, a React component, or even inside React Native apps, with configurable colors, greetings, and away messages. Your team sees a dashboard for managing conversations - close, assign, and prioritize - with Markdown and emoji in replies. The killer workflow is the reply-channel integration: connect Slack or Mattermost and every customer conversation becomes a synced thread your team answers without leaving the tool they already live in, with two-way message syncing handled by webhooks. Email and SMS channels extend intake beyond the widget, an analytics dashboard tracks communication patterns, and the Storytime feature adds real-time screen sharing to watch users navigate while you help them. A documented API supports fully custom chat UIs in Svelte, Flutter, or Vue. MIT-licensed and GDPR-conscious - customer data stays in your PostgreSQL.

With over 7,500 GitHub stars and 140 contributors, Matterbridge is the Go-powered chat bridge that connects over 20 messaging platforms through a single TOML configuration file, letting teams communicate across platform boundaries without forcing anyone to switch applications. The gateway architecture routes messages bidirectionally between any combination of Discord, Slack, Telegram, Matrix, IRC, Mattermost, Microsoft Teams, XMPP, Rocket.Chat, Nextcloud Talk, Keybase, Mumble, Twitch, WhatsApp, VK, Gitter, Zulip, ssh-chat, and Harmony, with transparent username and avatar spoofing so bridged messages appear native on each platform. Message edits and deletes propagate across bridges, file attachments and inline images transfer between protocols, threading and reply context is preserved where platforms support it, and private group bridging enables confidential cross-platform conversations. Multiple independent gateways can run simultaneously, each bridging different channel sets with different protocol combinations. The REST API enables third-party integrations and custom bridges without modifying the Matterbridge codebase, while the tengo scripting engine allows inline message transformation and filtering. Game chat support bridges Minecraft and Counter-Strike server chat into messaging platforms. Deployment runs as a single static Go binary with zero dependencies, or as the official Docker image with the configuration file mounted as a volume. 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.

Forum software rebuilt on the modern web stack: NodeBB runs the classic bulletin-board format - categories, threads, local accounts - in real time, on Node.js over MongoDB, Redis, or PostgreSQL. WebSockets stream new posts into open topics as they're written and deliver instant notifications for follows, likes, and subscriptions; built-in chat supports side-by-side private conversations. The headline of recent versions is core ActivityPub federation: your forum can follow, share, and converse with other NodeBB instances, Mastodon, Lemmy, and anything else that speaks the protocol, turning an isolated community into a fediverse node. Everything beyond the common core is a plugin - more than 500 plugins and themes install in one click from the admin panel, covering SSO providers, search backends like Elasticsearch and Solr, galleries, calendars, and more. The theming engine extends base templates with SCSS/CSS on Bootstrap 5, plus a drag-and-drop widget system and custom HTML/CSS/JS injection. Operators get a real-time analytics dashboard, human-readable SEO-friendly URLs with semantic markup, multilingual UI, and full read and write REST APIs for integration. Mobile-first rendering means the same install works everywhere. For communities that outgrew phpBB but don't want Discourse's weight, NodeBB is the natural middle.

With over 10,000 GitHub stars and a reputation forged in the frustration of laggy corporate screen sharing, Screego delivers what Microsoft Teams and Zoom screen share consistently fail to provide: instant, high-resolution screen streaming that lets remote colleagues actually read your code. Built on WebRTC peer-to-peer connections, Screego transmits screen data directly between browsers without routing through centralized servers, achieving sub-second latency and native-resolution quality that makes pair programming and code reviews genuinely productive. The server component, written in Go with a TypeScript frontend, deploys as a single binary or Docker container with minimal configuration — set your external URL, generate a secret key, and you're live. An integrated TURN server handles NAT traversal automatically, eliminating the need for separate STUN/TURN infrastructure, with configurable UDP port ranges and support for external TURN servers when scaling beyond a single instance. Authentication supports three modes — requiring login for all actions, only for TURN connections, or none — with user management via simple credential files. Rooms are created instantly and support multiple simultaneous viewers, with system and tab audio sharing available for demonstrations that need sound. The architecture supports reverse proxy deployment behind Nginx, Caddy, or Apache with automatic TLS termination, and recent releases added riscv64 architecture support alongside existing amd64 and arm64 builds. 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.

Diaspora lets you run your own social network node that federates with thousands of others, creating a network with no central authority and no advertising engine mining your behavior. The defining feature is aspect-based sharing: organize contacts into groups like Family, Work, and Close Friends, then control exactly who sees each post with granularity that mainstream platforms have never matched. Hashtag-based discovery connects conversations across the entire federation regardless of which pod participants call home, building communities around topics rather than algorithmic engagement bait. The Ruby on Rails backend (now running on Puma with Sidekiq workers instead of the heavier Unicorn configuration) handles federation delivery, media processing, and notifications efficiently. Photo albums, video embedding, Markdown posts, mentions, reactions, and resharing provide familiar social primitives for rich communication. Cross-posting bridges to Twitter and Tumblr maintain your presence on legacy networks while your canonical data lives on your own infrastructure. With 13,700+ GitHub stars and 270+ contributors since its 2010 launch, Diaspora proved early that social media can work without surveillance capitalism. The Docker Compose deployment runs the application alongside PostgreSQL, Redis, Sidekiq workers, and Nginx, providing a production-ready pod for your community.

Mox offers a complete mail server stack in a single Go binary requiring no external dependencies. The quickstart command configures a working mail server with SMTP, IMAP4, webmail, and full DNS authentication in under ten minutes. SMTP handling includes a delivery server on port 25, a submission server for authenticated clients, and a queue with automatic retries and DKIM signing. IMAP4rev2 implementation provides full mailbox synchronization with CONDSTORE and QRESYNC for efficient offline clients, NOTIFY for multi-mailbox monitoring, MULTISEARCH across mailboxes, and TLS client certificate authentication via the EXTERNAL SASL mechanism. The built-in webmail provides browser-based reading and composing with message threading, attachments, and HTML rendering without requiring a separate web client. Email authentication implements SPF validation, DKIM signing and verification with automatic key rotation, DMARC policy enforcement with aggregate and failure reporting, DANE with DNSSEC-protected TLSA records, and MTA-STS for certificate verification. Junk filtering combines reputation-based sender scoring with Bayesian content analysis trained per account. The web administration interface manages domains, accounts, DNS records, TLS certificates, delivery queue, and real-time log viewing. Internationalized email addresses with EAI and IDNA support handle non-ASCII domains and mailboxes. Account autoconfiguration publishes settings for Thunderbird autoconfig and Outlook autodiscover. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Running your own mail server usually means assembling five services and praying over DNS records; LanQin Email ships the whole stack in one container. Readers switch between mailboxes, search, label, star, and file messages into folders, then compose with a rich-text editor that handles fonts, colors, code blocks, attachments, emoji, and scheduled sending. Contacts, signatures, inbox rules with automatic forwarding, sender blacklists, and mail statistics make it a daily client rather than a demo. Administrators run the postal side from the same panel: add domains and generate DKIM keys, follow the DNS record checklist the system verifies for you, create mailboxes, set delivery aliases and catch-all addresses, and audit every message on the server. Accounts sign in with passwords or OAuth single sign-on, protected by TOTP two-factor codes and bot checks, while permission groups cap attachment size, sending rate, and mailbox count per user. Users can even request their own mailbox and wait for approval instead of filing a ticket. For programs, an Open API with bearer tokens sends mail idempotently and reports delivered, bounced, complained, rejected, and deferred events back through webhooks. External Gmail and Outlook accounts can be aggregated over IMAP, and a client-configuration page shows every IMAP, POP3, and SMTP setting in one place. A multi-container layout remains for debugging the stack piece by piece. 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.

DispatchMail is an SuperHuman alternative and delivers a self-hosted AI email assistant that processes your Gmail inbox through configurable OpenAI prompts without sending data to third-party cloud services beyond the LLM API itself. The Flask backend connects to Gmail via IMAP, retrieves new messages according to your schedule, and routes them through customizable whitelist rules based on sender address, subject keywords, or natural language descriptions before AI processing begins. Two distinct prompt configurations control behavior — the Reading Prompt instructs how the AI should analyze and classify incoming messages, while the Draft Prompt defines how responses should be composed, letting you maintain consistent tone and policy across all automated replies. Whitelist filtering ensures the AI only processes messages you explicitly authorize, preventing unnecessary API costs and keeping sensitive emails out of the LLM pipeline entirely. The React web interface provides inbox management with message previews, AI-generated summaries, draft editing with human-in-the-loop approval before sending, and configuration panels for prompts and rules. Automatic labeling and archival organize processed messages into categories without manual intervention. The sender research feature uses LLM-powered deep analysis to build background profiles of email contacts. All email content, credentials, and processing results persist in a local SQLite database with zero cloud storage dependencies. 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.

Your entire mail system can live in one self-hosted suite with OpenMail, from SMTP, IMAP, and POP3 delivery to three-pane webmail and the admin console that runs it. Standard clients such as Thunderbird, Apple Mail, and phone apps connect over SMTP ports 25, 587, and 465, IMAP ports 143 and 993, and POP3 ports 110 and 995, while people use the three-pane webmail with folder tree, conversation list, and reading pane at port 3000. You read, write, reply, forward, batch-organize, drag messages between folders, filter stars, search sender, subject, and body text, and follow conversations threaded automatically by their References headers. The rich-text composer autocompletes recipients, accepts dragged attachments and pasted screenshots, saves drafts every 12 seconds, sends on a schedule, and inserts reusable templates imported from HTML or generated with AI. Any OpenAI-compatible endpoint can draft replies, translate mail into twelve languages, and summarize messages, with provider keys encrypted on your server. Administrators get real-time mail statistics with 14-day send and receive trends, user quotas and bans, multi-domain aliases and catch-all addresses, outgoing queue visibility, and audit logs. Adding a domain generates DKIM keys and copy-ready SPF, DKIM, and DMARC DNS records with one-click checks, while rule-based spam scoring, TOTP two-factor authentication, and role-based permissions protect accounts in ten interface languages including right-to-left Arabic and Urdu. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Mastodon serves single-user and small-community instances poorly; GoToSocial, an ActivityPub server written in Go, was built precisely for them. Where Mastodon demands Ruby, PostgreSQL, Redis, and Sidekiq, GoToSocial is one binary using roughly 250-350 MiB of RAM with SQLite as the default database (PostgreSQL optional) - it runs comfortably on a $5 VPS or a repurposed laptop. The deliberate design choice is having no built-in web client: the server exposes profile pages, a settings panel, and a faithful implementation of the Mastodon API, and you post through the client app you already like - Tusky on Android, Feditext on iOS, Pinafore or Phanpy in the browser. Federation is the point: your instance follows, boosts, and replies across Mastodon, Misskey, Pixelfed, and the rest of the Fediverse, with your identity anchored to your own domain. Safety is a stated focus, with granular per-post visibility and interaction controls, content warnings, custom emoji, hashtag following, domain allow/blocklists, and OIDC login support. Built-in Let's Encrypt provisioning simplifies the mandatory TLS. AGPL-3.0 licensed and in active beta, federating cleanly with the ecosystem's major servers.

Email discussion lists - the venerable listserv pattern where one address relays to a whole group - without the notorious setup pain of Mailman or Sympa: that is Gray Duck Mail. Its architectural trick is requiring no mail server of your own: the C#/ASP.NET Core app monitors a POP3 inbox at any external email host supporting POP3/SMTP and aliasing, relays each incoming message to all list members via SMTP, and archives it for browsing in the web interface. Replies route back to the entire group automatically. The tedious parts of list management are handled by convention: dedicated aliases process join requests, subscription confirmations, and unsubscribes, while a bounce alias in the return-path catches delivery failures so dead addresses get handled instead of silently rotting. The web administration interface creates and removes lists, manages contacts, browses message archives, and imports or exports the local database for backup. GPLv3-licensed, Docker-distributed, and fully code-documented, it targets exactly the groups email still serves best - neighborhoods, schools, congregations, workplaces, and families - where one message keeping everyone in the loop beats yet another app nobody wants to install.