Operate in the bank
The platform runs in the bank’s data centre without a foreign SaaS dependency. Network tracks chain availability and incidents; 46 operations runbooks support platform operations.
Modules
Network
BUSINESS CONTINUITY
Keep custody operations in your institution’s hands.
Combine control of the deployment with an explicit recovery design and verifiable software releases.
Talk to salesBuilt for
- Bank operations teams
- Security teams
- Infrastructure teams
Capabilities for your workflow
Verify the release
Signed images, an SBOM and reproducible build inputs apply across the platform, including Vault Settings. Source code escrow supports the bank’s continuity arrangements.
Modules
Vault Settings
Plan recovery authority
Customer-controlled recovery uses two escrow holders. Vault Actions provides proactive share refresh and the kill switch.
Modules
Vault Actions
How it works
Define responsibilities
Agree the bank’s operating responsibilities, recovery authority and release acceptance criteria.
Verify before operation
Use signed images, the SBOM and reproducible build inputs to verify the deployed release.
Govern routine signing
Policy checks and maker-checker approval precede biometric approval and joint device/platform signing.
Prepare for disruption
Use the runbooks, kill switch and customer-controlled recovery design; preserve decisions in the WORM log.
- Policy engine
- Maker-checker approvals
- Transaction limits
- Address whitelists
- Immutable WORM evidence log
