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.
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.
Setting up my own ATProtocol PDS - Blooym
Details of my adventures self-hosting my own ATProtocol Personal Data Server (PDS), including the painful debugging process.
Other PDS
Compare other ATproto Personal Data Servers (PDS): see providers, regions, and tips for choosing where your handle and social data should live.
Other PDS
Compare other ATproto Personal Data Servers (PDS): see providers, regions, and tips for choosing where your handle and social data should live.
PDS Directory | ATProto PDS Index
Complete directory of Personal Data Servers in the Atmosphere.
atproto vancouver (@vancouver.atprotocol.community)
atproto community in Vancouver, Canada Hosted on @commonscomputer.com, a PDS host on a server at @z-space.ca Check out our @blento.app for more info: https://vancouver.atprotocol.community/
MobilePDS Working Group
The MobilePDS is a lightweight Rust implementation of an ATProto Personal Data Server designed to run locally on a user’s mobile device. It puts users back in control of their identity, posts, and credentials — while allowing caching and moderation infrastructure to scale separately via a mirror PDS. The MobilePDS is the canonical source of truth; the mirror is just a performance and compliance layer.
ATProto PDS Network Map
Interactive map tracking ATProto Personal Data Servers worldwide. Explore the decentralised Bluesky network!
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.
atproto pds self-hosting: some issues and antipatterns | friendmeat
The Bluesky personal data server (pds) repository is weirdly opinionated about stuff that's easy, and unhelpful with the stuff that's hard. They also insist on using a script that installs a whole HTTP server and Docker stack. But if you're gonna use Docker why assume that people don't already have their own stack? It's just weird and annoying. But here's how I did it.
the single most important part of atproto is the PDS as a user-controlled auth and storage layer to which clients can connect directly. death to appviews
Authenticated Transfer Enables Orchestration - nekomimi
blog.nekomimi.petI recently got super into the ATProto spec and how different services use PDS to store the data, I put together a quick client-only website that presents all those records in a single, consolidated feed of all my activity: at.diego.codes
at.diego.codes — Diego Vicente
at.diego.codesSelf-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.devPDS Hosting
Resources related to atproto Personal Data Server (PDS) hosting
Bluesky handle directory – PDSes
eny.space
Bitesize Proto: Two PDS containers at the same time; synchronized swimmers - Hitchhiker's Guide to the Atmosphere
