Skip to main content
Company Wallets are custodial wallets owned and operated by your organization. Your team controls who can sign, what they can sign, and under what conditions. The wallets belong to your business; 0xkey provides TEE-backed infrastructure to operate them securely at scale. Where Embedded Wallets give each end user their own wallet, Company Wallets centralize control within your organization. Backend services, operators, and automated systems sign through the Public API, governed by role-based access and the policy engine.

​
Why Company Wallets

  • Keys never leave the enclave. Signing happens inside AWS Nitro TEEs; only signatures are returned.
  • Deny-by-default policies. CEL rules evaluated in-enclave control recipients, contracts, selectors, chains, and values.
  • Multi-party approval. Require N-of-M consensus (or root quorum) before sensitive activities complete.
  • Server-first integration. API keys + @0xkey-io/sdk-server / Go SDK — no end-user Auth Proxy dependency.
  • Custodial send. Build, policy-check, sign, and broadcast on EVM, Solana, and Tron in one activity.
  • Enterprise gas sponsorship. Platform paymaster / fee-payer on supported chains (Enterprise plan).
  • Import / export. HPKE-protected wallet and key migration without plaintext key exposure.
  • Verifiable TEE. Remote attestation and boot/app proofs for independent verification.

​
How it works

Your backend authenticates with an API key. Inside the enclave, the policy engine evaluates the request. If allowed (and any required approvers have voted), the signer produces a signature or the coordinator completes a custodial send. Private keys never leave the TEE.

​
Access control model

Company Wallets use a parent organization (sub-organizations for tenant isolation). Within that org you define:
  • Users — human operators and API-only service accounts
  • Tags — role groups (e.g. deployer, treasury-ops, sweeper)
  • Policies — CEL effect + condition + optional consensus
  • Root quorum — threshold for org-level sensitive changes
See Policies, Root quorum, and Transaction management.

​
Company Wallets vs Embedded Wallets

​
Building with 0xkey

  1. Company Wallets quickstart — API key → wallet → sign / send
  2. Integration guide — policies, consensus, webhooks
  3. Policy templates — treasury 2-of-N, allowlists, agent deny
  4. Remote attestation — production verification checklist

​
Use cases

​
SDKs

​
Chain support (Company path)

​
Enterprise contact

For Enterprise plan (gas sponsorship, custom limits, private migration assistance): hello@0xkey.io.