atproto selfhosted services hosted in the southeast.
microcosm: atproto building blocks
Open-source atproto services and resilient community infrastruture to launch your next app
microcosm: atproto building blocks
Open-source atproto services and resilient community infrastruture to launch your next app
ATProto Boston (@atproto.boston)
We are a local community of technologists, enthusiasts, organizers and builders excited about the prospect of an open internet on atproto. 🔗 https://atproto.boston 🗓️ https://atmo.rsvp/p/atproto.boston organized by @tynanpurdy.com #atproto.local
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/
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
labs · luna
80+ small interactive labs — atproto tools, dev utilities, data explorers on uk open-gov / twitch / mastodon firehoses, media converters, and games.
jack ❄️ (@j4ck.xyz)
atproto box: beefy raspberry pi to locally run a small appview, pds, relay and local bluesky web client :D
OpenMeet-Team/atproto-devnet
A local ATProto network in Docker for developing and testing against a real PDS, Jetstream, and DID registry without connecting to production Bluesky.
Relay good news - Sri's leaflets
Introducing firehose.network - public infrastructure and tools for ATProto relays.
Relay good news - Sri's leaflets
Introducing firehose.network - public infrastructure and tools for ATProto relays.
third-party apis: community infrastructure on atproto - Keith's Thoughts
you can just build things from an open set of tools
Deep Dive into Wafrn: How One Platform Self-Hosts Both ActivityPub and Bluesky Identities
Deep Dive into Wafrn: How One Platform Self-Hosts Both ActivityPub and Bluesky Identities 26 February 2026 ActivityPub ATproto self-hosting architecture A technical analysis of Wafrn's dual-protocol a...
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.
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.devThe ATProto community built a ton of great features and products over the past year. For our next trick, let's mature them into products and businesses.
Mosh Lee
(2/n) A feature solves one problem well — even delightfully well. But features get copied easily or absorbed into larger products. They have no distribution or adoption model. If your whole thing can become a pane in someone else's app, it's a feature.
