Open Factor
  • Demo
  • Docs
  • Pricing
  • Changelog

Solutions

Continuous Pentester

Review authorized public attack surfaces from the source you supply. The report covers scoped security findings, reproduction evidence, impact explanations, and unresolved retest requirements. It compares earlier saved evidence when available and states coverage gaps.

Try the demoGet started

Factories/security

Working14-day run
Safe probes sent

0

read-only, inside your scope

Confirmed findings

0

1 high severity

Routes checked

0

new or changed, 38 clean

Spend

$0.00

of $25.00 cost budget

Probes by checklast 14 days

0probes sent0 confirmed

Missing auth0Exposed data0Verbose errors0Security headers0Open redirects0
Agent tasksLatest first
TaskStatus
Find the latest deploymentIdle
Probe new API routes for exposed dataIdle
Review 3 draft patch pull requestsIdle
Redact tokens from the evidenceIdle
Write a regression test for the auth fixIdle

Run plan

Each factory run probes new and changed routes in your latest deployment with safe, read-only requests, then patches each confirmed finding.

  • Send only safe, read-only probes in scope
  • Confirm each finding with request and response
  • Open each patch as a draft pull request
  • Cost budget $25.00, warn at 70%

Ready for your review

Review 3 draft patch pull requests

Each one has the redacted request and response, severity, fix, and test result.

Sample run: Security

From a new route to a confirmed finding

A sample run, start to finish. It maps what the deploy exposed, confirms a finding with the exact request and response, redacts the evidence, and reports which earlier findings are fixed.

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]

          Start with your source

          Provide the material and review the scope

          The trial begins with the material below. No mandatory OAuth connection is needed for accessible public sources or material you supply.

          Starting material

          Authorized app or staging URL + scope

          Your scope

          Set the targets, questions, acceptance criteria, and exclusions. The scope controls what the report investigates. Inspect only targets you own or have explicit permission to test. Stay within the authorized scope and use non-destructive checks. Enter the authorized target boundaries before running this template.

          Choose when to run

          Manual is the default. Choose hourly, daily, or weekly recurrence when repeated observation is useful.

          How the trial runs

          Map, probe, retest, confirm, report

          Map what the deploy exposed, probe what changed, retest open findings, then confirm each one before it reaches the report.

          Map the exposed surface

          List reachable routes, forms, and endpoints within your scope and note what changed since the last run.

          Probe new and changed routes

          Run passive and in-scope checks against what changed, recording each request and response.

          Retest open findings

          Replay earlier findings to see which the deploy fixed and which remain open.

          Confirm and rate findings

          Keep only findings reproduced with an exact request and response, rate their impact, and redact secrets.

          Write the security regression report

          Return confirmed findings, their reproduction, and the fixed or open status of earlier ones.

          What you review

          A job-specific report with its limits

          Scoped security findings, reproduction evidence, impact explanations, and unresolved retest requirements.

          New evidence makes recurrence useful

          Public sources can be read again. Uploaded files remain snapshots: provide a fresh upload to assess new private facts. Earlier saved evidence provides a comparison baseline, not a live connection to the original system.

          Coverage is stated, not assumed

          Browser interaction, code execution, authenticated access, and unsupported file formats may be unavailable in a run. Missing access or tools appear as coverage gaps, never as a passed test. Proposed fixes and drafts remain in the report.

          Review before taking action

          Returns a report and proposed next steps for your review. External messages, source changes, payments, and submissions are outside this trial. Inspect only targets you own or have explicit permission to test. Stay within the authorized scope and use non-destructive checks. Enter the authorized target boundaries before running this template.

          Start from a template

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

          Questions about this trial

          Inputs, recurrence, evidence, and the boundary of the report.

          Need help defining the source or scope? Contact us

          1
          What do I supply?
          Authorized app or staging URL + scope. Review the scope and criteria before the first run. If source material is inaccessible, the report identifies the gap.
          2
          Do I need to connect an account first?
          No mandatory OAuth connection is required for public sources and supplied material. This does not grant access to private sites or systems; inaccessible evidence remains an explicit gap.
          3
          What changes on later runs?
          A later run can compare current evidence with the previous saved baseline. The first run has no prior change history. Select manual, hourly, daily, or weekly execution; refresh uploaded files when private facts change.
          4
          Does a report prove that every relevant test ran?
          No. The report separates source-based findings, observed execution results, and unverified checks. A missing browser, runner, credential, or usable input is a coverage gap.
          5
          Will the trial apply its recommendations?
          It returns a reviewable report and proposed next steps. It does not send messages, change source systems, submit claims, or make payments.

          Start with the evidence you already have

          Supply the source, review the scope, and get an initial report before choosing a recurring cadence.

          Start this templateContact sales

          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