Thestrongroomfordigitalassets.

Hold and move digital assets and tokenized real-world assets (RWAs) for your fintech, exchange or payments company. Every withdrawal clears your policies, your approvers and a hardware-backed signature before it goes on-chain.

0/4Screening the destination250,000.00 USDC on Base

Custody and treasury. One set of controls.

Keep your digital assets safe, and run the money in them with the same policies, approvers and audit trail.

Six states between send and settled.

Most custodians give you a spinner. Blaaiz Vault shows every check a withdrawal clears, who cleared it and when. Here is one request, start to finish.

Withdrawalsr_01J9Q4X7M2

Pending policy evaluation

0.00USDC

Initiated by
Amara Obi Treasury
Policy
Evaluating
From
Treasury vaultBase
To
Settlement partner0x7a3f…91c2
Approvals
DKFA0 of 2
Signature
Not signed
Transaction
Not broadcast
Confirmations
0 / 12

Activity

Write the rules once. Every withdrawal obeys them.

Policies read like sentences, and so does the test. Drag any underlined number, or pick a different destination or person, and watch the decision change.

Test a withdrawal

Send 250,000 USDC to , requested by , with 600,000 USDC already sent in the last 24 hours.

Policies

4 of 4 active

  • Unknown destinations

    Reject when the destination is new and the amount is over 10,000 USDC.

    Not matched

  • Large transfers

    Ask Daniel Kariuki and Funmi Adeyemi when the amount is over 100,000 USDC.

    Matched

  • Daily limit

    Ask the CFO when more than 1,000,000 USDC leaves in 24 hours.

    Not matched

  • Operations team

    Ask the treasury lead when anyone in Operations starts a withdrawal.

    Not matched

Decision

For this withdrawal

Require approval

Because the Large transfers policy matched.

Waiting for

  • DKDaniel Kariuki
  • FAFunmi Adeyemi

evaluation #1,204 written to the audit log at 14:01:07

Every vault has its own box.

Each vault is its own multisig wallet, with its own address on one network. Like a box in a strongroom, it takes more than one key to open. Pick one to look inside.

Open a vault

Example vaults and balances.

Everything custody needs after the key.

Signing is one step. The rest is deposits, screening, sweeps, books and reserves, and they are one system. Follow a single deposit through it.

Follow the money

Simulated

  1. Deposit

    608.19USDT on BNB Smart Chaintx 0xc287…1290
  2. Screening

    CheckingSanctions and exposure0x6469…a200
  3. Sweep

    WaitingInto Treasury vault

    today 1,284,410.55

  4. Ledger

    Dr, pendingCr, pending

    balanced

  5. Reserves

    %

    of customer liabilities

    on-chain 6,398,865.10

Recent deposits

Each one screened and booked

FromStatus
  • 0xe43b…85ccSwept
  • 0xec18…eba9Swept
  • 0x8be0…4886Held
  • 0x5658…93e7Swept
  • 0x556c…e1d1Swept

Ledger

Double entry

Debit

Credit

Vault custody

Business liability

In-transit250,000.00

Compliance hold

Total

Total

Debits equal credits

Roles

5 of 14 permissions shown

PermissionTreasuryApproverViewer
View vaults
Initiate withdrawals
Approve withdrawals
Manage policies
Manage address book

Incidents

Payouts is active

Freeze a vault in one move. Every request stops, and the trail records who did it and why.

  1. 09:14Unusual withdrawal pattern flagged on Payouts
  2. 09:12Velocity alert: 6 requests in 4 minutes

Built for money that crosses borders. Connected to global markets.

Most custodians are built for one market. Vault is built for cross-border flows, with onboarding, screening and support for entities across regions and time zones.

Corridors

Example routes

Networks
Ethereum, Base, Polygon, BNB Smart Chain
Digital assets
USDC, USDT
Built for
Remittance and payments companies, exchanges, neobanks and corporate treasury teams

One request to move money. Every gate still applies.

