Zenity
changelog-20261017-45ad1d16 commercialThe section your link pointed to isn't on Zenity's page any more, so we've brought you to the top.
Zenity discovers, secures and governs enterprise AI agents from buildtime to runtime across SaaSSaaSSoftware delivered over the internet and run on the provider's infrastructure, so the buyer pays a subscription instead of installing or operating anything locally., endpoint and cloud.
@id("forbid_push_without_fresh_passing_tests")
forbid (
principal,
action == Repo::Action::"GitPush",
resource
) unless temporal {
!Repo::Action::"RunTests"::response{
input.repo: context.input.repo,
output.passed: false
} since within 15m
Repo::Action::"RunTests"::response{
input.repo: context.input.repo,
output.passed: true
}
};
Summary
Zenity is a commercial ai-security tool that discovers, secures and governs enterprise AI agents from buildtime to runtime across SaaS, endpoint, and cloud. It is designed for practitioners concerned with agentic-ai-security and ai-governance. Its documentation places it alongside other tools in the ai-security category. It launched in 2021.
Zenity discovers, secures and governs enterprise AI agents from buildtime to runtime across SaaS, endpoint and cloud.
How Zenity helps
Which AI agents and copilots are actually running across our SaaS, endpoint, and cloud environments?
builds an inventory and activity graph by connecting to each platform's agent stack, covering tools like GitHub Copilot, OpenAI Codex, and Microsoft Foundry with what they've done and what they can reach
Which tool calls made by our agents were reads versus actions that changed something?
classifies every call with a system taint of read or a mutative type such as write, update, delete, or execute, so rules can be written against what an action does rather than its name
Would a new rule have blocked or flagged last week's agent activity before we turn it on?
runs the draft rule against recent production activity on command and shows what it would have caught, before it applies in real time
Is a given finding a real problem or noise?
Blue Agent triages each new finding in suggest mode and returns a verdict of benign true positive, false positive, or true positive, with reasoning, confidence level, and the full trace attached
Which of our rules block in real time and which only flag after the fact?
every taint in the boundaries manager is labeled Prevent or Detect, so the enforcement mode is visible at a glance rather than discovered during an incident
Languages
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
Five scores for Zenity, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail Zenity puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Website history
zenity.io, every changeZenity's home page and 39 more pages as they looked each month from October 2021 to October 2026: 49 renders, 5 changes of tagline or palette. Step through them, play them, or put any two months side by side.
Website history is included with Researcher and Business.
See plans → Already subscribed? Sign in →← → or h l a month · Shift a year · [ ] previous / next change · Space play · 1 2 3 page · T whole page · C compare · F full size
← → or h l the right month · Shift the left · S swap · W wipe · T whole page · Esc back
Rebranding timeline
Dates bound when a change appeared between captures. Possible rebrands are AI suggestions; a redesign alone does not establish a rebrand.
Coverage
Missing something? Tell us
What Zenity connects to, runs on and detects, read from its release notes and docs. So far: 2 new integrations.
2 changes, tracked since Oct 28, 2026.
-
Seen Oct 282026
new Inline enforcement on Claude Code, Cowork, Microsoft Copilot Studio, Azure Foundry
Today, Boundaries enforce inline through hooks on platforms such as Claude Code and Cowork, Microsoft Copilot Studio, Azure Foundry, and others.
-
Seen Oct 282026
new Detection-only support for ChatGPT and Gemini
Some platforms, like ChatGPT and Gemini, only support detection today.
Coding agents 1
Chat & assistant apps 2
Model providers & gateways 2
Chat & collaboration 1
Nothing first seen in this window. That doesn't mean Zenity shipped nothing, only that we found no record of it.
How we count
Read from 2 of 29 release notes and docs updates we hold for Zenity. "First seen" is the earliest note that names something; "last" is the latest. Our history may start partway through Zenity's life, so an old integration can show a recent first-seen date.
Each change counts once: "added 40 checks" is one line, so the numbers measure how often coverage moves, not how big the catalogue is or how well it detects.
Releases
29 entries
No entries match these filters.
- October 20268
- September 20264
- August 20261
- July 20261
- June 20261
- May 20261
- March 20262
- January 20261
- December 20252
- November 20252
- September 20252
- August 20251
- May 20251
- April 20251
- September 20241
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.
Choose a badge style and copy the code →