Skip to content
0sec 0sec

0sec cloud

0sec cloud is the managed recurring-run surface built on top of the public 0sec engine.

The split is intentional:

  • 0sec is the OSS execution wedge: CLI, benchmarks, verification pipeline, and the public docs in this repo.
  • 0sec cloud is the managed layer: recurring scans, authenticated targets, operator review, artifact bundles, and orchestration around the same engine.

Nothing about the cloud product depends on a private fork of the agent. The scanner, benchmarks, and core verification logic remain in the OSS repo.

What the cloud layer adds

Section titled “What the cloud layer adds”
  • recurring scans instead of one-off local runs
  • orchestration across protected or authenticated targets
  • operator workflow for triage and review
  • customer-facing evidence packaging
  • managed storage and scheduling around the public engine

What stays public and OSS

Section titled “What stays public and OSS”
  • CLI scanning
  • benchmarks and methodology
  • blind verification
  • triage and reporting primitives
  • docs for the public engine

This is why the marketing site can cite public benchmark receipts while the managed layer sells reliability, continuity, and operations.

Section titled “Where to read next”