Tailgating Watch: the person who didn't badge in

What it does

Svid already describes every frame of the footage it watches. Tailgating Watch is a paid check over those descriptions, pointed at entrance cameras. Tailgating is a sequence rather than a pose, so the check judges the recent frames together: a door opening, the first person entering, a second slipping through without presenting anything. When the sequence matches, it raises an alert with a plain-English description of the people involved and a link to the exact moment.

The 3am problem

A staffed reception catches most of this. The trouble is the hours nobody staffs. A 24/7 gym or a coworking space runs most of its week on a badge reader and trust, and every person who slips in behind a member is unpaid membership at best. At worst it's a stranger in the building at 3am that no system has any record of, which is an uncomfortable sentence to say out loud after something's gone wrong.

The access log can't help, because as far as the access log is concerned nothing happened: one badge, one open, one close. The camera over the door saw the whole thing. Tailgating Watch is the part that actually watches it.

What an alert looks like

The alert lands on screen and by email with the description and the clip, and every alert is also available as a JSON webhook for whatever your security process already runs on. One event fires one alert; if the check fires again within two minutes, that's recorded as the same event continuing, not a new siren. It's a flag for a human: someone glances at the clip and decides whether it was a guest signing in late or a problem.

Where it runs

Like every check, it's switched on per camera, so it watches the controlled door and leaves the studio camera alone. It reads an RTSP feed from your existing recorder, uploaded exports, or a phone propped with a view of the entrance. A door event is quick, so the Precise watch level (a frame every second at 1080p) suits busy entrances; Standard, at a frame every 5 seconds, is often enough for slower gates. If you've got a folder of entrance cameras across sites, a check can be run across the whole folder in one action, and for buildings where footage can't leave the network there's a fully on-prem appliance mode.

What it costs

There's no rate card. The Store shows Tailgating Watch with a live monthly figure worked out from your own cameras, hours and watch level, as ‘+$X/mo at your usage’, before you buy. It joins a subscription priced from your own usage with a $9 a month floor, and the whole derivation is on screen at signup. The pricing section walks through the arithmetic.

Does it replace the access control system?

No. It doesn't read badge logs and it doesn't drive door hardware; it watches the camera and judges what's visible. The JSON webhook can feed whatever system you already run, so the alert lands wherever your process lives.

What about two members walking in together?

That's exactly why it's a flag rather than a verdict. Each alert carries a description and a link to the clip, so a glance settles whether it was a couple with a gym bag or a stranger timing the door.

Do I need a new camera over the door?

No. If a camera already covers the entrance, the check can run on it. Recorded footage goes through the same pipeline as live, so you can run it over last week's door footage first and see what it would have found.