Best Self Hosted Alternatives to Threads

Mastodon is an open-source social networking server that implements the ActivityPub protocol to create a federated microblogging network. It provides chronological timelines, media-rich posts, moderation controls, and APIs for third-party integrations.

Key Features

• Federation via ActivityPub: interoperable with other servers and fediverse software using open protocols.
• Chronological, real-time timelines with streaming updates for follows and local/global timelines.
• Rich media support: images, video, audio, polls, custom emojis, animated avatars, and accessibility captions.
• Moderation and safety tools: local instance rules, content warnings, muting, blocking, reporting, and configurable filters.
• Developer-friendly APIs: REST and streaming APIs with OAuth2 support for third-party apps and integrations.
• Distributed account model: independent servers (instances) with local administration and moderation policies.
• Scalable deployment options: containers, docker-compose and orchestration-friendly configurations with background job processing and caching.

Use Cases

• Community networks: small to large communities that want moderated, self-governed social spaces without centralized corporate control.
• Organizations and institutions: public bodies, nonprofits, and groups that need federated presence and policy-driven moderation.
• Creators and publishers: sharing media-rich microblogs, threads, and announcements with audience control and content warnings.

Limitations and Considerations

• Media storage and bandwidth can be resource-intensive; large instances need significant disk, CDN, or object-storage planning.
• Federation introduces moderation complexity: instance-level policies do not automatically control content hosted on remote servers.
• Operational overhead: running a production instance requires managing multiple components (web processes, streaming, background workers, DB, cache).

Mastodon provides a privacy-minded, standards-based alternative to centralized social platforms, emphasizing local governance and interoperability across the fediverse. It is suitable for projects that prioritize open protocols, community moderation, and control over data and timelines.

diaspora* is an open-source, federated social network that lets people join independently operated servers (pods) and control audience and data with fine-grained privacy controls called Aspects. It provides a social stream with familiar actions (hashtags, mentions, reshares, likes) and is implemented as a Rails application for pod hosting and federation. (diasporafoundation.org)

Key Features

• Pod-based federation model: users register on independently operated pods and communicate across pods via the diaspora federation protocol and standard discovery methods. Documentation and the project site describe pod-based federation and discovery. (diasporafoundation.org)
• Privacy-by-design Aspects: contacts are grouped into named Aspects so posts can be targeted to specific groups rather than all contacts.
• Familiar social features: support for hashtags, @mentions, reshares and a simple reaction (love/like) workflow.
• Cross-posting integrations: built-in options to cross-post to external services (examples include Twitter, Tumblr, WordPress) when configured by pod admins or users.
• Production-ready codebase and deployment tooling: the project includes Rails app artifacts, JavaScript assets, a Docker development folder and deployment guidance in its repository. (github.com)

Use Cases

• Community-run social networks: organizations or interest groups that want a privacy-respecting social stream can host a pod to serve members.
• Private or distributed social spaces: users who need segmented sharing (family, work, hobbies) can use Aspects to target posts.
• Research, teaching, or demos: institutions can deploy pods for classroom/demo environments to show federated social concepts. Documentation and install guides include instructions for pod setup and database configuration. (centron.de)

Limitations and Considerations

• Limited interoperability with ActivityPub-based Fediverse: diaspora* uses its own federation protocol and historically does not implement ActivityPub, which restricts direct federation with ActivityPub-only networks (e.g., many Mastodon instances). This is a notable interoperability consideration for deployment and community reach. (en.wikipedia.org)

In summary, diaspora* is a mature, privacy-oriented federated social platform focused on pod-based federation and audience control through Aspects. Its codebase and docs provide production deployment and administration guidance for communities that want decentralized social hosting.

Misskey is an open-source, federated social media (microblogging) platform for running your own community server. It connects to other compatible servers across the fediverse using ActivityPub, enabling cross-server following, posting, and interactions.

Key Features

• ActivityPub-based federation with other fediverse platforms
• Web-based timeline interface for posts and social interactions
• Customizable instance operation for communities (local policies, moderation, and user management)
• Media attachments and rich post interactions typical of microblogging platforms
• API support for integrations and third-party clients

Use Cases

