Aikido and Aevral

Aikido runs a platform across code, dependencies, secrets, and IaC, and publishes Code Security Audit. Aevral's scan is built for who has access to what; its PR review, live on install, also looks for a wider class list on the diff. Keep both.

Same repository, two questions.
RowAikidoAevral
Question it answersWhat does the platform surface, and what does Code Security Audit publish on source?Who has access to what, and did this change widen it?
Stated jobSAST, dependencies, secrets, IaC, pentest; Code Security Audit and Deep Review as publishedAccess-control and business-logic reading of the repo, and a wider security reading of the PR diff
Where it runsThe Aikido platform, Code Security Audit, and Deep Review, per Aikido's docsConsole scan on the default branch; PR review, live on install
Unit of workThe platform finding, or a Code Security Audit finding with evidenceThe finding as a lead with evidence, across files
Complementary?Yes, on the platformYes

Aikido is built as one platform for SAST, dependencies, secrets, infrastructure-as-code, and pentest. Keep that platform. Aikido also publishes Code Security Audit and Deep Review: agentic reading of source for authorization, IDOR, and business logic. Aevral's PR review, live on install, is its own security reading on the pull request. The whole-repo scan reads authorization, IDOR, and business logic on code already in the repository.

This page keeps the boundary honest: platform surfaces on one side, the specialist GitHub App on the other. Org-priced scan, fix prompt for the coding agent you already use, findings as leads. Keep both.

Aikido

Aikido is a developer security platform: SAST, dependencies, secrets, IaC, and pentest. It also publishes Code Security Audit and Deep Review, agentic reading of source for authorization, IDOR, and business logic. Aevral's whole-repo scan is built for that reading; its PR review, live on install, looks for that and a wider class list on the diff. Keep the platform.

Aevral

Security review, handled. PR review, live on install, looks for access control, business logic, SQL and command injection, XSS, SSRF, path traversal, unsafe deserialization, token and session flaws, and LLM-integration risks on the diff. Paid PR plans are live in the console. The whole-repo scan is live and self-serve, and reads authorization, IDOR, and business-logic access control only. A finding is a lead with evidence, and a human decides. No patches are auto-applied.

A support push that widens the admin gate.

This change relaxes the admin section's gate from an admin role to any signed-in user, so support staff can read admin reports during an incident without an admin account. The code is valid and the reports open for everyone signed in.

routes/admin.ts+1 −1
// gate the admin sectionrouter.use("/admin", requireRole("admin"))router.use("/admin", requireSignedIn())router.use("/admin", adminRoutes)
AevralWidened gate

The gate went from a role to a login. Every signed-in user, whatever their role, now reaches the admin section and its reports. The change is small, valid, and answers a real support need, and it still widens who has access to what. Aevral is built to read a diff for the gate itself: not whether the code runs, but who it lets through.

Run them together

Keep Aikido for SAST, dependencies, secrets, IaC, and the live pentest; run Aevral for the access-control reading of the repository, and a wider security reading of your pull requests through its PR review, live on install.

Questions engineers ask

Does Aevral replace Aikido?

No. Aikido does its stated job and keeps doing it. Aevral runs alongside it with its own reading: its PR review, live on install, looks for access control, business logic, injection, XSS, SSRF, path traversal, and LLM-integration security on the pull requests it reviews, and its whole-repo scan reads access control and business logic across the repository at rest.

Is this a catch-rate comparison?

No. This page states each product's job and shows one worked example of Aevral's own reading. Results on your code depend on your code; evaluations belong to you.

When can I run this?

Aevral is self-serve: install the GitHub App and log in to the console. The waitlist form is a launch-updates channel; joining does not reserve a price, access, or a contract.

More comparisons

The shorter version, at a glance: Aikido and Aevral on the works-alongside page.

See the wider field: Aikido alternatives.

Primary sources: Aikido Code Security Audit; Aikido documentation; Aevral whole-repo scan; Aevral PR security review.


Security review, handled.

Install the GitHub App and PR review starts on. Sign in with GitHub to connect it, then press Scan for the repository you already have.

Install the GitHub AppLog inSign up

For professional use. By installing, you confirm you can act for the account or organization that owns it, and you accept the Terms and DPA on its behalf.