Set the boundary
Give it an app URL you are authorized to test and the routes to check.
Give it an app URL you are authorized to test and the routes to check.
Confirm issues with request-and-response evidence and report which routes were checked.
Connect the repository for draft patches and regression tests where practical. Your team merges.
How a run works
An illustrative security run: check routes in scope, confirm a finding, redact the evidence, and prepare a draft patch when code is connected.
FactoriesSecurity run
IdleIllustrative runGET /api/invoices/inv_1042
Require a session on GET /api/invoices/[id]
Built for security teams
Each run checks what changed in your latest deployment and only patches what it can prove.
Sends only read-only requests inside your app URL and scope. Never destructive requests, brute force, or load tests.
Confirms each finding with the exact request and response, rates its severity, and names the code to fix.
Writes the fix and, where practical, a regression test that fails before it and passes after it.
Works with your security stack
Finds your latest deployment so each run checks what just shipped.
Reads the code behind the deployment, lists new or changed routes in scope, and checks it out to write and test each patch.
Probes each route in scope at the URL you set, and stays inside it.
Opens one draft per confirmed finding against your default branch. Your team merges.
Hobby is free with monthly credits. 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
What a run probes, what it proves, and what it never does.
Want to review your security requirements? Talk to us
Set an authorized URL and scope. Start with findings, then connect code for draft fixes.