• Hosting a community-run social network that can still interact with the wider fediverse
• Creating an organization or interest-group microblogging hub with local moderation policies
• Experimenting with federated social networking using ActivityPub

Limitations and Considerations

• Federation behavior and feature parity can vary across different ActivityPub implementations
• Running a public instance requires active moderation and operational planning

Misskey is a strong option for communities that want a modern microblogging experience while remaining interoperable with other federated networks. It is well-suited to both small private groups and larger public instances when paired with appropriate moderation practices.

Pixelfed is a decentralized photo-sharing social network that lets people publish and discover photos without centralized algorithmic timelines. It uses ActivityPub to federate with other Fediverse platforms, enabling cross-server social interactions.

Key Features

• Photo posts with social interactions such as likes and comments
• ActivityPub federation for following and interacting across Fediverse servers
• User profiles and follower/following model similar to mainstream photo networks
• Web-based interface with a modern front end
• Admin controls for operating an instance and managing local policies

Use Cases

• Run a community or organization photo-sharing platform with its own moderation rules
• Share photography publicly while still interacting with users on other Fediverse servers
• Host a private or invite-only photo network for a group, school, or club

Limitations and Considerations

• Federation behavior depends on compatibility and policies of other ActivityPub servers
• Media storage and bandwidth needs can grow quickly on larger instances

Pixelfed is a strong option for anyone who wants a federated, standards-based alternative to centralized photo-sharing platforms. It combines familiar social features with decentralized deployment and interoperability across the Fediverse.

Ech0 is a compact, open-source self-hosted platform for publishing short posts, notes and links. It focuses on low resource usage, fast deployment and federated connectivity so individuals can publish and share while keeping data locally controlled.

Key Features

• Atomic lightweight architecture: tiny memory footprint and small binaries, single-file SQLite storage for low maintenance.
• Federated protocols: ActivityPub support to interoperate with Fediverse services (Mastodon, Misskey, etc.).
• Simple deployment: official Docker images and Docker Compose manifests for one-command startup.
• Modern web UI: Vite-powered frontend with a Markdown-first editor, responsive layout and PWA support.
• Multiple management interfaces: Web UI, CLI and TUI for administration, backup and snapshot restore.
• Authentication & integrations: OAuth2 / OIDC support and Passkey (WebAuthn) login options for third-party and secure auth.
• Media & storage: built-in music/video card parsing and native S3-compatible storage integration for object media.
• Real-time monitoring and webhooks: WebSocket-based resource panel and webhook hooks for automation.
• Built-in features: todo management, tagging/filters, RSS, token management and open APIs for extensions.

Use Cases

• Personal publishing: run a small personal blog, notes or micro-post stream with full data ownership.
• Federated social presence: publish posts that appear in the Fediverse and follow/interact with other ActivityPub actors.
• Lightweight team or community hub: shared lightweight knowledge/announcements for small groups or communities.

Limitations and Considerations

• Scaling: single-file SQLite is excellent for low-cost self-hosting but may be a constraint for very high-traffic or large multi-user deployments.
• Federation completeness: some federation-related features and extended Fediverse endpoints require configuration or may be progressively implemented; advanced federation workflows may need extra setup.
• Feature scope: while rich for a lightweight system, Ech0 prioritizes minimalism over enterprise features (e.g., complex RBAC or large-scale analytics).

Ech0 provides a focused, low-friction way to publish and federate personal content. It is suited for individuals and small communities that value data sovereignty and simple operations while requiring federated connectivity.

Friendica is a decentralized social networking and communications platform you can run on your own server. It connects to the wider Fediverse, enabling interaction across multiple compatible networks while keeping control over your data and privacy.

Key Features

• Federation with other networks via ActivityPub and diaspora* (and legacy compatibility such as OStatus)
• Fine-grained privacy controls, including access lists per post and private group conversations
• Social features including posts with edits, comments, reactions (like/dislike), and direct messaging
• Events and profiles with public and private aspects
• Photo sharing with audience restrictions
• Content ingestion via RSS/Atom feeds and support for additional integrations through plugins
• Optional content expiration and personal data export

Use Cases

• Hosting a personal or community social network that federates with the broader Fediverse
• Privacy-focused group communication for clubs, NGOs, or teams using access-controlled spaces
• Aggregating blogs and feeds into a social stream while publishing to a federated network

