HEAD-TO-HEAD · FACTS ONLY
Koi vs Neo: 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: 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)
What are the facts, side by side?
| Fact | Koi | Neo |
|---|---|---|
| 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. | 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 | 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 | 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 control | 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 | 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 | Not in our sourcesNot described on the pages we read. | 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 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 covers | 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 | 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 runsDiffers | 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 | 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 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 | 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 | Not in our sources | MatchesHold an action for verified human approval. Source: Neo: platform · Read 13 Oct 2026 |
| Can block an agent, tool or action | 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 | MatchesBlock is one of its runtime actions. Source: Neo: platform · Read 13 Oct 2026 |
| Has a watch-only or simulation modeDiffers | Not in our sources | MatchesAudit mode before enforcement. Source: Neo: platform · Read 13 Oct 2026 |
| Records who or what took each actionDiffers | Not in our sources | 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 AI | 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 | 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) | 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 | None in our sources |
| Price | Not published. Source: Palo Alto Networks: Cortex Agentic Endpoint Security · Read 27 Sep 2026 | Not published (demo request). Source: Neo homepage · Read 13 Oct 2026 |
Where do they differ?
- Browser extension: Koi is not in our sources; Neo partly describes it.
- Decides on a tool call before it runs: Koi partly matches; Neo matches.
- Can warn or ask instead of only blocking: Koi is not in our sources; Neo matches.
- Has a watch-only or simulation mode: Koi is not in our sources; Neo matches.
- Records who or what took each action: Koi is not in our sources; Neo 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 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?
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.
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.