Skip to main content

Deploy to a Fleet

Waxell is built to be deployed by IT, with no action from the people using the machines. You push a small enrollment artifact for your workspace and the signed installer from the tool you already use; each device then:

  1. Enrolls with your workspace and gets its own device identity.
  2. Installs the browser extension into Chrome, Edge and Firefox and starts capturing browser AI chats.
  3. Registers the hooks that govern coding agents — Claude Code, Codex, Cursor and others.
  4. Discovers its AI apps and reports everything to Endpoints.

Choose your path​

You have…Use
Macs in Jamf, Kandji, Intune or HexnodemacOS
PCs in IntuneWindows
An RMM (NinjaOne, ConnectWise, Datto, Kaseya, Atera…)The RMM sections of macOS and Windows
One machine to try it onManual install

The artifacts​

Download everything from Endpoints → Setup. Enrollment artifacts are generated for your workspace and contain its enrollment key, so treat them as secrets. The installers are the same signed build for everyone.

PlatformEnrollmentInstallerBrowser extension
macOSBase profile (.mobileconfig) — certificate trust, system-extension approval, enrollment settingsWaxellSetup-arm64.pkg — Developer ID signed, notarizedBrowser AI profile (.mobileconfig)
Windowswaxell-setup.ps1 — certificate trust, enrollment settings in HKLM\SOFTWARE\WaxellWaxellSetup-x64.msi — signed by CallSine LLCInstalled by the MSI automatically

Optional extras on Setup: a macOS flow visibility profile (network metadata and on-device site/app blocking) and a Disable DoH policy for both platforms.

Installers are hosted at install.waxell.dev. The latest version is always at latest/WaxellSetup-arm64.pkg and latest/WaxellSetup-x64.msi; each version also has a fixed URL under v<version>/ if you pin versions.

Before you roll out​

  • Decide on capture. Browser capture is on by default, with secrets redacted on the device. If a team or region should start without content capture, turn Browser capture off for it on the Guard first — devices then hold captures locally.
  • Allow-list Waxell in any application-control or EDR tool (ThreatLocker, AppLocker, WDAC, CrowdStrike, SentinelOne…). Approving the installer is not enough: the browser starts the Waxell bridge and coding agents start wax-hook on every use. See Windows → Application control.
  • Set device owners if you can. An owner lets team policy and user blocks apply and attributes activity to a person; Waxell can fill it in from Hexnode.

After the push​

Each device appears on Health within minutes (macOS) or after the next MDM sync (Windows) and reports every 60 seconds. Hooks should read managed, and Capture reads on as soon as someone uses AI in a browser. If it reads no ext, see Browser Extension.