







comail
Cooperative email for atproto. Small self-hosters pool reputation through a shared relay so mail from their own domain reliably reaches the inbox.
FlockOff
Block everyone who engaged with a post. Customizable, reversible, and built on atproto.
ATProtocol Community
A community space for coordinating, convening, and collaboration around ATProto

ATProtocol Community
A community space for coordinating, convening, and collaboration around ATProto

Missive · Inbox collaboration for teams that run on email
See what’s going on, know who’s doing what, and collaborate behind the scenes — without changing your workflow. Try for free!

ATProtoFans - Support Your Favorite Creators
Decentralized supporter attestation service for the ATProtocol ecosystem. Support creators with cryptographically verifiable relationships.
ATProtoFans - Support Your Favorite Creators
Decentralized supporter attestation service for the ATProtocol ecosystem. Support creators with cryptographically verifiable relationships.

What is atproto?
What is atproto? atproto is two things: A protocol for creating open social networks An open social network atproto, the open social network Today the atproto network has 36+ million users and powers Bluesky and a handful of other apps. Almost all atproto data is public. Content like posts, likes, follows, and photos/videos are publicly accessible to any network participant in a permissionless way. As an example of how open the network is, here’s how easy it is to stream all public data on the network using a public atproto Relay like bsky.network:

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.devmade atproto.md awhile ago, just added some relay features. discover repos by collection and constellation backlinks. connect your agent to the /mcp to fetch records, resolve actors, discover repos and more. try it out, suggest stuff, contribute.
atproto.md — AT Protocol data as Markdown
atproto.mdoh i forgot to mention in my talk, but some of us small indie relay operators are getting together to make @firehose.club so we can share network limit bumps and bans and build some shared tooling. we can go further together <3
@metaflame.dev gave a great explanation in this mini-thread of the advantages for the #atproto network in having multiple, independent relays operating
Metaflame
Redundancy, resilience, and possibly distance Importantly, once enough independent relays are active, they are likely to disincentivize malicious behavior for any one of them. Having multiple implementations (that is, different code) adds further resilience.
Want to distribute compute to members of your organization in an ATProto native way? Check out socialweb.computer!