OmniVigilant gathers municipal open data, weather and traffic feeds, and officially published camera streams into one workstation for authorised analysts. Detection runs on the machine in front of you. Every privileged action is written to a tamper-evident log.
Accounts are created by your administrator. There is no public sign-up.
34
Published sources
34
States reached
13,864
Cameras counted
10
Quality grades
Each of these is a directory in the source tree and a document beside it. None of them is a roadmap entry.
Six live layers over four basemaps: weather and warnings, traffic incidents, flights, vessels, earthquakes and satellites, with routing that answers where a unit can get to inside a time budget.
Every tile and every feed passes through a caching proxy in the Rust core.
Thirty-four published catalogues, drawn as a web rather than a scatter, so density, corridors and gaps read straight off the map instead of having to be counted.
Each site links to its nearest neighbours under a fixed edge budget.
Cameras are graded on what they can actually support: resolution, refresh, framing and reliability. The catalogue sorts on it by default.
The grade refuses to claim a frame is usable for an identification.
A local vision model draws boxes, tracks, and a minimap over any feed. No frame is uploaded to run it, because the model is in the binary.
Detection unions the raw frame with the super-resolved one rather than replacing it.
Two upscaling tiers and optical-flow frame interpolation, with a reveal that puts the original beside the result so nobody presents an upscale as a photograph.
Smoothing probes the feed's real cadence before it interpolates anything.
A vehicle's dimensions are measured by projection from a calibrated camera, and its paint colour is recovered from the scene's own light rather than read off the pixels.
Solved against a synthetic camera with vehicles of known size, in the test suite.
Plates are read only above a measured character height and only past a confidence gate. Below either, the engine says it does not know instead of guessing.
The accuracy cliff sits at forty pixels, and it is documented rather than hidden.
Tracklets, behaviours and zones over selected feeds, searchable after the fact, with a cost model that decides what is worth keeping before it keeps it.
What it deliberately does not index is written down in the same document.
Evidence is filed by camera identity, hashed, and carries a custody history. A recorded clip is filed outside the chain, and the interface explains why.
Exhibit origin is minted from state the interface cannot influence.
Twelve state registers, normalised into one search, with a severity ladder that follows statute rather than a vendor's own scale.
Descriptors are never inferred from a photograph, only read from the register.
Direct, unit and organisation channels. No message can be edited or withdrawn by anybody, including administrators and including Ocsbe.
Reach is proved from an audience token list the security rules can check.
No roles ship with the product. An agency builds its own from a fixed permission catalogue, and editing one re-issues every holder's claims.
Administrator is a flag on an account, so no role can ever grant it.
The network was rebuilt around published United States sources. Seven non-domestic sources were removed, along with the three catalogue formats that existed only to read them. Coverage is what an agency can verify, not what a list can claim.
Alaska and Hawaii carry sources and are drawn beside the totals, not on the projection.
34 published catalogues reach 34 states. 13,864 cameras were counted at the last rebuild. The remaining sources page, so their totals move and no figure is printed for them here.
An instrument used in a proceeding is judged on what it will not claim. These are the refusals, and each one costs the product something it could otherwise have offered.
01
Case exhibits are re-fetched by camera identity, so their origin comes from state the interface cannot influence. A recorded clip cannot work that way, so clips are written outside the custody chain, never hashed as exhibits, and the confirmation explains the difference rather than hiding it.
02
Two gates stand in front of every read: a measured character height and a confidence floor. Below either, no plate is produced. The accuracy cliff was measured, and it is published rather than smoothed over.
03
Register entries carry the descriptors the register published. Nothing derives height, build or anything else from an image, because a number produced that way would be indistinguishable in a case file from one an agency recorded.
04
Not by their sender, not by an administrator, not by Ocsbe. The rules deny every update and delete, no command exists to attempt one, and the composer says so where the sender can read it before they send.
05
The device register compares a workstation's own clock against the timezone recorded for the unit its operator is posted to. That catches a machine somewhere it should not be without a coordinate, a lookup, or a location permission.
06
Nobody at Ocsbe knows what a shift supervisor at your agency is allowed to do. Agencies compose their own roles from a fixed permission catalogue, and administrator is a flag on an account rather than a permission, so no role can grant it.
07
It reaches the model through the platform's own service identity, so there is no credential to leak, rotate or hide. Access is withdrawn by removing a permission binding, not by rotating a secret and hoping every copy is gone.
08
The interface has no outbound network permission. Every request is made by the trusted core, where the credentials are, and credentials are held in the operating system keychain where the interface has no path to read them.
There is no shared login page. Every agency gets its own subdomain, and an account that belongs to one agency is refused at every other agency’s address even when the password is correct.
Your organisation is created with its seats, its entitlements and one administrator. It is given its own address at the same moment, and that address is the only door into it.
maplecounty.ocsbe.com
Signing in at that address, your administrator downloads the desktop application and creates each officer's account: address, role, unit, all in one action. The account arrives already belonging somewhere.
Identity, role and unit issued together
You send them the address. They sign in with the credentials your administrator handed them, take the build for their platform, and the same credentials work in the application.
Windows and macOS, behind the same sign-in
Not on the platform yet? Write to hello@ocsbe.com and we will provision your agency and its address together.