MapsHub is under active development — request early access
A working module ledger — the surface we are building against. Module names and compliance posture are final; 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, TLS 1.3 in transit, BYOK-capable at launch for clients who require it. Storage is region-scoped so HIPAA-tagged corpora can be pinned to Bedrock-routed inference instead of Anthropic-direct.
Immutable, queryable audit trail across every document, every counterparty interaction, every export. Logs are first-class data — they feed the Navigator compliance dashboard and the SOC 2 evidence pipeline.
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; SOC 2 and ISO 27001 are not retro-fitted after launch.
Waitlisted practitioners receive module previews, the SOC 2 evidence summary, and first access when Vault opens. We notify individually — never via blast.
Join the waitlist