Explainer
Security review priced per pull request, explained
Aevral prices its PR security review per organization, as a monthly allowance of pull-request reviews. On paid plans one pull request counts once per billing period, however often it is re-pushed. The free tier needs no card.
Tristan Roth,
Aevral prices its PR security review per organization, not per seat, as a monthly allowance of pull-request reviews. Free covers 25 private reviews a month.
Starter is $49 for 100 reviews a month, Pro is $199 for 500 reviews a month, Business is $999 for 3000 reviews a month, Scale is $1,999 for 6500 reviews a month.
On paid plans, a pull request counts as one review per billing period, however often it is re-pushed. Public repositories are free, 500 reviews per organization per month. Prices exclude VAT and other taxes.
The rest of this page is the plain version of that paragraph: what a review is, what each plan includes, what happens when the allowance runs out, and why the unit is the pull request and not the person.
What you are paying for
Picture a team of three where most pull requests are opened by coding agents. Nobody on the team is a security specialist.
Per-seat pricing would charge for the three people, and the agents that open most of the pull requests would not count at all. Aevral charges for the work instead: one security review of one pull request.
A review is what happens after the Aevral GitHub App is installed on a repository, live on install.
When a pull request is opened, reopened, or updated, Aevral reads the diff of the changed files, the most security-relevant in full, then posts an advisory Check on the head commit and, when there is a grounded finding, inline comments pinned to the added lines.
At most five findings per review, each with a suggested fix. It never blocks a merge.
What each plan includes
Free: $0 per org / month. 25 private pull-request reviews per month. Public repositories are free, 500 reviews per organization per month.
Starter: $49 per org / month for 100 PR reviews. Past the plan: $0.99 per extra PR review, only if the owner chose extras.
Pro: $199 per org / month for 500 PR reviews. Past the plan: $0.99 per extra PR review, only if the owner chose extras.
Business: $999 per org / month for 3000 PR reviews. Past the plan: $0.99 per extra PR review, only if the owner chose extras.
Plus a monthly export of the security reviews Aevral ran on your pull requests, with coverage and results, that may serve as supporting evidence for automated security testing in audits (for example ISO 27001 A.8.29, SOC 2 CC8.1), and EU-only processing when it is available (not live yet).
Scale: $1,999 per org / month for 6500 PR reviews. Past the plan: $0.99 per extra PR review, only if the owner chose extras. Everything in Business.
The paid plans are monthly allowances of the same review and differ by volume; Business also adds a monthly export of the security reviews Aevral ran on your pull requests, with coverage and results, that may serve as supporting evidence for automated security testing in audits (for example ISO 27001 A.8.29, SOC 2 CC8.1), and EU-only processing when it is available.
Scale is Business with more included reviews. Prices exclude VAT and other taxes.
What counts once, and what does not count
On paid plans, a PR review is one pull request per billing period. An agent that pushes to the same pull request ten times gets each push reviewed, and the pull request still counts once.
On Free and during the trial, a review is one pull request head (repository, pull request number, head commit): a new push is a new head, and the same head is never counted twice.
A review that is skipped or fails before posting is not counted. A posted review counts whether or not it found anything, because the work was done. Public repositories do not consume the private allowance.
Reviews are never counted as scans, and the whole-repo scan is a separate product with its own price list.
When the allowance runs out
The first time a paid organization goes past its plan, it gets 25% more PR reviews free, once.
After that, reviews pause at the plan's limit unless the owner turned extras on: $0.99 per extra PR review, only if the owner chose extras. A paused pull request gets a neutral Check saying why, so nothing fails silently.
On the free tier there are no extras: past 25 private reviews a month, a pull request gets a neutral Check and no review until the next month. No card is asked for on the free tier.
From install to the first comment
One: install the Aevral GitHub App on the repositories you choose; a GitHub owner or admin approves the install.
PR review is live on install: installing the App starts reviews on the next pull request, even before anyone signs in, and the owner can turn them off in Setup.
Two: sign in to the console with GitHub. That connects the install and starts a 14-day trial for private repositories: private reviews are free up to 500, and the trial ends at 14 days or 500 reviews, whichever comes first.
Three: open a pull request, or let your coding agent open one. Aevral reads the diff of the changed files, and the most security-relevant in full.
Four: read the result on the pull request. An advisory Check sits on the head commit, and when there is a grounded finding, inline comments sit on the added lines, at most five findings per review.
Each finding carries the evidence, a suggested fix, and a Fix with your agent prompt a human can paste into Claude Code, Cursor, or Codex. Aevral never pushes, applies, or merges anything, and it never blocks a merge.
You decide what ships.
Sources
Read next
PR security review and SAST are different questions; Reviewing pull requests for IDOR with a GitHub app; Build vs buy: a security review for pull requests; Install the GitHub App.
More guides
- What a whole-repo authorization scan reads
- PR security review and SAST are different questions
- Handing a security finding to your coding agent
- The Aevral launch-updates list, explained
- Reviewing a pull request for access control
- Working a scan report of access-control leads
- How IDOR happens in multi-tenant code
- Where access control hides in business logic
- Reviewing a pull request that wires in an LLM
- Reviewing pull requests for IDOR with a GitHub app
- Spotting a missing tenant check in a pull request
- Next.js and Supabase: the authorization check before launch
- Security review for pull requests written by Claude Code
- Vibe coding security: who reads the diff
- Why review bots get ignored, and what a grounded review does instead
- Security review for pull requests written by Cursor
- Security review for pull requests written by Codex
- Build vs buy: a security review for pull requests