Real-time collaboration without the cloud

Most "real-time collaboration" in software today means the same thing: your document lives on somebody else's server, and every keystroke is a round trip through it. noteloom's live collaboration is built differently, on purpose — there's no server that stores your document, no account, and no company that could read it even if it wanted to. This post is about what that actually means in practice, not just the pitch.

This isn't Google Docs with a different skin

Cloud collaboration tools all share one architecture: your content goes up to a server, everyone else's edits come back down from it, and the server is the single source of truth the whole time you're connected. That's a reasonable design — it's just not the only one, and it's not noteloom's. There is no noteloom server. Nobody hosts your documents for you. Nobody could, even if you wanted them to — the feature isn't built with a backend at all.

Peer-to-peer, like a video call

Instead, peers connect directly to each other over WebRTC — the same underlying technology behind browser-based video calls. Two people editing a document together are, technically, doing the same kind of thing as two people on a video call: a brief handshake to find each other, then a direct connection between exactly those two devices, no intermediary in the data path.

That handshake — called signaling — is the only place any third party is ever involved, and it never sees document content, only tiny connection-setup messages (the equivalent of "here's my phone number, call me"). Once the connection opens, editing traffic flows directly between the peers, and the signaling step drops out of the picture completely.

The Bitchat comparison

If this sounds like the same instinct behind offline-first, infrastructure-free apps like Bitchat — mesh messaging with no server, no phone number, no internet connection required — that's the right comparison to make. noteloom trades Bluetooth mesh for WebRTC over WiFi, but the underlying philosophy is identical: two devices in the same room should be able to work together without a company sitting in the middle of it, and it should still work when the internet doesn't.

What actually happens when three people edit at once

Call them A, B, and C. There's no "host" device the others route through — when C joins a document A and B are already editing, C opens two separate, direct connections: one to A, one to B. Every device holds its own full copy of the document. Here's what that means for the situations that actually come up:

Reconnects automatically, catches up automatically

A WiFi blip, a closed laptop lid, a relay restart — a watchdog notices the dropped connection and reconnects on its own the moment the network returns, then catches the device up on whatever it missed while it was gone. No dialog, no "reconnect" button, no lost work. The only visible sign is a small status indicator flipping from "connected" to "reconnecting" and back — the full pattern is documented in noteloom's own README and a runnable example, for anyone building on top of this themselves.

Same WiFi, zero internet — really

Because the whole model is peer-to-peer with a lightweight local handshake, none of this actually requires the internet at all. Two people in the same room, on the same WiFi, with the router itself disconnected from the wider internet, can still open a shared document and edit it together live — signaling just needs to be reachable on the local network, nothing more.

That's a meaningfully different claim than "cloud collaboration that happens to also work on WiFi" — this is collaboration that was never routed through the internet to begin with.

Try it

Two synced editors, side by side, right in your browser — no setup, no account, nothing to install. Or read the full technical walkthrough, including every scenario above worked through in more detail, plus how to wire it into your own app.