AIS Edition
AIS Command
AI-Augmented Site Operations
Multi-site operators — schools, retail, offices, facilities
The same engine pointed at operations rather than a household. Sites, buildings, and floors in one hierarchy, with the triage queue, case workflow, and audit trail a real security team needs.
North Gate
Site 1
Loading Bay
Site 1
Lobby
Site 2
Car Park E
Site 2
Dock 3
Site 3
Perimeter W
Site 3
Unrecognised plate at Loading Bay
09:42Site 1 · Vehicle · 2 min
Person loitering, Car Park E
09:31Site 2 · Person · 13 min
Door held open, Dock 3
08:58Site 3 · Access · 46 min
Recent activity
09:31 · Operator 2 assigned #4471
09:02 · Operator 1 resolved #4468, note attached
08:14 · Operator 1 armed Site 3 perimeter
The Command operator console, recreated. Site and camera names are generic — we do not publish screenshots of live client deployments.
Who runs Command
Organisations with more sites than operators
Schools and campuses
Multiple buildings, a small team, and a duty of care that does not tolerate a system nobody watches. Command ranks what needs a human and keeps the rest out of the way.
Retail and hospitality
Shrink, incidents, and disputes across sites that each behave differently. One event model, one identity register, one place the evidence comes from.
Offices and facilities
Access control that has grown organically over a decade, plus cameras nobody has reviewed since install. Command gives the whole estate one operational surface.
Operations
The parts that matter at two in the morning
Feature lists are easy. What separates a system a team actually uses is whether it holds up during a handover, an audit, or a dispute six months later.
Triage that survives a shift change
Events land in a queue with an owner and a state. The next operator can see what was handled, what was dismissed, and why — which is the part that always breaks when a team relies on a group chat.
Every privileged action is written down
Arming, disarming, PIN entry, user changes, and remote-access grants all write an audit record as they happen. That layer is enforced today; the searchable explorer over it is in build.
Evidence that leaves the building intact
An incident exports as an ed25519-signed packet containing summary, snapshot, clip, and manifest, verifiable with a tool that does not require us to be involved.
The alert logic will not go quiet on you
False-alarm learning tunes down the noise, but unknown persons, watchlist matches, loitering, and unrecognised plates are structurally excluded from suppression. Reducing noise must never produce silence.
What Command includes
What Command ships, and what is next
Command is the newer edition. Below is the build order as it actually stands — shipped surfaces first, then what is in flight.
Shipped and running
Live on a deployed system today.
Live
Site status at a glance with the operational indicators a duty operator actually watches.
Events and triage
The raw stream with real filters, plus an operator queue that tracks what has been handled and by whom.
Incidents and case workflow
Assign, annotate, resolve. Every incident exports as a signed evidence packet.
Identity
Employees, contractors, and banned individuals by face and plate, with a shared watchlist.
In build
Specified and on the build order. Not yet shipped — listed so you can judge the direction, not so you can count on it today.
Cameras and video wall
Saved layouts and alarm-driven pop-ups, so an event brings its own camera to the front.
Multi-site hierarchy
Sites, buildings, and floors as a real hierarchy, with every query and event stream scoped to it.
Investigations
Deep search across time, cameras, people, and plates, with the forensic timeline as a first-class tool.
Role-based access control
A permissions matrix over operators and admins. The enforcement layer exists today; the administrative interface is in build.
Audit explorer
Every privileged action already writes an audit record. The explorer that makes them searchable is in build.
SSO and SIEM
SAML and OIDC with SCIM provisioning, plus webhook delivery into an existing SIEM.
Data governance
Your footage does not become someone else's asset
For an organisation with a data protection officer, the useful property is not a privacy policy — it is an architecture where the sensitive data physically cannot be reached from outside the site.
Your property
The appliance in your building
Never crosses the line
- ✕Video and recordings
- ✕Face and plate images
- ✕Scene descriptions
- ✕Any personal or biometric data
Recording, recognition, and scene analysis all resolve here. There is no second copy anywhere, because one is never made.
Our control plane
Fleet health only
Leaves the property →
- →Heartbeat and subsystem status
- →Camera online state and frame rate
- →Storage, CPU, GPU, temperature
- →Error events (metadata only)
- →Appliance version
← Comes back
- ←Configuration changes
- ←Update packages
- ←Restart and self-heal commands
- ←Remote-diagnostic session grants
Compromise our infrastructure completely and you get uptime figures, temperatures, and version numbers. Not one frame of anyone's video.
One property, a household rather than an operations team?
AIS Estate is the better fitTell us how many sites, and who is watching them.
Command deployments start with a survey of what you already own. Existing ONVIF cameras can often be adopted rather than replaced.