ENDPOINTS


Govern the AI on every machine.
See the AI apps running on every enrolled Mac and Windows laptop from day one. What gets captured is set by your policy.
See the AI apps running on every enrolled Mac and Windows laptop from day one. What gets captured is set by your policy.
Waxell Endpoints discovers and governs the AI tools your team runs locally, such as Claude Desktop, Cursor, Copilot, ChatGPT and browser assistants, on real laptops rather than only the agents you build with an SDK. Endpoints is the Waxell product that sits on the device itself.
Endpoints governs the AI your team runs.
Observe and Runtime govern the agents you build.
Waxell Observe and Runtime govern the agents you build, and Waxell Connect governs the third-party agents your team adopts. Endpoints extends that governance to the machines themselves: the desktop apps, IDEs, CLIs and browser tabs that talk to a model provider all day, often touching source code, customer data and secrets.
These tools install themselves one developer at a time. Most organizations have no inventory of which are running, on whose machine, against which provider. Endpoints closes that gap.
Endpoints governs the AI your team runs.
Observe and Runtime govern the agents you build.
Waxell Observe and Runtime govern the agents you build, and Waxell Connect governs the third-party agents your team adopts. Endpoints extends that governance to the machines themselves: the desktop apps, IDEs, CLIs and browser tabs that talk to a model provider all day, often touching source code, customer data and secrets.
These tools install themselves one developer at a time. Most organizations have no inventory of which are running, on whose machine, against which provider. Endpoints closes that gap.
THE PROBLEM
AI traffic looks like normal HTTPS, and your existing stack was built before every employee had a continuous outbound connection to a model.
Every call to api.openai.com or api.anthropic.com goes out over port 443, with no anomalous port and no signature to match. Web proxies and SSL inspection can't reach desktop apps that route directly to provider APIs. EDR doesn't flag Claude Desktop or Copilot, because they aren't malicious. Network DLP works on identified traffic, and AI traffic isn't identified. The result: an average of $670,000 added to breach costs specifically from shadow AI, on a fleet you currently can't see.
THE PROBLEM
AI traffic looks like normal HTTPS, and your existing stack was built before every employee had a continuous outbound connection to a model.
Every call to api.openai.com or api.anthropic.com goes out over port 443, with no anomalous port and no signature to match. Web proxies and SSL inspection can't reach desktop apps that route directly to provider APIs. EDR doesn't flag Claude Desktop or Copilot, because they aren't malicious. Network DLP works on identified traffic, and AI traffic isn't identified. The result: an average of $670,000 added to breach costs specifically from shadow AI, on a fleet you currently can't see.
What Endpoints delivers
Know which AI apps run where
Endpoints reports every AI app it finds on each enrolled Mac and Windows device, such as Claude Desktop, Cursor and ChatGPT, per device and per user.
See who calls which provider
Endpoints records the metadata of outbound AI traffic: which process reached which provider host, when, and on behalf of which user.
Block or capture under policy
Policy leaves an app observe-only or blocks it at the network layer before data leaves the machine. Capture follows the policy you set, with secrets redacted.
One place for the whole fleet
Apps, devices, policy, captures and a live activity feed land in the Endpoints area of your Waxell workspace, for every enrolled device.
Governed vs. ungoverned
Why your current stack can’t do this, and how Endpoints does
Fleet-wide TLS interception is the usual answer, and most organizations that try it walk it back. Endpoints gets visibility without it: on macOS a signed system extension reads the plaintext hostname in the TLS handshake, and on Windows an ETW consumer does the equivalent. The network monitor records hostname, process, IP and timestamp.
Endpoints is governance, not another agent in the stack: the same policy plane that governs your SDK agents now reaches the laptops.
How you deploy it
A whole fleet → MDM.
Push one per-tenant profile plus the signed installer from Hexnode, Jamf, Kandji, Mosyle, or Intune. Devices trust your tenant's certificate authority, enroll silently, scan themselves, and appear in your workspace, with zero end-user action and no “Allow” dialogs. The profile uses only primitives every MDM supports, which is why it's MDM-agnostic.
One machine → manual install.
Download the signed app and install it yourself in a couple of minutes, with no MDM and no IT ticket. The right way to try Endpoints on your own laptop first.
Each tenant gets its own certificate authority, so one customer's CA never touches another's, and attribution stays clean.
What Endpoints supports
Platforms
macOS (signed and Apple-notarized) · Windows
Policy model
a layered Guard cascade: Global → App type → User group → Device → Agent group → Agent
Discovers
Claude Desktop, Cursor, Claude Code, GitHub Copilot, ChatGPT, Perplexity, browser assistants and more, from a curated catalog of 60+ AI provider domains, auto-synced
Deploys via
Hexnode · Jamf · Kandji · Mosyle · Intune, or manual single-machine install
Postures
observe-only · block (preventive) · capture (set by policy, redacted on the device)

