Skip to main content
Compliance dashboards usually ask you to trust the vendor. A green tick means the platform says you’re compliant — backed by its own attestation, in its own cloud. When your auditor, your regulator, or a court asks “prove it,” that green tick isn’t evidence. The Compliance Command Center is the opposite. It’s a self-hosted web console that sits over your AlgoVoi estate and shows one compliance-posture dashboard — where every figure is recomputed from a Falcon-1024 signed, hash-linked chain. Nothing is asserted; everything is proven, and your auditor can re-verify it themselves, offline, with no AlgoVoi software or service.
Sits above Records Vault. It ingests the evidence your products already export — it adds no new system of record. Self-hosted on your infrastructure; air-gap capable.

​
Proven, not asserted

GRC SaaS (Vanta / Drata / OneTrust)Compliance Command Center
EvidenceAttestation + dashboards, vendor-trustEvery figure backed by a signed chain
VerificationTrust the vendorOffline, public key only — re-verify it yourself
DeploymentSaaSSelf-hosted, air-gap capable, sovereign
CryptographyClassicalPost-quantum (Falcon-1024)
Change a single byte of any underlying evidence and the dashboard, the API, and the audit log all flag it. The trust base for verification is two public libraries — no AlgoVoi code takes part.

​
What it does

  • Aggregates your posture. Records preserved, read-access events, active legal holds, consents, key rotations — each tile shows its value and its verification status.
  • Re-verifies, continuously. Every signed chain across the ingested evidence is recomputed offline; a failure surfaces immediately.
  • Exports an auditor pack. One click bundles the evidence plus a verification summary into an archive your auditor, regulator, or counterparty verifies independently.

​
Enterprise from day one

  • Role-based access. Administrator, compliance officer, auditor, and read-only viewer roles govern who can see which evidence, run which reports, and export packs.
  • Single sign-on. Authenticate against your directory — LDAP / Active Directory — with directory groups mapped to roles. Local accounts for fully disconnected operation.
  • Bring-your-own-key custody. The console’s own signing key can live in your AWS KMS, HashiCorp Vault, or PKCS#11 HSM — unwrapped only at the moment of signing, never at rest.
  • A signed console audit log. Every console action — who signed in, who viewed what, who exported — is appended to a Falcon-signed, hash-linked chain. The console holds itself to the same standard: who did what in the console is itself offline-verifiable evidence.

​
How it fits

BelowRecords Vault and the rest of your estate — preserve records as signed evidence
Thisthe management layer — aggregate, re-verify, report, and export across the estate
Custodycomposes with Bring Your Own Keys

​
Availability

A self-hosted Enterprise product, available from the suite store (AV-CCC). Installs token-gated from the AlgoVoi private index — including fully air-gapped, with no PyPI. Runtime-licensed, fail-closed.

​
See also