The Fediverse is a decentralized network of interconnected social platforms where anyone can run their own server (instance) and users across different servers can interact. Unlike centralized platforms, you control your data, your community rules, and your server’s destiny.

While Mastodon is the most well-known Fediverse platform, it is not the only option. Misskey and its derivatives offer a very different social networking experience with unique features, while Akkoma provides a lightweight, privacy-focused alternative. This guide covers all three with deployment instructions and feature comparisons.

Quick Comparison

FeatureMisskeyMastodonAkkoma
GitHub Stars11,142+49,930+Self-hosted (Codeberg)
Last UpdatedMay 2026May 2026Active development
LanguageTypeScript (Node.js)Ruby on RailsElixir/Phoenix
Primary FocusRich social platformMicrobloggingLightweight microblogging
Federation ProtocolActivityPubActivityPubActivityPub
Timeline TypesHome, Local, Hybrid, GlobalHome, Local, FederatedHome, Local, Federated
ReactionsEmoji reactions (unlimited)Favorites + bookmarksEmoji reactions
Renotes (Quote Posts)Yes, with optional commentsBoost + quote tweetsBoost + quote posts
Custom EmojiPer-instance + per-userPer-instancePer-instance
Drive (File Storage)Built-in file managerMedia attachments onlyMedia attachments
ChannelsTopic-based content streamsNoNo
Antenna SystemKeyword-based content filtersNoNo
Resource UsageModerate (Node.js + PostgreSQL + Redis)Heavy (Ruby + PostgreSQL + Redis)Light (Elixir + PostgreSQL)
Docker SupportOfficial compose exampleOfficial Docker imageThird-party Docker images
LicenseAGPLv3AGPLv3AGPLv3

Misskey — Feature-Rich Decentralized Social Platform

Misskey is a Japanese-originated decentralized social platform that has grown into one of the most feature-rich options in the Fediverse. With over 11,000 GitHub stars, it offers capabilities that go far beyond simple microblogging.

Key Features

  • Rich Post Types: Text, images, polls, renote (quote posts), and reactions with unlimited custom emoji
  • Timeline Variety: Home, Local, Social (hybrid), and Global timelines give you different content views
  • Antenna System: Create custom content feeds based on keywords, users, hashtags, and sources
  • Channels: Topic-based content streams separate from your main timeline — think of them as sub-forums within your instance
  • Drive: Built-in file storage and management for all uploaded media, with folder organization
  • Pages: Create static pages on your profile (similar to a personal website or wiki)
  • Games: Built-in mini-games including Reversi that work across federated instances
  • Themes: Extensive UI theming system with custom CSS support
  • Moderation Tools: Robust instance-level moderation with silence, suspension, and relay configuration
  • Federation: Full ActivityPub support — interact with Mastodon, Pleroma, Akkoma, and other Fediverse servers

Docker Compose Deployment

Misskey requires PostgreSQL and Redis. The official compose example provides a solid starting point:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
services:
  web:
    build: .
    restart: always
    depends_on:
      db:
        condition: service_healthy
      redis:
        condition: service_healthy
    ports:
      - "3000:3000"
    networks:
      - internal_network
      - external_network
    volumes:
      - ./files:/misskey/files
      - ./.config:/misskey/.config:ro

  redis:
    restart: always
    image: redis:7-alpine
    networks:
      - internal_network
    volumes:
      - ./redis:/data
    healthcheck:
      test: "redis-cli ping"
      interval: 5s
      retries: 20

  db:
    restart: always
    image: postgres:15-alpine
    networks:
      - internal_network
    environment:
      POSTGRES_USER: misskey
      POSTGRES_PASSWORD: your_secure_password
      POSTGRES_DB: misskey
    volumes:
      - ./db:/var/lib/postgresql/data
    healthcheck:
      test: "pg_isready -U misskey"
      interval: 5s
      retries: 20

networks:
  internal_network:
    internal: true
  external_network:

The .config/default.yml file configures the instance URL, database credentials, and federation settings. After building with docker compose up -d, access your instance at http://localhost:3000 and create the admin account through the first-run setup.

