haileyok/cocoon

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.

julien.rbrt.fr/vow

BYOK Personal Data Server (PDS) written in Go

PDS Directory | ATProto PDS Index

Complete directory of Personal Data Servers in the Atmosphere.

🔎 atproto sqlite store - Google Search

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.

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.

hailey.at/cocoon

An atproto PDS written in Go

Overview · vlpds docs

An atproto PDS whose only durable storage is an object store. Any node serves any request, one node can run a personal server for free, and a few nodes can carry all of Bluesky's write load.

pdewey.com/atp

Go boilerplate library for building atproto apps

AT Protocol PDS

Explore this self-hosted AT Protocol Personal Data Server (PDS) with useful links and details.

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.