A second pair of eyes
Ship fast.
Know what's exposed.
We look at the app you shipped, find the mistakes AI builders make, and tell you how to fix them in plain English. No security team required.
customer data readable
supabase: `users` returned rows with the anon key
secrets: service_role key shipped in /assets/index.js
exposure: .env is publicly readable
headers: no Content-Security-Policy
Example check, not a customer.
Where we look
We look where AI-built apps usually break.
Data access, keys, auth, hosting, and the AI layer. We keep the exact checks private, because a public checklist is a map for attackers. You get the evidence and the fix.
HowItWorks
Three steps. No security team.
Add your app
Paste the URL. We give you a DNS record so only the owner can run a check.
Read the report
Plain English, the evidence, and the exact fix. Not a wall of CVSS scores.
Fix and run it again
Apply the fix, run the check again, and share a clean report with your customer or investor.
Showcase
See what people built with AI.
A public shelf for vibe-coded apps. Browse what shipped, see the stack behind it, or publish your own app after a free blackbox check.
What we are learning
Notes from the field
18 Nov 2026
When a hosted app blocks a security check
A blocked scan is not a clean bill of health. Here is what an inconclusive result means, and the honest way to handle it.
RuleOfEvidence
No finding without a receipt.
Every claim in a report points to a request, a returned row, or a line of source. If we cannot prove it, we do not ship it.
GroundRules
We only check what you can prove you own.
You verify the domain with a DNS record before we send a request. The checker is read only, rate limited, and blocks private and metadata addresses. Every request is logged. Secrets are redacted and never stored in full.
RunFreeCheck