What does Zenity do?
Agent governance for enterprises. It has reportedly raised more than $100M, though funding figures in this market are sometimes estimates.
Beam vs ZENITY
Beam vs Zenity
Zenity sells agent governance to enterprises and has raised more than $100M by reported figures. Governance means policy, ownership and control across many agents. Beam is a coding-agent control layer: workspace policy for owners and admins, Sentinel on browser AI chats, and a local timeline — not an org-wide agent inventory product.
Beam vs Zenity, side by side
Details below are drawn from a September 2026 review of the AI agent security market. Some figures are vendor-sourced or analyst estimates, and this is a fast-moving space — check with each vendor before you buy. Composio details come from its own pricing and documentation pages as of October 2026.
| Beam | Zenity | |
|---|---|---|
| What it is | Local-first activity monitor, policy enforcement, and pre-run scanner for AI coding agents, with a Sentinel browser extension for AI chats. | Enterprise agent governance platform. |
| Monitoring | Shell commands, file changes, tool calls, network endpoints and browser actions from harnesses such as Claude Code, Codex and Cursor, plus Beam Sentinel checks on supported AI chat sites before send. Normalised into local NDJSON with risk flags and evidence attached. | Agent governance across an organisation's AI agents. |
| Skill / MCP scanning | Yes. SKILL.md files and MCP configurations are scanned before you run them, using 11 heuristic patterns plus an MCP version-pin check. Workspace admins can also block an MCP server for the org or one user. | Not specifically covered in our source research. |
| Blocking / enforcement | Yes. Workspace owners and admins set observe, advisory, or enforce policy. Enforce denies matching tool calls on Claude Code and Codex PreToolUse hooks. The Sentinel Chrome extension pauses or blocks high-risk browser sends and can hold a send after redacting live secrets. | Governance and policy controls are part of the platform. |
| Individual use | Free for up to 3 people, and Pro for one person at $8/month. Team workspaces add owner/admin roles, org baselines, stricter member overrides and a control plane. | None. Enterprise platform sale. |
| Deployment | Local collector plus a workspace dashboard. Apple and Windows MDM. Sentinel Chrome extension for browser AI chats. Licensed self-hosted control plane for teams that need it on their own infrastructure. | Enterprise deployment. |
| Source / licence | AGPL-3.0 for the local CLI and collector; the multi-user control plane is proprietary. | Commercial, not open source. |
| Pricing | Free for up to 3 people. Pro $8/month for one person. Team $20 per developer and $5 per browser seat a month, billed yearly. | Enterprise custom quote, no public price. |
Zenity in numbers
As reported in our source research. Some figures are estimates.
- Funding
- Reported to have raised more than $100M; some funding figures in this space are estimates
- Focus
- Agent governance
Where Zenity does more
- Governance and policy over many agent types across an organisation, beyond coding-assistant hooks.
- Well funded, with more than $100M reported raised.
- Built for a security organisation's process, not a single developer's curiosity.
Where Beam differs
- Beam is a local record of what a coding agent did, readable without a governance programme around it.
- Beam includes a pre-run scan for skill files and MCP configurations.
- Beam sends no telemetry by default and redacts known credential formats before writing.
Beam’s current gaps
- Enforce is hook-based: a native deny is wired for Claude Code and Codex PreToolUse. Cursor, Copilot CLI and Gemini currently get a deny note, not a verified block.
- Missing, unreadable or expired cached policy allows the action. Beam is not a fail-closed kernel sandbox or an in-silicon watchdog.
- Scanning is heuristic pattern matching. It produces false positives, misses novel phrasing, and is not a guarantee of safety.
- There is no SOC 2 report and no default SIEM forwarder. Kernel isolation like OpenShell remains a different layer.
Which one fits
If your problem is governing agents across an organisation, Zenity is in that category and Beam is not. Beam is the smaller, earlier tool for seeing what one agent actually did.
FAQ
Does Beam do agent governance?
Not in Zenity's sense. Beam workspace owners and admins set observe, advisory, or enforce policy for coding agents and Sentinel browser checks. That is endpoint policy, not an enterprise governance platform over every agent type.
Can they be used together?
Our source research does not describe an integration between them, so treat that as untested.
See how Beam works
Beam is an early, local-first prototype. Read what it actually does today before comparing it further.