Primary line of work
Vigil is perception software. It watches live video, decides what is happening, grades how serious it is, and keeps the clip that proves it. It does not identify anybody, and that is deliberate.
Platform
01Motion detection fires on a bin bag in the wind. Vigil answers the question a person would ask: what is happening, how bad is it, and can you show me.
A running prototype today, with a local console, live camera input and a stored event history. It reads pose rather than pixels, which is what lets it tell a person who sat down from a person who went down.
Vigil · from frame to record
SchematicPrototype pipeline. Nothing in this chain identifies a person — see section 02.
Vigil · try it
Runs in your browserLive demo
This runs the reasoning Vigil runs: find the body, decide what posture it is in, then watch whether it stops moving. Stand back so your whole body is in the frame, then work down the checklist.
Your camera opens inside this page. The video never leaves your device, nothing is recorded, nothing is uploaded, and no attempt is made to work out who you are.
Your browser will ask permission first. Stop the demo at any time and the camera is released immediately.
The last one is the point: lying down is not the alarm. Lying down and staying still is.
Not the Vigil model. Vigil runs YOLOv8-pose on local hardware; nothing of that kind runs in a browser tab, so this demo estimates pose with MediaPipe instead. The classification above it — posture, then stillness over time — is the same reasoning. A pose model is fetched from a CDN on first press, so the demo needs a connection.
Limits
02Vigil does not identify anybody. No face recognition, no biometric matching, no watchlist. It classifies situations, not people.
This is a design decision, not a missing feature, and it is the one we get asked to reverse most often. Two reasons hold it in place.
Nothing on this site covers that. Try one of the suggestions, or press Esc and read on.
Try