Free Preview
- Quick local CLI scan only
- 100 file scan cap
- Terminal report only
- No MCP, CI, exports, or external linters
Start with local proof. Pay only when you need full scans, exports, agent workflows, or CI enforcement.
Free Preview proves the local signal. Solo adds full local scans, report exports, and MCP. Pro and Studio add agent prompts, premium rules, quality gates, and repository-scoped CI.
Checking checkout availability...
Checking checkout availability...
Checking checkout availability...
Plan fit
Use this when the visitor has not inspected findings yet.
Use this when the buyer needs local depth but no shared CI gate.
Use this when a team needs SARIF, fail-on thresholds, and reviewer evidence.
Use this when multiple developers need local scans and shared CI validation.
Verified benchmark
The figures below come from the repository's Criterion benchmark suite and include a reproducible environment, fixture, commit, and range.
10.703–10.819 ms
25.185–25.368 ms
13.494–13.586 ms
These measurements cover the maintained parser, rule, and scan-session fixture. They are not an end-to-end speed promise for every repository, machine, ruleset, or network condition.
Method →The key difference is whether the workflow stays local or becomes a shared agent and CI gate.
Resolve source handling, plan boundaries, and checkout behavior before paying.
No. Scans run on the developer machine or GitHub Actions runner. License checks and optional analytics use entitlement and product metadata, not repository contents.
Use Free Preview to verify the signal on a real repository. Choose Solo for full local scans, report exports, and MCP; choose Pro or Studio for agent repair prompts, premium rules, quality gates, or repository-scoped CI.
The catalog price remains visible as a fallback, checkout shows a clear error, and no sale is counted. Retry when Paddle is reachable.
Run Free Preview on a real repository, then choose the smallest plan that supports the workflow you need.