QuantineliQ AI
AI that watches every camera and device, and shows its evidence
RCC turns the cameras you already have into 290+ AI video analytics, face and plate recognition and search in plain words, with a copilot that drafts summaries and answers questions. QUME’s AI finds anomalies on laptops, phones and servers and drafts the fix. Every answer cites what it used, and every drafted action waits for a person.
Runs on your own serversAnswers that cite their evidenceDrafts wait for a person
RCCCopilot
Sees what you may seeSample data
Red jacket and a backpack at the north gate after 9 pm
- 1North gate 221:07:41Match 0.93
- 2North gate 321:09:02Match 0.88
- 3Lobby 121:12:30Match 0.81
One person matching the description came through North gate 2 at 21:07 1, walked past North gate 3 at 21:09 2, and reached the lobby at 21:12 3.
3 of 3 statements cite a clip · saved as a journey you can export
RCC · Vision AI
Every camera becomes a sensor that understands what it sees
Analytics run next to your cameras, on a GPU or a CPU, with no internet connection. In RCC an analytic is configuration, not another product, so adding one is a change to a camera rather than a project.
1 / 22Face recognition
RCC · Copilot
A copilot that drafts, answers and cites
The copilot drafts investigation summaries and shift briefings, answers questions in plain language and suggests actions. Every sentence in a report cites its evidence; any name, number or time not found in the cited results is removed and listed.
Investigation summaries
A first draft of what happened, with links to every clip and event it used.
Shift briefings
What the incoming shift needs to know, written from the outgoing shift’s record.
Plain-language search
Ask across video, events and records; the translation is shown before it runs.
Scoped to your role
The assistant sees only what the person asking may see, and every run is audited.
QUME · AI insights
AI that finds the anomaly on your endpoints and drafts the fix
QUME’s AI reads the events from every laptop, phone and server it manages. It flags anomalies, predicts what is about to go wrong, recommends changes, and drafts remediations and policies. Each one waits for a person’s review before it acts.
- Anomalies in sign-ins, processes and network activity
- Predictions, such as devices about to miss a patch window
- Recommendations with the evidence behind them
- Drafted remediations that act inside a blast-radius budget
- An assistant that explains any policy decision from its trace
QUMEAI insights
Sample data
AnomalySign-ins at night from a new network on three finance laptops03:12
14 sign-ins between 02:10 and 03:40 on ws-fin-114, ws-fin-118 and lt-fin-031, from a network none of them has used before. Mapped to MITRE ATT&CK T1110, brute force.
Drafted Require step-up sign-in for the finance group and open an investigation with the three devices attached.
Waits for review by a person before it acts
Prediction38 laptops will miss Tuesday’s patch window09:40
At their current check-in pattern, 38 laptops in the sales ring will not be online before the window closes at 18:00 on Tuesday.
Drafted Move them to Wednesday’s ring and tell their owners, with the patch cached at their branch.
Waits for review by a person before it acts
RecommendationTurn off SMBv1 on 112 Windows servers10:05
SMBv1 is still enabled on 112 servers, and no client has used it in the last 30 days.
Drafted A drafted policy turns it off in three rings, with a rollback if a server reports a failure.
Waits for review by a person before it acts
Drafted remediationIsolate srv-web-04 from the database network10:22
Web shell indicators on srv-web-04 (MITRE ATT&CK T1505.003), with outbound connections to an address seen nowhere else on the estate.
Drafted A drafted playbook isolates the server inside its blast-radius budget and keeps the console session for the investigator.
Waits for review by a person before it acts
QWorks · Gatehouse
AI at the gate, on one box
QWorks Gatehouse reads every vehicle’s number plate as it arrives, alerts the unloading team and opens the visit. Its analytics run on the gate’s own box, on a CPU or a GPU, and keep working when the internet is down.
Licence plate recognition
Every vehicle identified at the gate, and its visit opened from the plate read.
Vehicles in the yard
Checkpoint crossing, vehicle class in zone and dwell violations, raised as they happen.
Every visit on video
Live view and playback of every gate, with a sealed record of each visit.
AI you can trust
AI built for operations where a wrong answer has a cost
The same rules apply to every AI feature in RCC, QUME and QWorks.
Runs where your data stays
Analytics run on servers at the site, next to the cameras. Nothing needs the cloud, and air-gapped sites run the same software.
Evidence on every answer
Every sentence the copilot writes cites its source, and anything not found in the cited results is removed and listed.
A person decides
Drafted remediations, policies and recommendations wait for review, and automated responses stay inside a blast-radius budget.
Scoped and audited
The assistant sees only what the person asking may see, and every run is recorded in the audit trail.
Measured, not assumed
Each camera channel and engine has a reliability score, and confidence drift is tracked, so a degrading camera is noticed.
Your own models
The model lab takes your datasets through training, evaluation and deployment, beside the built-in analytics.
Questions
What buyers ask about the AI
Does the AI need the cloud or an internet connection?
No. Video analytics run on servers at the site, next to the cameras, and keep working without an internet connection. RCC runs the same way connected, on premises or air-gapped.
Can the AI act on its own?
Analytics raise events, and events start the SOPs you have configured. What the AI drafts, such as a remediation, a policy or a recommendation in QUME, waits for a person’s review before it acts, and automated responses pass a blast-radius budget.
How do we know the copilot is not making things up?
Every sentence in a copilot report cites the clip, event or record it came from. A name, number or time that is not in the cited results is removed and listed, so the reviewer sees what was taken out.
Can we use our own models?
Yes. The model lab handles datasets, training, evaluation and deployment, and RCC places your models on the same servers as the built-in analytics.
How do we know an analytic is still accurate?
Each camera channel and engine carries a reliability score, and confidence drift is tracked over time, so a camera whose picture is degrading is noticed before its alerts are trusted.
See the AI on your own cameras and devices
Bring a recording from one of your cameras, or a list of your devices. We will show you what RCC’s analytics and copilot, or QUME’s AI insights, find in it.





















