Keep Every Record Without Keeping the Risk
Envelope-encrypted storage, multi-party approval workflows and a policy engine that enforces your rules — every view, edit and signature on one auditable trail.
Records are where accountability becomes enforceable. A document is bytes, an approval is a row in a database, and a retention rule is a state machine — until the moment something goes wrong, at which point the only thing standing between an enterprise and a lost record is the engineering we did last year. Vault was built for that moment: envelope-encrypted storage where files never exist in plaintext at rest, multi-party approval workflows that keep every signer honest, and a policy engine that enforces your retention schedules, approval quorums and time locks as versioned, tested, immutable rules — not suggestions. Every view, edit and signature lands on one auditable trail that your auditors can read end-to-end.
We refuse the superstition that an "archive" means "compressed and forgotten". Our vault is online enough to be useful — operators can retrieve, audit access, and reconcile against the source systems in minutes, not days — and locked down enough to be safe, because the boundary between those two states is a policy engine your auditors can read, not a magic switch someone hopes to remember. Retention and access proofs ship daily, signed and timestamped, and your compliance team will accept them — not a quarterly export that lands three weeks after the quarter closed. The boring tools — envelope encryption, Postgres, Kafka, Rust — are boring on purpose. Exciting records management is a liability we cannot afford.
Key Capabilities
Multi-Party Approval Workflows
Drafter, reviewer, department head, auditor — state machines that keep every party honest and no document stuck.
Policy Engine
Retention schedules, approval quorums, time locks and device rules — versioned, tested, immutable in production.
Envelope Encryption
Per-document keys wrapped by KMS, dual-control rotations, tamper-evident logs — your files never exist in plaintext at rest.
Compliance-Grade Reporting
Daily retention and access proofs your auditors will actually accept.
Built With
Documents under management
Approval decisions / month
Records lost since launch
How It’s Built & Delivered
Architecture
Modular monolith with extracted key-management services; every boundary decision recorded as an ADR you can read.
Verification
Idempotency and quorum logic covered by 4,100+ tests; chaos drills rehearse KMS-region failure quarterly.
Delivery
Every release rides the gated pipeline: review, scans, signed provenance, canary, automatic rollback.
Success Stories
Nile Logistics Group
11M freight documents under retention, zero record losses in 3 years
Sahara Retail Group
Contract approval disputes down 92%, turnaround from 14 days to 4 hours
Vault questions
How are key rotations conducted?
Dual-control, tamper-evident logs, KMS-backed wrapping; document keys never exist in plaintext at rest. Every rotation is replayable from the audit log on demand.
Can the policy engine be audited?
Yes — versioned, tested, immutable in production. Every rule your auditors can read; every change ships through expand–contract review and is recorded as an ADR.
What happens if the KMS region fails?
Quarterly chaos drills rehearse it; the system degrades to read-only access, alerts the on-call, and no key is lost. The failover path is tested before the forward path ships.
How are retention proofs generated?
Daily, signed, and timestamped — your compliance team will accept them, not a quarterly export that lands weeks after the quarter closed.
Does it satisfy SOC 2 and ISO 27001 evidence requirements?
Yes. Daily retention and access reports, generated from the same audit log your auditors read — evidence in seconds, not weeks of export engineering.