Feature overview

Platform overview

Conditional-access vaulting across the lifecycle

Start with a quick summary, then dive into the areas that matter most to your team. Each section includes controls, signals, and outcomes Torvus manages for you.

Policy engine Duress & decoys Recipient verification Audit & provenance Developer surface Platform hardening

Policy engine

Compose inactivity windows, quorum approvals, and contextual signals. Preview outcomes before they go live.

Explore details

Duress & decoys

Freeze releases silently or hand over decoy packages while audit evidence continues to build.

Explore details

Recipient verification

Bind recipients to verified identities. Require passkeys first with TOTP fallback only where policy demands.

Explore details

Audit & provenance

Every release records who requested, who approved, and which controls passed with tamper-evident receipts.

Explore details

Policy engine

Compose inactivity windows, quorum approvals, and contextual signals. Preview outcomes before they go live.

Compose predicates from time windows, inactivity grace, quorum approvals, and external signals like attested TEE oracles.
Dry-run policies with simulated scenarios, showing pass/fail reasons for each predicate before deployment.
Version-controlled policy history with rollbacks, approvals, and automated notifications to stakeholders.

Duress & decoys

Freeze releases silently or hand over decoy packages while audit evidence continues to build.

Hardware and software duress triggers freeze releases in seconds while notifying designated responders.
Safe-mode content lets teams replace sensitive data with controlled narratives when working under observation.
Every duress state change is logged with provenance and can fan out to downstream security orchestration tools.

Recipient verification

Bind recipients to verified identities. Require passkeys first with TOTP fallback only where policy demands.

Passkeys backed by device attestation provide phishing-resistant authentication with minimal friction.
Policy-based release bundling ensures each recipient only sees the sealed material they are authorised to handle.
Optional KYC and IDV gates for estate executors, counsel, or investigative teams working across jurisdictions.

Audit & provenance

Every release records who requested, who approved, and which controls passed with tamper-evident receipts.

Integrity-checked audit trails stored in append-only logs replicated to customer-controlled destinations.
Data lineage for uploaded assets, including hashing, classification, and optional out-of-band validation events.
API-first reporting so governance teams can plug Torvus evidence directly into compliance workflows.

Developer surface

APIs and webhooks let you orchestrate policies from CI/CD, ticketing, or custom runbooks without sacrificing control.

Declarative policy definitions versioned in Git with automated validation on pull requests.
Event-driven webhooks for policy state changes, approvals, and release outcomes.
Language SDKs for vault ingestion, sealed key distribution, and recipient provisioning.

Platform hardening

Infrastructure attested through HSM-backed splits, hardware-backed secrets, and aggressive anomaly detection.

Keys sealed inside HSM/TEE shards with quorum release and integrity monitoring.
Continuous posture scanning with automated fix pathways and customer-visible status digests.
Strict CSP, isolated runtime sandboxes, and environment-level guardrails across every deployment.