The API goes through the same policy engine, approvals and signing as the dashboard. Your code cannot skip a control that your team set.

Protocol
REST over HTTPS, JSON
Amounts
Decimal strings, never floats
Statuses
PENDING_POLICY_EVAL to CONFIRMED
API keys and sandbox
Coming soon

POST/v1/vaults/{vault_id}/withdrawals

  1. const res = await fetch(
  2. `${API}/vaults/${id}/withdrawals`,
  3. {
  4. method: "POST",
  5. headers: {
  6. Authorization: `Bearer ${token}`,
  7. },
  8. body: JSON.stringify({
  9. asset: "USDC",
  10. network: "BASE",
  11. // amounts are strings, never floats
  12. amount: "250000.00",
  13. destination: "0x7a3f…91c2",
  14. }),
  15. },
  16. );
  17. const { data } = await res.json();

Response

No response yet

Press Send or ⌘↵ to run the example.

Status events

  1. 201PENDING_POLICY_EVAL0.28s
  2. 200PENDING_APPROVAL1.15s
  3. 200APPROVED2.35s
  4. 200SIGNED3.15s
  5. 200SUBMITTED3.85s
  6. 200CONFIRMED5.25s

Six layers between anyone and your funds.

Custody is a stack of controls, and each one fails closed. Pick a threat and watch where it stops.

Try to break in

What if ?

  1. 01Role-based access14 permissions, checked on every request.Waiting
  2. 02Security-key approvalsApprovers confirm with a security key. Nobody approves their own request.Waiting
  3. 03Encrypted at restData and documents are encrypted. No private key sits in the database.Waiting
  4. 04Dedicated HSM keysYour own signing key, created in KMS. It never leaves.Waiting
  5. 05Multisig walletTwo independent keys must sign. One is kept offline.Waiting
  6. 06Audit trailEvery attempt, approval and signature, with who and when.Recording

Outcome

Checking…

They can request a withdrawal, but they cannot approve their own, and approvers confirm with security keys that cannot be phished. Nothing is approved.

14:02:11 approval.self_approval_blocked

Built to international standards.

Our information security and business continuity follow ISO 27001 and ISO 22301.

  • ISO 27001 certifiedISO/IEC 27001Information security management
  • ISO 22301 certifiedISO 22301Business continuity management

What we are building next.

The platform is live today. This is what lands next, in the order we are shipping it.

Want it first? Join early access

  1. In development

    API keys and a sandbox

    Scoped API keys for your own systems, and a sandbox with test funds so your engineers can build the whole flow before go-live.

  2. Next

    Self-service vault freeze

    Freeze or restore any vault yourself from the dashboard, in one move, with the same audit trail behind it.

  3. Planned

    More networks

    Arbitrum, Optimism and Avalanche, followed by Tron and Solana, each with its own vaults.

  4. Planned

    DAI and more digital assets

    DAI first, then the dollar and local-currency assets our customers ask for.

Questions your risk committee will ask.

Straight answers on keys, controls, compliance and integration.

Not here? Ask a custody specialist

Custody

  • Your business gets its own signing key, created in KMS hardware security modules, and its own offline recovery key. Neither is shared with another client, and the signing key is never exported. Each vault is a multisig wallet that needs two of three keys to sign: your KMS key, your recovery key and a platform key.

    See the vault open

Controls

Compliance

Integration

Open your first vault with people who know custody.

Answer three questions and watch your setup plan take shape. A custody specialist then reviews it with you and tailors it to your entities and approval flow.

What do you need?

Monthly digital asset volume

Networks2 selected

Setup plan

Draft

Your company

Custody, $1M to $10M a month

Vaults
Treasury and Collections vaults
Networks
Base, Polygon
Approvals
2 of 3 approvers above 100,000 USDC
Starter policies
Large transfers, daily limit, unknown destinations
Reporting
Monthly proof of reserves

A starting point. Your specialist tailors it.