Probe what just shipped
Check new and changed routes with safe, read-only requests.
Solutions
Patch before attackers find it
Probe new and changed routes in your latest deployment with safe, read-only requests, and get a draft pull request that patches each confirmed finding.
Prove each finding
Confirm it with the exact request and response.
Get a patch with its test
Get a draft fix and, where practical, a regression test.
How a run works
From a new route to a draft patch
A sample run, start to finish. It probes what just shipped, proves a finding, redacts the evidence, and leaves a draft pull request for your team.
Factories/Security run
IdleIllustrative runMissing authHigh severity
- Request
- GET /api/invoices/inv_1042
- Response
- 200 OK
Evidence for the pull request200 OK
GET /api/invoices/inv_1042
- Confirmed findings
- 0
- Draft pull requests
- 0
Draft pull requestfix/invoice-session-checkmain
Require a session on GET /api/invoices/[id]
Built for security teams
Proof first, then a patch
Each run checks what changed in your latest deployment and only patches what it can prove.
Safe, read-only probes
Sends only read-only requests inside your app URL and scope. Never destructive requests, brute force, or load tests.
Confirmed before patched
Confirms each finding with the exact request and response, rates its severity, and names the code to fix.
Patches with tests
Writes the fix and, where practical, a regression test that fails before it and passes after it.
Works with your security stack
Checks what you just shipped
Vercel deployments
Finds your latest deployment so each run checks what just shipped.
GitHub repository
Reads the code behind the deployment, lists new or changed routes in scope, and checks it out to write and test each patch.
Your app URL
Probes each route in scope at the URL you set, and stays inside it.
Draft pull requests
Opens one draft per confirmed finding against your default branch. Your team merges.
Start from a template
All templates- AI Pen TesterMaps the routes each deploy adds or changes and probes them with read-only requests. Each finding comes with the request, response and a draft pull request with the fix.See template
- Continuous PentesterStart with Authorized app or staging URL + scope. Later scheduled cycles revisit accessible sources and saved cases. Coverage depends on the available sources and runtime. Tests and measurements require actual execution evidence; unavailable capabilities remain visible as coverage gaps.See template
- Website Privacy Behavior AuditorStart with Owned website + approved privacy expectations. Later scheduled cycles revisit accessible sources and saved cases. Coverage depends on the available sources and runtime. Tests and measurements require actual execution evidence; unavailable capabilities remain visible as coverage gaps.See template
Start on Hobby, move to Pro when you need more
Hobby is free with monthly FTAI. Pro is for heavier use. Eligible accounts can start Pro with a 7-day free trial.
What's included:
$1 daily login bonus
Everything in Hobby, plus:
Pay as you go
Multi-member teams
Free viewers
Beta Feature Opt-in
Security questions, answered
What a run probes, what it proves, and what it never does.
Want to review your security requirements? Talk to us
1Is it safe to run against a live app?
It only sends safe, read-only requests inside the app URL and scope you set. It never sends destructive requests, brute force, or load tests.
2Does it merge its own patches?
No. Each patch opens as a draft pull request, and your team reviews and merges it.
3What does it check for?
Missing auth, exposed data, open redirects, weak security headers, and verbose errors on new or changed routes.
4Is this a full penetration test?
No. It runs safe, read-only checks with proof against your latest deployment. It does not chain exploits or test anything outside your scope.
5How do I know a finding is real?
Each one comes with the exact request and response, a severity, and the file and lines to fix.
6Do secrets end up in pull requests?
The pull request shows the request and response with secrets, tokens, and personal data redacted.
7What do we need to connect?
GitHub for the code and pull requests, Vercel for deployments, and the app URL and scope to probe.
8What does a run return?
Findings by severity, each with its proof and draft pull request, plus the routes it checked and found clean.
Patch what you can prove
Connect GitHub and Vercel, set your app URL and scope, and get draft pull requests for confirmed findings.