> ## Documentation Index
> Fetch the complete documentation index at: https://docs.originhq.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Origin Agent Installation: Supported Platforms and Methods

> The Origin agent is a background service for Windows and macOS that monitors AI traffic in real time. Learn supported OS versions and deployment methods.

The Origin agent is a lightweight background service that installs on your endpoints and collects AI activity in real time. Once installed, the agent gathers events from the AI tools running on that host, enriches them with endpoint context, and reports the activity back to the Origin platform — giving your security team full visibility into how AI is being used across the fleet.

## How the agent works

The agent runs as two cooperating services: the **core agent**, which collects AI event data and reports telemetry, and a **watchdog service**, which starts at boot and automatically restarts the core agent if it ever stops.

Capture happens at the application layer on both platforms. The agent configures each AI tool's native **OpenTelemetry** exporter to report to a local collector it runs on the endpoint's loopback interface, and uses **application-level hooks** for applications that expose no telemetry of their own. There is no network proxy, no traffic interception, and no certificate to trust. All collected data is forwarded over outbound HTTPS to the Origin cloud.

<Note>
  The collector's loopback port defaults to 4318 and is configurable fleet-wide from **Settings → Settings**. Change it only if your endpoints already run a corporate OTel collector on that port — see [Console Setup](/getting-started/console-setup).
</Note>

## Supported platforms

| Platform       | Minimum version       |
| -------------- | --------------------- |
| Windows 10     | Latest builds         |
| Windows 11     | Latest builds         |
| Windows Server | 2022 and later        |
| macOS          | 15 (Sequoia) or later |

## Installation paths

You can deploy the agent in two ways:

* **Manual install** — an IT admin runs the installer directly on the endpoint. This is the fastest path for piloting on a single machine or a small group of machines.
* **MDM / management tool deployment** — the installer is pushed silently to a fleet of endpoints via your existing MDM or software-deployment tooling (Jamf, Intune, SCCM, etc.). This is the recommended approach for production rollouts.

Both paths require a **JWT provisioning token** scoped to your tenant. You can generate and download the token from **Settings → Installers** in the Origin dashboard.

## Before you begin

Review the prerequisites before starting any installation. Key requirements include outbound HTTPS access to Origin's registration and endpoint APIs, and — for the Windows MSI installer — the Microsoft Visual C++ 2015–2022 Redistributable (x64).

<Note>
  See [Prerequisites & Known Issues](/kb/prerequisites) for the full list of network endpoints, Visual C++ requirements, and compatibility notes for SASE and Application Control solutions.
</Note>

## Next steps

<CardGroup cols={2}>
  <Card title="macOS Installation" icon="apple" href="/getting-started/macos-installation">
    Run the `.pkg` installer, approve system extensions, and confirm the agent is reporting in the Origin dashboard.
  </Card>

  <Card title="Windows Installation" icon="windows" href="/getting-started/windows-installation">
    Deploy the MSI silently with a provisioning JWT, with options for enhanced logging and OTEL configuration.
  </Card>

  <Card title="MDM Overview" icon="building" href="/getting-started/mdm-overview">
    Push the agent fleet-wide using Jamf, Intune, or other management tooling.
  </Card>

  <Card title="Verifying Installation" icon="circle-check" href="/getting-started/verifying-installation">
    Confirm the agent is healthy and capturing AI activity using tray diagnostics, service checks, and test prompts.
  </Card>
</CardGroup>