Isolated by design
Each vault is a separate workspace - balances, API keys, and strategies don't bleed across. Blow up one vault, the rest stay clean.
A vault is a workspace - one venue or many, isolated balances, scoped API keys, and a hard kill switch. Every strategy and every flow runs inside one. You keep custody at the venue; we keep the orchestration crisp.
Whatever tier you pick, these four properties stay constant. The differences sit in capacity and where the platform runs - not in safety primitives.
Each vault is a separate workspace - balances, API keys, and strategies don't bleed across. Blow up one vault, the rest stay clean.
Connect via venue-issued API keys with the smallest privilege set required. Keys never leave the secure store, and rotation is a one-click operation.
Park a vault from any surface and every running flow halts within milliseconds. The danger-confirm dialog catches accidental panics.
Subscriptions, balances, orders, trades, and transactions stream into a five-tab detail view backed by the real-time event bus.
Start small, grow into the next tier when the strategies you're running outgrow the workspace. State carries forward; nothing is rebuilt.
One venue, one isolated subaccount.
The cleanest first step. A single venue, a dedicated subaccount, scoped API keys, and the same flow + strategy primitives that power everything heavier. Use it as a sandbox, a paper account, or as a real-money production vault for one strategy.
Up to 5 venues under one workspace.
Where most operators land once they outgrow a single venue. Cross-venue arb, hedged baskets, unified P&L, and a single-pane operational view across every connected exchange. Strategies can target one venue, all of them, or rotate.
Margin, perps, and futures - on the same primitives.
Leverage with discipline. Funding-aware position management, forced-liq guardrails, and a margin model that surfaces real numbers instead of euphemisms. Built so a strategy can switch between spot and derivatives without rewiring.
Regulated-entity grade. Audit-ready by default.
Everything in Leverage Vault plus the compliance layer baked in: segregated key vault with mTLS + AES-256-GCM, withdrawal whitelisting enforced at the vault perimeter, barrier-based key revocation, auditor read-only role, immutable activity log, and quarterly attestation reports - for the questions external auditors and fund admins ask first.
Run the entire vault stack on your own infrastructure - on request.
Available for select customers. Same UX, your hardware, your network, your audit trail. Annual license includes a reproducible image, the control plane, and updates. We engage on Sovereign deployments after a scoping call - retail growth is the priority right now.
| Solo Vault | Atlas Multi-Vault | Leverage Vault | Sovereign Vault | ||
|---|---|---|---|---|---|
| Connected venues | 1 | Up to 5 | Up to 5 | Up to 5 | Unlimited |
| Concurrent strategies | 3 | 12 | 20 | 20 | Unlimited |
| Margin & derivatives | - | - | ✓ | ✓ | ✓ |
| Cross-venue P&L | - | ✓ | ✓ | ✓ | ✓ |
| Live WebSocket updates | ✓ | ✓ | ✓ | ✓ | ✓ |
| Hard kill switch | ✓ | ✓ | ✓ | ✓ | ✓ |
| Immutable audit log + auditor role | - | - | - | ✓ | ✓ |
| Withdrawal whitelist enforced | - | - | - | ✓ | ✓ |
| Hosted by | TradeMire | TradeMire | TradeMire | TradeMire | You |
| Billing | Monthly | Monthly | Monthly | Monthly | Annual license |
Managed vaults are TradeMire's responsibility to keep alive. Sovereign vaults are yours. The platform is identical - the operations boundary moves.
Vault setup is a guided wizard - venue, API credentials, plan, host type, billing cycle - in that order. Most operators are running their first strategy in under ten minutes.