HEAD-TO-HEAD · FACTS ONLY
Noma 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: Noma
- 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 | Noma | Pluto |
|---|---|---|
| Owner | None | None |
| Positioning | 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. | "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 | 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 | (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 | 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 | 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 | MatchesNames Claude Code, Cursor and Codex. Source: Noma Security: endpoint agents · 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 runs | 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 | 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 runDiffers | MatchesThrough your existing EDR or MDM, with no new endpoint agent. Source: Noma Security: endpoint agents · 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 blockingDiffers | PartlyStates that runtime decisions can route to a human. Source: Noma Security: endpoint agents (re-read) · Read 13 Oct 2026 | Not in our sources |
| Can block an agent, tool or actionDiffers | MatchesBlocks unauthorized and malicious agents. Source: Noma Security: endpoint agents · 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 actionDiffers | 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 | Not in our sources |
| Also covers SaaS, cloud or homegrown AIDiffers | MatchesCovers endpoint, SaaS and homegrown agents. Source: Noma Security homepage · Read 27 Sep 2026 | Not in our sources |
| Has a public price or tiers (vendor site or marketplace)Differs | 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 | Not in our sources |
| Built into | None | 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 | 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 | Not published (demo request). Source: Pluto Security homepage · Read 13 Oct 2026 |
Where do they differ?
- On-device control: Noma describes it; Pluto partly describes it.
- Names the coding agents it covers: Noma matches; Pluto partly matches.
- Rolls out through EDR or device management you run: Noma matches; Pluto partly matches.
- Can warn or ask instead of only blocking: Noma partly matches; Pluto is not in our sources.
- Can block an agent, tool or action: Noma matches; Pluto is not in our sources.
- Records who or what took each action: Noma partly matches; Pluto is not in our sources.
- Also covers SaaS, cloud or homegrown AI: Noma matches; Pluto is not in our sources.
- Has a public price or tiers (vendor site or marketplace): Noma matches; Pluto is not in our sources.
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
Choose Pluto if
- You want guardrails on coding agents without a new endpoint agent
Which limits should you check?
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.
Pluto
- Pluto publishes little product detail on its own site, so this profile relies partly on a third-party report.
- No price is published.