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.

A single ejabberd node carries chat, device telemetry, voice calls, and federated messaging at once, because the same Erlang server speaks XMPP, MQTT, SIP, and Matrix over one authentication, storage, and clustering layer. Users get standards-based instant messaging with group chats, message archives, publish-subscribe, message carbons, push notifications, and OMEMO encryption, and your server federates with the global XMPP network out of the box. Devices publish and subscribe through the built-in MQTT broker on TCP or WebSocket transports, sharing accounts and access rules with your chat users instead of needing a second broker. Voice and video calls route through the integrated SIP gateway and STUN/TURN support, so WebRTC clients get signalling and media relay from the same deployment. Matrix support bridges federated rooms into the same infrastructure, letting two decentralised ecosystems interoperate without a separate bridge stack to babysit. Clustering with consistent hashing scales a deployment across nodes, and a single node is rated at two million concurrent sessions for very large communities. Operators manage everything from the web admin and command line, with SQL or Mnesia storage, LDAP authentication, and virtual hosting for multiple domains on one server. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. GPL-2.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.