What if that one minute has to be found two months from now?
Anyone can record. Finding the exact minute two months later is another matter.
A mid-sized site records tens of thousands of hours a month. When something happens, someone has minutes — not days — to pin down the moment, watch it alongside the neighbouring cameras and produce a copy that will hold up in front of a third party. IRIS covers that whole path on one screen: you search inside the video, you protect what must not be deleted, and you hand over a file the recipient can check for themselves, without depending on us and without internet.
At a glance
What it can do
Search inside the video
Fifteen filters that combine: which object, what colour, what it did, where in the frame and between which hours. Forty hours of footage come down to a short list.
Ask for it in words
Type “red cars between two and six” and the sentence turns into filters. Before searching it shows what it understood, and whatever it could not apply it says so, with the reason.
Search by likeness
Click an object in the image and look for where else it appears. The screen says it plainly: this is a likeness, not an identification, and a person reviews it.
Eight hours in minutes
The summary skips the dead time and shows only what happened. It can also lay everything that crossed the scene onto a single frame, filtered by object type and colour.
What does not get deleted
A locked stretch is not deleted — not when retention expires, not when the disk fills up. And if the system cannot check whether a lock exists, it deletes nothing and writes that down.
Verified without internet
The exported package carries its fingerprint, its signature and a checker that opens in any browser with no connection. Whoever receives the video confirms nobody has touched it, without depending on us.
Cover what must not be seen
Before handing it over, whatever must not leave is blurred, pixelated or blacked out, and it is baked into the video — not a layer anyone can peel off. If the masking fails, the export is aborted; the original never goes out believed to be masked.
Who watched what
Every viewing, jump, snapshot, download and export is logged with user, time and which stretch of video was watched. That log does not expire with the video it describes.
Four angles at once
Reconstructing an incident is not opening four windows: it is watching four cameras move together under one set of controls. The whole wall is taken to the same time, and the system says how many cameras have no footage at that moment.
If a machine goes down
Recording spreads across as many servers and sites as needed, and every clip is stamped with which server wrote it and which one serves it. One node going down does not drag the others with it, and when the network comes back, files left stranded are indexed again on their own.
When retention does not fit
The system compares the days you configured with the days actually on disk. If the disk fills up before retention expires, it says so on screen instead of keeping quiet and deleting anyway.
Masked while watching too
Some parts of the frame are blacked out for everyone, not only on export. Revealing them for a while requires a written reason, a time limit and, where the organisation demands it, a second person’s approval.
The day it matters
From the alert to a file that holds up in front of a third party
The problem is never too little video: it is too much. Someone describes what happened from memory — “a white van, in the afternoon, Tuesday I think” — and there begins a day lost in front of a timeline. IRIS changes the question: instead of watching hours, you filter. And there are fifteen filters, nameable one by one: date and time, cameras, object type, colour, colour mode, colour tolerance, region of the frame, behaviour, minimum duration, heading, motion inside a drawn area, likeness to a marked object, free text against the video itself, the plain-language sentence and the number of results. They combine with each other, and what comes back is not a stray box but one object with all of its sightings grouped together. When the list is trimmed it says so — so many out of so many — and it never passes an incomplete list off as complete.
The second question comes later: will that video still be there in three months? Each camera has its own retention, and the screen also shows how many days are really on disk — sometimes fewer than configured, because the disk fills up first. On top of retention sit two protections: marking one recording as evidence, and locking a whole stretch of a camera between two times, including what has not been recorded yet inside that stretch. A reason is mandatory and a lock can be left with no expiry. When an incident is opened, the material in its window locks itself. And if the disk fills up and the only old material left is locked, the system stops and writes it out in plain words rather than sacrificing evidence for want of space. Releasing a lock requires a reinforced permission and a written reason, and the record does not vanish: it stays marked as released, with who and why.
Then comes the moment of handing it over. An evidence package is not a loose video in a folder: it carries a manifest with who exported it, when, from which camera, which stretch and under which case reference; a fingerprint for every clip and one for the whole package; a digital signature; and a checker that opens in any browser and works with no connection. That last part is what almost nobody has, and it is what really changes the conversation: whoever receives the video can verify on their own that nobody has touched it — without calling us, without installing anything and without internet. The watermark burns in the real date and time of each frame, not the clock of whoever exported it. The package can be encrypted with a password, and before it is handed over it checks itself: if the check fails, it is not delivered. It is built to stand up in front of a third party; whether it does is always that third party’s call.
All of this connects to the rest of the site at one very concrete point: across the nine zones, every alert keeps its video. This is the part that explains what happens to that video afterwards. From the alert you jump to the exact instant, pull every camera in the wall to that same time and see what happened from several angles at once; the timeline never hides what is missing, and flags each gap with how many seconds it is. We also say what it does not do: likeness search keeps roughly the last two weeks and identifies nobody — it is a resemblance, reviewed by a person; face recognition is available only outside the European Union; and when the AI could not properly look at the video, it says so instead of returning an empty list. Everything travels over a single port, 443, so the network team does not have to open a whole range. And it works with no internet: the models are our own and live inside the customer’s installation, just like the checker inside every exported package.
An incident almost never fits inside one camera. IRIS puts the whole wall on the same instant under a single set of controls: you go forward, back and pause on all four at once, with twelve playback speeds — smooth reverse included — and frame-by-frame stepping when it has to be exact. You jump to a precise date and time, and the link to that instant can be pasted into an email: whoever opens it lands on the same second, not somewhere nearby. When you do not know what you are looking for, a whole day can be skimmed as a strip of stills or as a grid showing when there were people and when there were vehicles, hour by hour, minute by minute or second by second. And what someone writes down stays: a bookmark with its title, its note and its tags outlives the video that prompted it, because a person wrote it.
The question everyone who has ever lost footage asks is where this lives and how long it lasts. Recording spreads across as many servers and sites as needed — different countries and time zones — and is governed from one single view; every clip is stamped with the server that wrote it, the one that serves it and its camera’s time zone, so it plays back and searches the same from any workstation. Retention is set by the customer, camera by camera, and that setting overrides the server default: it can be left with no limit, and an odd value is never read as delete everything. When video does get deleted, it takes with it the eleven kinds of derived data it had generated, each with its own switch in case it is worth keeping; bookmarks are deliberately left out. And none of this is decided at our end: the material lives inside the customer’s installation and goes to no third party.
The figures
Counted, not estimated
- 15combinable filters for searching inside the video
- 32separate permissions: who watches, who exports and who releases evidence
- 9behaviours you can search for inside the recording
- 443the only port to open: video, search and export
- 11kinds of derived data deleted along with the video, each with its own switch
- 12playback speeds, smooth reverse included
Questions
Can something be found in the video without knowing the exact time?
Yes — that is what the fifteen filters are for. You narrow it down by date range, cameras, object type, up to four colours, a specific part of the frame and one of nine behaviours, and they all combine. You can also just write the sentence in plain language and the system turns it into those filters, showing what it understood first. And if the range is still long, the summary skips the dead time and turns eight hours into a few minutes of review.
How does the person receiving the video know nobody tampered with it?
Because they check it themselves. The exported package includes a fingerprint for each clip, one for the whole package, a digital signature and a checker that opens in any browser. That checker works offline: it calls no server, ours or anyone else’s. If anything has been changed — a frame, a byte, the manifest — the check fails and says so. And before being handed over, the package verifies itself; if it does not pass its own check, it is not delivered.
What if the disk fills up while that video is part of an open case?
It is not deleted. A locked stretch sits outside recycling, and the disk rule cannot override it. If the only old material left is locked, the system stops, writes it into the log in plain words and raises a warning, instead of sacrificing protected material to gain space. The check runs three times before anything is deleted; if any one of the three cannot be carried out, nothing is deleted — it is never assumed there were no locks when the truth is that nobody could look. The screen also shows how much disk is tied up by locks and how many of those have no expiry date.
How much video can really be kept, and who decides how much?
Retention is decided by the customer, camera by camera, and it overrides the server default; it can be left with no limit so nothing is deleted for being old. The real ceiling is not the software, it is the disk: that is why the screen does not just show the configured retention but the days actually on disk right now, and warns when there are fewer because the disk fills up first. Recording spreads across as many servers and sites as needed, so growing means adding disk where it is short. And the decision is not taken at our end: the material lives inside the customer’s installation.
And if someone tries to delete a recording tied to an open case?
They cannot, and the attempt is written down. Locked material sits outside automatic deletion, and deleting by hand needs its own permission plus having that camera assigned. Lifting a lock requires the reinforced permission — the same one that governs erasure requests — and a written reason; the lock record does not disappear, it is marked as released with who, when and why, and the lock history is permanent. And every deletion, every export and every release lands in the audit log with the state before and after, chained so that an altered or removed entry shows up.
The real interface, step by step
You set the rule once. IRIS applies it every time.
You will see a summary of the interface, played step by step and hands-free. Each round starts with another case. The complete tool does not fit in a demo.
- The alert fires
- You open it
- You confirm or dismiss
Next step
Public transport
Who watches a whole station at rush hour?
17 cases: 11 raise an alert when something happens and 6 only measure. You see each image as it is, and then with what IRIS understands on top.
Retail
Who sees the sales that never reach the till?
10 cases: 4 raise an alert when something happens and 6 only measure. You see each image as it is, and then with what IRIS understands on top.
And the best part
You already record.The hard part was always watching it.
Years of video that only get opened once something has gone wrong. IRIS understands those same images as they arrive, so the answer no longer lives only in the archive.
Tell us your problem and we will say whether IRIS understands it, or not yet.
We reply the same working day.