One preflight check is one risk analysis of a pull request. Browsing previous results or viewing receipts does not count. Only new PR analyses count toward your limit.
You can still browse all previously generated analyses and receipts. New preflight checks require upgrading to Team or waiting for the next billing cycle.
Enforcement
When Airlock blocks a high-risk PR, authorized team members can override the block by providing a written justification scoped to the specific commit SHA. Every override produces a tamper-evident receipt with a cryptographic hash chain.
Yes. Team plans include custom policy rules: define protected zones, set risk thresholds, configure which teams can override, and specify which file patterns trigger mandatory review.
Integration
Run airlock --mcp to start Airlock as an MCP server. Claude Code, Cursor, and other MCP clients can call Airlock tools directly to run preflight checks on any PR.
Enterprise
Yes. Enterprise customers can run Airlock on their own infrastructure with their own Anthropic API keys. The entire system is a single Rust binary with optional Postgres for caching.
Enterprise includes SOC-2 compliance, GDPR compliance, SSO via SAML/OIDC, and full audit logging. All plans include automatic secret redaction.