Skip to content
NewWatch the two minute introduction to EndLayerWatch now →

Deployment

How to roll out the Holistic AI EndLayer agent: one device in minutes, a fleet through Intune, Jamf or SCCM, supported platforms and network needs.

View as Markdown

Rolling out Holistic AI EndLayer, the Guardian Agent Platform, is two steps: install the Layer 1 Agent, then connect it to your organisation. Only the second step changes as you scale from one device to thousands.

Choose the rollout

RolloutUse it whenHow a device joins
One deviceA pilot, or your own laptopA short claim code, approved in the console
A fleetJamf, Kandji, SCCM, configuration management, or Intune by handOne enrolment secret, with nobody needed at each device
From the consoleYou use Intune or JamfEndLayer pushes the agent to the groups you pick. See integrations.
Containers and build machinesShort-lived machinesThe enrolment secret in a file

Supported platforms

PlatformSupported versionsPackage
macOSmacOS 12 and laterA universal installer, signed and notarised by Apple
WindowsWindows 10 and Windows Server 2019 and laterA per-machine installer with silent install
LinuxDebian, Ubuntu, RHEL, Fedora and SUSEPackages for Intel and Arm, plus a plain archive

Phones and tablets are listed through Microsoft Intune rather than an agent.

Installing needs administrator rights once. Running needs none: the agent runs as the person whose device it is. Installers come from your own organisation's console, and every download can be checked against a signed checksum manifest.

One device, in about ten minutes

  1. Install

    Download the installer from your console and run it.

  2. Point it at your organisation

    Add your organisation's EndLayer address to the agent's settings. Until you do, nothing leaves the device.

  3. Connect it

    Run endlayer enroll as the person who uses the device. It shows a short code, and somebody signed in to your organisation types it into the console.

  4. See the first report

    The device appears in the console after its first scan. If anything looks wrong, run endlayer doctor first.

A fleet, with nobody at any device

Connections, Fleet install creates one enrolment secret, with a device limit and an expiry you choose, and generates install scripts for Windows, macOS and Linux with your organisation's details already filled in. The secret is shown once. The page then shows enrolments per secret, so a rollout that stalls partway is visible at a glance.

Devices installed by hand can also show a small menu-bar or tray app: whether the device is connected, and the warnings and blocks its person has run into. It has nothing that changes the rollout.

What it asks of a network

NeedDetail
DestinationOne place, your organisation's EndLayer service, on port 443 outbound
InboundNone. Nothing listens on the device.
VolumeA few tens of kilobytes per report, every 15 minutes
TLS inspectionSupported, with your root certificate added. Certificate checks stay on.

The browser extension

The browser extension checks prompts, uploads and downloads on AI websites. Your device management tool installs it in Chrome, Edge, Brave, Vivaldi or Chromium, and it hands each check to the agent on the same device. Firefox support is planned.

After the first devices report

Until policy baselines are set, most checks report and stay ungraded on purpose. That is the honest answer to "does this match policy" when nobody has said what the policy is. Set these first:

  • Corporate domains: so accounts can be told apart as corporate or personal.
  • Agent modes you permit: for example, whether coding agents may skip permission prompts.
  • Domains browsers must block: the AI websites your policy rules out.
  • What you pay per tool: so seats can be set against use.

Then turn on the prompt scanner at Monitor, and move rules to Warn, Redact or Block once the events show what they would catch. See what it stops.

Updated 2026-11-20

EndLayer

Give AI room to work.And clear boundaries.

See the Guardian Agent Platform on your own fleet. Find every AI tool, understand what it reaches and costs, and apply the controls your team needs.

One connected layer of control
Devices · Cloud · ApplicationsSurface / Monitor / Govern