Plans & Credits
VULQN uses review credits so teams can align cost with pull request volume.
There are two credit types:
| Credit type | Used for |
|---|---|
| Normal review credits | Standard AI pull request reviews. |
| Peer review credits | Optional second-pass peer validation on repositories where peer review is enabled. |
Trial
Every account starts with a trial:
| Trial length | Included normal reviews | Included peer reviews |
|---|---|---|
| 15 days | 20 | 5 |
The trial is designed to test VULQN on real PRs: review quality, inline comment ergonomics, dashboard usefulness, and whether developers adopt the workflow naturally.
Plans
| Plan | Price | Normal reviews | Peer reviews | Best fit |
|---|---|---|---|---|
| Starter | $29.99/month | 100/month | 0/month | Small teams or focused repository coverage. |
| Team | $129.99/month | 500/month | 0/month | Teams with steady PR volume across several repositories. |
| Scale | $199.99/month | 1,000/month | 0/month | Larger teams that want broad standard review coverage. |
| Pro | $449.99/month | 500/month | 500/month | Teams that want peer review on high-risk repositories. |
| Enterprise | Custom | Custom | Custom | Dedicated support, SSO, custom contracts, and custom review limits. |
All listed plans include source-control integrations, inline comments, and PR summaries. Team, Scale, and Pro are positioned for workspaces that also need broader team management.
How normal credits are used
A new PR review uses 1 normal credit unless the tenant is billing-exempt.
When new commits are pushed to the same PR, VULQN automatically re-reviews while the PR remains inside its included re-review cycle. After a PR has been reviewed 5 times, VULQN pauses automatic reviews and posts a command notice.
At that point, you choose what happens next:
!vulqn reviewqueues an incremental review and uses a review credit.!vulqn full reviewqueues a full review and uses a review credit.!vulqn resolvecloses open VULQN findings without spending another review credit.
This pause behavior keeps long-running PRs from quietly burning credits and helps developers decide when another automated pass is actually useful.
How peer credits are used
Peer review is optional and enabled per repository in Settings.
When enabled, VULQN runs an additional validation pass for that repository’s reviews. Peer review is most valuable when the cost of a missed issue is high:
- Authentication and authorization.
- Payments and billing.
- Data migrations.
- Security-sensitive services.
- Critical shared libraries.
- High-volume repositories where review consistency matters.
Peer review has two advantages:
- It can challenge or refine the first-pass findings before developers see the final output.
- It can add findings the first pass missed, improving coverage on important PRs.
If no peer credits are available, VULQN falls back to a standard review and posts a warning on the PR. Normal review coverage continues as long as normal credits are available.
Credit pools
VULQN uses subscription credits first. When subscription credits are exhausted, it uses the oldest non-expired add-on credits of the same type.
Normal and peer credits are separate. A peer review does not consume normal credits as a peer credit, and normal review capacity does not automatically grant peer review capacity.
Billing page
Admins can open Settings -> Billing to:
- See the current plan and renewal date.
- Track normal and peer credit usage.
- View active add-ons and their expiry dates.
- Switch plans.
- Buy add-on credits.
- Open the Stripe billing portal.
Billing is admin-only. Managers and viewers do not have billing access.
When credits run out
If the workspace has no remaining credits for the review type VULQN needs, VULQN skips the review and comments on the PR with the next step.
If the subscription is inactive, expired, cancelled, or past due, VULQN skips new reviews and asks the team to renew or update billing.
Unexpired add-on credits can keep review activity available even when the workspace is not on an active paid subscription.