HEAD-TO-HEAD · FACTS ONLY
Neo vs Noma: 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: Neo
- 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)
What are the facts, side by side?
| Fact | Neo | Noma |
|---|---|---|
| Owner | None | None |
| Positioning | 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. | 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 | 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 | 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 control | 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 | 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 | 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 | 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 covers | MatchesNames Claude Code, Gemini CLI, GitHub Copilot and OpenAI Codex; Cursor is not named. Source: Neo: platform · Read 13 Oct 2026 | MatchesNames Claude Code, Cursor and Codex. Source: Noma Security: endpoint agents · Read 27 Sep 2026 |
| Decides on a tool call before it runsDiffers | MatchesIntercepts agent actions at the endpoint and allows, blocks or holds them for approval. Source: Neo homepage · Read 13 Oct 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 AI | Not in our sources | Not in our sources |
| Rolls out through EDR or device management you runDiffers | PartlyIts own lightweight sensor rather than a rollout through existing EDR or MDM. Source: Neo: platform · Read 13 Oct 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 blockingDiffers | MatchesHold an action for verified human approval. Source: Neo: platform · Read 13 Oct 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 is one of its runtime actions. Source: Neo: platform · Read 13 Oct 2026 | MatchesBlocks unauthorized and malicious agents. Source: Noma Security: endpoint agents · Read 27 Sep 2026 |
| Has a watch-only or simulation modeDiffers | MatchesAudit mode before enforcement. Source: Neo: platform · Read 13 Oct 2026 | Not in our sources |
| Records who or what took each actionDiffers | MatchesEvery action tied to the human or agent that caused it, in an immutable audit chain. Source: Neo homepage · Read 13 Oct 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 AIDiffers | PartlyNames SaaS and desktop AI such as Slack AI, Notion AI, Salesforce Agentforce and ChatGPT Desktop. Source: Neo: platform · Read 13 Oct 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 | Not in our sources | 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 | None in our sources | None in our sources |
| Price | Not published (demo request). Source: Neo homepage · Read 13 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?
- Browser extension: Neo partly describes it; Noma is not in our sources.
- Decides on a tool call before it runs: Neo matches; Noma partly matches.
- Rolls out through EDR or device management you run: Neo partly matches; Noma matches.
- Can warn or ask instead of only blocking: Neo matches; Noma partly matches.
- Has a watch-only or simulation mode: Neo matches; Noma is not in our sources.
- Records who or what took each action: Neo matches; Noma partly matches.
- Also covers SaaS, cloud or homegrown AI: Neo partly matches; Noma matches.
- Has a public price or tiers (vendor site or marketplace): Neo is not in our sources; Noma matches.
Choose Neo if
- You want to hold agent actions for human approval on the device
- You want an audit mode before enforcing rules
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?
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.
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.