The verdict is free. You pay for the fix.

The audit is free and unlimited on every plan: connect a repo, every push, every pull request. You pay for corrections, one run per correction pass, priced per developer. Free for open source, always.

Showing monthly pricing.

Free
$0/forever

For side projects and open-source repos.

Get started
  • Unlimited audits and PR verdicts
  • 20 corrections per month
  • 2 repository setups per month
  • 2 repositories
  • 1 developer, invites on Pro
  • Context artifacts (AGENTS.md, codemap, conventions)
  • Community support
  • Priority support
Pro
$30/developer/month

For teams whose coding agents need context that keeps up.

  • Unlimited audits and PR verdicts
  • 30 corrections per developer per month
  • 3 repository setups per developer per month
  • Unlimited repositories
  • Unlimited team members
  • 14-day free trial
  • Context artifacts (AGENTS.md, codemap, conventions)
  • Correction PR on every approval
  • Priority email support
Max
$60/developer/month

For teams keeping context fresh across every repo.

  • Unlimited audits and PR verdicts
  • 60 corrections per developer per month
  • 8 repository setups per developer per month
  • Unlimited repositories
  • Unlimited team members
  • Context artifacts (AGENTS.md, codemap, conventions)
  • Correction PR on every approval
  • Priority email support
Enterprise
Custom

Need something custom? Let’s talk about what your team needs.

Talk to us
  • Everything in Max
  • Custom correction allowances
  • Dedicated support
  • Custom integrations

Open-source repositories get Max plan features for free, always, with an allowance of 30 corrections and 1 repository setup a month. Audits are unlimited everywhere. No credit card required.

Frequently Asked Questions

Audits and PR verdicts are free and unlimited on every plan. They check supported references in selected files and disclose gaps; they do not judge every claim in the repository. A correction run, which can propose edits or regenerate enabled managed outputs, uses the monthly allowance. Repository setup has a separate allowance.

Corrections are queued until your allowance renews, and audits keep running the whole time: you always know what is broken, even at zero remaining corrections. Nothing is ever charged beyond your plan unless an owner or admin turns pay-as-you-go on, and it is off by default.

It is off by default, so a busy month can never become a bill nobody asked for. An owner or admin turns it on under Settings, then Billing, in one of two modes: on demand, where only a run someone starts by hand may go past the allowance, or automatic, where any trigger may. Work past the allowance is priced per regenerated artifact at $0.50, not per run, so a run that rebuilds six artifacts adds $3.00. You set the monthly ceiling yourself, up to $100,000, and leaving it blank means no ceiling at all. The ceiling is measured against what a month has already spent, so the run that crosses it still finishes and the month can end slightly above your number. Every charged run posts a receipt on its pull request saying how many artifacts it regenerated and what that added.

On Pro and Max, yes: team members are unlimited and you pay per developer, so the allowance grows with the team. On Free the allowance is computed on one developer whatever the head count, and inviting teammates needs Pro.

Yes. Upgrade or downgrade whenever you want. When upgrading, you get immediate access. When downgrading, the change takes effect at the end of your billing cycle.

Yes. Public repositories on GitHub or GitLab get Max plan features for free, no credit card required, with an open-source allowance of 30 corrections a month, 1 repository setup a month and 2 corrections an hour. Audits are unlimited there like everywhere else. A paying customer that opens one of its repositories never drops below what it bought.

Kontrua reads repository contents to audit them and can send selected context to the model provider during correction runs. It stores findings, run metadata, and proposed outputs. See the privacy policy for the data flow and retention details.

Find out what your docs get wrong

Connect a repo to check supported command and path references. The result shows what passed, what broke, and what could not be checked.