HEAD-TO-HEAD · FACTS ONLY
Bloom vs Noma: AI endpoint control facts side by side
Short answer
Bloom describes 0 of the four product control types on the pages we read and Noma describes 1; they differ on on-device control. On decisions, Bloom describes some control over tool calls and Noma describes some control over tool calls. 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?
- Filled or hatched marker: Bloom
- 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 | Bloom | Noma |
|---|---|---|
| Owner | None | None |
| Positioning | An endpoint security company built around "Securing the AI-Native Endpoint": discovery of the software, extensions and AI tools running on devices, with policy enforcement across package and extension marketplaces. Offices in Wilmington, Delaware and Tel Aviv. | 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 | Deployment method not published on the pages we read (re-checked 11 October 2026). Source: Bloom Security homepage · Read 27 Sep 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 controlDiffers | Partly describedDiscovers software, extensions and AI on the endpoint and automatically scales back overpermissioned MCP servers; how it reaches the device is not published. Source: Bloom Security homepage · Read 27 Sep 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 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 | Not in our sources | MatchesNames Claude Code, Cursor and Codex. Source: Noma Security: endpoint agents · Read 27 Sep 2026 |
| Decides on a tool call before it runs | PartlyAutomatically scales back overpermissioned MCP servers; decisions on individual calls are not described. Source: Bloom Security homepage · Read 27 Sep 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 | Not in our sources | 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 | Not in our sources | 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 actionDiffers | PartlyEnforces policies across npm, Chrome Web Store and Open VSX. Source: Bloom Security homepage · Read 27 Sep 2026 | MatchesBlocks unauthorized and malicious agents. Source: Noma Security: endpoint agents · Read 27 Sep 2026 |
| Has a watch-only or simulation mode | Not in our sources | Not in our sources |
| Records who or what took each actionDiffers | Not in our sources | 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 | Not in our sources | 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. Source: Bloom Security homepage · Read 27 Sep 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?
- On-device control: Bloom partly describes it; Noma describes it.
- Names the coding agents it covers: Bloom is not in our sources; Noma matches.
- Rolls out through EDR or device management you run: Bloom is not in our sources; Noma matches.
- Can warn or ask instead of only blocking: Bloom is not in our sources; Noma partly matches.
- Can block an agent, tool or action: Bloom partly matches; Noma matches.
- Records who or what took each action: Bloom is not in our sources; Noma partly matches.
- Also covers SaaS, cloud or homegrown AI: Bloom is not in our sources; Noma matches.
- Has a public price or tiers (vendor site or marketplace): Bloom is not in our sources; Noma matches.
Choose Bloom if
- Your first worry is unvetted extensions and packages arriving on developer machines
- You want an inventory of everything on the endpoint before you write AI-specific 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?
Bloom
- Deployment method and pricing are not published.
- Decisions on individual tool calls and an activity record are not described on the pages we read.
- Limited company information on its own pages: they do not name investors; funding is known from press coverage (Ctech, 30 July 2026).
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.