Policy engine
Define spend limits, approval thresholds, time windows, and guardians.
Design your custody like a product: multisig, time‑locks, spending policies, approvals, and tested recovery — built for teams and long‑term holdings.
Define spend limits, approval thresholds, time windows, and guardians.
Descriptor‑based multisig with flexible quorum (e.g., 2‑of‑3, 3‑of‑5).
Add delays to high‑risk spends and enable inheritance after a timelock.
Structured setup with checklists, shard distribution, and location plans.
Periodic restore tests with documented steps and sign‑off.
Watch‑only wallets for finance and proof‑of‑funds/signing workflows.
Define quorum, roles, limits, and time‑locks with stakeholders.
Generate and verify keys on approved devices; plan storage locations.
Deploy descriptors, addresses, and watch‑only views for finance.
Initiate spends, collect approvals, and keep audit‑ready logs.
Long‑term holdings with strict policies and delayed withdrawals.
Shared governance for small teams with role‑based approvals.
Designate beneficiaries with time‑locked recovery paths and documentation.
Compatible with common, standards‑based signing devices and PSBT flows.
Watch‑only for finance; exports and webhooks for reconciliation.
Connect to your node for address derivation and transaction broadcasting.
No. Plan B Vault is designed for self‑custody; you control the keys.
Quorum design and recovery drills ensure continuity; we document recovery paths.
Yes — policies can require delays, multi‑approvals, and per‑day limits.
Yes — designate beneficiaries and enable time‑locked access with governance steps.
We prioritize multisig for teams; single‑sig flows are available for smaller cases.
Request a demo; we’ll define policies, run the key ceremony, and set up your vault.
We’ll help you design policies, run key ceremonies, and test recovery — end to end.