Own Your Bluesky Identity: Self-Host a PDS on Open Source Cloud

Own Your Bluesky Identity: Self-Host a PDS on Open Source Cloud Your Bluesky account lives on a server you don't control. When Bluesky the company makes decisions about that server, you inherit them. The AT Protocol was designed to fix this — your identity is a DID (decentralized identifier) that can be anchored to a server you run. But most people never self-host because standing up a Personal Data Server is too much work. This guide gets you a running PDS in about five minutes. No Kubernetes experience required. Why it matters Your PDS is more than storage. It's the root of your AT Protocol identity. When your account lives on bsky.social , your DID resolves through Bluesky's infrastructure. When you self-host, your DID resolves through yours. You can migrate back to bsky.social or to any other PDS at any time — the AT Protocol guarantees portability. But you're never dependent on one company's availability or policies. For developers especially: a self-hosted PDS lets you experiment