Skip to content
Endpoint AI Finder

HEAD-TO-HEAD · FACTS ONLY

Lasso vs Pluto: AI endpoint control facts side by side

Short answer

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

Lasso: described at 3 of 4 product control positions (browser extension, network or sse proxy, ai or mcp gateway), partly at 1 (on-device control).AI servicesMCP serversDEVOn-device controlBRWBrowser extensionNETNetwork or SSE proxyGWYAI or MCP gatewayPOLPolicy: no product
  • Filled or hatched marker: Lasso
  • Dashed teal ring: Pluto, 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 Pluto Security, from each product's own pages. Differs is computed from recorded statuses, not wording.
FactLassoPluto
OwnerNoneNone
PositioningAn 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."The first workspace security platform for the AI era": visibility, risk understanding and real-time guardrails for AI builders, developer tools and business workspaces. Founding team from Unit 8200, Microsoft and Palo Alto Networks; part of AWS, CrowdStrike and NVIDIA accelerators. Publishes research on Claude Code hooks, exposed MCP servers and Open VSX malware.
How it reaches devicesSeveral 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

(secondary: SACR) Agentless, through API integrations and existing CrowdStrike, Defender and MDM infrastructure. Pluto's own site has no product or documentation page describing rollout.

Source: SACR (secondary): CISO guide to endpoint control and prevention, July 2026 · Read 13 Oct 2026 · secondary source

On-device controlPartly 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

Partly described(secondary: SACR) inline hook configuration on coding agents for runtime observability and enforcement.

Source: SACR (secondary): CISO guide to endpoint control and prevention, July 2026 · Read 13 Oct 2026 · secondary source

Browser extensionDiffersDescribedAI 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 proxyDiffersDescribedProxy 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 gatewayDiffersDescribedAn 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 coversDiffersMatchesClaude Code lifecycle hooks, and MCP discovery across Claude, Cursor and Windsurf.

Source: Lasso Security: AI coding assistants · Read 27 Sep 2026

PartlyPluto's research covers Claude Code; SACR (secondary) says it governs tools such as ChatGPT, Claude and Copilot.

Source: SACR (secondary): CISO guide to endpoint control and prevention, July 2026 · Read 13 Oct 2026 · secondary source

Decides on a tool call before it runsDiffersMatchesInspects every Claude Code tool call before it is executed.

Source: Lasso Security: AI coding assistants · Read 27 Sep 2026

Partly(secondary: SACR) inline hooks on coding agents for runtime enforcement.

Source: SACR (secondary): CISO guide to endpoint control and prevention, July 2026 · Read 13 Oct 2026 · secondary source

Controls what goes into browser AIDiffersMatchesUsage 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 runPartlyClaude 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

Partly(secondary: SACR) deploys through existing CrowdStrike, Defender and MDM infrastructure.

Source: SACR (secondary): CISO guide to endpoint control and prevention, July 2026 · Read 13 Oct 2026 · secondary source

Can warn or ask instead of only blockingDiffersPartlyAlert is an action; asking the user is not described.

Source: Lasso Security: MCP security · Read 27 Sep 2026

Not in our sources
Can block an agent, tool or actionDiffersMatchesBlock, alert or sanitize on MCP traffic.

Source: Lasso Security: MCP security · Read 27 Sep 2026

Not in our sources
Has a watch-only or simulation modeDiffersPartlyAlert without blocking.

Source: Lasso Security: MCP security · Read 27 Sep 2026

Not in our sources
Records who or what took each actionDiffersPartlyAudit-ready reports.

Source: Lasso Security: AI usage control · Read 27 Sep 2026

Not in our sources
Also covers SaaS, cloud or homegrown AIDiffersMatchesDiscovery and AI-BOM, posture management, red teaming and runtime enforcement for AI apps.

Source: Lasso Security homepage · Read 27 Sep 2026

Not in our sources
Has a public price or tiers (vendor site or marketplace)DiffersPartlyAWS 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 intoNoneNone
Works withThe 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

(secondary: SACR) deploys through existing CrowdStrike, Defender and MDM infrastructure. (secondary: SACR) deploys through existing CrowdStrike, Defender and MDM infrastructure.

Source: SACR (secondary): CISO guide to endpoint control and prevention, July 2026 · Read 13 Oct 2026 · secondary source

PriceMarketplace 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: Pluto Security homepage · Read 13 Oct 2026

Where do they differ?

  • Browser extension: Lasso describes it; Pluto is not in our sources.
  • Network or SSE proxy: Lasso describes it; Pluto is not in our sources.
  • AI or MCP gateway: Lasso describes it; Pluto is not in our sources.
  • Names the coding agents it covers: Lasso matches; Pluto partly matches.
  • Decides on a tool call before it runs: Lasso matches; Pluto partly matches.
  • Controls what goes into browser AI: Lasso matches; Pluto is not in our sources.
  • Can warn or ask instead of only blocking: Lasso partly matches; Pluto is not in our sources.
  • Can block an agent, tool or action: Lasso matches; Pluto is not in our sources.
  • Has a watch-only or simulation mode: Lasso partly matches; Pluto is not in our sources.
  • Records who or what took each action: Lasso partly matches; Pluto is not in our sources.
  • Also covers SaaS, cloud or homegrown AI: Lasso matches; Pluto is not in our sources.
  • Has a public price or tiers (vendor site or marketplace): Lasso partly matches; Pluto 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 Pluto if

  • You want guardrails on coding agents without a new endpoint 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.

Pluto

  • Pluto publishes little product detail on its own site, so this profile relies partly on a third-party report.
  • No price is published.

Questions people ask

Is Lasso or Pluto better for AI endpoint control?

Neither is scored on this site. Lasso describes 3 of four product control types and Pluto 0 on the pages we read, and they differ on 12 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. Pluto: Partly. Warn or ask: Lasso Partly, Pluto Not in our sources.

Do Lasso or Pluto 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. Pluto: Not published (demo request).