Analytics cookies only (Google Analytics, PostHog). No ad networks, no cross-site tracking. See our privacy policy.
A free, open-source federated microblogging platform that speaks ActivityPub, so its users can follow and be followed from Mastodon and the rest of the Fediverse. A server is the Node.js app plus PostgreSQL and Redis, and full-text search can be switched from the default SQL-like matching to PGroonga or Meilisearch.
Runs on a VPS from $12/mo (Kamatera 4GB, 4 GB RAM) · prices checked Nov 2026
Fits home hardware (464 MB measured idle, RAM only): Raspberry Pi 4 (4 GB) (arm64 untested), Raspberry Pi 5 (8 GB) (arm64 untested), Repurposed laptop (8 GB), Intel N100 mini PC (16 GB), AMD Ryzen mini PC (32 GB).
Pick Misskey when you want a Fediverse microblog that is not Mastodon: it is a free, open-source platform that federates over ActivityPub, so its users can follow and be followed from Mastodon and the rest of the network. It is AGPL-3.0, and the snippet pins the Docker Hub image `misskey/misskey:2026.10.1`, released 2026-10-23, adapted from the project's `compose_example.yml` and `docker_example.yml`. The stack is the Node.js server plus PostgreSQL and Redis, three containers, and full-text search starts as plain SQL matching with PGroonga and Meilisearch as options. Upstream gives no RAM minimum, so our 2 GB floor is an estimate based on that three-service layout. In this catalog Mastodon is the established server with the largest ecosystem and the same 2 GB estimate; GoToSocial is the lighter single-binary option that leaves posting to other apps; Lemmy is a link aggregator, and WriteFreely is for blogging. Misskey is the one to try if you prefer its own web client and settings over the Mastodon model.
Paid link — we earn a commission if you shop through it.
Run these commands on your server:
# Misskey — federated microblogging — adapted from the project's compose_example.yml and .config/docker_example.yml (published image instead of a local build), pinned to 2026.10.1
mkdir -p misskey/.config misskey/files misskey/db misskey/redis && cd misskey
sudo chown -R 991:991 files
DB_PASS=$(openssl rand -hex 24)
SETUP_PASS=$(openssl rand -hex 16)
cat > .config/docker.env <<EOF
POSTGRES_USER=misskey
POSTGRES_PASSWORD=$DB_PASS
POSTGRES_DB=misskey
EOF
# url must be the address people will really use, and cannot be changed after the first start; replace localhost with your domain (https) before federating
cat > .config/default.yml <<EOF
url: http://localhost:3000/
port: 3000
setupPassword: $SETUP_PASS
db:
host: db
port: 5432
db: misskey
user: misskey
pass: $DB_PASS
dbReplications: false
redis:
host: redis
port: 6379
fulltextSearch:
provider: sqlLike
id: 'aidx'
EOF
cat > compose.yml <<'EOF'
services:
web:
image: misskey/misskey:2026.10.1
restart: always
depends_on:
db:
condition: service_healthy
redis:
condition: service_healthy
ports:
- "3000:3000"
volumes:
- ./files:/misskey/files
- ./.config:/misskey/.config:ro
redis:
restart: always
image: redis:7.4.10-alpine
volumes:
- ./redis:/data
healthcheck:
test: "redis-cli ping"
interval: 5s
retries: 20
db:
restart: always
image: postgres:18.4-alpine
env_file:
- .config/docker.env
volumes:
- ./db:/var/lib/postgresql
healthcheck:
test: "pg_isready -U $$POSTGRES_USER -d $$POSTGRES_DB"
interval: 5s
retries: 20
EOF
docker compose up -d
timeout 300 bash -c 'until curl -fsS -o /dev/null http://localhost:3000/healthz; do sleep 3; done'
# → http://SERVER_IP:3000 (first visit asks for the setup password, which is the setupPassword line in .config/default.yml; federation needs a real domain with HTTPS in front)Misskey's example configuration is blunt about what to settle before the first start:
Misskey used 464 MB of RAM at idle on GCP e2-standard-2 · Ubuntu 26.04 LTS · Docker 29.9.3 (first boot, measured Nov 2026). We list a minimum of 2048 MB.
The Misskey install snippet is marked verified on Ubuntu 26.04 (Nov 2026).