HEAD-TO-HEAD · FACTS ONLY
Bay vs Lasso: AI endpoint control facts side by side
Short answer
Bay describes 1 of the four product control types on the pages we read and Lasso describes 3; they differ on on-device control, browser extension, network or SSE proxy and AI or MCP gateway. On decisions, Bay decides on a tool call before it runs and Lasso decides on a tool call before it runs. We do not score either; the right choice depends on the AI tools people use, your devices, your current stack and whether you block or guide.
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: Lasso, 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 | Lasso |
|---|---|---|
| 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. | An AI security platform with discovery and an AI-BOM, posture management, automated red teaming and runtime enforcement at the proxy, API or AI gateway layer, plus usage control through a browser extension and an open-source MCP gateway. |
| 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 | Several components: a browser extension and proxy integrations for usage control, an open-source MCP gateway, and Claude Code lifecycle hooks set through the enterprise management platform. Source: Lasso Security: AI usage control · Read 27 Sep 2026 |
| On-device controlDiffers | 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 | Partly describedConnects directly to Claude Code's lifecycle hooks via the enterprise management platform and inspects every tool call before it runs; a resident device agent is not described. Source: Lasso Security: AI coding assistants · 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 | DescribedAI usage control through a browser extension. Source: Lasso Security: AI usage control · Read 27 Sep 2026 |
| Network or SSE proxyDiffers | Not in our sourcesNot described on the pages we read. | DescribedProxy integrations for AI usage control; the page says it works with Palo Alto Networks or CrowdStrike. Source: Lasso Security: AI usage control · Read 27 Sep 2026 |
| AI or MCP gatewayDiffers | Not in our sourcesNot described on the pages we read. | DescribedAn open-source MCP gateway that discovers MCP servers across Claude, Cursor and Windsurf and can block, alert or sanitize. Source: Lasso Security: MCP security · Read 27 Sep 2026 |
| Names the coding agents it covers | 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 | MatchesClaude Code lifecycle hooks, and MCP discovery across Claude, Cursor and Windsurf. Source: Lasso Security: AI coding assistants · 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 Claude Code tool call before it is executed. Source: Lasso Security: AI coding assistants · Read 27 Sep 2026 |
| Controls what goes into browser AIDiffers | Not in our sources | MatchesUsage control through a browser extension. Source: Lasso Security: AI usage control · 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 | PartlyClaude Code hooks are set through the enterprise management platform; the other components are a browser extension, a proxy and a gateway. Source: Lasso Security: AI coding assistants · Read 27 Sep 2026 |
| Can warn or ask instead of only blockingDiffers | MatchesAsk is one of three answers, with Allow and Deny. Source: Bay homepage · Read 27 Sep 2026 | PartlyAlert is an action; asking the user is not described. Source: Lasso Security: MCP security · 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, alert or sanitize on MCP traffic. Source: Lasso Security: MCP security · 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 without blocking. Source: Lasso Security: MCP security · 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 | PartlyAudit-ready reports. Source: Lasso Security: AI usage control · Read 27 Sep 2026 |
| Also covers SaaS, cloud or homegrown AIDiffers | Not in our sources | MatchesDiscovery and AI-BOM, posture management, red teaming and runtime enforcement for AI apps. Source: Lasso Security homepage · Read 27 Sep 2026 |
| Has a public price or tiers (vendor site or marketplace)Differs | Not in our sources | PartlyAWS Marketplace lists Lasso for Employees with an annual commit for GenAI chatbots at $20,000 for 12 months (marketplace list price); prices for its other products are not listed there. Source: AWS Marketplace: Lasso for Employees · Read 11 Oct 2026 |
| Built into | None | None |
| Works with | None in our sources | The usage control page says it works with Palo Alto Networks. The usage control page says it works with CrowdStrike. Offers proxy integrations for AI usage control. Source: Lasso Security: AI usage control · 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 | Marketplace list price: Lasso for Employees, annual commit for GenAI chatbots, $20,000 for 12 months on AWS Marketplace. Other products: not published. Source: AWS Marketplace: Lasso for Employees · Read 11 Oct 2026 |
Where do they differ?
- On-device control: Bay describes it; Lasso partly describes it.
- Browser extension: Bay is not in our sources; Lasso describes it.
- Network or SSE proxy: Bay is not in our sources; Lasso describes it.
- AI or MCP gateway: Bay is not in our sources; Lasso describes it.
- Controls what goes into browser AI: Bay is not in our sources; Lasso matches.
- Rolls out through EDR or device management you run: Bay matches; Lasso partly matches.
- Can warn or ask instead of only blocking: Bay matches; Lasso partly matches.
- Has a watch-only or simulation mode: Bay matches; Lasso partly matches.
- Records who or what took each action: Bay matches; Lasso partly matches.
- Also covers SaaS, cloud or homegrown AI: Bay is not in our sources; Lasso matches.
- Has a public price or tiers (vendor site or marketplace): Bay is not in our sources; Lasso partly 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 Lasso if
- You want controls in several places at once: browser, proxy, MCP gateway and coding agent hooks
- You prefer an open-source MCP gateway you can inspect
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.
Lasso
- Several components to deploy and run.
- Asking the user before an action is not described, and the only public price covers its chatbot product on AWS Marketplace.