How Enlist works

Three parts. One quiet setup.

The console you use, the Enlist service that keeps your blueprints, and a small agent on each device. Tap any part of the map to see what it does, step by step.

The map

Tap a part to see how it works

Every connection is encrypted and starts from your side: your browser or the device. Nothing reaches into your clients' networks.

Passkey sign-in · TLS Outbound · mutual TLS The consoleYou and your team The Enlist serviceRun by Enlist The agentOn each PC and Mac Your toolsEmail, webhooks, PSA AD connectorOptional, on a server

You and your team

The console

A web app in any modern browser, on a desktop or a phone. This is where you set things up once and then watch.

  1. Sign in with a passkeyNo passwords and no text-message codes, so there's nothing to phish.
  2. Build the client's blueprintName, domain join, admin accounts, apps, settings and encryption. Start from a ready-made one.
  3. Make the USB or copy one commandOne per client. It tells a new device which client it belongs to.
  4. Watch it happen liveEach device's steps tick off as they finish.
  5. Step in only if askedIf a step stops you see what failed and why, then retry or skip it.

Run by Enlist

The Enlist service

The middle of the map. Your browser and every device talk to it, and to nothing else.

  1. Keeps each MSP walled offEvery MSP's data is kept apart by the database itself, not only by the app.
  2. Turns a blueprint into stepsThe exact list each device works through, in order.
  3. Scans every installerUploaded software is virus-scanned before any device can use it.
  4. Locks away the secretsDevice passwords and recovery keys are encrypted with a key for your MSP alone.
  5. Writes everything downEvery sign-in, change and sensitive view goes in a log that shows if an entry is altered.

On your clients' PCs and Macs

The agent

A small, signed app on each device. It does the work so nobody has to sit with it.

  1. Starts from the USB or a commandOn a new PC, at the first setup screen. On a Mac or an existing PC, with the installer.
  2. Gets its own certificateIt proves which client it belongs to and gets a certificate made for that one device.
  3. Calls out for its stepsOnly outbound, so no ports are opened on the client's network.
  4. Works and reportsEach step reports back as it finishes. A restart doesn't lose its place, and it retries before asking for help.
  5. Stays on the jobDaily standard checks, patching, scripts and a Terminal when you need hands on.

Where you already work

Your tools

You don't have to watch the console. Enlist tells you when a device is ready or needs you.

  1. Something happensA device is ready, or a step needs you.
  2. An emailIt says which device, what stopped and why.
  3. A signed webhookFor your own automations, signed so you know it came from Enlist.
  4. A ticket in your PSAHaloPSA, ConnectWise PSA or Autotask: a ticket per onboarding, notes and time entries.

Optional, on a client's server

The AD connector

For clients on Active Directory. A small service on one of their servers, with its own certificate.

  1. A new PC needs to join the domainIt can be anywhere, even off the client's network.
  2. The connector prepares the joinIt makes the PC's computer account on the client's own server.
  3. The PC joinsNo domain password ever goes to the PC.

One device, start to finish

Plug in. Walk away. It's enlisted.

Here is what a new laptop does on its own after you plug the client's USB in at the first setup screen. The same list runs from the installer on a Mac.

  • Every step reports back the moment it finishes
  • A restart doesn't lose its place
  • Ready checks run before it's called ready
LAPTOP-0142
  1. Renames itselffrom the client's naming rule
  2. Joins the domainEntra ID or Active Directory
  3. Creates the admin accountits own password, kept in Enlist
  4. Installs the client's appsincluding your RMM agent
  5. Applies settingswithout scripts
  6. Turns on encryptionBitLocker, key kept in Enlist
  7. Runs its ready checksbefore it's called ready
LAPTOP-0142 is readyEmail sent · ticket note added
An illustration of one Windows laptop onboarding. Sample data

Layers of protection

A device password, wrapped four times

Follow one admin password from the device to storage. Tap a layer to see what it does. The Security and trust page has the full list.

Who can see it

  • Each MSP sees only its own data, enforced by the database
  • Roles from owner to read-only, limited to one client or site if you like
  • Enlist staff can't look inside your MSP unless your support request opens it, and your owners get an email when they do

What can reach a device

  • Agent updates are code-signed (Windows Authenticode, Apple Developer ID) and checked against a signed list
  • Scripts are pinned to their exact text, and every run is logged
  • Uploaded software is virus-scanned before any device can install it

See it on your own devices

Join the beta waitlist and we'll be in touch when your spot opens.

Join the beta waitlist