Fireblocks for your treasury. Fortkey for your trading.
Fireblocks was built to secure assets at rest. When the job is low-latency execution, desks run Fortkey alongside it: a purpose-built trading wallet, microseconds from your venues.
Full p50/p99 benchmarks publishing soon.
Assets at rest
Fireblocks
Treasury, assets at rest
Hot path
Fortkey
Trading, hot path
Venues
Two jobs, two tools
Securing assets at rest and executing trades at speed are different jobs. Neither tool replaces the other.
Fireblocks: treasury
Fireblocks stays the system of record for custody, and stays exactly as configured.
- Treasury and assets at rest
- Governance and administration
- Cold storage
- Long-term custody
Fortkey: trading
Fortkey is the purpose-built wallet for latency-sensitive execution.
- Hot-path signing
- Per-order policy checks
- Co-location, microseconds from venues
- One wallet: HFT, API, and manual modes
How desks set it up
Create Fortkey vaults
Trading keys are generated fresh inside your own enclaves. Nothing is exported from Fireblocks.
Fund the trading float
Transfer the trading float from Fireblocks under your existing approval flows. Your treasury stays exactly where it is.
Trade, then sweep
Trade in HFT, API, or manual mode on the same keys. Sweep PnL back to treasury on your own schedule.
What changes and what does not
What stays the same
- Your Fireblocks setup is untouched
- Governance stays intact
- The trading float moves under your own approvals
What you gain
- Sub-1ms signing on the execution path
- One wallet for every mode: HFT, API, and manual
- No in-house signer to build and maintain