Bring the chains
you already hold.
Need another network?
We add networks on request. Each chain runs as its own adapter behind the same signer, policy engine and audit trail, so a new network never changes how your keys are held.
Run it on
the cloud you trust.
The same signer, policy engine and audit trail on each cloud, in your own account. The signer runs in the provider's attested enclave and its KMS releases keys only to the measured signer image.
Nitro Enclave
Deploy on AWS
- Signer inside an AWS Nitro Enclave, attested on every boot
- Keys released by AWS KMS only to the measured enclave image
- Runs on Amazon EKS in your own AWS account
Confidential Space
Deploy on Google Cloud
- Signer inside a Confidential Space workload, attested on every boot
- Keys released by Cloud KMS only to the attested workload image
- Runs on Confidential VMs in your own Google Cloud project
QingTian Enclave
Deploy on Huawei Cloud
- Signer inside a Huawei Cloud QingTian Enclave, attested on every boot
- Keys released by Huawei Cloud KMS only to the measured enclave image
- Runs on Huawei Cloud CCE in your own tenant
Everything it takes to hold assets
without holding your breath.
Sealed signer
Keys exist only inside an attested enclave.
Key isolation
Not even our operators can reach your keys.
Tamper-evident audit
Every action is hash-chained and replayable.
Quorum approvals
Value-tiered rules decide who approves, signed on each approver's own key.
Unlimited vaults
Segregated vaults on demand, each with its own address on every network.
Scoped access
Roles bound to vaults, assets and chains; privileged actions need a second factor.
One governed path to the chain.
- Submit a request: Every transfer starts as a typed intent. API, console or SDK · idempotent by key
- Check policy: Policy decides before anyone signs. Versioned rules · evaluated on every intent
- Reach quorum: No single person can move funds. Approvers sign with passkeys
- Sign & broadcast: Signed in the enclave, sent on-chain. Keys never leave attested hardware
Put custody behind every flow
you run daily.
Withdrawals clear policy and quorum automatically; larger ones wait for your approvers before anything is signed.
Custody sized to
your balance sheet.
Every deployment is scoped with you: networks, approval tiers, approver roster and where the signer runs. Tell us what you hold and we will come back with a plan.
- 01
Dedicated enclave signer
Isolated per client, attested on every boot
- 02
Policy design workshop
Approval tiers mapped before go-live
- 03
Migration support
Existing wallets moved through a recovery ceremony
- 04
Named engineering contact
A direct line to the team running your stack
What happens next
- We reply with a few scoping questions
- A 30-minute call with an engineer
- Sandbox workspace and a written proposal
A server shares its memory with the operating system and everyone who can log in to it. Our signer runs in an attested enclave with no shell, no network and no persistent storage, and it only unseals keys after KMS verifies its attested image.