Parking Violation: the fire lane, kept clear

What it does

Svid describes every frame of the footage it watches, and Parking Violation is a paid check over those descriptions, running on every analysed frame of the cameras it's enabled on. When a vehicle is somewhere it clearly shouldn't be, the alert describes the vehicle and exactly where it is, with a link to the moment, and lands on screen, by email, or by JSON webhook. One event fires one alert; re-fires within two minutes fold into the same continuing event, so a van sitting in the lane doesn't page anyone sixty times.

For the people who manage the tarmac

Property managers, residential blocks, private car parks, forecourts. The problem is rarely the ticket. It's the blocked exit while a delivery waits, the loading bay that one particular van keeps treating as its own, and the fire lane that's fine right up until the day it very much isn't. ‘We didn't know’ is a poor line in that meeting.

The alerts also settle the recurring disputes. When a tenant insists the bay is always taken and another insists it never is, a set of timestamped clips is a shorter conversation than either version.

Where it runs

It's enabled per camera, and a whole folder of car park cameras can have it applied in one action. A car park is a slow scene, so the Standard watch level (a frame every 5 seconds) is plenty and Economy (every 15 seconds) often does the job; all levels are motion-gated, so a quiet forecourt costs little to watch. It reads RTSP feeds from the existing recorder, uploaded exports, or a propped phone, and recorded footage runs through the same pipeline, so you can trial it over last month's footage first. A fully on-prem appliance mode exists for sites where footage can't leave the network.

What it costs

The Store prices Parking Violation from your own usage before you buy, shown as ‘+$X/mo at your usage’ next to the check. 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. If what you want is a running record of vehicles in and out rather than violations, that's the Vehicle Log check instead.

Does it read number plates?

No. There's no ANPR or LPR anywhere in Svid, deliberately. The check describes what's visible: colour, vehicle type, and exactly where it's stopped. If enforcement needs the plate, a human reads it off the clip.

Will a car parked there for an hour keep alerting?

One event fires one alert. Re-fires within two minutes are recorded as continuations of the same event, so a long stay reads as one continuing event rather than a page of duplicates.

What counts as a violation?

What's clearly visible: a vehicle blocking a fire lane, exit, loading bay or crossing, or parked across hatched or marked restricted bays. It judges the scene, not a permit list, so the alert is a flag for whoever manages the site.