Open foundations for community-owned digital spaces.
OpenFederation lets people, newsrooms and communities own their identity, their work and their audience, and take them along when they move. No single platform can lock them in.
New · 15 November 2026
The demo is public.
Create an account, make a pen name, prove it is yours and move it to another server. It runs in your browser on two demo servers and takes about 15 minutes.
Keep control
Communities keep control of their presence and history.
Move freely
Move between services without losing people or context.
Connect across
Connect across networks instead of rebuilding from zero.
Built on OpenFederation
Two projects run on the same server you can download from GitHub. Both are in early development.
Open Newsrooms
Helps independent journalists and small newsrooms own their name, their work and their readers, without depending on any platform. Journalists who need protection can publish under a pseudonym the server can't trace back to them, and prove it was them later if they choose.
Grvty
Gives sports clubs and their members a shared home for identity, roles, forums and events that the club owns, instead of renting it from a social network.
Architecture
A personal data server and federated identity layer, built on open social protocols and interoperable standards.
Roadmap
More has shipped than a short list can show. The breakdown below is grouped by what's released, what's built but still being proven, and what isn't built yet.
See the full breakdown ↓Where things actually stand
Grouped by real status, not by wishful sequencing. Last updated 19 November 2026. Everything released is in the public repository and runs on pds.openfederation.net, pds.grvty.app and the two demo servers. The latest numbered version is 0.6.0, from 12 November; versions are 0.x while the project is in development (0.6.0 was first published as 1.5.0), and 1.0.0 will be the first one recommended for production use.
View live on GitHub ↗Released
- Identity layer:
did:plc/did:web, sign-in, roles - Communities with custom roles and governance modes
- Governance decisions anyone can check, with a window to object
- Verifiable attestations, and sharing a private one with a chosen person for a limited time
- Contact graph: requests, blocks, mutual and friend-of-friend discovery
- Community forums, calendar events and RSVPs
- Cross-network identity bridging (Meshtastic, Nostr, WireGuard, SSH)
- Private communities stay on their own server, and outsiders get the same answer as for a community that doesn't exist
- Pen names (pseudonyms): a separate account the server can't link to you, opened with twelve words or a passkey, which you can later prove is yours in public, in private or in person
- Moving to another server: accounts, pen names and whole communities, also from the dashboard
- Three ways to hold your identity keys: the server holds them, you hold them with the server as a backup, or only you hold them
- Records a person signs with their own key, which the server cannot produce
- A takedown policy that gives the owner 30 days to download their data
- Profile pictures and banners, email verification
- SDK,
@open-federation/react, CLI and admin dashboard - Security: 81 hardening issues closed and a vulnerability reporting policy. Until 1.0, security fixes go into the latest 0.x release
- Install a server without being technical: a setup page in the browser, a Railway template, ready-made Docker images, a one-command installer for any Linux server, and a Synology NAS project
- Server settings an admin can change on a page, without a restart
- Dashboard screens for pen names, including creating and using one without signing in to your own account
- A public page where anyone can check a pen-name proof, with no command line
- Dashboard screens for key custody, recovery, devices and identity history, written in plain words
- Device signing: the device holds the key that signs a person's records, so the server cannot forge them. It covers profile, contacts, forum posts, RSVPs and votes, is switched on from the dashboard, and a new device can take over when the old one is lost
- Recovery without the server: a second recovery key, or the recovery phrase split among people you trust
- Tools for an application to notice a server writing in a person's name, and to leave that server without its help
- An account that holds its own keys moving into another server when the old one refuses to help, or is gone
- A person's own list of the public communities they belong to, so their server finds all of them, not only those on its peers
- Importing a Discord or Slack community's history as forum threads, with its images
- Invite codes that also join the new member to a community
- Two public demo servers, emptied every night, and a demo in the browser: create an account, make a pen name, prove it is yours and move it to the other server
- Community discovery and activity timelines across servers that list each other as peers
- Sign-in for other apps: Mastodon, Ghost and other apps that speak OpenID Connect let people sign in with their account here, or with any AT Protocol account, Bluesky included. Two live demos: a Mastodon server and a Ghost publication styled as Open Newsrooms, whose readers and staff sign in that way. Posts stay in the apps; OpenFederation only answers who you are
- Handles like
name.openfederation.netthat Bluesky and other AT Protocol services can look up
Built, still being proven
- Federation between servers: sign-in across servers, discovery, timelines and moving all work between servers we run. No server run by another organisation has joined yet
- The Night Desk stage demo on two live servers: the live mode is built, but it hasn't been rehearsed on them yet
- ActivityPub discovery: a running Mastodon server finds a community and shows the apps linked to it, and Lemmy does since a fix. It covers identity only; no posts are exchanged, and following a community stays pending
- Lemmy sign-in: ready, waiting for Lemmy 1.0, the first version that can sign people in this way
- On-chain governance, an optional module: tested against a local Ethereum node, never used on a public chain
- Wallets where the user holds the key (tiers 2 and 3): covered by tests; only the server-held tier has been used by an application
- The server's backup of identity keys (2-of-3 split): the round trip is tested, but no outside escrow provider exists to hold a share
Not built yet
- Publishing to AT Protocol relays and app views: the server has no live stream of changes (firehose) for them to follow yet
- Listing our identities in plc.directory, the directory most AT Protocol apps read. The tool is ready; we hold it back while we are still making test accounts, because nothing can be removed from that directory
- Uptime and health monitoring for our own servers
Follow the work
No spam. Just meaningful updates.