Enterprise install
Use these guides to install AgentKeeper Runtime on managed Windows, macOS, and Linux devices.
Use these guides to install AgentKeeper Runtime on managed Windows, macOS, and Linux devices.
Your software-distribution system installs the OS package. Managed configuration or a scoped token supplied over standard input enrolls the workstation. The runtime stores a per-device credential, repairs selected hooks, sends health, and reports runtime events.
The Windows package is released for production. The availability cards below show the current macOS PKG and Linux RPM. Use the signed fleet packages and verification metadata from the artifact index.
Current package versions and checksums are published with the release artifacts. See Download artifacts.
Current package versions and checksums are published with the release artifacts. See Download artifacts.
Choose a guide
| Guide | Use it for |
|---|---|
| Download artifacts | Pin Windows, macOS, and Linux package files, metadata, signatures, and checksums before assignment. |
| Windows enterprise install | Intune, GPO, SCCM, Workspace ONE, or another Windows software distribution tool. |
| macOS enterprise install | Jamf, Iru/Kandji, Intune, or another macOS MDM. |
| Linux RPM enterprise install (Beta) | Signed RPM, DNF repository, and offline deployment to x86_64 RHEL 8/9 and Rocky Linux 8/9. |
| AWS VDI golden images | WorkSpaces persistent and pooled/ephemeral image lifecycle. |
| Validate deployment | Prove service, enrollment, policy fetch, hook health, live event evidence, and a controlled BLOCK test. |
| Troubleshooting | Triage package success without AgentKeeper evidence, stale health, missing live events, or restart-required state. |
| Uninstall and rollback | Roll back a release, rotate credentials, remove runtime, or clean AgentKeeper-owned hooks. |
What enterprise deployment installs
| Item | Windows | macOS | Linux |
|---|---|---|---|
| Runtime package | Signed IntuneWin | Signed, notarized, and stapled PKG only when released | GPG-signed RPM, signed DNF metadata, or verified offline bundle |
| Managed enrollment config | Root/SYSTEM-readable config or MDM secret channel | Non-secret managed preference profile plus a root After-install script that stages the token over standard input | Token over standard input at first boot/session; never baked into an image |
| OS policies | Browser policies, network allowlists, and app assignment as needed | PPPC, background item, browser, and network policies as needed | systemd, SELinux, proxy/custom CA, repository pinning, and SSSD identity |
| Detection and repair | Package-matched PowerShell helpers | Package-matched shell helpers | Native reconciler plus system and global user timers every 15 minutes |
Do not put Microsoft Graph credentials, broad fleet API keys, or long-lived secrets into package metadata, LaunchDaemons, Windows service command lines, or world-readable files.
Network
| Destination | Required for |
|---|---|
| AgentKeeper app origin | Enrollment, policy fetch, heartbeat, support self-test, and runtime events. |
| AgentKeeper release artifact host | Runtime or gateway artifact download when a package is not staged offline. |
| MDM provider endpoints | Package assignment, inventory, and device state outside AgentKeeper. |
See Network requirements for egress, TLS inspection, and offline packaging guidance.
Success criteria
Package-manager or MDM success means the package installed. AgentKeeper success means the runtime enrolled, fetched policy, reported fresh health, installed the selected hook surface, and produced a live event from the target AI agent.
Full Integrity requires a live command preflight event from a supported pre-execution hook or gateway path. Self-test proves local runtime reachability; it does not prove the target AI agent loaded the hook.
Health states
Workstations and Setup present endpoint Runtime health as Full Integrity, Basic Coverage, Mixed, Standby, Degraded, Missing, or Unknown.
| State | Meaning |
|---|---|
| Full Integrity | Runtime is healthy and a recent live pre-execution event proves the expected enforceable path. |
| Basic Coverage | Runtime health is good but live enforcement proof is incomplete or not recent. |
| Mixed | Some selected surfaces are healthy and others are degraded, restart-required, or missing. |
| Standby | Runtime is installed, authenticated, and reporting with healthy expected hooks, but no AI-agent activity has been observed in the last 24 hours. It is neutral and does not claim verified live protection. |
| Degraded | Runtime has an explicit credential, policy, service, hook, or repair failure. Missing or old Activity and restart_required alone do not qualify. |
| Missing | AgentKeeper has explicit evidence that the expected Runtime is absent or not reporting. |
| Unknown | AgentKeeper has stale or insufficient Runtime evidence to classify the workstation. |
Fail-open local behavior is intentional. Explicit failures remain visible as Degraded without blocking developer work during transient backend or network outages. The customer-facing state is derived for presentation; the backend state remains available in advanced diagnostics.
Provider guides
Use the OS page first. Each provider guide covers upload, assignment, configuration, and detection for the same OS package: