The hard part was never the build. It's the users.

Everyone here is building their own thing — a community, a graph, a dataset, a service. The universally hard part is traction. Because it all runs on one connected network, people can carry their identity in and adopt what you build — so you grow from a network, not from zero. Identity, data, federation, and a widening catalog of PeerMesh modules handle the rest.

Request builder access See how peers.social is built

One connected network — cross-property SSO, live
Federated — ActivityPub live · AT Protocol native
peers.social — live reference deployment

Users, already connected

Traction is the real moat around every platform. People are already on the network and can carry their identity into what you build — so you launch with reach, not from zero.

More than social

You might not be building a social app at all. The PeerMesh module catalog — identity, data, storage, media, payments — handles the systems every product rebuilds. The Social module is live today; more are in development.

Keep sovereignty

Your system, your rules, your data. Federation means participating in the shared network without depending on it.

Building toward

A marketplace across the network, where anyone can offer their services to everyone connected.

How peers.social is built

Built on PeerMesh.

peers.social is a live reference deployment of the PeerMesh stack. Identity and single sign-on already work across its properties, it federates over ActivityPub and speaks AT Protocol natively, and the Social module is source-available. More modules — identity, data, storage, media, payments — are in development, and the same network carries every one of them.

Build on the network

Tell us what you're building.

Builder access is by request while we onboard early builders. Use the feedback control in the bottom-right corner — pick and tell us what you're building — and we'll be in touch.