Skip to main content
Zenable scales from single repo to entire organization. Requirements are composable: layer them by team, product, environment, or any combination.
Data Privacy: We never retain or train on your code. Learn more

Deployment Levels

Per-Repository

Project-specific requirements.
uvx zenable-mcp install
Setup guide →

Individual Developer

Install for all repos on your system.
uvx zenable-mcp install --global

Team-Wide

Add PR reviews, pre-commit hooks, and shared standards.

Organization-Wide

Set up your requirements once in our management console, and enforce them everywhere:
  • Architecture decisions
  • Security standards
  • Compliance requirements (HIPAA, PCI-DSS, SOC2)
  • Coding standards
  • Product or customer requirements
Learn about custom policies →

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. Mix and match scopes for precise control. For example: stricter security for payment repositories, or TypeScript standards only for frontend teams.

Rollout Strategies

Day 1: Install GitHub/GitLab PR reviewsWeek 1: Developers run uvx zenable-mcp installOngoing: Add custom requirements as needed
Week 1: PR reviews on all reposMonth 1: Upload company requirementsOngoing: Track metrics, refine

Pricing

Get Started