Skip to main content

​
Plans Overview

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

Default weekly limits per seat are shown below. Enterprise allowances can follow negotiated terms. Plus stops AI work if your endpoint fails. On Enterprise, a company administrator can require BYOK across all workspaces. BYOK requests do not automatically fall back to another model or managed inference. See Bring Your Own Key (BYOK).

​
How Reviews Work

AI-powered reviews consume credits each time a file is reviewed. Coding-agent checks and PR/MR reviews share one per-seat credit pool. Verifier rules (deterministic reviews and static analysis) have unlimited usage but are subject to capacity-based rate limiting and abuse prevention.
1

Agentic IDE writes code

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

Changes queued

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

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.
4

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.
5

Agentic IDE stops

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

​
Credit Cost Per File

Each AI review consumes credits for the model and credentials that complete the file review, multiplied by the file size below. BYOK means using your own API key.Decision-model routing is Zenable-managed. BYOK reviews currently skip Jev.Verifier rules and static checks are free. For Zenable-managed inference, if a fallback model completes the review, its model and credential rate applies. BYOK requests do not automatically switch to a fallback model. For example, a Zenable-managed Premium model costs 25 credits per file, including a review started in Fast mode.Configure your provider and models in Settings → BYOK.

​
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: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.

​
Credit Usage Examples

The AI review examples below use Zenable-managed models. Reviews using your own API key use the BYOK rates above.
Your IDE’s MCP server sends a conformance check with 3 files. No exclusions match.
  • Fast: 10 × 3 = 30 credits
  • Premium: 25 × 3 = 75 credits
zenable check "**/*.py" finds 10 files. Your config excludes generated.py, so 9 are checked. You have 25 verifier rules that apply to all .py files.
  • Verifier rules: 25 × 0 = 0 credits
  • Fast: 10 × 9 = 90 credits
  • Premium: 25 × 9 = 225 credits
A hook runs on commit with 5 changed files. Two match exclusion patterns, so 3 are reviewed.
  • Fast: 10 × 3 = 30 credits
  • Premium: 25 × 3 = 75 credits
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.
  • Fast: 10 × 5 = 50 credits
  • Premium: 25 × 5 = 125 credits
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.
  • get_requirements: 10 credits
  • create_requirement: 25 credits
  • Total: 35 credits
You open a PR with 6 changed files. One matches your skip patterns, so 5 are reviewed, all under 30,000 characters.
  • 25 × 5 = 125 credits, billed to your seat as the person who triggered the opening review
If someone else requests a later review, that review uses their allowance.
Your AI coding assistant identifies a flaky Semgrep verifier rule and calls the MCP server to regenerate it with your feedback.
  • get_verifier_rules: 10 credits
  • regenerate_verifier_rule: 550 credits
  • Total: 560 credits
Every run of the regenerated verifier rule afterward — in your hook, the CLI, or a PR review — costs nothing.

​
How Credits Refresh

If you exhaust your AI review credits, AI-powered reviews pause until your next weekly credit reset. Verifier rules and static checks continue to run.
Billing’s PR/MR review activity counts served reviews. A recorded request can exist without a completed review or a credit charge; free verifier rule checks can also record activity with zero credits. Compare matching date ranges: the current allowance meter follows the current reset period even when you view a past week’s activity.
Track your credit usage on the billing dashboard — per-seat usage, PR/MR review activity, and weekly trends.