Standing on Iroh
The layer that merges your library is ours, and it is called Lattice. The hard networking underneath it is not. Iroh, from the team at n0, does dial-by-key, hole punching and relays, and does them well. Until September 2026 Lattice spoke plain TCP and only on the local network. Moving to Iroh brought encryption, real device identity and the internet in one step, without adding a second way to sync.
If you would rather nothing left the building, choose Only on my local network in Sync settings. Relays go off and everything still works nearby.
RECN Node
RECN Node is the always-on server for a household or studio: one install per Mac, PC, Linux box or NAS. It is a library that is always awake, held on its own disk, so a device that was off can catch up from it and a library is reachable even when every laptop is shut. It is not a cloud and not an account. Rec and Work on a phone never need one.
Libraries. A Node holds libraries, one per person per product: your Rec library, your Work library, a housemate’s Work library. Each has its own store, its own files and its own key, so nothing is shared by accident. Several people can use one Node from day one.
Running it. Unpack the archive and run bin/recn_node service install. It registers as a per-user service that starts at login and prints the status page URL. That page is served on the machine itself, on localhost, and shows the Node’s people, libraries, devices and storage.
Pairing. The status page shows a pairing code per library. Scan it from Rec or Work on a phone or desktop and the two trust each other, the same way two of your own devices do. The code holds a key and a one-time token that expires in five minutes. One Node can also pair with another, so a home and a studio stay current with each other.
LAN or relay. Syncing runs over Iroh. On the same network your devices reach the Node directly, with no internet. Away from home they try a direct line first and fall back to a relay that forwards sealed packets and keeps nothing.
For agents. recn-node mcp starts an MCP server, so Claude Code, Codex and other harnesses can list projects and create notes and drawings in a library on the Node. They reach your devices through normal sync.
What isn’t there yet
- Relays are n0’s public ones for now. RECN-run relays come before launch.
- There are no accounts. Pairing is device to device, which also means no web access, and no recovery if you lose every device you own.
- There is no cloud copy. RECN Node is the always-on device you run yourself, speaking the same protocol, not a separate cloud sync.
- Desktop apps still hold their own copy of a library. Over time they will lean on a local Node instead, installed and started by the app itself.
- Phones sync while Rec or Work is open. Background sync is not built.