Collaborative community spaces powered by FolkJS
One secure, local-first identity across every tool in your community's rSpace. No passwords. No cloud accounts. Your keys never leave your device.
EncryptID uses WebAuthn passkeys as the root of trust — the same standard behind Face ID and fingerprint unlock. Your identity is bound to your device's secure hardware, so there are no passwords to leak, phish, or forget. End-to-end encryption keys are derived locally via HKDF, meaning the server never sees your private keys. If you lose your device, social recovery lets trusted guardians help you regain access without seed phrases or centralized reset flows.
Every community rSpace comes with a full suite of interoperable tools — voting, budgets, maps, files, notes, and more — all sharing the same EncryptID session. Sign in once on rSpace and you're already authenticated on rVote, rFunds, rFiles, and every other tool your community uses. No separate accounts, no OAuth redirects, no third-party identity providers. Your community, your identity, your data.
Data flows between your community's tools because they share a common foundation: the same identity, the same real-time sync layer, and the same local-first architecture.
EncryptID (identity)
|
v
┌─────────── rSpace CRDT Sync Layer ───────────┐
| |
| rVote rFunds rFiles rNotes rMaps ... |
| | | | | | |
| └───────┴───────┴───────┴───────┘ |
| shared community data graph |
└───────────────────────────────────────────────┘
|
v
Your device (keys & data stay here)
A budget created in rFunds can reference a vote from rVote. A map pin in rMaps can link to files in rFiles and notes in rNotes. Because all r-Ecosystem tools share the same Automerge CRDT sync layer, data is interoperable without import/export steps or API integrations. Changes propagate in real-time across every tool and every collaborator — conflict-free.
Every piece of community data is stored as a local-first CRDT document that your community owns. There's no central server gating access and no proprietary format trapping your data. Export everything. Fork your community. Move between hosts. The r-Ecosystem is designed so that the community — not the platform — controls the data.