Explainer
The Aevral launch-updates list, explained
The honest mechanics: the product is self-serve today, and the email list is an optional launch-updates channel that reserves nothing.
Tristan Roth,
This page used to be a waitlist explainer; today it is the launch-updates explainer. What the list is, what the product already does, and what you are and are not committing to. Short version: you are joining an email list, and that is all. The product is self-serve without it.
What you are joining
An email list, collected through a hosted form, used for one thing: product updates by email, like new scan classes and new surfaces. Joining does not reserve a price, access, or a contract. The product itself is self-serve without the list: install https://github.com/apps/aevral and log in to the console whenever you want. If you would rather talk to a human first, the contact form exists for exactly that, and nothing on this site requires an account to read.
What is live today, in order of signup
Install the GitHub App on any account, sign in to the console with GitHub (it connects the install), and run self-serve scans per the published pricing: authorization, IDOR, and business-logic access control on the default branch, per organization, USD 0 for authorized public repos, then the paid org tiers.
Today there is also an aevr_ API key from the console Developer API page and a start-scan request, so the console is one client among possible others. The PR security review sits beside it, live on install: installing the App starts reviews. An MCP server is planned after that, and there is no live MCP endpoint today.
What stays true
Findings are leads with evidence, not confirmations. No validation pass runs on findings, no suggested diff is applied for you, and a scan is not a clean bill of health. Priced by organization, not by seat, self-serve from USD 0. Public repositories keep their free lane: one authorized scan per calendar month, and PR review free at 500 reviews per organization per month, live on install.
If you need us
The contact form reaches a human at the company behind Aevral, Better ISMS, the same people behind ISMS Copilot. Waitlist or not, the door is the same.
Sources
Pricing (both SKUs); Install (self-serve: install, sign in, scan); For AI agents (the API facts).
Read next
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
- 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
- Security review priced per pull request, explained
- 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