Bluesky and the AT Protocol, explained
Bluesky is an app. The AT Protocol is the open network under it. Your identity, your data and the services that show them to people are separate pieces, so you can change one without losing the others.
Last reviewed on November 13, 2026
Most social networks run on one company's servers, from the sign-up page to the timeline. Bluesky splits that work between several kinds of service, which talk to each other through an open protocol: the Authenticated Transfer Protocol, or AT Protocol for short. Developers often write it atproto.
The three pieces
- Your identity. Every account has a permanent identifier, its DID, and a readable name, its handle. A handle is a domain name, such as
alice.bsky.social. - Your data. Your posts, likes and follows are records in your own repository, signed with your key and stored on a server called a PDS.
- The services that show it. Other services collect public repositories and turn them into what you see: timelines, threads, counts, custom feeds and labels.
The journey of a post
When you post, the post is saved in your repository, on your PDS. A relay picks up the change and passes it on, in one big stream with everything else happening on the network. An AppView reads that stream and builds the threads, timelines and counts that apps show. Feed generators and labelers work alongside, so you can choose what you see.
- Your app
- Your PDS
- Relay
- AppView
- Readers' apps
Alongside
- Feed generators
- Labelers
Start here
Each page answers one question. They are in reading order, but each one stands on its own.
- Step 1
What is the AT Protocol?
The AT Protocol is the open network behind Bluesky. What it is, how it differs from the app, and its building blocks: DIDs, repositories, lexicons.
Read: What is the AT Protocol? - Step 2
How Bluesky works
Follow one post through the Bluesky network: your PDS stores it, the relay streams it, the AppView builds timelines, feeds and labelers add choice.
Read: How Bluesky works - Step 3
Handles and DIDs: how Bluesky identity works
Your Bluesky handle is a domain name; your DID never changes. How the two are linked, did:plc vs did:web, and how a handle is verified.
Read: Handles and DIDs: how Bluesky identity works - Step 4
Is Bluesky decentralized? Federation and data portability
What you can move on Bluesky and what is still centralised: changing PDS, keeping followers, self-hosting, and an honest look at the network today.
Read: Is Bluesky decentralized? Federation and data portability - Step 5
How bots work on Bluesky
A Bluesky bot is an ordinary account that writes to its PDS. How bots post and listen, the Automation label, and where the rules are.
Read: How bots work on Bluesky - Step 6
AT Protocol and Bluesky glossary
Plain definitions of the words of Bluesky and the AT Protocol: PDS, relay, AppView, DID, handle, lexicon, labeler, feed generator and more.
Read: AT Protocol and Bluesky glossary
Why it is built this way
Because the pieces are separate, you can change one without losing the others. You can move your account to another server and keep your identity (your DID), your followers and your posts; a handle on your own domain stays too. You can pick the feeds you read and the labelers you trust. And since repositories are public, anyone can build a new app or service on the same accounts and data, using the same protocol as Bluesky's own systems. Is Bluesky decentralized? looks at what can move today, and what still depends on Bluesky.
Key words
- AT Protocol (atproto): the open protocol under Bluesky. It defines identities, data repositories and how services exchange them.
- Handle: an account's readable name, which is a domain name, such as
alice.bsky.social. It can change. - DID: an account's permanent identifier, such as
did:plc:…. It never changes, even when the handle does. - PDS (Personal Data Server): the server that hosts an account, its repository and its keys.
- Relay: a service that collects updates from many PDSes into one stream, the firehose.
- AppView: a service that indexes the network and builds the views apps show, such as timelines and threads.
- Feed generator: a service that picks the posts of a custom feed.
- Labeler: a service that puts labels on accounts and posts, which people choose to subscribe to.
How Bluesky.bot uses this
Bluesky.bot works with the identity layer. Every name.bluesky.bot handle is a domain name that answers with the bot's DID, so Bluesky and every other app on the network can check that the handle belongs to that bot. How to get a handle for your bot.
Frequently asked questions
- Is Bluesky the same as the AT Protocol?
- No. Bluesky is a social app made by Bluesky Social PBC. The AT Protocol, or atproto, is the open protocol it runs on. Other apps can use the same accounts and data, because the protocol is shared.
- Do I need to understand this to use Bluesky?
- No. You can sign up and post without knowing any of it. These pages help when you meet a word such as handle, PDS or labeler, or when you want to run a bot, use your own domain or change servers.
- Where does Bluesky.bot fit?
- Bluesky.bot is an independent service built on the AT Protocol, not affiliated with Bluesky. It gives bot accounts a name.bluesky.bot handle, proves that handle to the network, and lists the bots in a public directory.