Friendica is a practical choice for users who want a familiar social networking experience while remaining interoperable with other federated platforms. Its plugin and theme ecosystem makes it adaptable for personal sites, families, and small communities.

Open Source Social Network (OSSN) is an open-source PHP application for creating a full social networking website. It provides core community features like profiles, a newsfeed, groups, and messaging, plus an extensible component system to add more functionality.

Key Features

• User accounts with profiles, cover photos, friends management, and privacy-related controls (blocking)
• Newsfeed with posts, comments, likes/reactions, mentions, and media embedding
• Groups, blogs, photo albums/gallery, search, and notifications
• Messaging and live chat features, including real-time updates
• Admin dashboard with user management, configuration, themes/components management, and cache settings
• Extensible “components” system for adding extra features, plus multilingual UI support
• Web services API for integrations and custom development

Use Cases

• Private or public community platform for clubs, schools, or interest groups
• Internal social network for teams and organizations
• Niche social site with custom features added via components

Limitations and Considerations

• Feature set and scalability depend heavily on chosen components and hosting resources
• Requires correct filesystem permissions for the web server to operate properly

OSSN is a practical option for teams that want a traditional social network experience with a PHP stack and the ability to extend functionality through modules. It fits well for community-centric sites that need common social features without building everything from scratch.

Hyphanet (also known as Freenet) is a peer-to-peer platform for censorship-resistant communication and publishing. It provides a distributed, encrypted, decentralized datastore that applications and sites can run on top of without relying on centralized servers.

Key Features

• Encrypted, decentralized datastore for storing and retrieving content in a censorship-resistant way
• Plugin ecosystem enabling applications such as forums, microblogging, blogging, and media sharing
• Supports different network modes, including global participation (Opennet) and more private friend-to-friend connectivity
• Designed to improve privacy by minimizing reliance on centralized infrastructure and authorities
• Can be extended with tools intended to bridge disconnected networks via offline transfer workflows (e.g., sneakernet-style sharing)

Use Cases

• Publishing websites and content that is difficult to censor or take down
• Private communities and communication apps (forums, microblogging) built on decentralized storage
• Resilient information sharing in constrained or disrupted network environments

Limitations and Considerations

• Peer-to-peer systems can have higher latency and less predictable performance than centralized services
• Private friend-to-friend usage requires establishing trusted connections, which can reduce ease of onboarding

Hyphanet is suited to users who need privacy-preserving publishing and communication backed by decentralized storage. Its plugin-based approach enables a range of community and media applications while keeping infrastructure decentralized.

NeoDB is an open-source server and community platform for tracking, rating, and reviewing cultural media such as books, movies, TV shows, music, podcasts, games, and performances. It supports self-hosting and federation, enabling interaction across the Fediverse.

Key Features

• Shared media catalog with search and item creation, including links/imports from many third-party sources
• Personal collections with statuses (wishlist, in progress, complete, dropped), ratings, notes, and long-form reviews
• Tags (private or public), custom collections/lists, and progress tracking (for example reading challenges)
• Social feed of friends’ activities with per-activity visibility controls
• Microblogging features for posting statuses/photos and interacting with posts
• Federation via ActivityPub for following and interacting with users across NeoDB instances and other ActivityPub services
• Optional posting support to ATProto/Bluesky identities (NeoDB is not a PDS)
• APIs including a REST API with OpenAPI specification and a Mastodon-compatible API for client compatibility

Use Cases

• Replace proprietary trackers (for example for reading, watching, and listening) with a self-hosted, federated alternative
• Run a community instance for sharing reviews, lists, and recommendations across the Fediverse
• Build third-party apps or integrations using the REST and Mastodon-compatible APIs

NeoDB combines a media tracking database with social and federated communication, making it suitable for both personal collection management and community-driven discovery. It is designed to interoperate across instances while keeping users in control of their collections and sharing preferences.

Nextcloud Social is an app that integrates federated social networking into Nextcloud using the ActivityPub protocol. It lets Nextcloud users post, follow accounts on federated platforms, and keep their posts and profile data on their own Nextcloud server.

