Skip to content
Request beta access

Documentation

Clear guides. No guesswork.

Understand every scan, every evidence boundary and every next action. Start with one path or use the library as your reference.

Start with Quick startExplore all guides

Guide library

Start where your question begins.

Six focused paths take you from a first public URL to a safe operational response.

Quick start
Start with one public URL, review the evidence report and decide what to change before launch.
  1. Prepare the target
  2. Run the public scan
  3. Read the evidence
  4. Fix and verify
Open guide
Scan scope
Understand which evidence a public URL, an authorized repository and bounded backend checks can provide.
  1. Public website evidence
  2. Authorized repository evidence
  3. Bounded backend checks
Open guide
Verification
Confirm a changed state with the appropriate verifier instead of closing findings by assumption.
  1. Read the evidence
  2. Apply a scoped fix
  3. Run the verifier again
Open guide
Reports
Use the release gate, finding evidence and stated limits to make a traceable launch decision.
  1. Read the launch gate
  2. Sort critical findings
  3. Export the review bundle
Open guide
Security boundaries
Understand what bounded automated checks support and when qualified security review is still required.
  1. No destructive testing
  2. No raw secret reporting
  3. Review high impact changes
Open guide
Operations runbook
Use one clear response path when authentication, scans, integrations, billing or the dashboard stop working.
  1. Identify the affected path
  2. Protect users and data
  3. Recover the service
  4. Verify and document
Open guide

One continuous model

From observation to a verified change.

01

Confirm scope

Target and authorization are bound before the scan.

02

Read evidence

Rule, location, severity and confidence stay together.

03

Hand off the fix

One scoped prompt explains one change.

04

Check again

The appropriate verifier reruns the same rule.

Finding anatomy

Every claim stays attached to its evidence.

Not an isolated score. A finding shows identity, impact, evidence and the appropriate next action.

SEC_HEADER_002HIGH

Content Security Policy is missing

Observed response headersHigh confidenceHTTP verifier

AGENT HANDOFFAdd a bounded CSP without broadly allowing existing scripts.

More interfaces

The same model wherever you work.

MCP & CLI
Use findings with agents and in the terminal.
Learn more
REST API
Integrate scans and reports into workflows.
Learn more
Security boundaries
Understand what was tested and what was not.
Learn more

Common questions

The important boundary, answered directly.

Use Quick start for your first public URL. Read Scan scope before connecting a repository or requesting deeper checks.

Next step

Start with a real URL.

Quick start takes you from target confirmation to your first evidence report in a few clear steps.

Open Quick start