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

# Deployment & Adoption

> Roll out quality guardrails across your team: from single developer to entire organization

Zenable scales from single repo to entire organization. Requirements are composable: layer them by team, product, environment, or any combination.

<Note>
  **Data Privacy**: We never retain or train on your code. [Learn more](https://www.zenable.io/security)
</Note>

## Deployment Levels

### Individual Developer

Install for all projects on your system (default).

```bash theme={null}
zenable install
```

[Setup guide →](/integrations/mcp/getting-started)

### Per-Repository

Project-specific installation.

```bash theme={null}
zenable install --project
```

### Team-Wide

Add [PR reviews](/integrations/vcs-reviewers/github), [pre-commit hooks](/integrations/pre-commit/getting-started), and shared standards.

### Organization-Wide

Set up your requirements once in our [management console](https://www.zenable.app), and enforce them everywhere:

* Architecture decisions
* Security standards
* Compliance requirements (HIPAA, PCI-DSS, SOC2)
* Coding standards
* Product or customer requirements

[Learn about custom policies →](/use-cases/policy-as-code)

## Requirement Scopes

Target requirements precisely where they matter. Common scopes include:

* **Global**: Organization-wide (can be inherited, blocked, or force-inherited)
* **Repository**: Apply to specific repos (`frontend-app`, `payment-service`)
* **Team**: Target by team ownership (platform, mobile, backend)
* **File types**: Language-specific standards (`.py` → Python style, `.tsx` → React patterns)
* **Path patterns**: Target directories (`src/api/*` → API standards, `tests/*` → testing rules)

And more! See all scoping options in the [management console](https://www.zenable.app).

Mix and match scopes for precise control. For example: stricter security for payment repositories, or TypeScript standards only for frontend teams.

## Rollout Strategies

<AccordionGroup>
  <Accordion title="Start Small (Recommended)">
    **Week 1:** Install in 1-3 IDEs, measure bugs caught

    **Week 2-4:** Add PR reviews + pre-commit hooks

    **Month 2+:** Add company-wide requirements
  </Accordion>

  <Accordion title="Quick Team Deploy">
    **Day 1:** Install [GitHub](/integrations/vcs-reviewers/github)/[GitLab](/integrations/vcs-reviewers/gitlab) PR reviews

    **Week 1:** Developers run `zenable install`

    **Ongoing:** Add custom requirements as needed
  </Accordion>

  <Accordion title="Enterprise Deploy">
    **Week 1:** PR reviews on all repos

    **Month 1:** Upload company requirements

    **Ongoing:** Track metrics, refine
  </Accordion>
</AccordionGroup>

## Pricing

<CardGroup cols={3}>
  <Card title="Free" icon="gift" href="/integrations/mcp/getting-started">
    Built-in checks, IDE + PR reviews
  </Card>

  <Card title="Professional" icon="rocket" href="https://zenable.io/pricing">
    Custom guardrails, 10x limits
  </Card>

  <Card title="Enterprise" icon="building" href="https://zenable.io/pricing">
    Unlimited, dedicated environment
  </Card>
</CardGroup>

## Get Started

<CardGroup cols={3}>
  <Card title="Install Now" icon="terminal" href="/integrations/mcp/getting-started">
    30 second setup
  </Card>

  <Card title="Schedule Demo" icon="calendar" href="https://zenable.io/schedule-demo">
    See team deployment
  </Card>

  <Card title="Custom Policies" icon="shield" href="/use-cases/policy-as-code">
    Configure requirements
  </Card>
</CardGroup>