Key Features

• Implements ActivityPub to federate with fediverse services (supports following and delivering posts across instances)
• Uses existing Nextcloud user profiles and stores posts on the Nextcloud backend
• Web UI built with modern JavaScript and Vue components for feed, posting and profile interactions
• Server-side integration in PHP so interactions are handled through the Nextcloud app framework
• Emoji handling and database character support considerations (4-byte emoji support may require DB configuration)
• Includes administration utilities and occ commands to manage or reset social data
• Designed to interoperate with Mastodon/Pleroma and other ActivityPub-compatible services

Use Cases

• Provide an internal company or community social stream while allowing federation with the wider fediverse
• Enable Nextcloud users to follow and interact with accounts on Mastodon, Pleroma and other ActivityPub servers
• Consolidate social posts, profiles and media on a private Nextcloud instance for privacy and data control

Limitations and Considerations

• The app has been released in beta and may lack some advanced fediverse features and moderation tooling compared to mature standalone platforms
• Emoji support may require enabling 4-byte character support in your database; consult Nextcloud database requirements
• Functionality and compatibility depend on Nextcloud server version; verify supported Nextcloud releases before deployment

Nextcloud Social is a privacy-oriented way to add federated social features to Nextcloud, letting organizations and individuals host their own social data while remaining part of the fediverse. It is suitable for teams and communities that want integrated social functionality with Nextcloud's user and storage model.

Hollo is a headless, federated microblogging server designed for single-user personal instances. It implements ActivityPub and a Mastodon-compatible REST API so existing Mastodon clients can interact with a Hollo instance.

Key Features

• Federated single-user microblogging focused on personal journals, notes, and microblogs
• Mastodon-compatible REST API surface so most Mastodon clients can be used as frontends
• Implements ActivityPub for federation with other fediverse software
• Headless design (no built-in web UI); clients render and interact with posts
• Supports CommonMark (Markdown) and very long posts (up to 10,000 characters)
• Misskey-style quotes and emoji reactions compatibility for broader fediverse feature parity
• Multiple accounts can be hosted on a single instance with per-account profiles and settings
• Built on the Fedify ActivityPub framework and provided with Docker deployment options

Use Cases

• Host a personal, federated microblog or public journal while retaining full control of data
• Use existing Mastodon-compatible desktop or mobile clients to manage posts and followers
• Create a lightweight single-user presence on the fediverse without running a full multi-user server

Limitations and Considerations

• Hollo is headless and does not provide a native web UI; a compatible Mastodon client is required for full interaction
• Some client features or third-party integrations may vary in behavior compared to full Mastodon servers
• Intended for personal/single-user use; not optimized as a replacement for full multi-user fediverse instances

Hollo provides a lightweight, standards-based way to run a personal presence on the fediverse using familiar Mastodon clients. It is suitable for users who want a simple, federated microblogging setup without a full multi-user server stack.

Ktistec is a lightweight, writing-focused ActivityPub server intended for small numbers of trusted users. It provides a personal/federated publishing platform with rich editing, thread analysis, and basic site administration.

Key Features

• Implements the ActivityPub protocol for federation (publishing, following, liking, announcing, undoing, deleting).
• Two editing modes: rich text editor and Markdown editor with automatic Markdown-to-HTML conversion and hashtag/mention support.
• Image attachments with alt text support and federated focal-point positioning for thumbnails.
• Draft posts, autosave, threaded replies and prioritized self-replies to keep author threads coherent.
• Thread Analysis (key participants, timeline histogram, notable branches) to help navigate large conversations.
• Translations integration (supports external services such as DeepL or LibreTranslate if configured).
• @-mention and #-hashtag autocomplete, custom emoji rendering, polls, bookmarks, pinned posts, and RSS feeds.
• Content discovery and filtering, blocking, control over comment visibility, Open Graph metadata, and pretty URLs.
• MCP (Message Capture Protocol) support and OAuth for integrations; scripting, tasks, metrics, and theming support.

Use Cases

• Run a personal or small-group Fediverse instance for blogging, long-form writing, or microblogging.
• Host a low-volume community or trusted discussion space where every user is an administrator.
• Use as a platform for scripted publishing workflows, archiving notes, or research threads with thread analysis tools.

