See it work

Through a Canary’s eyes

Security cameras answer “what happened?” by keeping everything. A Canary answers by keeping almost nothing — a handful of tiny, chained events. This bench runs that idea live: watch a scene become a few events, the events become a record, and then try to rewrite history and get caught.

Runs entirely in this tab · nothing is uploaded, nothing is stored · close the tab and the session never happened.

off

Warming up…

What a camera would keep

The scene, in full — every frame, every pixel, forever. This is the pile most systems sit on.

the scene

raw pixels looked at, then let go 0 B

What this bench looks at

160 × 120, grayscale, edges, over a 3 × 3 motion grid — a working view that exists for a moment and is never kept. Only the events on the right are.

working retina

all zones asleep

What the Canary keeps

The only output: small events, each hash-chained to the one before. This log is the whole record.

    kept, in total 0 B

    The whole trick, as a number

    Watching…

    That bar is the log, drawn to scale against the footage. It is barely visible on purpose — the safest footage is the footage that never existed.

    What’s real here, and what isn’t

    This bench is a faithful miniature, not a mock — and where it differs from the hardware, the hardware is stricter.

    The edges view is this page’s illustration, not the kernel’s output

    It is here so you can watch detail drain away. The witness kernel once drew an edge thumbnail like it and removed it: an outline of someone standing close can still be recognized, and “you can’t get the pixels back” is a lower bar than “you can’t tell who it is.” So no edge image is ever kept or sent. What the kernel keeps is the list on the right.

    The grid speaks the event vocabulary

    “Motion in the north-west of the frame” is the level a witness reports at — a where and a when, never a who. Same idea as the kernel’s motion backend.

    The chain is real cryptography

    Every event is hash-chained with SHA-256, right here in your browser (WebCrypto). That is what makes the log tamper-evident: a rewrite cannot re-earn the chain built on the truth. On hardware, each link is also Ed25519-signed.

    The hardware is stricter than this page

    This demo is JavaScript in your tab, and your webcam feed never leaves it. A real Canary runs the pipeline on-sensor: the pixels die in device memory and never reach a browser at all. Read how it works, meet one witness, or see the vault that guards the rare exception.

    Why show a webcam demo at all, on a site about not being watched? Because the argument is easier to feel than to read: point a camera at yourself, watch what a witness would actually keep, and notice that you never appeared in it.