Fireblocks: digital-asset infrastructure, custody choices and operating controls

Fireblocks supplies the infrastructure behind institutional digital-asset operations: wallets, transaction governance, exchange connectivity and settlement. A brokerage can use it to run treasury movements and client-asset workflows while retaining its own trading, customer-account and risk systems. The first procurement decision is the operating model—customer-controlled infrastructure, a custody relationship, or a combination—because the responsibilities differ.[1]

Off Exchange reduces the need to pre-fund an exchange by separating collateral wallets from trading credit. Fireblocks describes this as reducing counterparty settlement exposure. It is not evidence that every connected arrangement removes insolvency, valuation, liquidation or settlement risk; those outcomes depend on the particular custody and collateral documents.[2]

The public developer stack includes a REST API, TypeScript SDK, Python SDK and Java SDK, alongside a command-line interface. The quick-start path covers an approved API user, a vault account and a test transaction. A sandbox is an integration environment; production requires its own credentials, policy and operational configuration.[6]

A successful transaction-creation response gives an identifier and initial state, followed by approvals, signing and blockchain confirmation. Fireblocks recommends a unique externalTxId to reject duplicate transaction submissions and a lookup before retrying an uncertain request. Its documentation explicitly separates this mechanism from the Idempotency-Key header used by other endpoints. Fee estimation and boost/replace tools address network fees and stuck transactions.[28]

Deployment assistance has separate package terms. Used engineer hours round up to a whole hour, meetings follow regular business hours, and purchased services are non-cancelable and non-refundable even when hours remain or the desired result is not achieved. The public package matrix has inconsistent headings and missing cells; the signed schedule is needed to establish the exact package, hours and validity period.[12]

A publicly filed agreement with NovaBay Pharmaceuticals illustrates the contract layer: its default is a one-year renewal unless either party gives written notice at least 30 days before expiry; renewal price changes require at least 45 days’ notice. Fees are normally non-refundable on order execution, with payment due 30 days from invoice unless the order states otherwise. These are that named client’s terms, not a universal offer.[30]

The hosted platform can retain the customer key share on a mobile secure enclave or an API co-signer. Fireblocks also markets regional hosting in the US, EU, Switzerland and Hong Kong, and KeyLink integration with existing key-management infrastructure. Region selection must be matched to the required features: a hosting choice can change available functionality, not simply the address of the server.[13]

Deposit crediting needs a reconciliation process. The current developer guide says to wait for a completed transaction, obtain a matching or later-height balance event, and compare against blockchain state before crediting an end user. Balance events contain a complete balance, not a change amount. Startup, downtime recovery and some assets require a fallback balance query; that query is not an independent blockchain check.[25]

Essentials is displayed with basic 8×5 support. The separately published Global Support terms apply their Standard package to Pro, Enterprise and Enterprise+; Premium or Platinum benefits require an order-form subscription. Technical incident severity and operational administration requests have different clocks.[11][32]

Premium and Platinum add designated technical account support and recurring reviews. The published comparison gives Premium 20 policy-management change requests annually and Platinum unlimited requests; Platinum also adds an urgent escalation hotline. These entitlements are separate from the technical response table.[17]

NYDFS’s current virtual-currency business list names Fireblocks Trust Company, LLC with a limited-purpose trust charter dated August 2024. Fireblocks’ entity page identifies custody as that company’s service and states that regulated subsidiary services require separate onboarding and contracting. A software customer does not acquire that custody relationship merely by purchasing the platform.[19][20]

Screening is configurable. The developer documentation’s default bypassScreeningDuringServiceOutages setting is true: a missed result can permit an outgoing transfer or release an incoming one. Setting it false instead fails/freezes those flows; delay thresholds vary. TRM Labs has its own timeout policy exception. Rules use first-match order and each screening tool has its own policy. This behaviour is material to a broker’s decision about how transfers proceed during a screening outage.[29]

The August 2026 privacy policy identifies Fireblocks Inc. and affiliates, while the actual contracting company is specified in the service agreement. Its controller policy covers business contacts, platform activity, API metadata, onboarding and support interactions. Retention depends on purpose and legal obligations rather than one published universal deletion period.[21]

Dynamic’s acquisition was announced as completed on 23 October 2025. Fireblocks announced the TRES Finance acquisition on 7 January 2026; current financial-data pages and July product terms incorporate the TRES service. These products are treated within the Fireblocks provider identity here, with their operational and contractual distinctions retained.[4][5][31]

The separate processor DPA, dated 11 March 2025, provides return or deletion of personal data after the relevant service ends, at the controller’s choice and subject to the main agreement. Legal retention and a permitted evidentiary copy are exceptions. It requires notice without undue delay after awareness of covered personal-data incidents; the customer remains responsible for its regulator and data-subject notifications.[33]

Operator

Fireblocks Inc. and affiliated contracting entities; regulated services use separately identified subsidiaries.

Service scope

Digital-asset wallet infrastructure, settlement connectivity, policy controls and operational data for institutions. Qualified custody and other regulated services require separate onboarding and contracts.

Customer types

Institutional trading firms; Brokerages; Exchanges; Fintechs; Banks; Asset managers

Delivery

SaaS; API; Hybrid

Pricing publication

Public and quoted pricing

Platforms

Fireblocks Console; Fireblocks API; Dynamic; TRES Finance

Pricing scope

Public entry-plan pricing and a custom-plan starting price coexist with negotiated services, allowances and add-ons.

Implementation

Hosted platform with role-controlled APIs, customer-hosted co-signers and optional deployment services. Sandbox workflows and regional environments support integration planning.

Support

Plan-specific support portal and escalation arrangements. Standard, Premium and Platinum entitlements and response targets are scoped in the profile.

Permissions and regulatory scope

Fireblocks separates software provision from regulated subsidiary services. NYDFS lists Fireblocks Trust Company, LLC with a limited-purpose trust charter; that entry is not a group-wide software licence.

Provider metadata checked 20 Oct 2026Source 1Source 21Source 9Source 31Source 3Source 13Source 11Source 6Source 32Source 19Source 20Source 4

The product terms make AI use optional and put responsibility for prompts, output suitability and verification on the customer. A conversational interface should therefore be assessed alongside the API role, transaction policy and signing configuration described above.[22]