Sandbox keys on day one, and no charge for your first month of production usage. Network fees for the migration itself are covered under the migration offer. Nothing is billed before your integration is live — after the free month you're on the plan your wallet count puts you in.

It's measured against your current invoice, not a list price. Share a recent bill or your signature and wallet volumes and the estimate compares them line by line: Growth is $0.0009 per signature on a $1,200 monthly minimum, Scale is $0.00048 on $2,400, and every paid plan includes 150,000 signatures — three times what comparable platforms bundle.

Your codebase, not your funds. The prompt maps every call into your current provider's SDK onto the Shuttle API — wallet creation, signing, transfers, webhooks — keeps your existing user identifiers so nobody has to re-onboard, and opens a pull request you review. It never sees key material: signing stays inside the enclave, and you run the whole flow against the sandbox before production traffic moves.

Keys are generated and used inside a hardware-isolated enclave. Embedded wallet transactions are authorized by the user; server wallet transactions are authorized by your policies and limits, checked at signing time rather than after the fact. Every operation is recorded in an audit log you can read.

Growth covers up to 2,000 wallets. Past that you're on Scale, where the per-signature price drops from $0.0009 to $0.00048. Below the monthly minimum you pay the minimum; above it, usage pricing applies. Annual billing takes 20% off either plan.

36+ chains on every plan, including the chain-specific work teams usually end up writing themselves: TON jettons and wallet versions, TRON energy and bandwidth, EVM fees, Solana token accounts, Stellar trustlines. Adding a chain is a parameter, not a second integration — the same API covers wallets, transfers and events.

Export your keys at any time, in a format any wallet can import. No proprietary formats, no exit fee, no notice period. We're the ones carrying the risk of you leaving — that's deliberate, and it's the only honest way for a new vendor to ask for your keys.

Nowhere, as a whole key. Custody is split into two shares that only meet inside a hardware-isolated enclave, where they produce one signature and the reconstructed key is discarded immediately. The enclave has no disk, no outbound network and no shell — so an attacker holding your infrastructure, or ours, still has nothing to sign with. Shuttle is SOC 2 certified and the report is available under NDA, along with the whitepaper, the threat model, reproducible build instructions and published enclave measurements.