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.

Teams and organisations

Shadow protects one machine at a time. Shadow Hub brings those machines together for an organisation: admins invite employees, every enrolled laptop and server reports what Shadow protected, and the hub shows it per person, per machine and across the workforce, including what kinds of data leak most and to which AI services.

Shadow Core (everything else in this documentation) is free for individual users and works on its own. Shadow Hub is $3 per user per month, with a 30-day free trial and no card required: see Shadow Hub and pricing, or write to support@getshadow.dev.

An admin creates an invite in Shadow Hub and shares the join link. On the join page the employee sees what the organisation will be able to see, and a one-line command:

Terminal window
# macOS and Linux
curl -fsSL https://hub.getshadow.dev/core/install.sh | SHADOW_ENROLL='https://hub.example.com/join/inv_...' sh
Terminal window
# Windows
$env:SHADOW_ENROLL='https://hub.example.com/join/inv_...'; irm https://hub.getshadow.dev/core/install.ps1 | iex

With SHADOW_ENROLL set, the installer:

  1. installs Shadow (and the menu-bar app on macOS);
  2. connects the machine to the organisation (shadow hub connect --yes <join link>);
  3. installs the background service, trusts the local CA and turns on the system proxy (shadow install --apply --system-proxy), so browsers and chat apps are covered too.

On a machine where Shadow is already installed, connecting is one command. Shadow shows the organisation and what it will see, and asks before anything is sent:

Terminal window
shadow hub connect 'https://hub.example.com/join/inv_...'
shadow hub status # the organisation and what is shared
shadow hub disconnect # stop reporting from this machine

See Connect a machine for what is sent and never sent.

The organisation chooses a sharing level in Shadow Hub. Each machine fetches it with every upload and trims what it sends before anything leaves the machine; the hub enforces it again on arrival.

LevelSent to the organisation
FullActivity counts, plus each incident’s prompt as written and as the AI received it, the values caught and what replaced them, the app and process, and the machine
SanitisedActivity counts, plus each incident’s prompt only as the AI received it (fakes). Real values never leave the laptop
CountsActivity counts and categories: which AI services, which apps, how many values of each type, what was blocked

Every level includes the machine’s hostname, operating system and user name, and the person it is enrolled to. Traffic that is not going to an AI service is never recorded, at any level.

People using an enrolled machine are told, in the menu-bar app (“Shadow is protecting this Mac · managed by Acme”), on the local dashboard and in shadow status, which organisation manages it and what is shared. Depending on where you operate, monitoring employees’ use of AI may require telling them in writing or consulting a works council. Choose the sharing level with that in mind.

  • Enrolment stores the hub address and a device token in <data dir>/hub.json, readable only by the user (0600).
  • While Shadow runs, it uploads new activity events every few seconds over HTTPS, with the device token. Uploads are idempotent, so a lost connection never duplicates or loses events; they resume from where they stopped.
  • Incident details (prompt text) are kept in Shadow’s memory for the last 200 incidents. An enrolled machine uploads them within seconds, so the hub keeps them under the organisation’s retention policy.
  • The local dashboard at http://127.0.0.1:8877/shadow/ui keeps working as before.

Frequently asked questions

How do employees join?

An admin creates an invite in Shadow Hub and shares the join link. The employee runs the one-line command on the join page: it installs Shadow, enrols the machine with the organisation and turns on protection, including the system proxy.

What does the organisation see?

It depends on the sharing level the organisation sets: full (incidents with prompts and the values caught), sanitised (prompts only as the AI received them, real values never leave the laptop) or counts only. The level is applied on the laptop before anything is sent.

Do employees know their machine is managed?

Yes. The menu-bar app, the local dashboard and shadow status all say which organisation manages the machine and what is shared with its admins.

How is Shadow Hub priced?

Shadow Core, which protects each machine, is free for individual users and never phones home. Shadow Hub, the central dashboard for organisations, is $3 per user per month for up to 500 users, everything included, with a 30-day free trial and no card required. Larger organisations can talk to us about Shadow Enterprise. See Shadow Hub.