Visibility first. Capture by policy.
Installing Endpoints turns on discovery and metadata: which app reached which AI provider, as which user, and when.
Prompt and response content is captured only under the policy you set, and secrets are redacted on the device before a capture leaves it.
You get an inventory and activity picture right away, and you decide how far capture goes for the whole workspace, a team or a single device.
Governed vs. ungoverned
Why your current stack can’t do this, and how Endpoints does
Fleet-wide TLS interception is the usual answer, and most organizations that try it walk it back. Endpoints gets visibility without it: on macOS a signed system extension reads the plaintext hostname in the TLS handshake, and on Windows an ETW consumer does the equivalent. The network monitor records hostname, process, IP and timestamp.
Endpoints is governance, not another agent in the stack: the same policy plane that governs your SDK agents now reaches the laptops.
Why your current stack can’t do this, and how Endpoints does
Why your current stack can’t do this, and how Endpoints does
Fleet-wide TLS interception is the usual answer, and most organizations that try it walk it back. Endpoints gets visibility without it: on macOS a signed system extension reads the plaintext hostname in the TLS handshake, and on Windows an ETW consumer does the equivalent. The network monitor records hostname, process, IP and timestamp.
Endpoints is governance, not another agent in the stack: the same policy plane that governs your SDK agents now reaches the laptops.
How you deploy it
A whole fleet → MDM.
Push one per-tenant profile plus the signed installer from Hexnode, Jamf, Kandji, Mosyle, or Intune. Devices trust your tenant's certificate authority, enroll silently, scan themselves, and appear in your workspace, with zero end-user action and no “Allow” dialogs. The profile uses only primitives every MDM supports, which is why it's MDM-agnostic.
One machine → manual install.
Download the signed app and install it yourself in a couple of minutes, with no MDM and no IT ticket. The right way to try Endpoints on your own laptop first.
Each tenant gets its own certificate authority, so one customer's CA never touches another's, and attribution stays clean.
What Endpoints supports
Platforms
macOS · Windows
Policy model
a layered Guard cascade: Global → App type → User group → Device → Agent group → Agent
Discovers
Claude Desktop, Cursor, Claude Code, GitHub Copilot, ChatGPT, Perplexity, browser assistants and more, from a curated catalog of 60+ AI provider domains, auto-synced
Deploys via
Hexnode · Jamf · Kandji · Mosyle · Intune, or manual single-machine install
Postures
observe-only · block (preventive) · capture (set by policy, redacted on the device)
Platforms
macOS · Windows
Deploys via
Hexnode · Jamf · Kandji · Mosyle · Intune, or manual single-machine install
Policy model
a layered Guard cascade: Global → App type → User group → Device → Agent group → Agent
Postures
observe-only · block (preventive) · capture (set by policy, redacted on the device)
Discovers
Claude Desktop, Cursor, Claude Code, GitHub Copilot, ChatGPT, Perplexity, browser assistants and more, from a curated catalog of 60+ AI provider domains, auto-synced
FAQ
What is Waxell Endpoints?
What does Waxell Endpoints record?
How is Waxell Endpoints different from a web proxy or SSL inspection?
How do I deploy Waxell Endpoints?
Which AI tools does Waxell Endpoints discover?
Deploying Waxell? See how teams roll it out.
Your team is already running AI on their laptops.
Waxell Endpoints shows you which tools, on whose machine, against which provider, and gives you the policy to control them.
FAQ
What is Waxell Endpoints?
What does Waxell Endpoints record?
How is Waxell Endpoints different from a web proxy or SSL inspection?
How do I deploy Waxell Endpoints?
Which AI tools does Waxell Endpoints discover?
Deploying Waxell? See how teams roll it out.
© 2026 Waxell. All rights reserved.
Patent Pending.
© 2026 Waxell. All rights reserved.
Patent Pending.
© 2026 Waxell. All rights reserved.
Patent Pending.

