Product

Scans

Each scan runs a set of security checks against one target. One successful scan consumes one scan credit.

Starting a scan

From the dashboard, choose a target and run a scan. You need at least one scan credit. The CLI and API follow the same credit rules.

Scan lifecycle

  • Pending — scan queued, job starting
  • Running — checks executing; progress shows checks completed vs total
  • Complete — findings available
  • Failed — job or scan error; see failure message on the scan page

Scans typically take a few minutes depending on the target. Progress updates in real time on the scan detail page.

Credits

A credit is deducted when a scan completes successfully. Failed scans do not consume credits. Your balance is the sum of your monthly plan allowance and any purchased scan packs.

Plans & usage explains monthly resets vs pack rollover.

Automation

Use the CLI or API to trigger scans from CI/CD. See CI/CD.