> ## Documentation Index
> Fetch the complete documentation index at: https://docs.algovoi.co.uk/llms.txt
> Use this file to discover all available pages before exploring further.
# Self Hosted Compliance Evidence Platform
> Self hosted, air gap capable evidence estate for HIPAA, GDPR and eIDAS: post quantum signatures, a tamper evident audit log, RFC 3161 trusted timestamps.
The AlgoVoi Verifiable Compliance Suite is a self-hosted, air-gap-capable
compliance evidence and long-term records platform with post-quantum signatures
(Falcon-1024 and ML-DSA-65) and offline-verifiable integrity proofs. It is the
digital-preservation and audit-evidence estate for regulated sectors (health,
insurance, defense) that must keep records provably intact and confidential for
decades, on their own infrastructure, with no cloud dependency and no vendor in
the verification path.
*Last updated: 3 August 2026.*
**This is the on-prem bundle.** One commercial licence unlocks and runs the whole compliance estate on
your own infrastructure. The payment-rails estate ships separately as the
[Payment Rails bundle](/payment-rails-sqlite).
## What it is
The **Verifiable Compliance Suite** is the verifiable long-term data estate for regulated sectors:
health, insurance, defense, and any records that must stay provably intact and confidential for decades.
It is a single encrypted deliverable. Your Falcon-1024-signed licence is **both** the decryption key
**and** the runtime licence, so the whole estate installs and runs fully offline, air-gap capable, with
no PyPI and no phone-home.
Documents are preserved write-once in a tamper-evident, content-addressed archive: encrypted at rest,
RFC-3161 timestamped, and offline-verifiable with no vendor in the loop. Post-quantum signing
(Falcon-1024 and ML-DSA-65) keeps the evidence verifiable as cryptography evolves, the durability that
long-lived and defense records require. Records are added and removed the compliant way: a legal hold
blocks deletion, then a signed erasure tombstone leaves proof the record existed while the content is
irrecoverable. The Compliance Command Center re-verifies every signed chain offline and shows one proven
posture, where every figure is recomputed, not asserted.
The Substrate 2 core, the Compliance Command Center and control plane, Records Vault, Recovery Vault,
Archive Auditor, the doc-archive engine with HSM, KMS, HashiCorp Vault and S3 key custody, Compliance
Gate, Retention, Sanctions Monitor, Travel Rule, and the Verifiable Audit Log. One key runs them all.
Falcon-1024 and ML-DSA-65 signatures over ML-KEM-1024-sealed records. Evidence you sign today stays
verifiable after the migration to post-quantum cryptography, for the decades-long windows these
records must survive.
Write-once, tamper-evident, content-addressed archive. RFC-3161 trusted timestamps, legal and
e-discovery holds, and signed erasure tombstones that prove a record existed while its content is
cryptographically shredded.
The [Compliance Command Center](/compliance-command-center) ingests every product's signed evidence,
re-verifies each chain offline, and renders one posture dashboard. Every figure is recomputed from the
evidence, not vendor-asserted.
Hold the Falcon-1024 signing and ML-KEM keys in your own HSM, AWS KMS, HashiCorp Vault, or PKCS#11.
AlgoVoi never sees a private key, and the signed output is unchanged so verification stays identical.
Verifies and decrypts fully offline. No network, no phone-home, no PyPI. Evidence supporting HIPAA,
GDPR, eIDAS, and long-term retention mandates, verifiable from the public key alone.
## What is inside
| Layer | Components |
| --------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Core | Substrate 2 (Falcon-1024 + ML-DSA-65, ML-KEM-1024, JCS canonicalisation, policy binding), control plane, Retention, [Crypto-Agility](/crypto-agility): classical-to-post-quantum migration with provable continuity, Keystone lifecycle evidence |
| Hub | [Compliance Command Center](/compliance-command-center): evidence console and one-posture dashboard, IQ/OQ/PQ self-validation pack, clean-box validation gauntlet |
| Records | [Records Vault](/records-vault) with [.epi export](/epi-evidence-export), [Recovery Vault](/recovery-vault), Archive Auditor, the [Verifiable Archive](/verifiable-archive) engine with S3, KMS, PKCS#11 and Vault custody, Volume Importer (Merkle batch and per-document strategies, bridge and store modes) |
| Evidence | [Sanctions Monitor](/sanctions-monitor), [Travel Rule](/travel-rule), [Retention](/retention-app), [Verifiable Audit Log](/audit-log) |
| Controls | [Compliance Gate](/compliance-gate-v2): policy-bound ALLOW / REFER / DENY decision engine |
| Sealed delivery | Sealed encrypted containers (.acv): ML-KEM-1024 to one recipient, opaque-names mode, offline revocation, k-of-n Shamir and console key-loss recovery |
## Manage from one hardened console
The [Compliance Command Center](/compliance-command-center) is not only a posture dashboard. From one
place an operator runs the regulated-records lifecycle, and every action is written to the console's
signed audit chain.
Browse and verify records, notarize and retrieve a document, place and release legal holds, work the
retention and disposition queue, review every signed evidence stream (consent, custody, key rotation,
redaction, read-access), and manage local accounts, all from the console.
A strict Content-Security-Policy with anti-clickjacking and anti-sniff headers on every page, cookies
marked Secure over HTTPS, a brute-force backoff on sign-in and the step-up re-check, and a fresh
credential confirmation before sensitive actions such as notarizing, retrieving, or releasing a hold.
Optional authenticator-app two-factor (RFC 6238 TOTP): enroll from the Security page by scanning a QR
code, opt-in then required, with no SMS or email dependency so it stays fully air-gap friendly. Every
enroll and two-factor sign-in is written to the signed console audit chain.
Optional live streaming of the signed audit chain to your SIEM (RFC 5424 syslog, CEF, or webhook).
Each record carries the entry seq and sha256 so it ties back to the tamper-evident chain. Off unless
a sink is configured, non-blocking, and never breaks the signed append.
## Regulatory coverage
The evidence chains produced by the suite directly support the documentary requirements in these frameworks. Your counsel certifies compliance; the suite provides the tamper-evident, independently verifiable evidence that certification rests on.
| Framework | Provision | Evidence the suite provides |
| ------------------- | ----------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
| HIPAA | §164.312(b) audit controls | Signed tamper-evident read-access log: principal, record, granted or denied, reason; exportable for SIEM and GRC |
| HIPAA | §164.312(c)(1) integrity | Write-once content-addressed archive; Falcon-1024-signed chain breaks on any alteration |
| GDPR | Art 17 right to erasure | Signed erasure tombstones: content is crypto-shredded; a signed proof the record existed survives |
| GDPR | Art 5(1)(f) integrity and confidentiality | ML-KEM-1024-sealed records at rest; offline-verifiable chain integrity |
| eIDAS | Qualified timestamps | RFC-3161 tokens from an independent TSA; air-gap record falls back to a signed chain with no external call |
| 21 CFR Part 11 | §11.10(a) validation documentation | IQ/OQ/PQ self-validation pack generated by the [Compliance Command Center](/compliance-command-center) on installation |
| Long-term retention | Decades-scale verifiability | Falcon-1024 and ML-DSA-65 keep evidence verifiable after the post-quantum cryptography migration |
## Import at scale
Bringing an existing document estate into the Verifiable Archive is a first-class operation. The
**Volume Importer** add-on ingests a filesystem tree, a SQLite blob table, or an S3 bucket, and lets you
choose the signing strategy per import to trade granularity against throughput.
One Falcon-1024 signature per batch over a SHA-256 Merkle root, so throughput is bounded by reading
and hashing rather than signing. Every document keeps a short offline inclusion proof against the
signed batch root, so it stays independently verifiable.
One Falcon-1024 signature per document for maximum granularity, where each record is an independent,
individually revocable signed archive entry.
Both strategies run in **bridge** mode (notarise content hashes, no bytes moved, the zero-disruption
on-ramp) or **store** mode (ML-KEM-encrypt and store each blob). The import is idempotent and resumable,
so a re-run skips already-committed records, and it hashes the filesystem in parallel.
Throughput measured end to end on real 100 KB files read from disk with real Falcon-1024. Merkle
throughput is bounded by reading and hashing rather than signing, so it scales with CPU cores (hashing
runs in parallel) and MB/s is the stable figure. The ranges below span a single vCPU at the low end to a
multi-core box at the high end:
| Strategy and mode | Throughput (100 KB docs) | Bandwidth |
| --------------------------------- | --------------------------- | --------------------- |
| Merkle, bridge (hash only) | about 2,000 to 6,500 docs/s | about 380 to 660 MB/s |
| Merkle, store (encrypt and store) | about 950 to 1,150 docs/s | about 100 to 120 MB/s |
| Per-document Falcon, bridge | about 110 to 130 docs/s | signing bound |
At those rates a ten-million-record estate at 100 KB average imports in roughly **30 to 90 minutes** in
merkle bridge mode (fewer cores, longer), a few hours in merkle store mode, versus days per document with
per-document signing (about 20 to 56 times faster in bridge mode, widening with more cores). Larger
documents lower the docs/s but hold the MB/s, so size the estimate by total bytes. Verification stays
offline either way: per-document receipts for the per-document strategy, per-document inclusion proofs
against the signed batch root for merkle. The Compliance Command Center re-verifies every imported chain
offline, recomputed rather than asserted, and its **Import** page drives the importer directly over a
folder, SFTP, or rsync landing zone, with an optional folder watcher for a standing feed.
The Volume Importer ships inside this suite bundle and is also available as a standalone add-on to
[Records Vault](/records-vault). It requires a valid Records Vault or suite licence and is fail-closed.
## Sealed encrypted containers
Hand a set of records to an auditor, regulator, or counterparty as one portable, encrypted file that only
they can open, offline, with no AlgoVoi software.
The content key is wrapped with ML-KEM-1024 to the recipient's post-quantum public key, so only that
recipient can open the container. The body is AES-256-GCM encrypted under a Falcon-1024-signed header
that is verified before anything is decrypted.
Optional opaque-names mode keeps document filenames and the container title out of the cleartext
header; the real names travel encrypted in the body and are restored only after decryption.
Revoke a container from the Command Center. The issuer publishes a signed revocation list and the
offline extractor refuses to open a revoked container, even one already delivered.
Two options, chosen per container. Split the content key into k-of-n custodian shares (audited Shamir
SLIP-39) so any k custodians reconstruct it if the recipient's key is lost, shares shown once and
never stored. Or mark a container console-recoverable, and the Command Center recovers it 100% on its
own from a console-held key with no custodians. Recipient-only stays the default.
The [Compliance Command Center](/compliance-command-center) creates and revokes containers, signed by
the console key, and shows a live issued, active, and revoked posture.
The recipient opens it with a self-contained extractor that imports no AlgoVoi software:
```bash theme={null}
# normal: open with the recipient's ML-KEM secret, checking the revocation list
python acv_unseal.py --key @recipient_sk.b64 --revocation-list @crl.txt --out ./unsealed container.acv
# recipient key lost? reconstruct from k custodian recovery shares instead
python acv_unseal.py --recover-share "..." --recover-share "..." --out ./unsealed container.acv
```
Every unsealed document is checked against the signed header's SHA-256 before it is written, and document
names that try to escape the output directory are refused, so a tampered or malicious container never
yields a document or writes outside where you asked.
## Updates you control
Upgrades reach your deployment only when you ask for them. There is no phone-home: online update checks
are **off by default**, and the console never contacts the network on its own.
An operator enables online checks and presses Check; only then does the console make a single request
to `pip.algovoi.co.uk`. It shows what is available and applies it on approval. No timers, no
background polling, and it is one switch to turn off again.
Every release is Falcon-1024-signed by AlgoVoi. The console verifies the signature first, then checks
the downloaded bundle and every wheel against the signed manifest, before anything is installed.
Nothing unsigned is ever run.
No connectivity? Transfer the same signed update package onto the host and apply it from a file with
no network at all. Identical verification either way.
Updates are never auto-applied. Every check and apply is written to the console's signed, offline-
verifiable audit chain, and the previous version is retained for rollback.
## Supply-chain provenance
Enterprise security reviews and regulated procurement ask for a Software Bill of Materials and a signed
build provenance in their own format. The suite ships both with every download, and the same offline tool
lets you regenerate and verify them yourself. No network call is involved, so it fits the air-gap posture
of the rest of the suite.
A full Software Bill of Materials for the bundle in both **CycloneDX 1.5** and **SPDX 2.3** JSON. Every
component is pinned by SHA-256 with its `pkg:pypi/...` package URL and declared licence, ready to load
straight into Dependency-Track, Grype, or your procurement portal.
A **SLSA Provenance v1** attestation (in-toto) that pins the bundle and both SBOM files by digest,
signed offline with the AlgoVoi release key (Falcon-1024 over RFC 8785 canonical bytes), the same key
that signs the release manifest. One published public key verifies it.
`algovoi-sbom verify` checks three things with no network access: the provenance signature validates
under the release key, every pinned subject digest matches the file on disk, and every SBOM component
hash matches its wheel. All three must pass. The SBOM is reproducible, so it can be pinned and rechecked.
Drop an OSV advisory feed you exported once next to the SBOM and `algovoi-sbom cve` matches your pinned
components against it entirely offline. The same SBOM also feeds your own scanner, so this is a
convenience, not the only path.
```bash theme={null}
# Regenerate and verify the supply-chain evidence from your installed wheelhouse, offline
algovoi-sbom generate ./wheelhouse --out ./sbom --name algovoi-substrate2-onprem --version 1.6
algovoi-sbom verify --dir ./sbom --pub-key release.pk --wheelhouse ./wheelhouse
algovoi-sbom cve --sbom ./sbom/sbom.cyclonedx.json --feed ./osv-advisories.json
```
## Buy and install
The suite is a one-time purchase on a perpetual licence, self-serve from the
[suite store](https://api.algovoi.co.uk/suite-store). The flow is **pay, download, key**:
1. **Pay** the one-time licence fee. On settlement you receive a download link and your Falcon-1024
bundle licence.
2. **Download** the single encrypted deliverable (`bundle.algv`) plus the offline extractor.
3. **Key**: your licence decrypts and installs the whole estate, and runs it. The same key is the
runtime licence.
```bash theme={null}
# 1) prerequisites (one line)
python -m pip install cryptography pqcrypto rfc8785 fastapi uvicorn httpx
# 2) save your licence key to licence.key, then extract + install (offline, verified)
python algovoi_unbundle.py --license @licence.key --out ./algovoi --install bundle.algv
# 3) run the estate (your bundle licence runs them all)
export ALGOVOI_LICENSE_KEY="$(cat licence.key)"
algovoi-substrate2-controlplane # control panel + policy bridge
uvicorn algovoi_command_center.app:create_app --factory --port 8200 # Compliance Command Center
```
The extractor verifies your licence against AlgoVoi's issuer key, then decrypts and writes each wheel
with a SHA-256 integrity check. Nothing installs unless the licence is valid and unexpired, and it all
happens with no network access. For the full walk-through (accounts, roles, two-factor sign-in, every
console page, the security model, and a verification checklist), see the
[Compliance Suite deployment guide](/vcs-deployment-guide).
**Not the payment estate.** The Verifiable Compliance Suite is the compliance and long-term-data half.
If you need the agentic payment rails (x402, MPP, AP2, A2A across seven chains), that is the separate
[Payment Rails bundle](/payment-rails-sqlite).
## Frequently asked questions
### What is the AlgoVoi Verifiable Compliance Suite?
The Verifiable Compliance Suite is a self-hosted compliance evidence and
long-term records platform. It preserves documents write-once in a
tamper-evident, content-addressed archive, signs every evidence chain with
post-quantum cryptography (Falcon-1024 and ML-DSA-65), and lets anyone verify
integrity offline from the public key alone, with no AlgoVoi software or
network call in the trust path.
### Is the Verifiable Compliance Suite self-hosted or cloud?
It is fully self-hosted and air-gap capable. The entire estate installs and
runs on your own infrastructure from a single encrypted deliverable, with no
cloud service, no phone-home, and no PyPI dependency at runtime. A Falcon-1024
licence is both the decryption key and the runtime licence, so nothing contacts
AlgoVoi to install, run, or verify.
### Is it a self-hosted alternative to Preservica and Arkivum?
Yes. Preservica and Arkivum are cloud-first managed preservation platforms. The
Verifiable Compliance Suite runs the equivalent long-term preservation estate on
your own servers under your own keys, adds post-quantum signatures and
offline-verifiable integrity that those platforms do not offer, and is licensed
once perpetually rather than as an annual subscription. See the
[Arkivum alternative](/arkivum-alternative) and
[Preservica alternative](/preservica-alternative) pages for the detailed
comparison.
### What makes the archive tamper-evident?
Every record is stored write-once in a content-addressed archive and bound into
a Falcon-1024-signed hash chain. Altering, reordering, or removing any record
breaks the signature, which anyone can detect offline. Records are removed the
compliant way: a legal hold blocks deletion, and a signed erasure tombstone
leaves cryptographic proof the record existed after its content is shredded.
### How does post-quantum signing protect long-term records?
Records that must survive for decades will outlive today's classical signature
algorithms once a cryptographically relevant quantum computer exists. The suite
signs with Falcon-1024 and ML-DSA-65 (both NIST post-quantum standards) and
seals with ML-KEM-1024, so evidence signed today stays verifiable through the
post-quantum migration rather than becoming forgeable.
### Can the evidence be verified offline or in an air-gapped environment?
Yes. Verification needs only the record, its signature, and the published public
key. There is no issuer call, no registry lookup, and no network dependency, so
an auditor or regulator checks the evidence on an air-gapped machine using a
bundled offline verifier. Sealed containers (.acv) open with a self-contained
extractor that imports no AlgoVoi software.
### Which regulations does the suite provide evidence for?
The suite produces the tamper-evident, independently verifiable evidence
underlying HIPAA (audit controls and integrity), GDPR (right to erasure,
integrity and confidentiality), eIDAS (RFC-3161 qualified timestamps), 21 CFR
Part 11 (IQ/OQ/PQ validation), EU AI Act Articles 12/19/26 record-keeping, and
MiCA/DORA logging. Your counsel certifies compliance; the suite provides the
evidence certification rests on.
### How much does the Verifiable Compliance Suite cost?
It is a one-time purchase on a perpetual licence, bought self-serve from the
[suite store](https://api.algovoi.co.uk/suite-store). One licence installs and
runs the whole estate (Substrate 2 core, Compliance Command Center, Records
Vault, and the full evidence stack) with no per-seat or per-record fee and no
recurring subscription.
### How do I verify a record without AlgoVoi software?
Each record recomputes from its own canonical bytes: canonicalise under RFC 8785
(JCS), hash with SHA-256, and check the Falcon-1024 signature against the
published public key. The conformance corpus ships a first-principles verifier
that rebuilds the bytes with standard libraries only, so the result is a
property of open standards, not of AlgoVoi's code.
## See also
* [EU AI Act record-keeping](/eu-ai-act-recordkeeping) -- meeting Articles 12, 19, and 26 (automatic AI decision logging, six-month-plus retention, tamper-evident integrity) with the estate; Annex III obligations apply from 2 August 2026.
* [Regulated-records self-hosting guide](/regulated-records-self-hosting-guide) -- what a compliant self-hosted preservation estate requires: RFC-3161 timestamping, tamper-evident audit logging, legal and e-discovery holds, and offline verification.
* [Post-quantum evidence longevity](/post-quantum-evidence-longevity) -- how Falcon-1024 and ML-DSA-65 signing keeps the suite's evidence verifiable for decades, plus bring-your-own-key custody.
* [SCIM 2.0 provisioning](/scim-provisioning) -- auto-provision Command Center operators from Okta, Azure AD, or OneLogin, with every provisioning event on the signed audit chain.
* [Compliance Suite deployment guide](/vcs-deployment-guide) -- the full install, roles, MFA, and verification walk-through.
* [Arkivum alternative](/arkivum-alternative) and [Preservica alternative](/preservica-alternative) -- honest comparisons for teams evaluating the suite against managed cloud preservation platforms.