HEAD-TO-HEAD · FACTS ONLY
Koi vs Pluto: AI endpoint control facts side by side
Short answer
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: Koi
- 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)
What are the facts, side by side?
| Fact | Koi | Pluto |
|---|---|---|
| Owner | Palo Alto Networks (acquisition completed 14 April 2026) | None |
| Positioning | Koi, 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. | "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 devices | Available 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 | (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 controlDiffers | DescribedAgent-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 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 extension | Not in our sourcesNot described on the pages we read. | Not in our sourcesNot described on the pages we read. |
| Network or SSE proxy | Not in our sourcesNot described on the pages we read. | Not in our sourcesNot described on the pages we read. |
| AI or MCP gateway | Not in our sourcesNot described on the pages we read. | Not in our sourcesNot described on the pages we read. |
| Names the coding agents it coversDiffers | MatchesA 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 | 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 runs | PartlyBlocks 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 | 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 AI | Not in our sources | Not in our sources |
| Rolls out through EDR or device management you run | PartlyA Cortex XDR module, or its own standalone agent. Source: Palo Alto Networks: Cortex Agentic Endpoint Security · 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 blocking | Not in our sources | Not in our sources |
| Can block an agent, tool or actionDiffers | MatchesStops 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 | Not in our sources |
| Has a watch-only or simulation mode | Not in our sources | Not in our sources |
| Records who or what took each action | Not in our sources | Not in our sources |
| Also covers SaaS, cloud or homegrown AIDiffers | PartlyPalo 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 | Not in our sources |
| Has a public price or tiers (vendor site or marketplace) | Not in our sources | Not in our sources |
| Built into | Offered as a Cortex XDR module. Source: Palo Alto Networks press release: acquisition of Koi completed · Read 27 Sep 2026 | None |
| Works with | None in our sources | (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 |
| Price | Not published. Source: Palo Alto Networks: Cortex Agentic Endpoint Security · Read 27 Sep 2026 | Not published (demo request). Source: Pluto Security homepage · Read 13 Oct 2026 |
Where do they differ?
- On-device control: Koi describes it; Pluto partly describes it.
- Names the coding agents it covers: Koi matches; Pluto partly matches.
- Can block an agent, tool or action: Koi matches; Pluto is not in our sources.
- Also covers SaaS, cloud or homegrown AI: Koi partly matches; Pluto is not in our sources.
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 Pluto if
- You want guardrails on coding agents without a new endpoint agent
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.
Pluto
- Pluto publishes little product detail on its own site, so this profile relies partly on a third-party report.
- No price is published.