no-instructions155k downloadsCollaborate in real time with live cursors. Share folders. Manage access to updates.
True multiplayer mode for Obsidian. 💃🕺

Relay is a collaborative editing plugin for Obsidian by System 3. It uses CRDTs to enable snappy, local-first, real-time and asynchronous collaboration.
Join our Discord for support and a good time.
In a nutshell, Relay:
Great question. CRDT stands for conflict-free replicated data type and it's a technology that's critical to making local-first real-time collaboration work.
The fundamental idea is this: You have data. This data is stored on multiple replicas. CRDTs describe how to coordinate these replicas to always arrive at a consistent state. [1]
For a great intro and overview, watch the first 10 minutes of this video by Martin Kleppmann. If you want to get into the nitty-gritty, watch the whole thing.
For more, check out this video: Intro to the Modern State of Synchronization by Kevin Jahns. Jahns is the maintainer of Yjs, which is the open source CRDT that we use in Relay.
Oh, the things you can do.




If you're the owner of a relay, you can destroy the copy on the server.
If you're a member but not the owner, you can leave the relay (destroy your connection to the server), and you can destroy the local data.
Asked more or less frequently.
Relay currently has two types of storage, document storage and attachment storage. Document storage is backed by our real-time CRDT servers, while Attachments are stored as file blobs.
Document storage:
Attachment storage:
You need to have available Attachment storage in order to sync images/audio/video/PDFs/etc.
We offer discounts for educational use.
Relay is local-first -- this means that all of your edits are tracked locally and the server is used to relay the edits to your collaborators. You can work offline and your edits will be merged once you come back online.
We use a Conflict-Free Replicable Data Types (CRDTs) provided by the excellent yjs library.
The Obsidian plugin code is MIT licensed (this repo).
The Relay Server is a fork of y-sweet and is MIT licensed.
Our login, permissions, and billing server code is proprietary.
We support "On-Prem" deployment of a Relay Server.
If you self-host your Relay Server on a private network then your users will still perform login and permissions checks through our servers, but they will connect directly to your server. Your content will be completely private and inaccessible by us.
For instructions on hosting your Relay Server on fly.io, see Relay Server Template.
Join our Discord for help on configuring your on-prem deployment.
Relay is made by System 3. The legal entity behind System 3 is No Instructions, LLC.
Right now the whole operation is two people:
Yes: https://system3.md/Privacy+policy.
Please email [email protected]
You can search for Relay in the Obsidian Community plugins list,
or click this Obsidian Plugin Link.
[1] Intro to CRDTs by Lars Hupel https://lars.hupel.info/topics/crdt/01-intro/