Limitations and Considerations

• Designed for low-volume, trusted deployments: every account is effectively an administrator and the software is not targeted at large public instances.
• Requires compiling a Crystal-language server binary and building JS/CSS assets (Node.js + Webpack) for development; a prebuilt "dist" branch is available for simpler deployment.
• Relies on SQLite3; some SQLite versions (notably certain 3.39.x and 3.40.x builds) are known to have issues with bloom filters and recursive queries—use a compatible SQLite release.
• Not intended as a drop-in replacement for high-scale ActivityPub servers that depend on separate DBs or queues (e.g., PostgreSQL + Redis).

Ktistec is a compact, developer-friendly option for someone who wants a personal or small-group federated publishing server with rich editing, analysis tools, and scripting facilities. It emphasizes simplicity and minimal runtime dependencies while providing a broad set of social features suitable for low-volume Fediverse usage.

Mbin is a decentralized content aggregator, voting, discussion and microblogging platform that participates in the Fediverse via ActivityPub. It is a community-driven fork of kbin providing a web UI for submitting links, posts, comments and votes, and interoperates with other ActivityPub services.

Key Features

• Full ActivityPub support for federation with Mastodon, Lemmy, Pleroma, PeerTube and similar services
• Posting, link aggregation, threaded discussion, and up/down voting model for community moderation
• Web UI built with PHP and Symfony using Twig templates and JavaScript enhancements
• Docker and Docker Compose deployment options and documentation for bare-metal installations
• Multi-language support and community-driven translations via integrated localization workflow
• Code security practices with composer dependency management and regular audits

Use Cases

• Running a federated community forum or link aggregator that interoperates across the Fediverse
• Hosting a microblogging site with voting and threaded discussions similar to Reddit/Lemmy
• Integrating community-moderated content streams and magazines for niche interest groups

Limitations and Considerations

• Requires familiarity with PHP/Symfony and typical web hosting stacks for installation and maintenance
• Federation behavior can vary depending on ActivityPub implementations of other servers; interoperability nuances may require tuning
• Smaller project and ecosystem compared to some larger Fediverse implementations; administrative resources and third-party tooling are more limited

Mbin is suited for operators who want a community-focused, federated aggregator and discussion platform with active development and a focus on interoperability and usability.

Hatsu is a bridge service that lets static websites participate in the Fediverse by exposing site users and posts as ActivityPub actors and objects. It automates discovery, follow handling, posting to followers, and backfeeding replies using site feeds.

Key Features

• Maps site-level user identifiers and URLs to ActivityPub actors and object URIs for federation
• Uses site feeds (JSON / Atom / RSS) as the source of truth for create/update detection
• Automatically accepts follow requests and delivers new posts to followers' inboxes
• Receives replies from Fediverse actors and backfeeds them to the originating static site (backfeed feature is a work-in-progress)
• Performs HTTP signatures for outgoing requests to improve compatibility with secure Mastodon and GoToSocial instances
• High-performance Rust backend with Docker deployment support and aarch64 builds
• Designed to work with any static site generator and many static hosting setups

Use Cases

• Enable a static blog or website to have Fediverse accounts for authors and posts without running a full social server
• Push new site content automatically to followers on Mastodon-compatible servers
• Collect replies and interactions from the Fediverse and surface them back to a static site

Limitations and Considerations

• ActivityPub-only: does not support other social protocols such as Nostr or AT Protocol
• Some backfeed functionality is still marked as work-in-progress and may have limited features
• Compatibility nuances can exist across Fediverse implementations; HTTP signature behavior and compatibility modes are provided to mitigate interoperability issues

Hatsu provides a focused, automated bridge for static sites to participate in ActivityPub federation with minimal ongoing maintenance. It is suitable for site owners who want Fediverse presence without running a full social platform.

tootik is a federated, text-first social network that presents a minimal, text-based interface over the Gemini protocol while speaking ActivityPub for federation. It is implemented in Go, stores all instance data in a single SQLite database file, and ships as a single static executable for simple deployment.

Key Features

