Open Factor
  • Demo
  • Docs
  • Pricing
  • Changelog

Solutions

Patch before attackers find it

Start with an app URL you are authorized to test and a clear scope. Run read-only checks, review confirmed findings with redacted evidence, and add a repository to get draft patches. Your team reviews and merges.

Try the demoCheck my security coverage.

Set the boundary

Give it an app URL you are authorized to test and the routes to check.

Separate findings from suspicion

Confirm issues with request-and-response evidence and report which routes were checked.

Take proof into code review

Connect the repository for draft patches and regression tests where practical. Your team merges.

How a run works

From an authorized check to a finding you can verify

An illustrative security run: check routes in scope, confirm a finding, redact the evidence, and prepare a draft patch when code is connected.

Factories/Security run

IdleIllustrative run
    Missing 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
          • Property CampaignsFind high-value homes without pools, generate a personalized backyard preview, and prepare homeowner outreach for booked estimates.
            See template

          Start on Hobby, move to Pro when you need more

          Hobby is free with monthly credits. Pro is for heavier use. Eligible accounts can start Pro with a 7-day free trial.

          Compare all plansContact sales

          Hobby

          $0/ month

          $5 in monthly credits

          Get started

          What's included:

          $1 daily login bonus

          Pro

          $20/ month

          $20 in monthly credits

          Get Pro

          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

          1
          What can I start with?
          An app URL you are authorized to test and an explicit scope. A repository is optional for an outside-in report; add GitHub for code-based patches. Vercel deployment context is optional.
          2
          How does broader coverage stay useful?
          Check routes inside the agreed scope, confirm findings with evidence, and return findings by severity alongside checked and unprobed routes. Coverage is a record of checks performed, not a guarantee that a route has no vulnerability.
          3
          What requests does it make?
          Read-only requests for missing authorization, data exposure, redirects, headers and verbose errors. No destructive requests, brute force or load tests. This is not a full penetration test or a security guarantee.
          4
          Who approves the fix?
          Your team reviews and merges draft patches. Evidence is redacted, and regression tests are included where practical. Run again for new scope or configure a workflow schedule.
          5
          What kinds of findings does it investigate?
          Missing authorization, exposed data, open redirects, weak headers and verbose errors within your approved scope.
          6
          Does the report expose secrets?
          The workflow redacts secrets, tokens and personal data from request-and-response evidence before returning it.
          7
          Can it prioritize a new deployment?
          When deployment context is connected, it checks the latest deployment and prioritizes changed routes in scope.
          8
          Can it test a target I do not own?
          Only with authorization to test that target and a defined scope. Account access alone does not grant testing authority.

          Know what needs your attention.

          Set an authorized URL and scope. Start with findings, then connect code for draft fixes.

          Keep this runningTalk to us

          Product

          • Demo
          • Pricing
          • Templates
          • App

          Platform

          • Blog
          • Changelog
          • Customers
          • Developers
          • Docs
          • Stats

          Resources

          • Home
          • Book
          • Contact
          • Sales
          • Support

          Company

          • About
          • Brand
          • Terms of Use
          • Privacy Policy
          • Cookie Notice
          • DPA

          Ask AI

          Open Factor
          Platform activity