Best For

Misskey is ideal for users who want a rich, customizable social experience. Its antenna system, channels, and drive features make it more than just a microblogging platform — it is a full social networking environment.

Mastodon — The Standard-Bearer of Decentralized Social

Mastodon is the most widely deployed Fediverse platform and the gateway for most users entering decentralized social networking. Its familiar Twitter-like interface makes it easy for newcomers to understand.

Key Features

  • Familiar Interface: Three-column layout (home timeline, notifications, compose) that mirrors mainstream social platforms
  • Content Warnings: Built-in content warning system for sensitive topics
  • Polls: Create time-limited polls in posts
  • Lists: Curate custom timelines from specific accounts
  • Instance Relay: Share public posts between instances without full federation
  • Strong Moderation: Per-instance moderation with domain blocking, silence, and suspension
  • Accessibility: Robust screen reader support and keyboard navigation
  • Mobile Apps: Official apps for iOS and Android, plus numerous third-party clients

Docker Deployment

Mastodon provides an official Docker image with an interactive setup wizard:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
services:
  web:
    image: ghcr.io/mastodon/mastodon:latest
    restart: always
    env_file: .env.production
    ports:
      - "3000:3000"
    depends_on:
      - db
      - redis
    volumes:
      - ./public/system:/mastodon/public/system

  streaming:
    image: ghcr.io/mastodon/mastodon:latest
    restart: always
    env_file: .env.production
    ports:
      - "4000:4000"
    command: node ./streaming
    depends_on:
      - db
      - redis

  sidekiq:
    image: ghcr.io/mastodon/mastodon:latest
    restart: always
    env_file: .env.production
    command: bundle exec sidekiq
    depends_on:
      - db
      - redis

  db:
    image: postgres:15-alpine
    restart: always
    environment:
      POSTGRES_USER: mastodon
      POSTGRES_PASSWORD: secure_password
      POSTGRES_DB: mastodon
    volumes:
      - ./postgres:/var/lib/postgresql/data

  redis:
    image: redis:7-alpine
    restart: always
    volumes:
      - ./redis:/data

Run docker compose run --rm web bundle exec rake mastodon:setup to generate the configuration file and create the admin account.

Best For

Mastodon is the best choice for users who want the largest Fediverse experience — the most instances, the most users, the most third-party tools and apps. Its familiar interface reduces the learning curve for newcomers.

Akkoma — Lightweight, Privacy-Focused Microblogging

Akkoma is a fork of Pleroma, designed to be a lightweight, fast, and privacy-respecting Fediverse server. Written in Elixir, it runs efficiently on minimal hardware while providing a full social networking experience.

Key Features

  • Lightweight: Elixir/Phoenix architecture handles thousands of concurrent users on modest hardware
  • MST API: Compatible with Mastodon’s API, enabling most Mastodon clients to work with Akkoma
  • Rich Media: Support for various media types including polls, emoji reactions, and rich text formatting
  • Federation: Full ActivityPub support with configurable federation policies
  • Customization: Extensive per-user and per-instance customization options
  • Low Resource Usage: Significantly lower RAM and CPU requirements compared to Mastodon
  • Privacy Focus: Granular privacy controls and federation policy management

Docker Deployment

Akkoma can be deployed using community-maintained Docker images:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
services:
  akkoma:
    image: akkoma/akkoma:latest
    restart: always
    ports:
      - "4000:4000"
    environment:
      - AKKOMA_INSTANCE_HOST=your-domain.example.com
      - AKKOMA_DB_HOST=db
      - AKKOMA_DB_NAME=akkoma
      - AKKOMA_DB_USER=akkoma
      - AKKOMA_DB_PASS=akkoma_password
      - AKKOMA_ADMIN_EMAIL=admin@example.com
    depends_on:
      - db
    volumes:
      - ./uploads:/opt/akkoma/uploads

  db:
    image: postgres:15-alpine
    restart: always
    environment:
      POSTGRES_USER: akkoma
      POSTGRES_PASSWORD: akkoma_password
      POSTGRES_DB: akkoma
    volumes:
      - ./postgres:/var/lib/postgresql/data

