Case Studies
Real audits. Clear outcomes.
These are working sessions on real products: what we looked at, what surfaced, and what changed afterward.
The number was right. What it counted was wrong.
One AI model analysed 32 security audits, checked its own work, and passed it. Two models from two other AI companies found the error by two different routes. What the data really said, and what shipping it would have cost.
Internal review council · not a product run · models not named
What happens when Claude Code gets independent AI reviewers?
A recorded build of an AI Email Drafter. Claude Code wrote and reviewed its own plan, then the same work went through MegaLens for independent review before and during the build. Claude stayed the decision-maker throughout.
Full screen recording · all 167 tests passed
Claude Code vs Cursor: two projects reviewed with MegaLens.
Two real projects, two IDEs. On an AI Email Drafter built with Claude Code and a PR Description Drafter built with Cursor, each IDE's own review was set beside a MegaLens review. The findings and the method are written up and the repos are public.
2 projects · 2 IDEs · comparison table · public repos
15 gaps caught before writing a single line of code.
Claude Code wrote the plan and the code for an AI Email Drafter. MegaLens reviewed the plan before implementation and each commit during the build. Full repo included.
Plan audit + 12 per-commit reviews · 15 findings · public repo · live build video
We audited our own legal setup and found 9 risks in 5 minutes.
Before drafting a privacy policy, we audited our own product architecture. The review surfaced critical gaps in GDPR readiness, cross-border transfers and Chinese provider disclosure.
9 findings · 3 critical · 4m 55s
23 issues found before writing a single line of code.
Two reviewers checked a 7-step UI plan before any code was written. They found 23 issues across security, architecture, UX and performance. 15 changes were made to the plan before the build.
2 reviewers · 23 issues · 15 plan changes before the build
Passing tests didn't mean it was safe to ship.
74 files, 10 end-to-end tests, all passing. Two AI reviewers in our own development process still found 14 more issues: concurrency bugs, silent failures, and credential exposure risks. This review ran outside MegaLens.
2 AI reviewers · 17 total issues · 14 fixed same session
The SSRF fix that passed its tests and was still unsafe to ship.
A production SaaS had 7 security findings to patch in one session. The first-pass fixes compiled and tested. Independent review then caught two bugs hiding inside the patches themselves.
2 reviewers · 2 review rounds · 4 files · 14 tunnel-aware test cases · same-day deploy
Our audit pipeline reviewed its own expansion, from inside the editor.
We wired MegaLens into the IDE and ran the first end-to-end test on a real task: our own expansion. The review raised structural risks before code existed, and a second pass raised more, including the one real high severity defect.
49/49 regression