• Gemini-based text UI designed for low-bandwidth and accessibility-focused clients
• Implements a pragmatic subset of ActivityPub for federation with common Fediverse servers
• Three post privacy levels: public, followers-only, and mentions-only
• Support for sharing, quote posts, multi-choice polls, bookmarks and full-text search
• Communities modeled after Lemmy-style groups with follow-to-join and mention-to-thread behavior
• Account portability, follower synchronization, and account migration tools
• TLS client-certificate authentication with support for multiple client certificates and invite-only signup
• Single-file SQLite storage for easy backups and low operational overhead; binary can be built static
• Upload support for posts and avatars via the Titan upload mechanism
• Automatic deletion of old posts and compact, easily inspectable schema for educational/hacking use

Use Cases

• Run a small, privacy-minded Fediverse instance optimized for old devices or low-bandwidth connections
• Provide an accessible, text-first social layer for communities that prefer minimal interfaces and strong anonymity options
• Study or prototype ActivityPub implementations and federation workflows using a compact, readable Go codebase

Limitations and Considerations

• User interface requires a Gemini client; there is no native browser-based web UI or official mobile app
• Intentionally implements a limited subset of ActivityPub and reduces rich media to text/links, so advanced media workflows are not supported
• Single-file SQLite storage is convenient for small instances but may not scale well to very large, high-throughput deployments

tootik is a focused, lightweight alternative for federated social networking where simplicity, accessibility and privacy are primary goals. It is suitable for hobby instances, educational use and communities that prefer a non-graphical, low-bandwidth interface.

Mitra is a self-hosted, federated microblogging platform built on ActivityPub for publishing and following posts across the Fediverse. It aims to be lightweight while still offering modern social features and compatibility with common Mastodon-style clients.

Key Features

• ActivityPub federation with interoperability across many Fediverse services
• Mastodon-compatible REST API (with some additional Mitra-specific endpoints)
• Rich posting features including quote posts, reactions, polls, custom emojis, and Markdown-style formatting
• High default character limit (5000)
• Account migration support, including detaching identity from a specific server
• Optional content subscriptions for private posts with monthly payments (supports Monero)
• Federation support over Tor and/or I2P
• Small memory footprint target and low system requirements for single-user/small instances

Use Cases

• Running a personal or community microblogging instance that federates with the wider Fediverse
• Hosting a lightweight alternative with Mastodon-client compatibility for web, mobile, and CLI apps
• Offering subscriber-only posts with privacy-focused payments

Limitations and Considerations

• Client-facing APIs beyond the Mastodon-like endpoints may change, and some APIs are explicitly noted as unstable
• IPFS integration is experimental and not actively maintained

Mitra is well-suited for operators who want a compact ActivityPub server with strong interoperability, modern posting features, and optional monetization. Its focus on lightweight operation and federation-friendly capabilities makes it a flexible choice for small to mid-sized deployments.

Yarn.social is a decentralized social networking platform built around the Twtxt format (with optional extensions). It provides a self-hosted “pod” server (yarnd) with a web UI and API, designed to be privacy-first with no ads or tracking.

Key Features

• Twtxt-based microblogging (“twts”) with optional extensions (e.g., subjects and hashes for threads)
• Decentralized, pull-based model where users follow feeds across pods
• Web interface plus a built-in HTTP API for clients and integrations
• Command-line client (yarnc) for posting and interacting with a pod
• Supports single-user or multi-user pods with configurable registrations and profiles
• Media uploads supported when ffmpeg is available

Use Cases

• Run a small private social space for a team, family, or community
• Participate in the wider Twtxt/Yarn ecosystem while keeping data on your own pod
• Build alternative clients or tooling using the pod API

Limitations and Considerations

• Some features (e.g., media handling) require extra system dependencies such as ffmpeg
• Federation/discovery depends on external feeds and the pull-based follow model rather than push federation

Yarn.social fits users who want a lightweight, transparent social platform centered on plain-text feeds and user-controlled hosting. It works well both as a full pod server with accounts and as part of a broader Twtxt-compatible ecosystem.

Snac is a minimal ActivityPub server implementation written in portable C. It provides basic federated social networking features with very small runtime dependencies and a simple, JavaScript-free web interface.

Key Features

