Local-First · Zero-Knowledge · Community-Owned

(you)rSpace

Collaborative community spaces powered by FolkJS

Build digital spaces for your community with an infinite collaborative canvas, real-time CRDT sync, and zero-knowledge identity. All open source.

Create a Space Try the Demo

🎨

Spatial Canvas

Infinite collaborative workspace

🔄

Real-time Sync

📡

Offline-First

Works without internet, merges on reconnect

🌐

Your Subdomain

community.rspace.online

EncryptID

One secure, local-first identity across every tool in your community's rSpace. No passwords. No cloud accounts. Your keys never leave your device.

🔑

Passkey Login

Hardware-backed biometric auth. Phishing-resistant by design.

🏠

Local-First

Cryptographic keys are derived and stored on your device, never uploaded.

🔗

One Login, All Apps

Authenticate once and access every r-Ecosystem tool seamlessly.

Secure by default, not by opt-in

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.

A common login for your community's toolkit

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.

Offline-First, Always Available

rSpace works without an internet connection. Edit your canvas on a plane, in a field, or underground — your changes merge automatically when you're back online. No sync buttons, no conflict dialogs.

💾

Local Persistence

Your canvas is cached in the browser. Refresh the page — it loads instantly, even offline.

🔀

Auto-Merge

Automerge CRDTs resolve conflicts automatically. Multiple people can edit the same canvas offline and merge without data loss.

⚡

Incremental Sync

Only new changes are transferred on reconnect — not the whole document. Fast even on slow connections.

How it works

Every rSpace canvas is an Automerge CRDT document stored locally in your browser's IndexedDB. When you open a canvas, it renders from the local cache first — no waiting for the server. Edits you make are saved locally and synced to the server via WebSocket when a connection is available. If you go offline, the app keeps working: a Service Worker serves the app shell from cache, and your changes accumulate in the local CRDT document. When connectivity returns, Automerge's incremental sync protocol reconciles your changes with everyone else's — conflict-free, automatically. No manual merge, no "which version do you want to keep?" dialogs.

Interoperable by Design

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)

Your data, connected across tools

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.

No vendor lock-in, no data silos

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.

🌌 rSpace 💰 rWallet 🗳 rVote 🗺 rMaps 📁 rFiles 📝 rNotes ✈ rTrips 💸 rFunds 🕸️ rNetwork 🛒 rCart 🎬 rTube 💬 rChats 💭 rForum 👕 rSwag 📊 rData

🔐 Learn more about EncryptID