Is Lasso or Noma better for AI endpoint control?

Neither is scored on this site. Lasso describes 3 of four product control types and Noma 1 on the pages we read, and they differ on 9 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. Noma: Partly. Warn or ask: Lasso Partly, Noma Partly.

Do Lasso or Noma 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. Noma: Marketplace list price: $200,000 for a 12-month contract on AWS Marketplace. No pricing page on noma.security.

HEAD-TO-HEAD · FACTS ONLY

Lasso vs Noma: AI endpoint control facts side by side

Short answer

Lasso describes 3 of the four product control types on the pages we read and Noma 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 Noma describes some control over tool calls. 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: Noma, 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 Noma Security, from each product's own pages. Differs is computed from recorded statuses, not wording.
Fact	Lasso	Noma
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.	An AI security platform with AI-SPM, Agent Access Control, AI detection and response and AI red teaming, covering agents on endpoints, in SaaS and in homegrown apps.
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	Discovers endpoint agents through your existing EDR or MDM, with no new endpoint agent to deploy. Source: Noma Security: endpoint agents · Read 27 Sep 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	DescribedDiscovers endpoint agents such as Claude Code, Cursor and Codex with their MCP servers and skills, blocks unauthorized and malicious ones, and inspects activity at runtime. Source: Noma Security: endpoint agents · Read 27 Sep 2026
Browser extensionDiffers	DescribedAI usage control through a browser extension. Source: Lasso Security: AI usage control · Read 27 Sep 2026	Not in our sourcesNot described on the pages we read.
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, Cursor and Codex. Source: Noma Security: endpoint agents · Read 27 Sep 2026
Decides on a tool call before it runsDiffers	MatchesInspects every Claude Code tool call before it is executed. Source: Lasso Security: AI coding assistants · Read 27 Sep 2026	PartlyRuntime inspection of the event, the session, the identity behind the agent and the data it reaches; decisions on individual tool calls are described less specifically. Source: Noma Security: endpoint agents · Read 27 Sep 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 runDiffers	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	MatchesThrough your existing EDR or MDM, with no new endpoint agent. Source: Noma Security: endpoint agents · Read 27 Sep 2026
Can warn or ask instead of only blocking	PartlyAlert is an action; asking the user is not described. Source: Lasso Security: MCP security · Read 27 Sep 2026	PartlyStates that runtime decisions can route to a human. Source: Noma Security: endpoint agents (re-read) · 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	MatchesBlocks unauthorized and malicious agents. Source: Noma Security: endpoint agents · Read 27 Sep 2026
Has a watch-only or simulation modeDiffers	PartlyAlert without blocking. Source: Lasso Security: MCP security · Read 27 Sep 2026	Not in our sources
Records who or what took each action	PartlyAudit-ready reports. Source: Lasso Security: AI usage control · Read 27 Sep 2026	PartlyKeeps a live registry of allowed agents, MCP servers and skills and inspects the identity behind each agent. Source: Noma Security: endpoint agents · Read 27 Sep 2026
Also covers SaaS, cloud or homegrown AI	MatchesDiscovery and AI-BOM, posture management, red teaming and runtime enforcement for AI apps. Source: Lasso Security homepage · Read 27 Sep 2026	MatchesCovers endpoint, SaaS and homegrown agents. Source: Noma Security homepage · Read 27 Sep 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	MatchesAWS Marketplace lists the Noma Security Platform at $200,000 for a 12-month contract (marketplace list price); noma.security has no pricing page. Source: AWS Marketplace: Noma Security Platform · Read 11 Oct 2026
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	Marketplace list price: $200,000 for a 12-month contract on AWS Marketplace. No pricing page on noma.security. Source: AWS Marketplace: Noma Security Platform · Read 11 Oct 2026

Where do they differ?

On-device control: Lasso partly describes it; Noma describes it.
Browser extension: Lasso describes it; Noma is not in our sources.
Network or SSE proxy: Lasso describes it; Noma is not in our sources.
AI or MCP gateway: Lasso describes it; Noma is not in our sources.
Decides on a tool call before it runs: Lasso matches; Noma partly matches.
Controls what goes into browser AI: Lasso matches; Noma is not in our sources.
Rolls out through EDR or device management you run: Lasso partly matches; Noma matches.
Has a watch-only or simulation mode: Lasso partly matches; Noma is not in our sources.
Has a public price or tiers (vendor site or marketplace): Lasso partly matches; Noma matches.

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 Noma if

Agents run on laptops, in SaaS and in apps you build, and you want one place to see them
You want discovery through existing EDR or MDM without a new agent

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.

Noma

A watch-only or simulation mode is not described on the pages we read.
Decisions on individual tool calls are described less specifically than discovery, and the only public price is a $200,000 a year marketplace listing.

Line up Lasso and Noma with others Run the finder