Dhi's architecture is designed to meet the security and privacy requirements of unions, regulators, and enterprise security teams.
Trust Signals
These proof points stay visible as text so privacy, legal, and operations stakeholders can assess data movement, retention, encryption, and review paths before they ever open a call.
Privacy posture
The page explicitly states what leaves the premises and what never leaves the premises so privacy reviews can happen from source text alone.
Data movement
Operators can review the event payload, retention posture, and clip-governance model before any live security meeting.
Encryption
The page answers how data is protected in transit and at rest rather than relying on vague trust language.
Stakeholder path
Visitors can move from research into a security review without being forced through a generic demo ask.
Compliance signal
The compliance section and metadata payload give legal, OT, and privacy teams concrete material to inspect.
Dhi's edge-native architecture ensures that sensitive video data stays under your control
Raw video never leaves your premises by default. All inference happens at the edge, ensuring complete control over sensitive footage.
Only structured events and policy-approved clips are transmitted off-site. Configurable policies ensure compliance with internal and regulatory requirements.
All data in transit uses TLS 1.3. Data at rest is encrypted using AES-256. Key management follows industry best practices.
Granular permissions for viewing events, accessing clips, and configuring patterns. Full audit trails for all access and configuration changes.
Complete audit logs for all system access, configuration changes, and data exports. Designed to support FIPS and FedRAMP requirements.
Configurable retention policies for events and clips. Automated data lifecycle management and secure deletion capabilities.
Dhi's privacy firewall ensures only approved data is transmitted
Dhi generates structured metadata events at the edge. Below is a sample operative payload showing how person-down alerts are formatted before being pushed to your VMS Alarm stack.
{
"event_id": "evt_9x2kL01",
"timestamp": "2026-03-30T10:14:22.451Z",
"pattern": "PERSON_DOWN",
"confidence": 0.984,
"location": "Platform 4 - South Wing",
"edge_node_id": "node_772",
"metadata": {
"latency_ms": 142,
"vms_alarm_triggered": true,
"privacy_masked": true
}
}Dhi is designed to meet the requirements of regulated industries and government agencies
For detailed security documentation, compliance reports, or to discuss specific requirements, please contact our security team.
Review the edge-node, camera-ingest, and alert-routing model that sits behind the security controls.
Use the comparison page when procurement needs the latency and privacy tradeoff in one place.
Share the checklist with privacy, OT, and operations teams before the first implementation review.
Security traffic is high intent when the team can quickly access architecture details, deployment controls, and a human conversation for stakeholder review.
Use this path when privacy, union review, or regulated-environment sign-off is the blocker.
See the flow on a real operating scenario and scope a pilot around one facility or corridor.
Review camera ingest, edge inference, alert routing, and what stays on-premises.
Download the deployment checklist buyers use before green-lighting an industrial AI pilot.
Bring camera count, VMS constraints, latency expectations, and privacy requirements to a technical review.