Skip to content
Install Core free
ProductsCompare Core, Hub, Connect and MDM pricing
Solutions
Docs
ResearchPricing
CompareCompare all AI data-leak tools
TrustBenchmarks
Start 30-day free trial

Shadow Hub for your business

Tell us about your team and we'll help you get started.

We use these details only to reply to your enquiry. No newsletter, no cookies, no trackers.

Roll out Shadow with Jamf, Intune, Kandji or Shadow MDM

There are two ways to get Shadow onto every laptop in your organisation:

  • You already run an MDM (Jamf Pro, Microsoft Intune, Kandji or similar): push Shadow Core with a script and connect each machine to your Shadow Hub workspace. Your MDM keeps managing device settings.
  • You don’t have an MDM, or want a lighter one: people install Shadow from their invite link, and Shadow MDM, included in Hub, then manages device settings from inside the same agent, with every change approved by you.
  1. In Shadow Hub, create an invite link for the people you are rolling out to (People → Invite). The link decides which workspace machines join.
  2. Pick a pilot group of a few machines on each operating system you use.
  3. Decide your sharing level; people see it when their machine connects.

Run the install as the signed-in user, not as root or SYSTEM: Shadow’s background service and certificate trust are per user. Adding Shadow’s local certificate to the user’s keychain or certificate store may ask the user to confirm; test this on your pilot group.

On macOS and Linux, the installer installs Core, connects the machine to Hub and turns on protection in one step when it gets the invite link:

Terminal window
curl -fsSL https://hub.getshadow.dev/core/install.sh | SHADOW_ENROLL='<your invite link>' sh

On Windows (64-bit), install Core with PowerShell, then connect without the confirmation prompt:

Terminal window
irm https://hub.getshadow.dev/core/install.ps1 | iex
shadow install --apply
shadow hub connect '<your invite link>' --yes

--yes skips the question shadow hub connect normally asks before anything is sent, for scripts and MDM. See the CLI reference.

  1. In Settings → Scripts, add a script with the macOS install command above. Jamf runs scripts as root, so wrap it to run as the signed-in user:

    #!/bin/sh
    USER_NAME=$(stat -f%Su /dev/console)
    USER_ID=$(id -u "$USER_NAME")
    launchctl asuser "$USER_ID" sudo -u "$USER_NAME" sh -c \
    "curl -fsSL https://hub.getshadow.dev/core/install.sh | SHADOW_ENROLL='<your invite link>' sh"
  2. Create a policy with that script, scoped to your pilot group, triggered at check-in or from Self Service, once per computer per user.

  3. Add an extension attribute with the health check below so you can build a smart group of machines where Shadow is not running.

  • macOS: add a shell script under Devices → macOS → Shell scripts with the macOS install command, set Run script as signed-in user to Yes, and assign it to your pilot group.
  • Windows: add a PowerShell script under Devices → Windows → PowerShell scripts with the Windows commands above, set Run this script using the logged on credentials to Yes, and use 64-bit PowerShell.
  • Use the health check as a custom compliance script or a remediation detection script.

Add a Custom Script library item with the macOS install command, wrapped to run as the signed-in user as in the Jamf example, set it to run once per device, and assign it to a pilot blueprint first. Add the health check as an audit script.

Terminal window
shadow status --quiet && echo ok || echo "shadow not running"

shadow status --quiet exits 0 when Shadow is running and 1 when it is not. In Shadow Hub, connected machines appear under People with the last time they reported.

If you don’t run an MDM, have people install Shadow from their invite link (the macOS and Linux command above, or the Windows commands). Once machines are connected:

  1. Shadow Hub shows each device’s posture (disk encryption, screen lock, firewall, patches and more), included in Hub.
  2. Pick the frameworks you follow; Shadow builds the blueprint.
  3. Turn on Shadow MDM, included in Hub, to approve Proposals and roll changes out in stages, with one-click rollback.

Two limits today: remote lock and wipe on macOS need Shadow’s Apple MDM enrolment, which is coming (the Apple certificate is pending), and Linux disk encryption is report-only. See the Shadow MDM FAQ.

  • shadow status on a pilot machine shows the organisation and sharing level.
  • The machine appears in Shadow Hub with its person and the time it last reported.
  • A test prompt to an AI tool shows up in Hub as masked, at your sharing level.

Then widen the scope from the pilot group to everyone.

Frequently asked questions

Why does the script run as the signed-in user and not as root?

Shadow's background service and its local certificate trust are per user, so each person's AI traffic is protected by their own Shadow. Run the install as the signed-in user; a root install would protect the wrong account.

Will people see that their machine is connected?

Yes. The menu-bar app, the local dashboard and shadow status show that the machine is managed, by which organisation, and what is shared at your sharing level.

Can we use Shadow MDM and Jamf or Intune together?

Yes. If a device reports another MDM, Shadow MDM sends it no enforcement and changes nothing; it only reports posture, free, as evidence. Use your MDM to deploy Shadow and manage settings, and Shadow for AI privacy, posture evidence and the Enforcement Map.

Does Shadow MDM install Shadow Core?

Shadow MDM runs inside the Shadow agent, so each device needs Shadow Core installed and connected to Hub first: with the invite command, or with your MDM as shown on this page.