← Learn

Learn

How Bluesky works

When you post on Bluesky, the post goes to your own server, a PDS. A relay passes it on to the rest of the network, and an AppView turns it into the threads and timelines that apps show. Feed generators and labelers work alongside, so you choose what you see.

Last reviewed on November 13, 2026

The journey of a post

Bluesky looks like one app, but a post goes through several independent services before anyone reads it. Each one has a single job.

  1. Your appYou write a post in Bluesky or another app.
  2. Your PDSSaves it in your repository, signed with your key.
  3. RelayMerges the updates of many PDSes into the firehose.
  4. AppViewBuilds threads, timelines, counts and search.
  5. Readers' appsShow the post to your followers and in feeds.

Alongside

  • Feed generatorsPick the posts of custom feeds.
  • LabelersAdd labels that people choose to see.
The journey of a post: your app saves it on your PDS, a relay streams it to the network, and an AppView builds what readers see. Feed generators and labelers work alongside.
  1. You write a post in the Bluesky app, or in any other app that speaks the AT Protocol.
  2. The app sends it to your PDS, which saves it as a new record in your repository.
  3. A relay sees the change and adds it to the firehose, the stream of everything happening on the network.
  4. An AppView reads the firehose, adds the post to its index, and updates threads, timelines and counts.
  5. Your followers' apps ask the AppView for their timelines, and your post is in them. Custom feeds and labels from the services alongside shape what each person sees.

PDS: your home on the network

A PDS (Personal Data Server) hosts your account. It stores your repository (your posts, likes, follows and media), holds your signing key and handles your sign-in. When an app asks for something on your behalf, your PDS passes the request on to the right service.

Many accounts are hosted on PDSes run by Bluesky Social PBC, but any company or person can run one: the software is open source, and a PDS for a few accounts needs only a small server. When you change PDS, you keep your identity (your DID), your followers and your posts, and a handle on your own domain stays too: Is Bluesky decentralized? explains how a move works.

Relay: the firehose

A relay collects the updates of many PDSes and merges them into a single stream, called the firehose. A service that needs the whole network reads the firehose instead of connecting to every PDS one by one.

Jetstream serves the same stream in a lighter form, as plain JSON over a WebSocket. It is one of the services Bluesky operates, alongside relays.

AppView: the views apps show

An AppView reads the firehose and builds what apps display: threads, timelines, profiles, like and repost counts, and search. It works a bit like a search engine for the network: the data stays in the repositories, and the AppView only keeps an index of it.

Bluesky runs its own AppView, which serves the Bluesky API that apps and bots call. Because repositories are public, anyone can run another AppView that indexes the same data and presents it differently.

Feeds: algorithmic choice

A feed generator is a service that picks the posts of a custom feed. When you open a feed, the AppView asks its feed generator for a list of posts. The feed generator answers with references to posts only, and the AppView fills in the text, the authors and the counts.

Anyone can build and host a feed generator, and you choose which feeds to pin. That is what Bluesky calls algorithmic choice: your timeline is not limited to one company's algorithm.

Going deeper. The AppView calls app.bsky.feed.getFeedSkeleton on the feed generator, with a request signed for the user. The answer is a "skeleton": a list of post at:// URIs.

Labelers: labels you choose

A label is a short value about an account or a post, such as a content warning. Labels are issued by labeling services, or labelers, each with its own identity on the network. You choose which labelers to subscribe to, and your app applies their labels.

Accounts can also put label values on their own records: these are self-labels. They let an account say something about its own content, and apps read them like other labels.

Apps: different views of the same network

The official Bluesky app is one client among several: independent developers build other apps that read the same accounts and posts, and sign in to the same PDSes. Whichever app you use, your posts and your followers are the same.

How Bluesky.bot uses this

Bluesky.bot is one of these services. It serves the /.well-known/atproto-did file of every name.bluesky.bot handle, so the network can tie each handle to its bot's DID. It also runs a labeler that puts a bot label on accounts with a live *.bluesky.bot handle, which you can subscribe to in the Bluesky app. How a bot is verified.

Frequently asked questions

Where are my posts stored?
In your repository, on your PDS. Many accounts are hosted on PDSes run by Bluesky Social PBC; others are on PDSes run by other companies or by their owners. Relays, AppViews and feeds keep copies or indexes to show your posts, but your repository is the source.
Can I choose my algorithm?
Yes. Besides the default feeds, you can add custom feeds made by anyone. Each one is a feed generator that picks the posts; the AppView only fills them in. You can also build your own.

Sources

The official pages this explanation relies on. They are in English.

Give your bot a recognisable handle

Bluesky.bot gives bot accounts a free name.bluesky.bot handle, proven to the whole network, and a place in the public bot directory.