Download artifacts
Pin one AgentKeeper Runtime version before assigning it through MDM. Keep metadata and checksums with the deployment record.
Pin one AgentKeeper Runtime version before assigning it through MDM. Keep metadata and checksums with the deployment record.
Windows
- Version metadata
- Package metadata
- Checksums
- Signed IntuneWin latest alias
- Intune source ZIP
- amd64 runtime ZIP
- arm64 runtime ZIP
Use the signed .intunewin when present. If you wrap the source ZIP with the Microsoft Win32 Content Prep Tool, validate the result with Windows enterprise install before assigning it broadly.
macOS
Current package versions and checksums are published with the release artifacts. See Download artifacts.
These download links are the customer artifact feed. Internal source and architecture ZIPs are packaging inputs, not fleet installers. Do not build a customer PKG from them.
Before uploading the PKG to any MDM, verify the exact downloaded file on a Mac:
shasum -a 256 agentkeeper-runtime-macos-latest.pkg
pkgutil --check-signature agentkeeper-runtime-macos-latest.pkg
xcrun stapler validate agentkeeper-runtime-macos-latest.pkg
spctl -a -vv -t install agentkeeper-runtime-macos-latest.pkg
The SHA-256 must match checksums.txt. Installer signature output must name
Developer ID Installer: RAD Security, Inc. (F65622XJDP), stapler validation
must succeed, and Gatekeeper must report a notarized Developer ID source. Stop
if any check differs.
Linux RPM (Beta)
The Linux release includes a GPG-signed RPM, signed DNF repository metadata, detached checksum signature, offline bundle, CycloneDX and SPDX SBOMs, and build provenance. The packaged MCP Gateway is pinned to the runtime release and uses the credentialless local broker contract.
Current package versions and checksums are published with the release artifacts. See Download artifacts.
Use the exact RPM filename from package-metadata.json. Each signed repository snapshot includes the current package and retained prior signed RPMs so dnf can pin or downgrade. Mirror the current and previous approved versions into your internal repository before fleet rollout.
Package records
For each assignment, record:
- Runtime version.
- Artifact filename.
- SHA-256 from
checksums.txt. - MDM provider and assignment name.
- Assignment group and rollout ring.
- Validation evidence link from Validate deployment.