Detection on the Streams AxxonSoft Already Carries
No AxxonSoft connector is prebuilt. The connection would be to the stream, on the RTSP path that already carries Axis, Hanwha and Verkada, and AxxonSoft is one of the platforms that path has been exercised against, so an engagement scopes configuration and verification rather than development. AxxonSoft builds video management and analytics software deployed across industrial and municipal sites, and it would stay in place as the video management system. AI Live Insight would read streams alongside it.
How it connects
Streams would be consumed over RTSP, from the cameras or republished by AxxonSoft, each source added by address, port, stream path and credentials. Encoding would stay where it is: the existing H.264 or H.265 bitstream read as emitted with the codec detected per source, so nothing is re-encoded and no encoder load is added to the recording servers.
The flow would be inbound only. Detections would become a timed metadata track beside each recorded segment, and the clip around an event would be filed in the library under one Recording Folder organized by camera, carrying its access control, retention and chain of custody. Classes, thresholds, severity, zone rules and the seconds kept either side of an alert would be set per camera in the portal.
Nothing would flow back. Camera control, device management, AxxonSoft's own analytics and its user management would stay with AxxonSoft. Where AxxonSoft is already running its own detection, an engagement would settle which system is authoritative for which event rather than leaving two sets of alerts to be reconciled by an operator. Because analysis reads the live stream, it would run on a GPU server on the same network.
What you can do together
- Add detection to an existing AxxonSoft estate without replacing a camera or changing how it records.
- Keep the clip around an event as evidence under retention and a custody record, while continuous recording stays where it is.
- Decide per camera what is worth an alert, rather than applying one rule to an industrial site.
- Run the analysis on site, so an alert arrives in seconds.
A scenario
- ScopingThe engagement would confirm which cameras cover the compounds, how their streams are reached, and which events AxxonSoft should keep owning.
- SetupA GPU server would be placed in the utility's own network, and the compound cameras added.
- ConfigurationA zone rule would cover the fenced area, active outside working hours, with clip length set to show the approach.
- A nightA detection would raise an alert on the dashboard, and the clip would be filed in the library under that station's folder with its custody record.
- AfterwardsThe investigation would work from the library clip and its timed detections, while AxxonSoft holds the continuous footage.
What stays where
AxxonSoft remains the video management system
Cameras, recording, its own analytics and its users stay there.
The stream is the whole of the connection
Inbound only, with nothing written back.
Evidence lands in the library
Clips around events carry access control, retention and chain of custody.
Processing would run on site
A GPU server on the same network is what keeps alert latency low, and it is the deployment this work is projected for.
Products and solutions
Next step
See it on your own AxxonSoft instance. We will show the connection made, the data moving and the output, then size it for your deployment.
Request a demonstration or write to sales@vidizmo.ai
sales@vidizmo.ai · vidizmo.ai/integrations/catalog/axxonsoft