01
The time is unknown
The incident surfaces in a count, not from a witness. You are left with a wide time window.
Your cameras already capture everything. ACALAS turns that footage into searchable incident intelligence — what happened, when, and what it cost. Entirely on your own infrastructure.
An illustrative example query. This field is not interactive.
THE PROBLEM
The count comes up short. The weighbridge shows a gap. Damage turns up in the morning. Nobody knows when it happened. Scanning three weeks of footage across dozens of cameras takes days — and the loss rarely justifies it. So nobody looks. It gets written off. Everyone moves on.
What goes uninvestigated repeats. By year end the write-off line has grown and nobody knows where it came from.
01
The incident surfaces in a count, not from a witness. You are left with a wide time window.
02
Reviewing footage takes days of someone's time. So most incidents are never looked at.
03
The money spent on cameras produces evidence, but not decisions.
THE PLATFORM
Conventional systems store footage. ACALAS reads it: which object, in which zone, for how long, at what time. The output is not a pile of clips — it is a queryable record of what happened.
Find an incident you cannot timestamp by describing the event instead.
Entry, dwell and exit as one continuous timeline instead of scattered clips.
You will be able to export an incident's clips, timestamps and camera IDs as a single file — for insurance, legal, and audit.
You will be able to follow a vehicle or person across cameras as one continuous story.
You will see what is happening at remote sites from a single operations view.
ROADMAP
ACALAS is not a search box. The goal is a system that can account for what happened across an entire operation — and eventually anticipate it. We are building it in five stages, and we say plainly which stage we are on.
01
Locate an incident when you don't know when it happened. Place, action and duration are searched together.
02
You will be able to follow a subject across cameras and reconstruct the full sequence of an incident.
03
You will be told when a situation you defined occurs, instead of searching for it afterwards.
04
Footage will become operational data: dwell times, bottlenecks, repeat violations. Security data will become operations data.
05
Hundreds of cameras across multiple sites will run under one sovereign deployment.
Every stage is measured on real footage before it ships. We do not present anything as working that we have not measured.
WHERE IT WORKS
The pattern is always the same: many cameras, long retention, and incidents discovered by a count rather than a witness. Nobody knows when it happened, so nobody looks.
The scale changes. The problem does not.
PRIMARY FOCUS
01
Scrap movement, shift changeover, unexplained line stoppages.
Usually asked by operations or plant management.
01Scrap movement, shift changeover, unexplained line stoppages.
Usually asked by operations or plant management.
02Inventory gaps, dock dwell time, loading outside schedule.
Usually asked by warehouse management or finance after a stock count.
03After-hours access, material removal, delivery verification.
Usually asked by the site manager or after an insurance claim.
04Damage disputes, parts movement, unauthorised test drives.
Usually asked by the service manager during a customer dispute.
05Stockroom exits, staff exits, return disputes.
Usually asked by loss prevention or regional management.
The same problem exists at a different scale.
These environments share the same problem at a larger scale. The platform is being built toward them; we are not deployed there yet.
EXPANDING TO
Container movement, gate transits, cargo damage disputes
Vehicle flow, inspection lanes, bonded warehouse access
Apron activity, baggage areas, perimeter integrity
Remote unmanned areas, fuel movement, equipment accountability
Large perimeters, distributed cameras, incident review
DATA SOVEREIGNTY
ACALAS runs on your own servers. No cloud, no external transfer, no dependency on an internet link. In camera systems the highest regulatory risk is transfer — and that risk closes at the architectural level, not with a policy document.
This was not added later. It is the founding constraint of the product. For ports, customs, energy and defence-adjacent operators — and increasingly for industrial groups under KVKK and GDPR — sovereignty is no longer a preference.
OUR LIMITS
Vendors rarely say where their system stops. We say it up front.
No face recognition
No person re-identification — it counts as biometric data
No counting
No licence-plate reading
No small-object detection at distance
What we do is place, action and time. We do that well.
Before we sell you anything, we want to test it on your site. Give us a sample from an incident you already know about, and we will share the result in writing — whether it works or not.