Devices
Guided rollout
Halo and Windows
Use Halo Endpoint on Windows for guided, metadata-first discovery of supported AI signals.
How Halo works with Windows
Halo Endpoint supports guided discovery on Windows, including signals from AI applications, browsers, IDE plug-ins, developer tools, local runtimes, and model artifact locations.
The sensor uses metadata-first collection and can provide paths, hashes, and permissions as evidence. Standard collection excludes prompts, responses, documents, clipboard content, and credentials.
Governance
What Halo governs for Windows
AI application signals
Surface supported application, browser, IDE plug-in, and developer tool signals on enrolled Windows devices.
Runtime and artifact signals
Discover supported local AI runtime and model artifact location signals.
Metadata-first evidence
Use paths, hashes, and permissions to support review of detected AI-related items.
Collection boundaries
Keep prompts, responses, documents, clipboard content, and credentials out of standard collection.
Setup
Get connected in three steps
- 1
Plan guided deployment
Review Windows enrollment scope and discovery settings with Halo.
- 2
Enroll devices
Deploy Halo Endpoint to selected Windows devices and confirm that they report signals.
- 3
Review inventory findings
Classify AI records from device metadata and route items for follow-up review.
FAQ
Questions, answered
No. Standard collection is metadata-first and excludes prompts, responses, documents, clipboard content, and credentials.
Halo Endpoint discovery uses guided rollout to review device enrollment and collection scope.
Put a halo around the AI your business runs.
See discovery, runtime policy, approvals, and evidence working together on your own use cases.