Evidence Lock to STRAVIX Cloud - Automatically
Operators create a single evidence lock in Smart Client. The integration handles the rest - exports the locked video, writes case metadata, and hands it off to STRAVIX Cloud for ingest.
STRAVIX Cloud Uploader listens to the MIP event bus for new evidence locks. When a lock matches the configured export profile, it walks the lock's cameras, drives a full MKV export per camera via ExportPathMkv, writes a JSON sidecar with case/lock/camera metadata, and drops the pair into a watch folder for STRAVIX Cloud ingest. Designed to replace the operator-driven export workflows that quietly fail in production.
The technical surface.
What it does, said plainly.
Profile-driven filtering
Only locks tagged with your configured export profile trigger an export. Routine locks are seen and ignored - no noise in the pipeline.
Per-camera MKV export
Each camera in a multi-camera lock exports independently to MKV with audio when available. One bad camera doesn't block the rest.
Chain-of-custody sidecar
A JSON sidecar lands next to every MKV - case ID, lock metadata, exporter, time range, file size, and SHA-256 hash (when enabled).
Host-agnostic core
All logic lives in a Core library. Ships as a console host today and converts to a Windows Service with a 50-line host swap.
How it's wired.
- 01Smart Client user creates an evidence lock with the configured profile
- 02Milestone Management Server raises EvidenceLockChanged on the MIP event bus
- 03Service filters by profile, fetches lock metadata, exports each camera to MKV
- 04Sidecar JSON written next to the MKV with full case + lock context
- 05Watch folder ingest in STRAVIX Cloud picks up the file pair
Real customer scenarios.
Bring STRAVIX Cloud Uploader into a deal.
Demo against your customer's actual workflow. Pricing the same day.