Bluesky Identity and Data Portability

This portability is Bluesky’s clearest moat, because it turns the app from a place that owns the audience into a network where the user owns the audience. In practice, a Bluesky account is anchored to a stable DID, while posts live in a signed repository on a Personal Data Server. When someone switches servers, the DID stays the same, the repo can move, and downstream services can keep resolving the same identity, social graph, and content instead of treating the user like a brand new account.1 2 3 4 5

• The important technical split is identity versus hosting. AT Protocol makes the user the primary object and the server the replaceable host. That is why moving servers is more like changing cloud providers than abandoning an account and starting over.2 3 5
• This is a real difference from Mastodon. Mastodon lets users move followers between servers, but its documentation says posts and media do not move because of technical limits. Bluesky’s design is built to carry the repository itself, not just a forwarding address.1 4
• That design also opens a business path beyond ads. As more groups run their own Personal Data Servers, Bluesky can sell relay, indexing, and moderation services while users keep ownership of identity and data, similar to how WordPress grew around hosting and infrastructure rather than owning every site.6 7

The next step is a social stack where identity, hosting, feeds, and moderation become separate layers. If Bluesky keeps making migration routine and invisible, it can become the default identity rail for open social apps, while monetizing the infrastructure and discovery layers that sit around that identity.2 5 6