unanymOne you.
Many places.
For networks of community websites. Approve once; members choose what each site sees.
- Release candidateNot yet independently security-reviewed.
- Open sourceApache 2.0. Anyone can read, run or audit it.
- Pilots welcomeTry it with your community first. Get in touch
A fictional example
One approval. Two independent websites.
Robin belongs to an Amsterdam cohort. An international workshop website and a Berlin cohort’s resource page are run by different people. Both agree to recognise Amsterdam’s members.
Amsterdam approves
The cohort’s organiser records Robin’s membership once.
Robin chooses
She uses “Robin” on the workshop site and “R.” in Berlin, choosing separately to share her Amsterdam membership. Email and other memberships stay out.
Both sites recognise it
Each website checks that approval and opens its member page, without maintaining a separate membership approval list.
Approval ends
Amsterdam withdraws approval. Both sites close their protected pages on Robin’s next checked visit.
Each website decides whose approvals it accepts and what they open. Sites keep their own accounts. Earlier copies cannot be recalled.
Connect a websiteFor community networks
Bring your community
For independently run websites that agree to recognise each other’s members. Name your organisers; connect your sites.
For members
Each website meets a different you
Every website gets its own name and identifier for you, and never your email. Change what it sees, or disconnect, in Your Unanym.
Who runs it
Choose who holds the middle
Mavie.uk runs unanym.org. It holds the records and keys, and could link your websites. Your community can pick another operator or host its own.
Join the conversation
Ask questions, share feedback, or help build Unanym.