After starting, run the initial setup wizard to configure your instance details, admin account, and federation settings.

Best For

Akkoma is ideal for users who want a lightweight Fediverse server with low resource requirements. Its Elixir foundation means it can serve a large community on a small VPS that would struggle to run Mastodon.

Why Self-Host Your Social Platform?

Data Sovereignty: On a self-hosted Fediverse instance, you control every piece of data — user profiles, posts, media uploads, and interaction history. No corporate algorithm decides what you see. No advertising system monetizes your attention. No data broker sells your social graph.

Community Governance: Each Fediverse instance sets its own rules. You decide what content is allowed, who can register, and how moderation works. Small communities can thrive without the pressure of platform-wide policies designed for millions of strangers.

Federation Freedom: Your instance connects to the broader Fediverse, so your users can interact with people on Mastodon, Misskey, Pleroma, Pixelfed, Lemmy, and hundreds of other platforms. But you control which instances you federate with — block harmful communities at the server level.

No Account Bans or Service Shutdowns: When you host your own instance, no central authority can suspend your account or shut down the service. As long as your server runs, your community persists.

Cost-Effective: A small VPS (2GB RAM, 1 vCPU) can host a community of 100-500 users on Misskey or Akkoma. The monthly cost is a fraction of what cloud platform subscriptions would run.

For a broader introduction to decentralized social networking, see our Fediverse guide. For setting up HTTPS and security, check our TLS certificate automation guide.

Which Platform Should You Choose?

  • Choose Misskey if you want the most features and customization options. Its antenna system, channels, drive, and pages make it the most versatile Fediverse platform for users who want more than just microblogging.

  • Choose Mastodon if you want the largest ecosystem — most instances, most users, most third-party apps and tools. Its familiar interface makes it the easiest onboarding path for newcomers to the Fediverse.

  • Choose Akkoma if you need a lightweight server with low resource requirements. Its Elixir architecture handles high traffic on minimal hardware, making it perfect for budget-conscious deployments or small VPS setups.

All three platforms support ActivityPub federation, meaning users on any of them can interact with users on all the others. You are not locked into one ecosystem.

FAQ

Can users on different Fediverse platforms communicate with each other?

Yes. Misskey, Mastodon, and Akkoma all implement the ActivityPub protocol. A user on your Misskey instance can follow, reply to, and boost posts from users on Mastodon, Akkoma, Pixelfed, and any other ActivityPub-compatible server. Federation is automatic — no manual configuration is needed for basic interoperability.

How many users can a self-hosted instance support?

It depends on the platform and hardware. Akkoma (Elixir) can serve 500+ users on a 2GB VPS. Misskey (Node.js) handles 100-300 users comfortably on similar hardware. Mastodon (Ruby) is the most resource-intensive, typically supporting 50-200 users on 2GB RAM. For larger communities, scale up PostgreSQL and add Redis caching.

Do I need a domain name to run a Fediverse instance?

Yes. Fediverse federation relies on domain-based identity (e.g., @username@example.com). You need a registered domain name pointed at your server’s IP address. Let us Encrypt provides free TLS certificates, and tools like cert-manager automate renewal.

Can I migrate my account between instances?

Mastodon supports account migration between Mastodon instances — you can move your followers and following list to a new server. Misskey has its own migration tools. Cross-platform migration (e.g., Mastodon to Misskey) is more limited, as each platform stores different data structures.

How do I moderate a self-hosted Fediverse instance?

All three platforms provide admin panels with user management, content moderation, and federation controls. You can silence or suspend users, block entire domains, configure federation policies (allowlist, blocklist, or open), and review reports. Misskey additionally offers relay configuration to control which public content flows through your instance.

Yes. Running a social networking server is legal in virtually all jurisdictions. However, you are responsible for the content hosted on your server and must comply with local laws regarding content moderation, data protection (GDPR in Europe), and illegal content removal. Most instance administrators publish clear community guidelines to set expectations.