For IT, OT & Security Architects
AI on your cameras, without opening your network.
Camnitive reads your existing cameras over RTSP and ONVIF, runs on a GPU box at each site, and keeps raw video inside your perimeter. Devices only ever connect out.
Sound familiar?
What gets in the way.
Cloud video is a non-starter
Streaming plant footage to someone else’s cloud fails residency, privacy and OT-security reviews before the evaluation starts.
Another vendor on the network
Every new system brings firewall exceptions, agents and a larger attack surface that your team owns for ever.
Black-box AI can’t be governed
If you can’t explain why the system flagged an event, you can’t defend it to a review board, a works council or a regulator.
Detect. Measure. Comply. Improve.
The four steps, in your terms.
The same cameras and the same data, each step feeding the next.
01Detect
How detect worksInference stays inside your perimeter
FloFrame runs detection, tracking and rules on its own NVIDIA GPU, next to the cameras. It keeps working offline and catches up when the link returns.
02Measure
How measure worksOnly numbers leave the site
Alerts, the evidence you choose and measurements travel outbound on port 443, each device with its own key. No inbound ports, no VPN.
03Comply
How comply worksGoverned and logged by design
Roles down to the page and the device, strict tenant isolation, audit logs and retention by policy. Every alert traces to a rule a person wrote.
04Improve
How improve worksHosted, or in your own estate
Use FloFusion hosted by Camnitive, or deploy it privately in your own cloud or data centre. Scoped API clients and signed webhooks connect your systems.
In practice
Straight answers for your security review.
- What leaves the site? Alerts, the evidence you choose and measurements. Never the raw video stream.
- Footprint: one x86 box with an NVIDIA GPU per site, standard RTSP and ONVIF, no camera firmware changes.
- Network: outbound only, on 443, with a key per device. Nothing on the internet reaches in.
- Access: roles down to the device, SSO and audit logs; retention is enforced by policy, not habit.
Put our architecture in front of your architects
A technical deep dive: deployment options, network topology, integrations and the security documentation behind them.