What Is Decentralized Social Media?
Decentralized social media spreads a social network across many independent servers that talk to each other over an open protocol, instead of one company running everything.
Mastodon, Pixelfed, Lemmy, PeerTube, Bluesky and Nostr are the working examples.
You gain control over your account and your moderation, and you give up the reach, search and polish of a centralized app.
Decentralized social media is social networking that runs on many independent servers instead of inside one company's platform. Your account lives on a server you picked, or one run by someone you trust, and that server exchanges posts with thousands of other servers over an open protocol. You can follow, reply to and boost people whose accounts live somewhere else entirely, the same way you can email someone whose address ends in a different domain than yours.
There is no head office. No single company holds the whole user list, sets one ranking algorithm for everybody, or can change the terms for the entire network on a Tuesday morning. That is the appeal, and the source of nearly every tradeoff. This guide covers how the plumbing works, the three designs in real use, what changes day to day, and the parts that are honestly worse than a big centralized app.
The short answer, and what it replaces
A centralized social network is one company running one database. Facebook, Instagram, TikTok and X each own the accounts, the posts, the follow graph and the code that decides what you see. If you disagree with a rule, there is one place to appeal, and it rarely answers.
Decentralized social media splits that job across servers run by different people. Each server, often called an instance, holds its own accounts, posts, storage bill and rules, and passes posts back and forth with the others. The network is the sum of those connections, not a product owned by anyone.
The comparison most people find useful is email. Your address ends in one domain and your friend's in another, but you can still write to each other, because both mail servers speak the same protocol. Nobody owns email. Decentralized social media applies that idea to timelines, photos, video and forums.
Your ability to keep posting then depends on your server staying up and staying reasonable, rather than on one company's good graces. That is one concrete form of data sovereignty: the machine holding your words is one you or your neighbours can actually reach.
How federation actually works
Sign up on a server and you get a handle with two parts, like @[email protected]. The first part is your name, the second is the server holding your account, and together they are your address on the network.
When you post, your server does not push it to a global feed. It works out which servers your followers live on and delivers a copy to each. Those servers store the copy and show it in their timelines. A reply travels back the same way. Nothing passes through a central switchboard.
That delivery model explains most of the odd behaviour newcomers notice. Your timeline holds only what your server has already received, so a post from a stranger nobody on your server follows may simply not be there. Reply threads can look incomplete and follower counts drift, because servers have seen different amounts of history.
Admins also control which other servers they talk to. An admin can defederate from a server hosting spam or harassment, and every account on their server stops receiving it. That is a powerful moderation tool and a political one, because the admin makes that call on your behalf.
Three designs in real use: ActivityPub, AT Protocol and Nostr
ActivityPub is a W3C standard and the most widely deployed of the three. Servers exchange signed copies of posts directly. The software includes Mastodon and GoToSocial for microblogging, Akkoma and Misskey for the same job with different cultures, Pixelfed for photos, PeerTube for video and Lemmy for forums. Because they share a protocol, a Mastodon account can follow a PeerTube channel and see new videos in an ordinary timeline.
AT Protocol is the design behind Bluesky. Your posts live in a personal data server, a relay collects the firehose, and separate app views build feeds and search from it. Identity is genuinely portable, and a domain you own can be your handle. In practice most people sit on one company's data server and one relay, so it behaves more centrally than the architecture requires.
Nostr has no accounts on servers at all. Your identity is a cryptographic keypair, your client signs each post, and relays such as strfry accept and rebroadcast signed events. Nobody can deplatform a key. The flip side is blunt: lose the private key and the identity is gone, with no reset link.
Matrix is the neighbour worth knowing: federated chat rather than social media, same idea, encrypted end to end by default.
What changes day to day
The first thing people notice is the timeline. On the ActivityPub side it is chronological by default: posts from people you follow, newest first, nothing inserted. No engagement ranking is working to keep you scrolling, which makes the feed quieter and, at first, emptier. Bluesky adds algorithmic feeds, but they are opt-in and you pick between many.
There are no ads, so nobody needs the tracking apparatus that goes with selling attention. Servers are paid for by admins, donations or members instead, which is a different set of incentives and a different set of failure modes. Norms differ too: content warnings and image alt text are expected rather than optional on most Mastodon-style servers.
| Centralized app | Decentralized network | |
|---|---|---|
| Who sets the rules | One company, globally | Your server admin, locally |
| Feed order | Ranked for engagement | Chronological, or a feed you chose |
| Ads and tracking | Core business model | None; costs paid directly |
| Moving your account | Not possible | Followers move; old posts do not |
| Search and discovery | Strong | Weak, often opt-in only |
Who moderates, and who pays the bill
Somebody is paying for the server your account sits on: a machine, a database, object storage for images and video, bandwidth and a domain. Media is the cost that surprises people: a server caches copies of remote images and video its users have seen, so storage grows with your community's reading habits, not just its posting.
Most servers run on donations, a membership fee, an Open Collective, or one person quietly absorbing the cost. Ask which before you sign up; it tells you how long the server is likely to last. No funding model plus one exhausted admin is the most common way people lose an account here, and it has nothing to do with the technology.
Moderation is the harder cost: unpaid emotional labour at inconvenient hours, and it does not scale by adding servers. Small servers with clear rules and two or three active moderators tend to be better moderated than very large ones, which is the opposite of what people assume.
Governance is worth settling early. A server run by one benevolent admin works until that person changes their mind. One that publishes its rules, its budget and how decisions get made is far more durable. Communities that want members to vote on rules or spending can run verifiable ballots with software like Folkmoot.
Where decentralized social media is genuinely worse
Discovery is weak. There is no global index, so finding people is slow. Full-text search is limited and often opt-in per account, and hashtags do work a search engine would otherwise do. If your reason for being on social media is reach, this will frustrate you.
Direct messages are not private in the way you expect. On ActivityPub servers a DM is a post with a restricted audience. It is stored in plain text on your server and the recipient's, and an admin at either end can read it. Nothing is end to end encrypted. Use Signal or Matrix for anything sensitive, and treat a fediverse DM as a postcard.
Deletion is best effort. Once a post has been copied to fifty servers, deleting it sends a delete request to fifty servers. Well-behaved software honours it; software that is offline, out of date or hostile may not. Assume anything you publish is permanent. Your data is also only as safe as your admin's backups.
Onboarding is genuinely harder. Being asked to choose a server before you know what any of them are is a real barrier, and pretending otherwise helps nobody. Moderation quality varies enormously, so a bad first pick can sour the whole network for you.
What it takes to run your own server
Running an instance is a real commitment. Mastodon is the heaviest of the common options: Ruby, PostgreSQL, Redis and background job workers, plus Elasticsearch if you want search. GoToSocial and Akkoma are much lighter and run happily on a small machine for a handful of users. Pixelfed, PeerTube and Lemmy each bring their own storage profile; PeerTube will eat disk.
Three things bite new admins. Media storage grows on its own as your users follow accounts elsewhere, so plan for object storage and a cache policy. Outbound email for sign-ups and password resets is the classic hidden problem, because a fresh server's mail lands in spam until it earns reputation. Upgrades are frequent, sometimes with database migrations that need a maintenance window.
The honest version: a one-person server for one person is a second job with no users. A shared server for a neighbourhood, a workplace or a co-op is where the effort pays off, because cost and moderation are split among people who already know each other.
The same reasoning applies to mail, files and photos. Our step-by-step guide to leaving Google covers that ground, and how mesh networks work covers the layer underneath.
How to try it without burning your existing accounts
Choose a server rather than agonising over one. Look for three things on its about page: a published moderation policy, a stated funding model, and an admin who posts like a human being. Mid-size servers, a few thousand accounts rather than a few hundred thousand, tend to balance stability against actual moderation best.
Do not delete anything yet. Keep the old accounts, cross-post for a while, and watch where the replies come from. Then follow forty or fifty people before you judge the experience. A chronological timeline with eight accounts in it looks like a dead network because it is one.
Export your follow list as CSV every so often. On Mastodon-style servers that file is your escape hatch: if the server closes or the admin turns unpleasant, you import it elsewhere and keep your network. Try one format at a time, Pixelfed for photos or Lemmy for forum threads, rather than replacing everything at once. More guides are in our learn section.
One thing to be clear about, since the two often get mixed up: off-grid LoRa radio mesh, like the hardware from Blackout Labs, carries short text messages when the internet is down. It is not a way to run social media without an internet connection.
Frequently asked questions
Is decentralized social media the same as the fediverse?
Not quite. The fediverse is the group of servers that speak ActivityPub, so Mastodon, Pixelfed, PeerTube and Lemmy are all part of it. Decentralized social media is the broader category, and it also covers systems built on other designs, such as Bluesky on the AT Protocol and Nostr, which do not federate with the fediverse.
Do I need to run my own server to use decentralized social media?
No. Almost everyone joins a server someone else already runs, exactly as most people use an email provider rather than hosting mail themselves. Running your own instance gives you full control over rules and data, but it means paying for hosting, applying upgrades, keeping backups and handling moderation yourself. Start as a user first.
Can I move my account to another server later?
On Mastodon-style servers, yes for your followers. You set up the new account, point the old one at it, and your followers are moved across automatically. Your old posts normally stay behind on the old server rather than travelling with you. Export your follow list and block list as CSV first, since those imports fill most of the gap.
Are direct messages private on decentralized social media?
On ActivityPub servers, no. A DM is just a post with a restricted audience, stored unencrypted on your server and on the recipient's server, and administrators at either end can read the database. There is no end-to-end encryption. For anything sensitive use Signal, or Matrix, which encrypts by default and is still federated.
Is Bluesky actually decentralized?
The AT Protocol it runs on is designed to be, with personal data servers, relays and app views as separate roles that anyone can operate. Today most users sit on infrastructure run by one company, so it feels centralized in practice. The portable identity is real, though, and using a domain you own as your handle is a genuine advantage.
What happens to my posts if my server shuts down?
Copies already delivered to other servers stay there, but your account, your archive and your ability to post go away with the machine. This is the most common way people lose a presence in this world. Pick a server with a stated funding model, export your data periodically, and treat any single server as impermanent.