• Implements core ActivityPub/ActivityStreams operations for publishing, following, replying, liking/boosting and private messages.
• Multiuser support with local account management and man-page style documentation for administration.
• Very small dependency footprint: written in C and depends only on libcurl and OpenSSL at build/runtime.
• Optional compatibility layer for the Mastodon API (can be compiled out with a build flag).
• No external database required; server stores data on disk and uses compact internal formats.
• Minimal, accessible web UI (no JavaScript, no cookies) and examples for Docker + nginx deployment.
• Designed for interoperability with other Fediverse software and lightweight hosts (Raspberry Pi and small VPSes).

Use Cases

• Host a small, low-resource federated social instance for a personal community or project team.
• Run a privacy-focused or resource-constrained Fediverse node where minimal dependencies and no DB are desirable.
• Provide an ActivityPub-compatible backend for Mastodon-compatible clients in small deployments.

Limitations and Considerations

• Mastodon API support is indicated as work in progress and may not implement every endpoint or behavior expected by all Mastodon clients.
• No built-in TLS termination: the daemon is intended to run behind a TLS-capable web server or reverse proxy (examples use nginx).
• The "no database" design simplifies operation but can limit scalability and some advanced features compared with full-featured, database-backed Fediverse servers.
• The web UI is intentionally minimal; some advanced client workflows (rich media management, complex moderation UIs) are limited or absent.

Snac is a pragmatic, low-footprint ActivityPub server focused on simplicity, portability and interoperability. It is well-suited for hobbyists, small communities and constrained environments where minimal runtime requirements and straightforward administration are priorities.

Iceshrimp.NET is a decentralized and federated social networking service that implements the ActivityPub standard. It continues the legacy of the Iceshrimp project with a new codebase focused on performance, stability, and maintainability.

Key Features

• ActivityPub federation for decentralized social networking
• Resource-efficient backend built on .NET
• Web frontend built with Blazor WebAssembly
• Configurable, HTML-only public preview for unauthenticated visitors
• Mastodon-compatible API intended to work with a broad range of Mastodon clients
• Migration path for existing Iceshrimp-JS instances

Use Cases

• Run a community-focused fediverse instance for an organization or interest group
• Host a personal or small-community social server while remaining compatible with common Mastodon clients
• Experiment with ActivityPub federation and client interoperability in a .NET-based stack

Limitations and Considerations

• Client compatibility depends on the Mastodon-compatible API surface and may vary by client features
• As an actively developed new codebase, features and behavior may change between releases

Iceshrimp.NET is a solid option for operators who want an ActivityPub server with a modern .NET backend and a Blazor-based web UI, prioritizing performance and long-term maintainability.

Akkoma is a specialised fork of Pleroma that implements the ActivityPub protocol to operate as a federated social network. It emphasizes expressive posting (Misskey-flavored markdown, rich reactions) and supports multiple frontends and compatibility with other fediverse servers.

Key Features

• Implements ActivityPub for federation with other fediverse services.
• Misskey-flavoured Markdown and rich post formatting for animated/rich markup.
• Custom emoji reactions and unlimited attachments per post.
• Multiple frontends supported (default Pleroma-FE plus optional Mastodon-style frontend and third-party frontends).
• Unlimited post edits, quoting, polls, and list-based timeline customization.
• Performance and operational tooling: Elixir/Phoenix-based backend, PostgreSQL, background job processing and S3-compatible uploads; Docker and docker-compose resources are provided for deployment and testing. (akkoma.social)

Use Cases

• Host a community-oriented federated social network instance with expressive post features.
• Experiment with fediverse UX and frontends (Mastodon-style and Pleroma/Akkoma-specific frontends).
• Migrate or fork existing Pleroma installations to a project with faster development cadence and additional formatting/reaction features.

Limitations and Considerations

• Real-time chat functionality was deliberately removed compared to some Pleroma forks; Akkoma focuses on ActivityPub timeline and posting features rather than integrated chat. (akkoma.social)

Akkoma is a developer- and community-driven Elixir/Phoenix project intended for operators who want an expressive, ActivityPub-compatible server with multiple frontend options and performance-focused improvements. It is maintained with tooling and deployment resources (Docker, compose, nginx config and CI) to support instance operators and contributors. (akkoma.dev)