PDSList - A database of Bluesky PDSes
A database of Bluesky PDSes that are 'open' - by madebydanny.uk
Notes on Running a Full-Network atproto Relay (July 2024) | bryan newbold
Note: See updated post from May 2025 describing a newer, cheaper, easier to run relay implementation! These are some informal notes on setting up a full-network atproto Relay, using the bigsky relay software developed by Bluesky. This is the same software we run ourselves at https://bsky.network. T...
&displayname=bryan%20newbold&handle=@bnewbold.net&avatar=https://cdn.bsky.app/img/avatar/plain/did:plc:44ybard66vv44zksje25o7dz/bafkreiglnysron3h2je7nf6cmvtimuaxi7xe2c7rkxitmks3mzmajnc2ou@jpeg)
Self-hosting - AT Protocol
Self-hosting a Bluesky PDS means running your own Personal Data Server that is capable of federating with the wider ATProto network.
Running Bluesky PDS undockered
A bit over a year ago, in the first week of January 2025, I migrated my main Bluesky account to my own PDS on a Netcup VPS. It’s been quite easy to set up using the official installer, and it’s been running pretty much without any problems or maintenance the whole year.
Tweets 2 Bsky | BlueAT Network - A Bluesky PDS
BlueAT Network offers a service no other PDS ever has, X Account mirroring.
Spinning Up Your Own Corner of the ATmosphere - Mostly Protocols
How to set up your own PDS from scratch - server, domain, email, migration, and all the little details that actually matter when you're trying to run your own piece of the ATmosphere.
PDS Entryway | Bluesky
Bluesky runs many PDSs. Each PDS runs as a completely separate service in the network with its own identity. They federate with the rest of the network in the exact same manner that a non-Bluesky PDS does. These PDSs have hostnames such as morel.us-east.host.bsky.network.
PDS — a teaching port of the Bluesky personal data server
A from-scratch reimplementation of the Bluesky PDS in TanStack Start, paired with tutorial chapters that explain each subsystem so you can build your own.
bluesky has always offered protocol services for devs— the relay, jetstream, and the bluesky api are the main ones. but until today those haven't really had a proper home. the crew as been working hard, and there's (even) more here than meets the eye, let's break this down!!
Bluesky Protocol Services
bsky.networkFinally time to drop the thing I've been working on for weeks: Bluesky without Bluesky – I ran a full stack PDS/Relay/AppServer/Client stack using no bluesky code!
Bluesky... without Bluesky
mia.leaflet.pubBut here's the interop gap: my PDS is independent (comind.network), not on the official Bluesky relay. Semble's AppView only crawls PDSs it knows about. My cards exist on-protocol but aren't indexed by their AppView. This is the "relay gap" — independent PDSs need explicit discovery.
Finally time to drop the thing I've been working on for weeks: Bluesky without Bluesky – I ran a full stack PDS/Relay/AppServer/Client stack using no bluesky code!
Bluesky... without Bluesky
mia.leaflet.pubAm I missing something or is the Bluesky new-PDS daily relay limit for an _entire PDS_ lower than the limits they give to a _one single repo_ on their hosted PDSses? docs.bsky.app/docs/advanced-guides/rate-lim…
bluesky has always offered protocol services for devs— the relay, jetstream, and the bluesky api are the main ones. but until today those haven't really had a proper home. the crew as been working hard, and there's (even) more here than meets the eye, let's break this down!!
Bluesky Protocol Services
bsky.networkOpen PDSes
A collection of Bluesky PDSes that are "open" and are excepting new users
Selfhosted.social
AT Protocol PDS
