Is Lasso or Neo better for AI endpoint control?

Neither is scored on this site. Lasso describes 3 of four product control types and Neo 1 on the pages we read, and they differ on 10 recorded facts. Which fits depends on the AI tools people use, your devices, where the work happens and whether you block or guide; the finder checks those.

Which of the two decides on a tool call before it runs?

Lasso: Matches. Neo: Matches. Warn or ask: Lasso Partly, Neo Matches.

Do Lasso or Neo publish prices?

Lasso: Marketplace list price: Lasso for Employees, annual commit for GenAI chatbots, $20,000 for 12 months on AWS Marketplace. Other products: not published. Neo: Not published (demo request).

HEAD-TO-HEAD · FACTS ONLY

Lasso vs Neo: AI endpoint control facts side by side

Short answer

Lasso describes 3 of the four product control types on the pages we read and Neo describes 1; they differ on on-device control, browser extension, network or SSE proxy and AI or MCP gateway. On decisions, Lasso decides on a tool call before it runs and Neo 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: Lasso
Dashed teal ring: Neo, 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)

The map shows where each product's own pages describe a control, or where your answers point. It is not a measure of how well a product works.

What are the facts, side by side?

Lasso Security and Neo, from each product's own pages. Differs is computed from recorded statuses, not wording.
Fact	Lasso	Neo
Owner	None	None
Positioning	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.	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.
How it reaches devices	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	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
On-device controlDiffers	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	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
Browser extensionDiffers	DescribedAI usage control through a browser extension. Source: Lasso Security: AI usage control · Read 27 Sep 2026	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
Network or SSE proxyDiffers	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	Not in our sourcesNot described on the pages we read.
AI or MCP gatewayDiffers	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	Not in our sourcesNot described on the pages we read.
Names the coding agents it covers	MatchesClaude Code lifecycle hooks, and MCP discovery across Claude, Cursor and Windsurf. Source: Lasso Security: AI coding assistants · Read 27 Sep 2026	MatchesNames Claude Code, Gemini CLI, GitHub Copilot and OpenAI Codex; Cursor is not named. Source: Neo: platform · Read 13 Oct 2026
Decides on a tool call before it runs	MatchesInspects every Claude Code tool call before it is executed. Source: Lasso Security: AI coding assistants · Read 27 Sep 2026	MatchesIntercepts agent actions at the endpoint and allows, blocks or holds them for approval. Source: Neo homepage · Read 13 Oct 2026
Controls what goes into browser AIDiffers	MatchesUsage control through a browser extension. Source: Lasso Security: AI usage control · Read 27 Sep 2026	Not in our sources
Rolls out through EDR or device management you run	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	PartlyIts own lightweight sensor rather than a rollout through existing EDR or MDM. Source: Neo: platform · Read 13 Oct 2026
Can warn or ask instead of only blockingDiffers	PartlyAlert is an action; asking the user is not described. Source: Lasso Security: MCP security · Read 27 Sep 2026	MatchesHold an action for verified human approval. Source: Neo: platform · Read 13 Oct 2026
Can block an agent, tool or action	MatchesBlock, alert or sanitize on MCP traffic. Source: Lasso Security: MCP security · Read 27 Sep 2026	MatchesBlock is one of its runtime actions. Source: Neo: platform · Read 13 Oct 2026
Has a watch-only or simulation modeDiffers	PartlyAlert without blocking. Source: Lasso Security: MCP security · Read 27 Sep 2026	MatchesAudit mode before enforcement. Source: Neo: platform · Read 13 Oct 2026
Records who or what took each actionDiffers	PartlyAudit-ready reports. Source: Lasso Security: AI usage control · Read 27 Sep 2026	MatchesEvery action tied to the human or agent that caused it, in an immutable audit chain. Source: Neo homepage · Read 13 Oct 2026
Also covers SaaS, cloud or homegrown AIDiffers	MatchesDiscovery and AI-BOM, posture management, red teaming and runtime enforcement for AI apps. Source: Lasso Security homepage · Read 27 Sep 2026	PartlyNames SaaS and desktop AI such as Slack AI, Notion AI, Salesforce Agentforce and ChatGPT Desktop. Source: Neo: platform · Read 13 Oct 2026
Has a public price or tiers (vendor site or marketplace)Differs	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	Not in our sources
Built into	None	None
Works with	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	None in our sources
Price	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	Not published (demo request). Source: Neo homepage · Read 13 Oct 2026

Where do they differ?

On-device control: Lasso partly describes it; Neo describes it.
Browser extension: Lasso describes it; Neo partly describes it.
Network or SSE proxy: Lasso describes it; Neo is not in our sources.
AI or MCP gateway: Lasso describes it; Neo is not in our sources.
Controls what goes into browser AI: Lasso matches; Neo is not in our sources.
Can warn or ask instead of only blocking: Lasso partly matches; Neo matches.
Has a watch-only or simulation mode: Lasso partly matches; Neo matches.
Records who or what took each action: Lasso partly matches; Neo matches.
Also covers SaaS, cloud or homegrown AI: Lasso matches; Neo partly matches.
Has a public price or tiers (vendor site or marketplace): Lasso partly matches; Neo is not in our sources.

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

Choose Neo if

You want to hold agent actions for human approval on the device
You want an audit mode before enforcing rules

Which limits should you check?

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.

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.

Line up Lasso and Neo with others Run the finder