Self-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.devAug 18, 2026 at 11:39 AM
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.
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.
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.
Notes on hosting an ATProto PDS on Cloudflare
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.
cove.town/cove.town
Self-contained atproto self-hosting setup with PDS, knot, spindle, and hold
cove.town/cove.town
Self-contained atproto self-hosting setup with PDS, knot, spindle, and hold
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.
third-party apis: community infrastructure on atproto - Keith's Thoughts
you can just build things from an open set of tools
The week-end is over so I'm pressing ⏸️ on my custom PDS project for now. Here's part 2 of my dev journal. I've learned a lot already and so far I feel like it might actually be worth finishing. It's really cool to get a more intimate understanding of ATProtocol and it's implementation.
How to Make a PDS - Part 2 - Zicklag's Leaflets
zicklag.leaflet.pubWant to distribute compute to members of your organization in an ATProto native way? Check out socialweb.computer!
I saw requests for a new way to find atproto alternatives, so I made alternativeproto.net - an atproto spin on AlternativeTo. It itself is on atproto, so you can log in and make submissions, votes, and reviews that are stored on your PDS. Give it a try and go easy, it's my first public atproto app.
AlternativeProto - Decentralized Web Catalog
alternativeproto.netDid 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.pubContinuing the series of atproto self-hosting posts, here's a guide for ATCR and the hold component, an atproto container registry! jola.dev/posts/self-hosting-atproto-co…
Self-hosting an atproto container registry
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
