Plans and Usage - Zenable Governance Platform

Plans Overview

Free
Professional
Enterprise

The Free plan is designed for individual developers getting started.

2-Click Setup
Automated PR Summaries
Documentation
API Access

Get started for free — no credit card required.

For a side-by-side plan comparison, see the Pricing page.

Usage Limits

	Free	Professional	Enterprise
PR Reviews	50/week (per account)	1,400/week (per account)	Negotiable
Agentic Code Review Credits	1,000/day (per seat)	10,000/day (per seat)	100,000/day (per seat)

How Reviews Work

Coding Agents
Chat & MCP Tools
PR Bot Reviews

AI-powered reviews consume credits each time a file is reviewed, which is why the credit limits are substantially higher than PR reviews. Guardrails (deterministic reviews and static analysis) have unlimited usage but are subject to capacity-based rate limiting and abuse prevention.

Agentic IDE writes code

An agentic IDE writes code using Claude Code, Cursor, VS Code, or any supported IDE.

Changes queued

Zenable identifies files that changed between the start and end of the agentic IDE’s work and queues them for review.

Review runs

Files matching your skip patterns are removed from the queue. The remaining files are reviewed.

If multiple branches were touched during that agentic loop, each is reviewed independently and findings are passed back to the agentic IDE per branch.

Agentic IDE remediates

At the end of the agentic IDE’s workload, if there are findings from the review, those are passed back and work continues. Only additional file changes after this point are re-reviewed.

Agentic IDE stops

If the agentic IDE makes no additional changes, nothing additional is reviewed, and it stops.

Credit Cost Per File

Each AI-model review consumes credits based on your model tier and the file size; Guardrails and static checks are free.

Check Type	Credits
Guardrails & static checks	0 (unlimited)
Standard AI model	10 per file
Premium AI model	25 per file

Configure your AI model tier in company settings.

Large files

Most files fit a single 30,000-character review. Larger files are still reviewed in full as jumbo files — the review scales to the file, and so does the credit cost. A large file gets a deeper, more context-heavy review, so jumbo files are priced at 2× their size.A jumbo file is measured in 30,000-character chunks, and the cost is 2× that chunk count applied to your per-file rate above:

File size	Review size	Credit cost
up to 30,000 chars	1× (standard)	base (10 or 25)
up to 60,000 chars	2×	4× base
up to 90,000 chars	3×	6× base
…	…	…
up to 300,000 chars	10×	20× base

Jumbo reviews are itemized on the usage dashboard, so you can see exactly which files were jumbo and at what multiple. The largest reviewable file is 300,000 characters (10×); larger files are noted in the review summary. These limits may change.

The in-app chat assistant and the Zenable MCP server expose the same set of tools for managing requirements, guardrails, and scopes. Read tools cost a flat 10 credits; write tools cost more. All of these tools deduct from the same daily per-user Agentic Code Review Credits pool as coding-agent conformance checks.

Credit Cost Per Tool Call

Tool	Credits	Direction
`search_marketplace_requirements`	10	Read
`search_requirements`	10	Read
`search_guardrails`	10	Read
`list_scopes`	10	Read
`create_scope`	10	Write
`reinstate_prior_guardrail_version`	10	Write
`create_requirement`	25	Write
`regenerate_guardrail`	25	Write

Write tools require a Professional plan or an active trial. Free-tier users without a trial can use the read tools but not the write tools.

The usage dashboard breaks activity out so you can see how much of your daily pool went to coding-agent scans vs. chat/MCP requirement management, even though they share the same counter.

PR Bot Reviews are triggered automatically when a pull/merge request is opened on GitHub or GitLab. They are counted per PR, not per file.

PR opened

On GitHub or GitLab, a pull/merge request is created.

Zenable explores and reviews

Codebase explore agents research impact and gather context. Branch patterns can be excluded (e.g. Dependabot and other automated maintenance PRs) from reviews automatically in company settings.

1 review counted

Each PR review, regardless of file count or updates, counts as 1.

If a PR is closed and reopened, or a review is re-requested via a /zenable comment, it counts as another review.

Review Limits

Limit	Value	Behavior
Files per PR	150	Files beyond the limit are skipped. The review completes for the remaining files and a notice is added suggesting to split the PR.
File size	400KB	Files where the combined content and patch exceed 400KB are skipped. The review completes for the remaining files and a notice is added suggesting to break the file into smaller pieces.

These limits are subject to change.

Skipped files are reported in a collapsed section of the review summary so you know exactly what was and wasn’t reviewed.Branches or files can be excluded from review using skip patterns (e.g. Dependabot PRs, lock files) on the settings page.

Credit Usage Examples

MCP Server — 3 files

Your IDE’s MCP server sends a conformance check with 3 files. No exclusions match.

Standard: 10 × 3 = 30 credits
Premium: 25 × 3 = 75 credits

CLI — 10 files, 1 excluded

zenable check "**/*.py" finds 10 files. Your config excludes generated.py, so 9 are checked. You have 25 guardrails that apply to all .py files.

Guardrails: 25 × 0 = 0 credits
Standard: 10 × 9 = 90 credits
Premium: 25 × 9 = 225 credits

Hook — 5 changed, 2 excluded

A hook runs on commit with 5 changed files. Two match exclusion patterns, so 3 are reviewed.

Standard: 10 × 3 = 30 credits
Premium: 25 × 3 = 75 credits

Multi-branch — 2 branches, overlapping files

Your agentic IDE touches files across two branches in one session. On feat/a, it changes auth.py, utils.py, and config.py. It then switches to feat/b and changes utils.py and api.py. Even though utils.py was touched on both branches, each branch is reviewed independently — 3 files on feat/a, 2 files on feat/b.

Standard: 10 × 5 = 50 credits
Premium: 25 × 5 = 125 credits

Chat — search and create a requirement

You ask the in-app chat assistant to find an existing requirement and, not finding a match, it creates a new one on your behalf.

search_requirements: 10 credits
create_requirement: 25 credits
Total: 35 credits

MCP — regenerate a guardrail from your IDE

Your AI coding assistant identifies a flaky Semgrep guardrail and calls the MCP server to regenerate it with your feedback.

search_guardrails: 10 credits
regenerate_guardrail: 25 credits
Total: 35 credits

How Credits Refresh

Coding Agents
PR Bot Reviews

If you exhaust your AI review credits, AI-powered reviews pause until your next credit reset. Guardrails and static checks continue to run.

Cadence	Resets at
Daily	00:00 UTC
Weekly	Monday 00:00 UTC
Monthly	1st 00:00 UTC

A credit usage tracking dashboard is coming soon. Subscribe to this feature request to be notified when it goes live.

​Plans Overview

​Usage Limits

​How Reviews Work

​Credit Cost Per File

​Large files

​Credit Cost Per Tool Call

​Review Limits

​Credit Usage Examples

​How Credits Refresh

Plans Overview

Usage Limits

How Reviews Work

Credit Cost Per File

Large files

Credit Cost Per Tool Call

Review Limits

Credit Usage Examples

How Credits Refresh