Quick start.
A typical pilot deploys in two phases — a one-week sensor onboarding window
followed by two weeks of operational tuning. Reference hardware and access
credentials are provided after the briefing.
- Phase 1
- Network access · feed inventory · edge install
- Phase 2
- Model tuning · alert calibration · operator training
- Go-live
- Production rollout · monitoring · on-call
System architecture.
A four-layer pipeline: ingestion, perception, fusion, and command.
Each layer is independently scalable across on-prem, edge, or hybrid cloud.
- Ingestion
- RTSP · WebRTC · ONVIF · drone SDKs
- Perception
- Detection · tracking · re-identification
- Fusion
- Cross-camera handoff · scene model
- Command
- Alerts · dispatch APIs · evidence export
Camera onboarding.
Cameras are registered through the admin console or via the configuration API.
Each feed is auto-calibrated and benchmarked before joining the active fleet.
- Discovery
- ONVIF auto-discovery on local subnets
- Authentication
- Per-feed credentials in secure vault
- Calibration
- Automatic homography
- Health
- Continuous stream and uptime monitoring
API reference.
Stable REST endpoints for event subscription, subject queries, and case
export. Streaming events available over WebSocket for low-latency surfaces.
- Auth
- OAuth 2.0 / OIDC · scoped tokens
- Events
- GET /v1/events · WS /v1/stream
- Subjects
- GET /v1/subjects/:id (history, links)
- Export
- POST /v1/cases/:id/export (signed bundle)
Edge runtime.
The runtime ships as a hardened container image with model weights and
accelerator drivers preconfigured. Updates are signed and verified at boot.
- Targets
- Jetson Orin · Hailo-8 · Intel iGPU · x86 + GPU
- Image
- OCI-compliant · signed releases
- Footprint
- < 1.4 GB RAM per stream
- Updates
- A/B partitions with rollback
Security & access.
Role-based access with fine-grained audit trail. All telemetry is encrypted
in transit and at rest. Event records are tamper-evident for evidentiary use.
- Encryption
- AES-256 · TLS 1.3 (FIPS 140-2)
- Access
- RBAC · MFA · SAML / OIDC SSO
- Audit
- Append-only log · signed export
- Privacy
- Configurable retention & redaction
Billing rail.
Usage metering is per stream-hour and per event class. Settlement is
Solana-first, with Ethereum and Monero phases planned for broader compliance
and privacy-preserving use cases.
- Phase 1
- Solana — micropayments · subscriptions
- Phase 2
- Ethereum — enterprise procurement
- Phase 3
- Monero — privacy-preserving settlement
- Metering
- Stream-hours · event classes · retention tier
Support & SLAs.
Production deployments include 24/7 on-call response and a named deployment
engineer. SLA tiers cover detection availability, latency, and uptime.
- Response
- P1 < 15 min · P2 < 4 hours
- Uptime
- 99.3% baseline · 99.9% tier-1
- Channels
- Email · priority phone · on-site review