Sovereign Deployment
QUORUM is deployed inside the institution's own environment — on-premise or in its private cloud — so decision data, models and keys stay under the institution's control. There is no QUORUM-hosted SaaS today.
- Requests, behavioural signals and decision records
- Rules, the audit ledger and SAR/STR cases
- The fine-tuned AI models, which run locally (Ollama)
- Signing keys (Nitro Enclave in production)
- RFC 3161 timestamp requests (a hash only)
- Public sanctions lists and IP-reputation feeds
- Vendor attestation collateral (can be supplied offline)
- An external AI integration for red-team test generation and public threat feeds — switched off entirely with STRICT_ON_PREM=true
In production, the master HMAC key and the ML-DSA-65 key pair are decrypted only inside a measured AWS Nitro Enclave; the application never sees them, and production start-up requires the enclave. Implemented, not yet exercised on Nitro hardware.
FROST (RFC 9591) approvals use distributed key generation, so no single party ever holds the whole approval key.
QUORUM verifies AMD SEV-SNP and Intel TDX evidence against pinned vendor roots and collateral. Not yet run on a QUORUM-operated confidential VM.
Every WebAssembly cryptography module is hash-pinned and checked before it is loaded. Each release comes with a software bill of materials covering 837 components, the licence status, and the dependency-advisory and secret-scan results, and third-party notices ship in the container image.
Signed offline update packages for fully disconnected sites are not provided today.