30 self-hosted Twitter alternatives

Last reviewed Aug 26, 2026 · 469 words

You cannot self-host an audience. That is the uncomfortable core of every "leave Twitter" guide: the software is replaceable, the network effect is not, and anyone who moved to the fediverse expecting their reach to follow has been disappointed. What self-hosting gets you instead is an identity nobody can suspend, rename, or algorithm into oblivion - your handle on your domain, federating with millions of accounts over ActivityPub.

What you gain and what you give up

Gained: ownership of your handle and post history, chronological timelines, real moderation control, and an exit that works - fediverse accounts can migrate between servers and take their followers along, which is precisely the move Twitter never allowed. Given up: the audience, quote-tweet culture, DM ubiquity, and trending discovery. Fediverse search and discovery remain deliberately weaker than Twitter's, partly by design. Also given up: your evenings, occasionally, because federation means running a public server that strangers' servers talk to, with the moderation and patching duties that implies.

Which replacement fits which user

Hosting for a community: Mastodon (50,252 stars) is the standard, with the deepest app ecosystem and moderation tooling, but it is a Hard install - Ruby, Postgres, Redis, Sidekiq - wanting 2 GB of RAM before your first toot. Same idea on half the hardware: Pleroma runs in 512 MB, speaks the Mastodon client API, and suits a small instance on a cheap VPS, at the cost of a smaller community and rougher admin tools. Just you, no roommates: Microblog.pub is a single-user ActivityPub server in 256 MB, and snac is the minimalist extreme - plain C, no database, happy in 64 MB. I run single-user precisely because moderating strangers is the part of Twitter I wanted to quit.

What survives the move

Nothing, functionally. Twitter's archive download hands you every tweet as data, and you should request it before deleting anything, but no fediverse server imports it as live, dated posts - it is a backup, not a migration. Followers do not transfer from Twitter at all; you rebuild from zero. This is why the standard advice is to move once: pick a server (or host one), post your new address in your Twitter bio for a month, and accept the reset. Migration within the fediverse, by contrast, genuinely moves followers - so a wrong first choice of server is cheap to fix later.

The default pick

Most people should not start by hosting Mastodon - 2 GB of always-on Ruby for one account is a bad trade. Join an established instance to learn the culture, then self-host the single-user way: snac if you want the smallest possible footprint, Microblog.pub if you want something friendlier. Host full Mastodon only when actual other humans are moving in.