Tessr, the home pageProof
Join the waitlist

Proof · the rooms engine in your browser

Don't take our word for it. Run it.

This is the rooms engine, the code under client rooms, compiled for your browser and run on this page, as a research prototype not reviewed outside Tessr. Play both sides: set up a firm, invite a client, seal a file, share a 45 minute review, sign an agreement, remove the client, lose a laptop. After every step, the panel beside it shows what the server holds, and you can search it for any word you typed. Real keys are made for sample names. Nothing you type or pick leaves your browser.

The rooms engineNot started
  1. Firm, current step
  2. Room
  3. Invite
  4. File
  5. Log
  6. Review
  7. Signing
  8. Removal
  9. Lost laptop
  10. The disk
Step 1 of 10Demo clock: the real one, until jumped

A law firm sets up Tessr

The firm's root key comes from 24 words, shown once on paper and never to a server. A recovery key is split in three; any two open it, one alone shows nothing. Two devices join the signed company directory.

Honest limits

Long-lived keys like the root and admin keys belong in the installed apps, not a browser tab: a browser can give away how long a secret took to use. Here they are made for this run and die when you leave the page.

The code has not been reviewed by anyone outside Tessr. An external audit comes before any real client data touches it.

A server that shows two devices two different company histories is caught only when those histories meet: a shared room log, or two people comparing safety codes.

  • 2 of 3Recovery shares open a room when a laptop is lost. One alone shows nothing.
  • 5Wrong codes, then the server deletes the invite. It keeps only its ID.
  • 120 sThe log holds still for a key change. Nobody writes their way out of it.
  • 0Requests to anyone else. The engine's three files come from this site, once.

A research prototype, not reviewed outside Tessr, with no real client data. Sample names and files, unless you bring your own. The invite's code is shown here only because you play both sides; an app would show it only after the link is copied, to send another way. Nothing leaves your browser: the engine's files come from this site, nothing is sent or stored, and the server is a model inside the engine. The text in typewriter letters is the engine's own output.

What this proves, and what it doesn't.

The engine runs; the apps, the server and the hosting around it are not built yet. The limits are listed under each step, and the plain list of what Tessr can't do is on the home page.

What Tessr can't doOr follow one file through Tessr