Solutions

Engineering controls, mapped to audit criteria.

The reliability criteria are the hardest part of the audit to evidence, because the proof is in code and in practice, and you own neither. Revelara collects it where it lives.

Compliance postureTeams view
Controlcheckoutpaymentsplatform
SLO-Tied AlertingRC-001 · detective–2–
Synthetic MonitoringRC-002 · detective1––
Alert Noise ReductionRC-004 · corrective975
On-Call CoverageRC-005 · preventive––2
Incident RunbooksRC-006 · preventive4––

Example data. A lit row is one failure class that recurs across teams. A lit column is one team with many.

Coverage by criterion

A 70-control compliance matrix, mapped to Common Criteria and Availability. Each control shows its evidence status, for each team that owns a part of it.

PlanThe compliance matrix starts at the Plus plan. See pricing.

Evidence that names its scope

Evidence has four scope states: team, service, global, and unknown. Evidence from before scoping existed is marked unknown and queued for a new scope. It is never silently counted as organization-wide.
rvl — evidence
$ rvl evidence submit --control=RC-004 --team=checkout \
--type=document --name="Monthly alert review" …

Evidence carries a scope: team, service, or global. A control counts for the organization only when every team is covered.

What leaves the environment

The Revelara scanner and rvl CLI run in your own environment and never upload your repositories or source files. A scan sends, at most, structural metadata about API usage (client type, method, language and a call-site count), never source code. When you choose to submit findings, which needs an API key, each finding can carry file paths, line numbers, commit and branch identifiers, and short excerpts of code or configuration that your coding agent quoted. --dry-run shows you the exact payload before anything is sent. Your AI coding agent reads your code under your own agreement with its model provider. It acts for you, not for Revelara.

The CLI is open source, so your reviewer can verify this in the code. Read the security page.

Readiness, not certification

Revelara supports readiness for the reliability criteria. Your auditor still issues the report.

Run your first scan free.

Install the CLI, scan a repo, and read the findings in your terminal. Your repositories are never uploaded.