Custody is a small surface.
Wallets, transfers, policy, audit. We resist the urge to bolt on platform features that don't belong. The smaller the surface, the smaller the blast radius.
Company
Built by people who run custody in production.
zenvault is a Zen Atlas Group product — alongside Zen OTC, Zen Pays, ZenPulse and Zen Wallet. We've operated production custody for the products that fund our infrastructure work. zenvault is the engine we kept wishing existed.
Brand family
The trust layer beneath every Zen product.
Zen is a branded house. Each product line owns its customer experience and its data; zenvault owns the wallets and the signatures. Now we're opening that engine up to teams outside the family.
Zen · brand architecturebranded house
Product families
Zen Markets
- Zen OTC
- Zen Mini Exchange
Zen Payments
- Zen Pays
- ZenPulse
Zen Identity & Risk
- ZenTrust
Zen Consumer
- Zen Wallet
- Zen Card
zv
powers · 4 familieszenvault
custody infrastructure · trust layer
How we work
Four principles, in the code.
Audit is part of the operation.
Security-sensitive writes commit alongside their audit row in the same transaction. There is no "action succeeded, audit dropped" failure mode in our system.
Defaults are the security model.
Every defensive primitive is on by default. There is no checkbox to flip for replay protection, scoped keys, or fail-closed audit. If it shipped, it is enforced.
Honest about the roadmap.
We don't claim certifications we don't hold. We don't ship status pages with green dots when there are open incidents.
Get in touch
We pick up.
Sales calls, pen-test scoping, 11pm production questions — the same person who wrote the code that broke is on the other end of the line.