Is Bluesky decentralized? Federation and data portability
Bluesky is designed so that every piece of the network can be run by someone else, and your account can move to another server with its identity, its followers and its posts. Today, Bluesky Social PBC still runs important shared pieces, such as the main relay and the AppView, while other companies and people run their own servers alongside.
Last reviewed on November 14, 2026
Decentralised does not mean that nobody runs anything. On Bluesky, it means that each job on the network is done by a separate kind of service, that more than one operator can run each of them, and that your account is not tied to any one of them.
What can be swapped
Each piece described in How Bluesky works is a separate service, and none of them has to be run by Bluesky Social PBC:
- Your PDS, the server that hosts your account. You can choose another host, or run your own.
- The relay, which merges the updates of many PDSes into one stream. Its software is open source, and there is more than one implementation.
- The AppView, which builds timelines and threads. Repositories are public, so anyone can index the same data and present it differently.
- Feed generators and labelers, which anyone can run, and which you pick one by one.
- The app you read Bluesky with: the official app is one client among several.
What ties it all together is your DID, the permanent identifier of your account. It does not belong to any of these services, which is what lets you move between them.
Moving to another PDS
The PDS is the piece that holds your data, so changing it is the move that matters most. Your DID stays the same, so your followers, your posts and your likes stay attached to your account: from your followers' point of view, your profile is still there, under the same handle if it is on your own domain.
- New accountCreated on the new PDS with the same DID, switched off for now.
- Copy the dataRepository, media files and preferences go to the new PDS.
- Update the DIDThe DID document now names the new PDS, signed with a rotation key.
- Switch overThe new account goes live, and the old one is switched off.
Stays the same
- Your DID
- Your followers and your posts
- A handle on your own domain
A move copies three kinds of data from the old PDS to the new one:
- your public repository: your posts, likes, follows and other records;
- your media files, the blobs, one by one;
- your private preferences, the settings your PDS keeps for apps.
Then the DID document is updated to name the new PDS, the new account is switched on and the old one is switched off. Tools do these steps for you, such as goat, Bluesky's command-line tool, or community-made ones.
Some things do not move:
- A handle ending in
.bsky.socialcomes with Bluesky's hosting, so it does not follow you: you choose a new handle on the new PDS. A handle on your own domain does follow. - Only what your PDS holds is copied. What other services keep about you stays with them.
- The new PDS has to accept you. Some ask for an invite code or a check before they create an account, and
bsky.socialonly takes back accounts that started there.
Going deeper. The protocol's account migration guide lists the main calls:
com.atproto.server.createAccounton the new PDS,com.atproto.sync.getRepothencom.atproto.repo.importRepofor the repository,com.atproto.identity.signPlcOperationon the old PDS andcom.atproto.identity.submitPlcOperationthrough the new one, thencom.atproto.server.activateAccounton the new PDS andcom.atproto.server.deactivateAccounton the old one.
Rotation keys and recovery
With a did:plc identity, the right to change your DID document belongs to a few rotation keys. Your PDS usually holds one, which is why a normal move asks the old PDS to sign the update, after a code sent to your email. You can also add a rotation key of your own, kept somewhere safe such as a password manager.
That key is what makes recovery possible. If your PDS shuts down or stops cooperating, a rotation key of your own lets you point your DID to a new PDS without its help, and a backup of your repository brings your posts back. Without a backup or a public mirror, the account still works on the new PDS, but its old posts are missing. And if a wrong or hostile update gets through, a higher-priority rotation key can undo it within 72 hours.
A did:web account can change PDS too: whoever controls its domain updates the DID document published there. Its limit is the domain itself: losing the domain means losing the identity.
Running your own PDS
Bluesky publishes its PDS software as open source, with install steps and Docker images. Other teams have written their own, such as Tranquil, in Rust, and Cocoon, in Go. A PDS for yourself or a small group needs a server and a domain name, and you take care of it like any other server.
Since February 2024, Bluesky's services have accepted accounts hosted on independent PDSes. Bluesky's relay applies default limits to a new PDS, such as a maximum number of accounts, to limit abuse, and raises them on request for hosts that grow. The protocol's self-hosting guide is the place to start.
Who runs what today
The design lets anyone run every piece, but the network still depends on Bluesky Social PBC for some of them. This is the picture in November 2026, from Bluesky's own announcements and documentation:
- Bluesky runs the PDSes where its sign-up puts new accounts by default, behind the
bsky.socialentryway; the main relay,bsky.network, which moved to a new implementation in January 2026; the AppView that serves the Bluesky API; and Jetstream. In August 2026, it gathered this infrastructure under the name Bluesky Protocol Services. - The PLC directory, which resolves every
did:plc, was developed by Bluesky, which has run it so far. In September 2025, Bluesky announced an independent organisation, a Swiss association, to operate it, and the directory's site now says the PLC Organization was founded in 2026 as a neutral steward. Since February 2026, a reference implementation lets anyone run a live copy of the directory, a read replica. - Others run PDSes, such as Blacksky, Northsky and Eurosky, alongside people who host their own; other PDS and relay software, such as Blacksky's relay; and feeds and labelers that people subscribe to. In March 2026, a Bluesky grant funded Hubble, an independent project to mirror the public data of the whole network.
- On governance, Bluesky's protocol team named "hard decentralization", a network that "relies less on Bluesky PBC's existence", as one of its three goals in October 2025. In March 2026, the IETF created a working group to standardise the protocol's core.
So the honest answer to "is Bluesky decentralized?" is: partly. Your identity and your data can already leave Bluesky's servers, and each service can be replaced. But the official app reads the network through Bluesky's AppView, and running another AppView means indexing the whole network, which takes far more resources than running a PDS.
Not the same federation as Mastodon
Mastodon is federated too, but it runs on another protocol, ActivityPub, and works differently. On Mastodon, your server is part of your username and shapes what you see. On Bluesky, your server only hosts your data: what you see comes from feeds and services that gather posts from the whole network, so you can change servers and keep your identity, your followers and your posts (and your username, if it is on your own domain). A Mastodon account can also move to another server with its followers, but the AT Protocol's FAQ notes that this needs a redirect from the old server and cannot bring earlier posts: portability is one of the main reasons the AT Protocol was built as a separate protocol.
Independent services called bridges can also bring accounts and posts from other networks onto Bluesky. Bluesky's 2025 transparency report mentions them, and notes that it can act on bridged content within its own network.
How Bluesky.bot uses this
A name.bluesky.bot handle does not depend on where a bot is hosted: Bluesky.bot serves the bot's DID from its own domain, and the DID stays the same when the bot moves. So a bot can change PDS and keep its handle: on its new PDS, it sets name.bluesky.bot as its handle again, so that its DID document names it. How a bot is verified.
Frequently asked questions
- Can I leave Bluesky's servers and keep my followers?
- Yes. Moving your account to another PDS keeps your DID, so your followers, your posts and a handle on your own domain come with you. A handle ending in .bsky.social does not follow: you choose a new one. The new PDS has to accept you, and some ask for an invite code.
- Can Bluesky delete my account from the network?
- Bluesky Social PBC can take down an account or its posts on the services it runs: its PDSes, its relay, its AppView and its app. An account hosted on another PDS keeps its repository and its DID there, and other services can still show it. With a rotation key of your own and a backup of your data, you can also move an account away from a PDS that no longer cooperates.