HEAD-TO-HEAD · FACTS ONLY
Bay 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: Bay
- 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 | Bay | Onyx |
|---|---|---|
| Owner | None | None |
| Positioning | An endpoint-first control layer for AI agents, coding assistants and MCP servers on employee devices. Bay describes itself as a fully preventive, agentless platform that classifies, governs and prevents risks across every AI agent and tool on enterprise endpoints. | "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 | Deploys through your existing EDR or MDM, with no new agents and no new tools; Bay says it scans in minutes and exits cleanly. Source: Bay homepage · Read 27 Sep 2026 | Endpoint agents, browser extensions, APIs and gateways. Source: Onyx Security: AI security platform · Read 27 Sep 2026 |
| On-device control | DescribedInventories AI agents, MCP servers, tools, credentials and extensions on the device, and its Enforcer returns Allow, Ask or Deny locally on prompts, pre-tool calls and post-tool responses on supported agent surfaces. Delivered as Wave, an ephemeral binary that runs through your existing MDM or EDR. Policies can be scoped by agent, group, endpoint or device. Source: Bay blog: Ghostjacking (re-read) · Read 11 Oct 2026 | DescribedEndpoint agents cover coding assistants and desktop AI agents. Source: Onyx Security: AI security platform · Read 27 Sep 2026 |
| Browser extensionDiffers | Not in our sourcesNo browser extension is described. Bay's Application Control can allow or block browsers and extensions as applications, which is a device rule, not a control on what goes into browser AI. Source: Bay blog: Ghostjacking (re-read) · Read 11 Oct 2026 | 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 | MatchesManaged settings for Claude Code, Codex and Claude Desktop lock permission rules, preserve managed hooks, restrict MCP servers and constrain plugin sources. Source: Bay blog: Ghostjacking, an AI agent attack (August 2026) · Read 27 Sep 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 | MatchesEvaluates prompts, pre-tool calls and post-tool responses and returns Allow, Ask or Deny locally, which Bay states takes under 4ms with no cloud round-trip, on supported agent surfaces. Source: Bay blog: Ghostjacking (re-read) · Read 11 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 | MatchesDeploys through your existing EDR or MDM; no new agents. Source: Bay homepage · Read 27 Sep 2026 | Not in our sources |
| Can warn or ask instead of only blocking | MatchesAsk is one of three answers, with Allow and Deny. Source: Bay homepage · Read 27 Sep 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 | MatchesDeny stops an action. Rules cover MCP servers (an allow or block list, and per-tool rules for read, create, update, delete and execute), applications, CLIs, browsers, IDEs and extensions, credentials and files, network egress allow lists, and capability rules such as shell execution, package installation and cloud CLIs. Source: Bay blog: Ghostjacking (re-read) · Read 11 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 | MatchesSimulation Mode runs a rule without enforcing it. Source: Bay blog: Ghostjacking, an AI agent attack (August 2026) · Read 27 Sep 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 | MatchesRecords who triggered an action, whether a human was involved, and the chain from prompt to system action. Source: Bay homepage · Read 27 Sep 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 | Not in our sources | 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. Bay's site has a demo request and no pricing page (re-checked 11 October 2026). Source: Bay homepage (re-read) · Read 11 Oct 2026 | Not published. Source: Onyx Security homepage · Read 27 Sep 2026 |
Where do they differ?
- Browser extension: Bay is not in our sources; Onyx describes it.
- AI or MCP gateway: Bay is not in our sources; Onyx describes it.
- Names the coding agents it covers: Bay matches; Onyx partly matches.
- Controls what goes into browser AI: Bay is not in our sources; Onyx matches.
- Rolls out through EDR or device management you run: Bay matches; Onyx is not in our sources.
- Has a watch-only or simulation mode: Bay matches; Onyx partly matches.
- Records who or what took each action: Bay matches; Onyx partly matches.
- Also covers SaaS, cloud or homegrown AI: Bay is not in our sources; Onyx matches.
Choose Bay if
- Your developers run coding agents with many MCP servers and you want a decision on each action before it runs
- You want to add AI agent control through the EDR or MDM you already run instead of rolling out another agent
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?
Bay
- Endpoint only: no browser extension, network proxy or AI gateway is described, and nothing on SaaS or cloud-hosted AI apps.
- One of the smallest public footprints here: a single homepage, two blog posts, no documentation portal and no published pricing (re-checked 11 October 2026).
- Headline figures such as under 5 minutes to deploy, under 1% false positives and 100% of shadow AI discovered are Bay's own statements and have not been verified.
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.