HEAD-TO-HEAD · FACTS ONLY
Bloom vs Sun: AI endpoint control facts side by side
Short answer
Bloom describes 0 of the four product control types on the pages we read and Sun describes 0 and their control positions match. On decisions, Bloom describes some control over tool calls and Sun decides on a tool call before it runs. 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: Sun, 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 | Sun |
|---|---|---|
| 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. | AI agent security that says it sits in the path of every AI agent across workstations, cloud and SaaS, with three capabilities: discovery, posture management that learns each agent's purpose, and runtime checks of every tool call, connection and resource draw against that purpose before it executes. |
| 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 | Not described; the site says you can get started in 5 minutes. Source: Sun Security homepage · Read 13 Oct 2026 |
| On-device control | 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 | Partly describedCovers agents on workstations; the on-device method is not described. Source: Sun Security homepage · Read 13 Oct 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 | PartlyNames Cursor and Claude Cowork; Claude Code, Codex and GitHub Copilot are not named. Source: Sun Security homepage · Read 13 Oct 2026 |
| Decides on a tool call before it runsDiffers | PartlyAutomatically scales back overpermissioned MCP servers; decisions on individual calls are not described. Source: Bloom Security homepage · Read 27 Sep 2026 | MatchesEvery tool call, connection and resource draw is checked against the agent's purpose before it executes. Source: Sun Security 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 | Not in our sources | Not in our sources |
| Can warn or ask instead of only blocking | Not in our sources | Not in our sources |
| Can block an agent, tool or action | PartlyEnforces policies across npm, Chrome Web Store and Open VSX. Source: Bloom Security homepage · Read 27 Sep 2026 | PartlyIts demo shows a stopped action. Source: Sun Security homepage · Read 13 Oct 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 | PartlyIts demo shows an action log. Source: Sun Security homepage · Read 13 Oct 2026 |
| Also covers SaaS, cloud or homegrown AIDiffers | Not in our sources | MatchesNames Copilot Studio and AWS Bedrock agents. Source: Sun Security homepage · Read 13 Oct 2026 |
| Has a public price or tiers (vendor site or marketplace) | Not in our sources | Not in our sources |
| 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 | Not published (demo request). Source: Sun Security homepage · Read 13 Oct 2026 |
Where do they differ?
- Names the coding agents it covers: Bloom is not in our sources; Sun partly matches.
- Decides on a tool call before it runs: Bloom partly matches; Sun matches.
- Records who or what took each action: Bloom is not in our sources; Sun partly matches.
- Also covers SaaS, cloud or homegrown AI: Bloom is not in our sources; Sun 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 Sun if
- You want each agent action checked against that agent's purpose
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).
Sun
- Sun's site is a single marketing page, so most details are not described.
- How it reaches devices is not described, and no price is published.