Fair Usage Limits Policy

What this policy covers

Inkspect is designed for code reviews within a team’s normal development workflow. Fair usage keeps shared processing capacity available and makes resource consumption understandable.

Cloud and Cloud BYOK share Inkspect’s hosted infrastructure, so both are subject to operational limits. Self-hosted instances use your infrastructure and your provider’s limits instead of Inkspect Cloud capacity limits.

Seats and shared usage credit

Cloud includes $10 of AI usage credit per paid seat each month. These contributions form one shared organization balance, so your team can use the allowance where the review work happens. Five Cloud seats contribute $50 per month.

This balance pays for AI work inside the Inkspect review service. It is not transferable provider credit or a separate model provider account. Paid seats cover developers enabled for reviews; read-only viewers and billing administrators are free. Seat changes show the associated billing adjustment before confirmation.

Annual billing reduces the seat subscription price by 20%. The included credit remains a monthly allowance; it is not made available as a full year’s balance upfront. See your subscription settings for renewal timing and treatment of unused credit.

Why reviews use different amounts

A review may read a diff, retrieve related code, investigate dependencies, and check its reasoning. Larger changes and deeper investigations can consume more AI resources than a small, local change. A review can consume resources even when it returns no findings.

The included balance is a usage allowance, not a guaranteed number of reviews. A subscription does not promise unlimited AI consumption or unlimited concurrent processing.

• Change size: the amount of code and context that needs to be read.
• Investigation depth: additional searches and model calls required to understand the change.
• New review requests: reviewing another revision or intentionally rerunning a review can consume additional usage.

Limits that protect shared capacity

Cloud processing may be bounded by request rate, concurrent reviews, review size, context size, or execution time. These controls are separate from the available AI balance: having credit does not remove capacity limits.

Your plan and review status show applicable thresholds and explain when a limit affects a review. Check these limits when configuring your team’s workflow.

• Request or concurrency limit: wait for capacity or an active review to finish before retrying.
• Change or context limit: split a large change into smaller pull requests or narrow the review scope.
• Time or investigation limit: check which parts of the review completed before requesting further work.
• Provider limit: check your provider quota or billing settings when using your own key.

When a budget runs out

New reviews pause when the available organization budget is exhausted. An annual subscription does not bypass a monthly allowance or a configured spending limit.

Additional usage must be enabled by an authorized organization administrator after its rate and spending controls have been presented. Automatic top-ups require explicit opt-in. Review the displayed rate before enabling additional usage.

If a review reaches its own budget or processing limit, its result should identify the incomplete scope. A partial review must not be presented as a complete review. Administrators can wait for the allowance to renew or enable additional usage under the terms shown in the app.

Cloud BYOK

With Cloud BYOK, the seat subscription covers the hosted platform. You supply your own model provider key and pay the provider directly. No Inkspect AI usage credit is included.

Your provider’s charges, quotas, and rate limits apply alongside Inkspect’s Cloud operational limits. The annual seat discount does not reduce provider charges. Provider spending controls should be configured in your own provider account.

Self-hosted deployments

Self-hosted software has no Inkspect subscription fee. Your organization pays for infrastructure and AI consumption and manages its own processing capacity, budgets, access, and updates.

Inkspect Cloud usage allowances and capacity limits do not apply to reviews processed entirely on your own instance. Your model provider and connected services can still impose their own limits.

Keep usage within the intended workflow

Do not bypass limits by rotating accounts or keys, flood the service with repeated requests, share seats to evade billing, or use the review service as a general-purpose AI proxy. Review only code your organization is authorized to access and process.

Usage that threatens availability may require throttling or a temporary pause. Any restriction should explain the affected scope and the steps needed to resume normal reviews. If an unexpected limit affects legitimate work, record the review reference and ask your organization administrator to investigate.

Changes and related documentation

The displayed update date identifies the current version of this policy. Review your plan-specific limits and billing terms when activating paid service or enabling additional usage.