Hosted verifier waitlist
A badge is a point in time. Trust decays. Someone should keep watching.
Confidential compute promises your data stays protected. That promise needs checking, and re-checking: new attacks are disclosed, firmware ages, and a deployment that was safe last month may not be today. The hosted verifier keeps checking and tells you when the answer changes.
Continuous monitoring
Re-verifies your deployments as the attack database grows and CVEs land. A badge that was F last month may be D today, or worse. You find out when it changes, not at the next audit.
Policy enforcement
Rules over the graded evidence: deny a workload a key if its TCB is behind, require re-attestation on a schedule, block single-vendor deployments where your policy says otherwise. Enforced in the pipeline, not in a review meeting.
Compliance reports
C5:2026 and other frameworks want verifiable attestation evidence. The hosted service turns your graded verdicts into the evidence an audit asks for, continuously instead of annually.
Attack database
The open, growing catalog of attacks on confidential compute, graded by cost and mapped to compliance controls. The reference the grading runs on, kept current as attacks are disclosed.
Blast radius
When a CVE lands, the hosted service knows which of your deployments are affected, what workloads and secrets sit on them, and what the exposure is. The question after an attack is published, answered in minutes.
Incident response
Triage against the graded evidence: which attacks apply, what the fix threshold is, whether your TCB is behind it. The starting point for patching, not a blank page.
Join the waitlist
Your interest also tells us what to build first. The waitlist is the roadmap input.
The engine itself is open source and runs locally right now. No waiting required for that: try it today.