You know what I want: a "headless" PDS. @roomy.space needs a way to create an ATProto account for every space that is created. That means we need a legit PDS repo. We don't want to implement a PDS ourselves, so we'd rather use Tranquil or the reference PDS.
Jul 21, 2026 at 8:08 PM
Making Roomy More ATProto-Native - Zicklag's Leaflets
We've said Roomy's server was like a PDS, but what if it actually was a PDS?
Embracing ATProto, part 1: Setting up a PDS
In this series of posts, I'll explore my journey into setting up my workflows and services for atproto. The first step is setting up my PDS. Let's start with a bit of explanation for all this lingo.
Self-hosting your PDS | jola.dev
How to set up your own atproto Personal Data Server using tranquil-pds and docker compose, walking you through it step by step.
Adversarial ATProto PDS Migration | Blog
An ATProto account lives on a Personal Data Server (PDS), and that service needs to be hosted somewhere by someone. There are a lot of options here, like a Raspberry Pi in your closet, a rented VPS in a datacentre, or a batteries-included service like bsky.social.
PDS operator guide — atproto-crates
Operating atproto-pds: production status, endpoint surface, storage profiles, build flags, the full environment variable reference, and the deployment modes that are deliberately not wired up.
What is required to make a PDS implementation?
This Github thread from July 2024 had a long answer by Bryan Newbold that is included below:
Did a quick write up on the work I've been enjoying to make a PDS distributed. #atproto
The journey to a distributed PDS - Wills thoughts
willdot.leaflet.pubShower thought idea: What about expanding the role of the PDS for account management? E.g. when signing up on atproto with any app/service for the first time, redirect to the already existing account interface (`/account/`) already present on reference PDS, making this flow mandatory to support.
Atproto Spaces (buckets, we hardly knew ye) have moved from a proposal to real live working — AND VERY MUCH ALPHA DO NOT USE THIS IN PRODUCTION — code. We even set up a working PDS for y'all to use, head over to bsky.network/account to get going
AT Protocol Developers
The most significant extension to the protocol since launch—atproto spaces—is now officially alpha software you can start testing with. Here's more about the goals and how to start testing. atproto.com/blog/atproto-spaces-alpha
Building a PDS the Hard Way agent.io/posts/building-a-pds
Building a PDS the Hard Way
agent.ioSelf-hosting your own atproto infrastructure is very much attainable and after going through the process, I wanted to do a little series of write ups on how to go about it. Starting with the PDS! jola.dev/posts/self-hosting-your-pds
Self-hosting your PDS
jola.devWe're very pumped to announce that the reference PDS now has an account management page! atproto.com/blog/pds-account-management You can now manage permissions, update your password, or deactivate your account directly from your PDS, as a regular user — no command line tools or Bluesky interfaces required!
The Reference PDS Gets an Account Management Page
atproto.com
