Trust and security
Trust and security at Hilt.
Hilt collects metadata only and runs single-tenant inside the customer's own cloud, so telemetry about data movement never leaves the customer boundary and Hilt never reads the payload. This page documents the deployment model, the data Hilt does and does not touch, and the controls behind it.
Trust and security at Hilt
Hilt watches how data moves, which means the trust question comes before the product question. Two properties answer most of it.
Metadata only. The collector records identity, path, process, timing, volume, and destination. It does not read the payload. Content inspection is an optional collection mode you turn on where you need it, not the default.
Single-tenant in your own cloud. Hilt deploys inside your boundary, one collector per host or workload, around 0.1% of one core on average. On-prem and airgapped environments are supported. Telemetry about your data movement does not leave your environment to reach a vendor's multi-tenant backend.
See the platform for how collection, identity resolution, detection, and response fit together, or book a walkthrough to review the deployment model with an engineer.