MapsHub is under active development — request early access
Vault is the heaviest compliance surface in the MAPS™ ecosystem — role-based access, secure enclaves, encrypted storage, and an immutable audit trail, purpose-built for diligence and post-merger collaboration. SOC 2 Type II aligned and ISO 27001 aligned (self-assessment); no SOC 2 report or ISO certificate issued.
A working module ledger — the surface we are building against. Module names are final; compliance posture is a self-assessment; release sequence is indicative.
Granular access mapped to MAPS™ pillars and deal stage. Permissions move with the transaction — discovery, diligence, integration — so the right counterparties see the right corpus at the right moment.
Encrypted workspaces for each transaction, with isolation between deal teams. Counterparty corpora never co-mingle, and revocation is instantaneous — sessions, downloads, watermarked extracts all expire on signal.
AES-256 at rest and TLS 1.3 in transit. Model traffic uses authenticated Cloudflare AI Gateway sole egress; regulated PHI workflows are not enabled.
Immutable, queryable audit trail across every document, every counterparty interaction, every export. Logs are first-class data — they feed the Navigator compliance dashboard and our SOC 2 self-assessment.
Threaded review, side-by-side redlining, and structured Q&A — purpose-built for diligence and post-merger collaboration. Designed for the heaviest compliance surface in the ecosystem, not retrofitted from a general workspace tool.
Diligence is the heaviest surface in the deal — the infrastructure underneath it should be the most considered.
— Platform doctrine. Vault is engineered to compliance-first posture from the first commit. Its controls are mapped to SOC 2 and ISO 27001 as a self-assessment; no SOC 2 report or ISO certificate has been issued.
Waitlisted practitioners receive module previews and first access when Vault opens. We notify individually — never via blast.
Join the waitlist