Feature Library
<0.01 CPU ms
A still of the Sealed relay demo
Still
The live demo starts when it’s in view.Tick or rename a line in A and watch it cross the relay as noise · try a forged edit, a tampered message or a replay

End-to-end encrypted live collaboration over a relay that can’t read.

What it costs a frame

<0.01 ms
GPU
not used
CPU, median
<0.01 ms
CPU, 95th pct
<0.01 ms
Draw calls
0
Weight
Light

Measured 13 November 2026 on RTX 4060 Laptop, 13th Gen Intel(R) Core(TM) i9-13900H, Chrome 157, 1920×1080 at 1×. 600 frames × 3 rounds, median kept (rounds ranged CPU <0.01–<0.01 ms). What ran: Measured with the demo running its three attacks in a loop at a 60 ms network delay: real AES-GCM sealing and ECDSA signing and checking in the page for every message, a forged edit, a tampered message and a replay refused, presence every 3 s, and both lists re-rendering on every change. Outside the bench, only the presence heartbeat runs between changes. Phones: tiers are being measured next.

On every machine it was measured on
MachineGPU msCPU msCPU p95
RTX 4060 Laptop · 13th Gen Intel(R) Core(TM) i9-13900Hreference · measuring toolnot timed<0.01<0.01
apple · Apple A19 Proin a browser tab · 16 November 2026not timed<0.01<0.01
Intel Arc 140V (Xe2-LPG) · Intel Core Ultra 7 258Vin a browser tab · 15 November 2026not timed<0.01<0.01

Bars against one 16.7 ms frame. A browser-tab run is timed in a visible tab without the tool’s scripted input, so read it as close, not exact.

What it needs

Renders with
DOM and CSSPlain DOM and CSS: every current browser.
Your browser
Runs hereNo WebGPU needed
Depends on
NothingNo other packages

What it’s for

  1. Sharing a live board or document by link, with nothing readable on the server
  2. A read-only link that can watch but never change
  3. Collaboration on a local network with no cloud
  4. A relay or server you don’t have to trust
  5. Rehearsing a sync protocol without a network
  6. Testing that tampered, forged and replayed messages are refused

Pitfalls, in brief

  1. The link is the key. Anyone who sees the whole link can read (and, with the edit link, change) everything: browser history, a synced profile, a chat log, a screenshot.
  2. The part after # never reaches a server, but every script on the page can read it (location.hash).
  3. crypto.subtle exists only on secure pages: https, or localhost.
  4. The relay can drop, delay, reorder and replay messages.
  5. A signature proves “someone holding the edit link”, not who.
6 more in brief
  1. Updates are not queued while the relay is away; the whole document goes out on every reconnect and to everyone who joins.
  2. The relay still sees the room’s name, how many are connected, their addresses, and the size (to the padding step) and time of every message.
  3. One sealing key for the session’s whole life: no forward secrecy and no rotation.
  4. The last-write-wins list refuses a write whose clock is more than 2^32 ahead of the highest it holds (MAX_JUMP), so one bad edit link can’t push the clocks to where they no longer count.
  5. Peer ids are random per page load (the default).
  6. The Cloudflare adapter is reference code: it follows the documented Durable Object API but has not run on the platform from here.
11 pitfalls in full, the hook-up guide, the module source and its tests come with the part.

Where it comes from

From SpaciousPro. Fully custom code.

W3C Web Cryptography API: AES-GCM (NIST SP 800-38D) with a random 96-bit nonce, and ECDSA on P-256 with SHA-256, as the browser provides them; nothing is implemented here

RFC 6455, The WebSocket Protocol: the framing in server/relay.mjs, written from the RFC in the source app

RFC 5280, X.509 certificates: the self-signed certificate server/relay.mjs encodes by hand (DER), from the source app

Lamport, Time, Clocks, and the Ordering of Events in a Distributed System (1978): the logical clocks behind the last-write-wins list

Cloudflare Durable Objects: WebSocket hibernation: acceptWebSocket and getWebSockets as documented; the adapter is the library’s own code

WAI-ARIA Authoring Practices Guide (W3C): toggle buttons (aria-pressed) for the link switch and the attacks, and announcements through a polite live region, in the demo

end-to-end encryptionE2EEAES-GCMECDSAP-256Web Cryptocrypto.subtlesignaturesread-only linkshare linkURL fragmentrelayWebSocketlive collaborationpresencereplay protectionpaddingCRDTlast write winsYjsself-signed certificateCloudflare WorkersDurable Objectslive region

Near it in the frame