> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zenable.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Plans and Usage

> Compare Zenable's Free, Pro, and Enterprise plans and learn how usage, seats, and billing work.

## Plans Overview

<Tabs>
  <Tab title="Free" icon="gift">
    The Free plan is designed for individual developers getting started.

    * 2-Click Setup
    * Automated PR Summaries
    * Documentation
    * API Access

    <Info>
      [Get started for free](https://zenable.io/github?utm_source=docs\&utm_medium=web) — no credit card required.
    </Info>
  </Tab>

  <Tab title="Professional" icon="bolt">
    The Professional plan is for teams that need guardrails, custom requirements, and higher limits.

    * Everything in Free
    * Team Management
    * Custom Guardrails for AI IDEs
    * PR Guardrails (custom requirements)
    * Ensure AI Follows Your Requirements
    * Onboarding Support
    * Training Videos

    <Info>
      [Start a 14-day free trial](https://zenable.app?trial=true\&utm_source=docs\&utm_medium=web) — no credit card required.
    </Info>
  </Tab>

  <Tab title="Enterprise" icon="building">
    Enterprise is for organizations with 100+ developers that need dedicated infrastructure, custom terms, and higher limits.

    * Everything in Professional
    * Dedicated Runtime Environment
    * Dedicated Customer Success Manager
    * Custom Branding
    * Negotiable Terms of Service

    <Info>
      [Contact us](mailto:hello@zenable.io?subject=Zenable%20Enterprise) to discuss Enterprise pricing.
    </Info>
  </Tab>
</Tabs>

For a side-by-side plan comparison, see the [Pricing page](https://zenable.io/pricing?utm_source=docs\&utm_medium=web).

## Usage Limits

| | Free | Professional | Enterprise |
| - | - | - | - |
| Zenable Credits | 5,000/week (per seat) | 200,000/week (per seat) | 800,000/week (per seat) |

## How Reviews Work

<Tabs>
  <Tab title="Coding Agents" icon="robot">
    AI-powered reviews consume credits each time a file is reviewed. Coding-agent checks and PR/MR reviews share one per-seat credit pool. Guardrails (deterministic reviews and static analysis) have unlimited usage but are subject to capacity-based rate limiting and abuse prevention.

    <Steps>
      <Step title="Agentic IDE writes code">
        An agentic IDE writes code using Claude Code, Cursor, VS Code, or any [supported IDE](/integrations/mcp/getting-started#supported-ides).
      </Step>

      <Step title="Changes queued">
        Zenable identifies files that changed between the start and end of the agentic IDE's work and queues them for review.
      </Step>

      <Step title="Review runs">
        Files matching your [skip patterns](https://www.zenable.app/settings?utm_source=docs\&utm_medium=web) are removed from the queue. The remaining files are reviewed.

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

      <Step title="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.
      </Step>

      <Step title="Agentic IDE stops">
        If the agentic IDE makes no additional changes, nothing additional is reviewed, and it stops.
      </Step>
    </Steps>

    ### 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](https://www.zenable.app/settings?utm_source=docs\&utm_medium=web).

    #### 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.
  </Tab>

  <Tab title="Chat & MCP Tools" icon="comments">
    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 weekly per-seat Zenable Credits pool** as coding-agent conformance
    checks and PR/MR bot reviews.

    ### Credit Cost Per Tool Call

    | Tool | Credits | Direction |
    | - | - | - |
    | `get_requirements` | **10** | Read |
    | `get_guardrails` | **10** | Read |
    | `get_scopes` | **10** | Read |
    | `get_findings` | **10** | Read |
    | `get_agent_feedback` | **10** | Read |
    | `get_human_feedback` | **10** | Read |
    | `create_scope` | **10** | Write |
    | `reinstate_prior_guardrail_version` | **10** | Write |
    | `create_requirement` | **25** | Write |
    | `regenerate_guardrail` | **550** | Write |

    <Note>
      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.
    </Note>

    ### Guardrail Regeneration

    Running a guardrail free and unlimited on all plans; generating a guardrail costs 550 credits.

    | Action | Credits |
    | - | - |
    | Enforcing a guardrail (CLI, hooks, IDE, PR reviews) | **0** — unlimited on every plan, including Free |
    | Generating a new guardrail version — `regenerate_guardrail`, **Regenerate now** on the guardrail page, or automatic self-healing after a runtime failure | **550** per regeneration |

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

  <Tab title="PR Bot Reviews" icon="code-pull-request">
    PR Bot Reviews are triggered automatically when a pull/merge request is opened on GitHub or GitLab. They are priced **per reviewed file**, from the same credit rate card as every other AI review — small PRs cost little, and a PR whose files are all skipped costs nothing.

    <Note>
      Reviews are billed to the PR author's per-seat credit pool. The author's
      GitHub or GitLab account must be linked to their Zenable user (Settings →
      User Management); on paid plans, unlinked authors share a per-installation
      pool with one seat's worth of credits, and on the Free plan unlinked
      authors are prompted to link before reviews run.
    </Note>

    <Note>
      As of September 6, 2026, all usage reporting is credit-based. Before that
      date, usage plans used a mix of credits and PR/MR review counts. For usage
      details from before September 6, 2026, contact
      [hello@zenable.io](mailto:hello@zenable.io).
    </Note>

    <Steps>
      <Step title="PR opened">
        On GitHub or GitLab, a pull/merge request is created.
      </Step>

      <Step title="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](https://www.zenable.app/settings?utm_source=docs\&utm_medium=web).
      </Step>

      <Step title="Credits charged per reviewed file">
        Each reviewed file costs **25 credits**, scaled by the same
        [jumbo multiplier](#large-files) as other AI reviews (measured on the
        file's content plus its diff). Skipped files — skip patterns, the
        per-PR file cap, oversized files — cost nothing.

        <Note>
          If a PR is closed and reopened, or a review is re-requested via a `/zenable` comment, the new review is charged again for the files it reviews.
        </Note>
      </Step>
    </Steps>

    ### 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 | 300,000 characters | Files whose combined content and diff exceed the jumbo ceiling are skipped. The review completes for the remaining files and a notice is added suggesting to break the file into smaller pieces. |

    <Warning>
      These limits are subject to change.
    </Warning>

    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](https://www.zenable.app/settings?utm_source=docs\&utm_medium=web).
  </Tab>
</Tabs>

## Credit Usage Examples

<AccordionGroup>
  <Accordion title="MCP Server — 3 files" icon="server">
    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**
  </Accordion>

  <Accordion title="CLI — 10 files, 1 excluded" icon="terminal">
    `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**
  </Accordion>

  <Accordion title="Hook — 5 changed, 2 excluded" icon="code-commit">
    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**
  </Accordion>

  <Accordion title="Multi-branch — 2 branches, overlapping files" icon="code-branch">
    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**
  </Accordion>

  <Accordion title="Chat — search and create a requirement" icon="comments">
    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**
  </Accordion>

  <Accordion title="PR review — 6 files, 1 skipped" icon="code-pull-request">
    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 the PR author's seat
  </Accordion>

  <Accordion title="MCP — regenerate a guardrail from your IDE" icon="wand-magic-sparkles">
    Your AI coding assistant identifies a flaky Semgrep guardrail and calls the
    MCP server to regenerate it with your feedback.

    * `get_guardrails`: 10 credits
    * `regenerate_guardrail`: 550 credits
    * **Total: 560 credits**

    Every run of the regenerated guardrail afterward — in your hook, the CLI,
    or a PR review — costs nothing.
  </Accordion>
</AccordionGroup>

## How Credits Refresh

<Tabs>
  <Tab title="Coding Agents" icon="robot">
    If you exhaust your AI review credits, AI-powered reviews pause until your next weekly credit reset. Guardrails and static checks continue to run.
  </Tab>

  <Tab title="PR Bot Reviews" icon="code-pull-request">
    If a PR's estimated cost exceeds the author's remaining weekly credits, Zenable leaves a comment on the PR indicating that the limit has been reached and the review was not performed — nothing is charged for a withheld review.
  </Tab>
</Tabs>

| Cadence | Applies to | Resets at |
| - | - | - |
| Weekly | Zenable Credits (all surfaces) | Monday 00:00 UTC |

<Tip>
  Track your credit usage on the [billing dashboard](https://www.zenable.app/billing?utm_source=docs\&utm_medium=plans-and-usage) — per-seat usage, PR/MR review activity, and weekly trends.
</Tip>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.