What a PR review looks like

Security review, handled. The review is its own product, not one of the included whole-repo scans and not a replacement for the scan plans. Reviews start at install. The owner can turn them off. USD per organization, B2B; paid plans are live in the console.

How a review runs

For the mechanics behind these steps (what is read, how files are packed, the grounding gate, verdicts, and the limits as numbers), see How Aevral reviews a PR.

1. Trigger. Pull requests opened, reopened, and synchronized after the App is installed. After the first review of a pull request, a re-push reviews only what changed since the last reviewed commit; a force-push, a rebase or a reopen gets a full review again. On paid plans a pull request counts as one PR review per billing period, however often it is re-pushed; on Free and the trial, each new head is a new review and the same head is never counted twice.
2. Read. The diff of the changed files is read, most security-relevant first, and the most security-relevant files are also read in full at head. Generated files, lockfiles, and locale and fixture data are skipped by rule, and the review names them. Aevral looks for access control, business logic, SQL and command injection, XSS, SSRF, path traversal, unsafe deserialization, token and session flaws, and LLM-integration risks.
3. Post. An advisory Check on the head commit plus inline comments pinned to the exact added lines. Never blocks a merge. Each finding is a lead, not a confirmed exploit. On a re-push, a new review is posted only when there are new findings; the summary review is edited in place. To have the whole pull request reviewed again, comment @aevral review (see GitHub App permissions).
4. Bound. Up to five findings per review; when there are more, the Check says how many were held back. Leads Aevral could not prove are listed in the Check under "Unverified, worth a look", never as comments. Silence when there is nothing to publish. On a large pull request, Aevral reviews the most security-relevant files first, and the review says which files it covered.

Grounded on added lines

Every inline comment is pinned to a line the pull request actually added, on a file the pull request actually touched. If the evidence cannot be grounded, the comment does not post. A large pull request gets its most security-relevant files reviewed first, with the covered files named, never a partial review sold as complete. A pull request past the reading budget gets a Check that says it was too large to review.

Fix with your agent

Each inline finding comment ends with a collapsed Fix with your agent block: a prompt you paste into Claude Code, Cursor, or Codex. It names the file and line, the problem, the missing control, and the suggested fix (a lead, not a patch). It asks your agent to check the finding against the code first, make the smallest change with a test, and stop before commit or push. Text that comes from the reviewed code sits in a marked block the agent is told not to follow. Aevral never applies or merges a change.

The Check summary and the review footer also carry a one-line notice: installing Aevral accepts the Terms and DPA for your organization.

Plans

Free tier: public repositories are free, 500 reviews per organization per month, and private repositories get 25 pull-request reviews a month free. Before anyone signs in, 25 private reviews a month are free; connecting the install in the console starts a 14-day private trial with a 500-review cap, no card. Paid plans are purchasable in the console.

PR security review plans, USD per organization per month (paid plans live in the console):

On paid plans, a PR review is counted per pull request per billing period; a re-push does not count again. The first time an organization goes over its plan, it gets an extra quarter of the plan's PR reviews free, once. After that, $0.99 per extra PR review if the owner turned extras on, at checkout or later in the console; otherwise reviews pause until the next billing period, with a Check on the pull request explaining why. Extras stop at a monthly spend cap the owner can change in the console. Business and Scale add a monthly export (CSV) 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). Scale is the highest self-serve plan (Business for an organization on an older price list); at its limit, the path is extras or contact us about Enterprise, from $4,000 a month. Every paid plan includes the standard DPA. Existing subscriptions keep their price. On Free and the trial, failed or skipped reviews release their reservations; a new head commit is a new review, while replaying the same head does not count twice. Public reviews remain free, 500 per organization per month, and do not consume the private allowance. Scan and PR allowances are separate.

Using reviews as evidence in an audit, including what to show an ISO 27001 auditor and where the record lives on each pull request: https://aevral.com/audit-evidence.

Permissions note

Each review runs on a token capped to Contents read, Metadata read, Checks write and Pull requests write, minted for that job and that repository. Your organization accepts the App permissions at install; the App holds more than the token, reserved for announced features that are not live. Reviews start at install; Setup Complete or the Reviews page can turn them off. See GitHub App permissions.

Start

Install the GitHub App (reviews start on the next pull request), then sign in to the console with GitHub; it connects the matching install automatically. The whole-repo scan is a separate product with its own price: What a scan looks like.