FAQ

Is Aevral open source?

No. Aevral is not open source. The engine, the planted-vulnerability corpus, and the judge stay private. What is public: the transparency report, the methodology page, the agent-setup prompt, and the plugin repo. This documentation is published on purpose; published documentation is not an open-source product. How the scan works, in prose: How Aevral hunts.

Does Aevral block merges?

No. The GitHub Check from a scan reports the outcome on the scanned commit; it never blocks a merge. PR review is live today as a free tier (public repositories free, 500/org/month, 25 private reviews per month). PR reviews start at install, before anyone signs in; Setup Complete or the Reviews page can turn them off. Its Check is advisory and its inline comments never block a merge either.

What does Aevral look for?

Two surfaces, two scopes. Pull-request reviews look for authorization, IDOR, and business-logic access control, plus SQL and command injection, XSS, SSRF, path traversal, unsafe deserialization, token and session flaws, and LLM-integration risks (prompt injection into tools, unsafe model output). Reviews are advisory and never block a merge; on a large pull request the most security-relevant files are reviewed first, and the review says which files it covered. Whole-repo scans read authorization (who has access to what, enforced where, missed where), IDOR (object-level access checks that are missing or wrong), and business-logic access control (rules the code intends but does not enforce) only. Neither surface covers memory corruption, secrets, dependencies, or supply chain. Aevral is not a general SAST. Each finding includes evidence and a suggested fix you apply in Claude Code, Cursor, or Codex. Review it before you change production code.

Details: What a pull-request review looks like and What a scan looks like. Across scans, the findings worklist keeps those findings and a human archive. A later scan that omits a finding does not mean it is fixed.

Is Aevral SAST?

No. SAST engines match code against rules and dataflow patterns, deterministically, across the whole tree. Aevral is an AI review: it reads the diff of each pull request plus the full head content of security-critical changed files, reasons about who can reach what, and must ground every published finding on lines the pull request actually added before it posts. It never reads git history and never executes code. It is complementary, not a replacement: keep your SAST for exhaustive pattern coverage, secrets, and dependencies; Aevral covers cross-file authorization, business logic, and identity classes that rules cannot express. The two-direction comparison: aevral.com/is-aevral-sast.

What does the model actually see, and where does it run?

The diff of every changed file, the full head content of up to 40 security-critical changed files, the pull request title and description, and a bounded trust-boundary map. Generated files, lockfiles, translation and fixture data are skipped by rule and named; secret-looking paths are never sent. Paid plans run on GLM-5.3, the free tier on GLM-5.3 Flash, through OpenRouter with a pinned provider list and zero data retention; your code is not used to train models. Full detail: How Aevral reviews a PR and Security and data.

The Check says "confirmed" but you call findings leads. Which is it?

Both, and the distinction matters. "Confirmed" is an internal verdict: the added lines of this diff themselves demonstrate the path (attacker, input, route, missing control). It is not a claim that the exploit was executed, and it is not a patch: the finding is a lead with evidence and a suggested fix, and a human decides what to change. Findings that pass grounding but depend on facts outside the diff are listed as unverified in the Check, never posted as comments.

How do I get access?

Aevral is self-serve: install the GitHub App, then sign in to the console with GitHub; it connects the matching install automatically. Free organizations get two private scans in 14 days; paid first scans use the included scan allowance. Questions or procurement: contact form.

What does it cost?

PR security review, the lead product, is priced in USD per organization per month: Free $0 (public repositories free, 500 reviews per organization per month; 25 private reviews per month; reviews start at install), Starter $49 (100, then $0.99), Pro $199 (500, then $0.99), Business $999 (3,000, then $0.99, plus 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 $1,999 (6,500, then $0.99, everything in Business); paid plans live in the console, billed monthly, each with the standard DPA. Enterprise starts at $4,000 a month by quote (custom DPA). Existing subscriptions keep their price. On paid plans a PR review is counted per pull request per billing period, a re-push does not count again, and the $0.99 extras apply only if the owner chose them. Free and the trial count each pull request head. Whole-repo scan plans are priced in USD per organization per month: Public repositories $0 (1 authorized public-repo scan per calendar month), Team $99 (4 default-branch scans, then $29), Business $399 (16, then $19), Scale $1,699 (100, then $17), Enterprise by quote from $3,300 per month equivalent. The two products are billed separately; neither requires the other. All prices exclude VAT, B2B. Full tables: Pricing and plans.

Is the GitHub App public?

Yes. The App is public: install it on any account or organization from https://github.com/apps/aevral. Every token Aevral mints is capped to Contents read, Metadata read and Checks write, plus Pull requests write for PR reviews (on by default). The App itself holds more, reserved for announced features that are not live: GitHub App permissions.

Who is behind Aevral?

Aevral is a Better ISMS product, by ISMS Copilot. Security: aevral.com/security. Binding: DPA section 1.7 and the Aevral sub-processor page. Privacy: privacy policy.

What is not live yet?

A fully documented public API contract (keys exist today on the console Developer API page), and an MCP endpoint. Everything future-tense on this site stays future-tense until it ships. Paid PR plans and the findings worklist are live in the console.

Do I need to return every week?

PR reviews run automatically from install, before anyone signs in. Setup Complete or the Reviews page can turn them off. Paid scan plans also support up to four automatic checkpoints per configured repository each billing month, sharing the included scan quota. They do not incur overage; unchanged commits reuse the report within the billing period and exhausted quota waits for renewal. This is not a free weekly private scan plan. See Recurring scans and quota.