Fireblocks is the institutional digital-asset infrastructure provider founded in 2018 that supplies key-management, transfer, tokenisation, and DeFi-access plumbing to banks, exchanges, asset managers, and fintech issuers. The platform is built around MPC (multi-party computation) key management, a policy engine for transfer authorisations, and a network of pre-connected counterparties for settlement. Unlike a federally chartered trust bank (Anchorage) or a state-chartered qualified custodian (Zodia Custody, BitGo, Coinbase Custody Trust), Fireblocks operates a technology-and-infrastructure model where the regulated custody perimeter sits with the customer (the bank, the exchange, the issuer) rather than with Fireblocks itself. For an institutional tokenisation operator, Fireblocks is the most-cited example of the back-end infrastructure provider that quietly sits behind a large share of regulated-counterparty digital-asset flows in the US, EU, and Asia.
What it does
Fireblocks supplies four main product surfaces. First, the wallet-and-custody-tech infrastructure: an MPC-based key-management system that splits private-key shares across multiple parties (Fireblocks, the customer, optionally a third-party signer) so that no single party can move funds unilaterally. Second, a transfer-policy engine that lets institutional customers codify approval workflows, velocity limits, counterparty allow-lists, and segregation-of-duties controls on every outbound transfer. Third, the Fireblocks Network, a pre-connected counterparty graph that lets institutional customers settle against named exchanges, OTC desks, and other Fireblocks-using counterparties without re-onboarding wallet addresses for each settlement. Fourth, a tokenisation engine and DeFi-access layer that lets banks and asset managers mint tokenised products and integrate with permissioned DeFi venues from inside the same institutional perimeter.
The legal stance is structurally important. Fireblocks itself is not, in the canonical sense, the qualified custodian for the customer's assets. The customer holds the regulated custody perimeter (the bank licence, the SEC qualified-custodian status, the relevant local-regime equivalent), and Fireblocks supplies the technology stack that the customer uses to discharge that custody obligation. A second mode is the partner-custody arrangement, where Fireblocks integrates with a regulated custodian (a trust company, a bank-chartered subcustodian) and the customer takes regulated coverage from that partner.
Tokenisation and platform footprint
The named participation threads are concentrated in three areas. First, the bank-and-fintech back-end: Fireblocks publicly cites named tier-one bank, neobank, and payments-fintech customers across the US, EU, and Asia. These institutions use the platform to run digital-asset desks, stablecoin treasury operations, and tokenised-product issuance from inside their existing regulated perimeter. Second, the tokenisation-platform layer: Fireblocks's tokenisation engine is used by issuers running tokenised-fund and tokenised-securities programmes, with the platform providing the issuance, transfer, and lifecycle-management mechanics. Third, the stablecoin-issuer toolchain: Fireblocks supplies parts of the infrastructure stack used by named stablecoin issuers for treasury operations, mint-and-burn flows, and reserve-attestation support.
The APAC presence is real and growing. Fireblocks operates client-facing teams across Singapore, Hong Kong, Japan, and Australia, with named institutional users across the regional bank, exchange, and fintech set. The platform shows up in the back-end of several APAC tokenisation programmes without surfacing in the headline branding.
Regulatory positioning
Fireblocks itself holds a set of jurisdiction-specific licences and registrations across markets where the platform operates as a regulated-counterparty itself (rather than purely as an infrastructure vendor to a regulated customer). The US licensing footprint includes state money-transmitter licences in the relevant set, with the customer-facing custody perimeter typically sitting with the customer or with an integrated regulated-custodian partner. In EMEA, Fireblocks holds VASP-style registrations in the relevant jurisdictions, with the EU MiCA regime under EU MiCA now the dominant framework. In APAC, Fireblocks operates through a combination of local-entity registrations (where the activity touches a regulated perimeter) and infrastructure-vendor relationships (where the customer is the licensed party).
The structural read for an institutional tokenisation counterparty is that Fireblocks is the platform that the regulated counterparty runs on, rather than the regulated counterparty itself. The contractual stack therefore involves a primary engagement with the regulated bank or trust company and a back-end engagement with Fireblocks for the technology layer.
Recent activity
- 2024-2026. Continued expansion of named bank and fintech customers across US, EU, and APAC, with the SAB 121 rescission removing one of the structural constraints on US bank customers building digital-asset operations on Fireblocks.
- 2024-2026. Tokenisation-engine activity expanded as more issuers ran tokenised-fund and tokenised-securities programmes through the platform; the consolidated mandate map is not consistently disclosed.
- The competitive map continued to evolve as several Fireblocks competitors (BitGo, Anchorage, Zodia, the bank-internal custody desks) pursued different combinations of trust-charter, qualified-custodian, and infrastructure-platform positioning.