Case study · Computer vision
Phantm Vision
Warehouse monitoring in which camera video never leaves the building: only events and single frames reach the cloud.
- 01Problem
- Warehouse events need to be detected without sending entire camera streams to the cloud.
- 02Solution
- Local video analysis paired with an event dashboard. Only events and individual frames reach the cloud.
- 03Result
- A verified end-to-end flow from the camera to acknowledging an event in the dashboard. The project is not yet released.
01 · Context
Why it exists.
A small logistics company wants to know who was in the warehouse after hours. An NVR system costs too much and needs someone to run it, and cloud products ask you to send the camera feed to someone else’s server. A company like this has no IT department, but it does have a few cameras already on the walls.
Hence the rule everything else follows from: the video stays in the warehouse. And the product is not the model that recognises people, it is correct events - a system that does not wake the owner at three in the morning because the wind moved a tarpaulin.
02 · What I built
What is in it.
- A Windows app next to the cameras: a live view, a camera grid, zones and lines drawn on the image, and a night mode.
- Event filters: entering a zone, crossing a line, staying too long, moving the wrong way. They sift out the noise before anything reaches the owner.
- Working offline: when the network drops, events wait on disk and go out once it is back.
- A browser dashboard: trends, events with thumbnails to acknowledge, cameras and user roles. New events appear without a page refresh.
- A package you unzip and run: the warehouse computer needs neither Python nor a graphics card.
03 · Decisions
The decisions that mattered.
The model only looks at the image when something moves.
WhyFor most of the day nothing happens in a warehouse. A simple motion check drops about 80% of frames before they reach the model, so an ordinary computer is enough and no events are lost.
Helmet and vest recognition was withdrawn.
WhyThe model caught fewer than half the cases of a missing helmet. A safety feature that is wrong half the time is worse than none, because someone starts relying on it.
The customer’s version runs on the processor alone.
WhyThe working environment weighed over 5 GB, almost all of it support for graphics cards that warehouse computers do not have. A separate, lighter build is what made the product installable at a customer’s site at all.
04 · Status
Where it stands now.
The project is not released yet. On 23 August 2026 the first real event went the whole way: from the camera, through the filters and the cloud, to the dashboard, where it was acknowledged 16 seconds later. Installation on a clean Windows machine is still unchecked, and the agent runs as an ordinary program, so someone has to start it. Next come email alerts and reports.




