Skip to content
Endpoint AI Finder

HEAD-TO-HEAD · FACTS ONLY

Koi vs Lasso: AI endpoint control facts side by side

Short answer

Koi 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, Koi describes some control over tool calls 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?

Koi: described at 1 of 4 product control positions (on-device control).AI servicesMCP serversDEVOn-device controlBRWBrowser extensionNETNetwork or SSE proxyGWYAI or MCP gatewayPOLPolicy: no product
  • Filled or hatched marker: Koi
  • 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)
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?

Koi (Palo Alto Networks) and Lasso Security, from each product's own pages. Differs is computed from recorded statuses, not wording.
FactKoiLasso
OwnerPalo Alto Networks (acquisition completed 14 April 2026)None
PositioningKoi, now sold by Palo Alto Networks as Cortex Agentic Endpoint Security, gives visibility into models, MCPs and extensions on endpoints, removes insecure packages, extensions and AI tools in one click, and stops malicious actions.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 devicesAvailable as a Cortex XDR module or as a standalone agent. koi.ai now redirects to the Palo Alto Networks page.

Source: Palo Alto Networks: Cortex Agentic Endpoint Security · 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 controlDiffersDescribedAgent-based visibility into models, MCPs and extensions, one-click removal of insecure packages, extensions and AI tools, and blocking of unsafe AI application interactions.

Source: Palo Alto Networks: Cortex Agentic Endpoint Security · Read 27 Sep 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 extensionDiffersNot in our sourcesNot described on the pages we read.DescribedAI usage control through a browser extension.

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

Network or SSE proxyDiffersNot 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 gatewayDiffersNot 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 coversMatchesA Palo Alto Networks blog of 18 August 2026 names Claude Code, Cursor, Codex and Antigravity.

Source: Palo Alto Networks blog: A Quarter of Innovation with Koi Agentic Endpoint Security · Read 11 Oct 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 runsDiffersPartlyBlocks unsafe AI application interactions and prevents prompt injections; decisions on individual tool calls are not described.

Source: Palo Alto Networks: Cortex Agentic Endpoint Security · Read 27 Sep 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 AIDiffersNot in our sourcesMatchesUsage control through a browser extension.

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

Rolls out through EDR or device management you runPartlyA Cortex XDR module, or its own standalone agent.

Source: Palo Alto Networks: Cortex Agentic Endpoint Security · 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 blockingDiffersNot in our sourcesPartlyAlert is an action; asking the user is not described.

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

Can block an agent, tool or actionMatchesStops malicious actions and removes insecure packages, extensions and AI tools in one click.

Source: Palo Alto Networks: Cortex Agentic Endpoint Security · Read 27 Sep 2026

MatchesBlock, alert or sanitize on MCP traffic.

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

Has a watch-only or simulation modeDiffersNot in our sourcesPartlyAlert without blocking.

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

Records who or what took each actionDiffersNot in our sourcesPartlyAudit-ready reports.

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

Also covers SaaS, cloud or homegrown AIDiffersPartlyPalo Alto Networks plans integration with Prisma AIRS, its wider AI security platform.

Source: Palo Alto Networks press release: acquisition of Koi completed · Read 27 Sep 2026

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)DiffersNot in our sourcesPartlyAWS 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 intoOffered as a Cortex XDR module.

Source: Palo Alto Networks press release: acquisition of Koi completed · Read 27 Sep 2026

None
Works withNone in our sourcesThe 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

PriceNot published.

Source: Palo Alto Networks: Cortex Agentic Endpoint Security · Read 27 Sep 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: Koi describes it; Lasso partly describes it.
  • Browser extension: Koi is not in our sources; Lasso describes it.
  • Network or SSE proxy: Koi is not in our sources; Lasso describes it.
  • AI or MCP gateway: Koi is not in our sources; Lasso describes it.
  • Decides on a tool call before it runs: Koi partly matches; Lasso matches.
  • Controls what goes into browser AI: Koi is not in our sources; Lasso matches.
  • Can warn or ask instead of only blocking: Koi is not in our sources; Lasso partly matches.
  • Has a watch-only or simulation mode: Koi is not in our sources; Lasso partly matches.
  • Records who or what took each action: Koi is not in our sources; Lasso partly matches.
  • Also covers SaaS, cloud or homegrown AI: Koi partly matches; Lasso matches.
  • Has a public price or tiers (vendor site or marketplace): Koi is not in our sources; Lasso partly matches.

Choose Koi if

  • You already run Palo Alto Networks Cortex XDR
  • You want to find and remove risky extensions and packages across the fleet

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?

Koi

  • Agent-based: it adds an agent unless you run it as a Cortex XDR module.
  • Warn or ask actions and a record that separates a person from an agent are not described on the pages we read, and no pricing is published.

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.

Questions people ask

Is Koi or Lasso better for AI endpoint control?

Neither is scored on this site. Koi describes 1 of four product control types and Lasso 3 on the pages we read, and they differ on 11 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?

Koi: Partly. Lasso: Matches. Warn or ask: Koi Not in our sources, Lasso Partly.

Do Koi or Lasso publish prices?

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