HEAD-TO-HEAD · FACTS ONLY
Neo vs Onyx: AI endpoint control facts side by side
Short answer
By The Device Desk · Endpoint AI Finder · Published 2026-10-11
Desk research from public vendor pages read on 27 September and 11 October 2026. Profiles follow our published method; we did not run the products.
Vendor pages read September and October 2026 · updated 2026-10-13
Where do their controls sit?
- Filled or hatched marker: Neo
- Dashed teal ring: Onyx, described
- DEV Filled marker: described on the product pages we read
- DEV Hatched marker: partly described (another component, a narrower scope, or method not detailed)
- DEV Dashed marker: not in our sources (it may exist; we did not find it)
What are the facts, side by side?
| Fact | Neo | Onyx |
|---|---|---|
| Owner | None | None |
| Positioning | Agentic Software Control from Neo Security, Inc. (neo.ai, not Pulumi Neo): a live inventory of agents, models, skills, MCP servers and extensions on every endpoint, and runtime control that intercepts agent actions and allows, blocks or holds them for approval. Launched 20 July 2026 with $100M from Andreessen Horowitz and Bessemer; HQ Boston. | "The Secure AI Control Plane for the Agentic Era": inline inspection of prompts, tool calls and model responses across browser AI, coding assistants, desktop AI agents, cloud workloads and MCP servers. Based in Tel Aviv and New York. |
| How it reaches devices | A lightweight endpoint sensor with no kernel module, no reboot and no OS hooks; analysis stays on the device. OS support is not listed on the pages we read; SACR (secondary) says it needs no MDM. Source: Neo: platform · Read 13 Oct 2026 | Endpoint agents, browser extensions, APIs and gateways. Source: Onyx Security: AI security platform · Read 27 Sep 2026 |
| On-device control | DescribedA live inventory of agents, models, skills, MCP servers and extensions on every endpoint, with runtime control that intercepts agent actions. Source: Neo homepage · Read 13 Oct 2026 | DescribedEndpoint agents cover coding assistants and desktop AI agents. Source: Onyx Security: AI security platform · Read 27 Sep 2026 |
| Browser extensionDiffers | Partly described(secondary: SACR) user-mode endpoint and browser security. Source: SACR (secondary): CISO guide to endpoint control and prevention, July 2026 · Read 13 Oct 2026 · secondary source | DescribedBrowser extensions cover browser AI. Source: Onyx Security: AI security platform · Read 27 Sep 2026 |
| Network or SSE proxy | Not in our sourcesNot described on the pages we read. | Not in our sourcesNot described on the pages we read. |
| AI or MCP gatewayDiffers | Not in our sourcesNot described on the pages we read. | DescribedGateways and APIs inspect traffic inline. Source: Onyx Security: AI security platform · Read 27 Sep 2026 |
| Names the coding agents it coversDiffers | MatchesNames Claude Code, Gemini CLI, GitHub Copilot and OpenAI Codex; Cursor is not named. Source: Neo: platform · Read 13 Oct 2026 | PartlyCovers coding assistants; specific tools are not named on the pages we read. Source: Onyx Security: AI security platform · Read 27 Sep 2026 |
| Decides on a tool call before it runs | MatchesIntercepts agent actions at the endpoint and allows, blocks or holds them for approval. Source: Neo homepage · Read 13 Oct 2026 | MatchesInspects every prompt, tool call and model response inline. Source: Onyx Security: AI security platform · Read 27 Sep 2026 |
| Controls what goes into browser AIDiffers | Not in our sources | MatchesCan mask data in browser AI as well as block it. Source: Onyx Security: AI security platform · Read 27 Sep 2026 |
| Rolls out through EDR or device management you runDiffers | PartlyIts own lightweight sensor rather than a rollout through existing EDR or MDM. Source: Neo: platform · Read 13 Oct 2026 | Not in our sources |
| Can warn or ask instead of only blocking | MatchesHold an action for verified human approval. Source: Neo: platform · Read 13 Oct 2026 | MatchesFive actions: alert, block, mask, steer or ask. Source: Onyx Security: AI security platform · Read 27 Sep 2026 |
| Can block an agent, tool or action | MatchesBlock is one of its runtime actions. Source: Neo: platform · Read 13 Oct 2026 | MatchesBlock is one of five actions. Source: Onyx Security: AI security platform · Read 27 Sep 2026 |
| Has a watch-only or simulation modeDiffers | MatchesAudit mode before enforcement. Source: Neo: platform · Read 13 Oct 2026 | PartlyAlert is one of five actions; a simulation mode is not described. Source: Onyx Security: AI security platform · Read 27 Sep 2026 |
| Records who or what took each actionDiffers | MatchesEvery action tied to the human or agent that caused it, in an immutable audit chain. Source: Neo homepage · Read 13 Oct 2026 | PartlyIntegrates with Okta, Entra and Splunk; separating a person from an agent is not described. Source: Onyx Security: AI security platform · Read 27 Sep 2026 |
| Also covers SaaS, cloud or homegrown AIDiffers | PartlyNames SaaS and desktop AI such as Slack AI, Notion AI, Salesforce Agentforce and ChatGPT Desktop. Source: Neo: platform · Read 13 Oct 2026 | MatchesCloud workloads and MCP servers as well as devices. Source: Onyx Security: AI security platform · Read 27 Sep 2026 |
| Has a public price or tiers (vendor site or marketplace) | Not in our sources | Not in our sources |
| Built into | None | None |
| Works with | None in our sources | Lists CrowdStrike among its integrations. Source: Onyx Security: AI security platform · Read 27 Sep 2026 |
| Price | Not published (demo request). Source: Neo homepage · Read 13 Oct 2026 | Not published. Source: Onyx Security homepage · Read 27 Sep 2026 |
Where do they differ?
- Browser extension: Neo partly describes it; Onyx describes it.
- AI or MCP gateway: Neo is not in our sources; Onyx describes it.
- Names the coding agents it covers: Neo matches; Onyx partly matches.
- Controls what goes into browser AI: Neo is not in our sources; Onyx matches.
- Rolls out through EDR or device management you run: Neo partly matches; Onyx is not in our sources.
- Has a watch-only or simulation mode: Neo matches; Onyx partly matches.
- Records who or what took each action: Neo matches; Onyx partly matches.
- Also covers SaaS, cloud or homegrown AI: Neo partly matches; Onyx matches.
Choose Neo if
- You want to hold agent actions for human approval on the device
- You want an audit mode before enforcing rules
Choose Onyx if
- You want masking or steering rather than only allow or block
- AI use spans the browser, desktop apps, coding tools and cloud workloads
Which limits should you check?
Neo
- Uses its own sensor rather than the EDR or MDM you run, and OS support is not listed on the pages we read.
- No price is published.
Onyx
- Uses its own endpoint agents and browser extensions, so there is something new to roll out to devices.
- No pricing published, and specific coding agents are not named on the pages we read.