Interactive demo

A normal Thursday, then the day we hand you the keys.

Three simulators, all running in your browser. Steer the morning, question the vault, and run the handover with real keys generated on this device.

WhatsApp

Morning briefing

It speaks first. Choose how to reply and watch it handle a voice note, four photos, a PDF and a question fired at it in ten seconds.

07:59
12ZilarchAssistantonline
Today
.
  1. 01
    It messages you first.

    Your day, a follow-up going stale, a reply drafted on an email that came in overnight.

  2. 02
    It shows its working.

    Every claim carries where it knows it from. Drafts are handed to you, and calendar changes wait for your yes.

  3. 03
    Nothing gets dropped.

    A voice note, four photos, a PDF and a question in ten seconds. One answer, everything handled in order.

One continuous WhatsApp chat with its own number, so your personal WhatsApp stays untouched. Tap a reply button under its message to steer the morning.

voice notes · photos · PDFs · questions, all in one thread
The vault

Document recall, with citations

Every answer points at the note it came from. Switch between keyword and meaning search to see what deeper search adds: “handover” finds the email that only says “keys transferred”.

vault · 5 notes · 8 passages · AES-256 at rest
What did we agree with the Dutch buyer about handover?
Assistant · 3 sources

Here's what I have. Pieter agreed to a 60-day completion, with the keys transferred in person at the Marina office rather than via the agent. He asked that the furniture inventory be attached to the SPA as Schedule B, signed before transfer. Dutch buyer, introduced by Sara at the March investor dinner. Prefers WhatsApp voice notes, replies late evenings CET.

[1]email/2026-04-02 Re: Dutch buyer — terms.md
[2]email/2026-04-02 Re: Dutch buyer — terms.md
[3]notes/People/Pieter van Dijk.md
The handover

Cryptographic lockout handover

The last step of every build. You generate the keys, rotate every credential we touched, seal the vault with your own passphrase, and watch our login fail.

  1. 1
    Generate your own keypair
    On your laptop. The private half never leaves it.
  2. 2
    Rotate every key we touched
    Each build-time credential is replaced by you.
  3. 3
    Set the vault passphrase
    Derived in this browser tab. We never see it.
  4. 4
    Watch our access fail
    We try to log in and open the vault, in front of you.
vault-01 · handover sessionkeys: 0
# vault-01 · reachable only over your private link
Real WebCrypto in your browser: keys, signatures and AES-GCM sealing all happen locally.