Workspace Environments

Fireblocks has 3 types of workspaces. The workspace environment you use will determine your capabilities, so it's important to know which workspace type you're working in.

Developer Sandbox environments and Testnet workspaces are used for development and testing. Mainnet workspaces are used to deploy into production (with real funds).

While each workspace type has different capabilities, they utilize the same APIs and SDKs, allowing you to develop and test your code against "lower" environments before deploying to the live production environment.

Workspace Type Comparison

Developer SandboxTestnetMainnet
Workspace TypesQuick ExperimentationDevelopmentStaging/Production
PurposeBuilt specifically for developers to get started using Fireblocks APIs and SDKs quicklyAPI and Console testing on testnet blockchains and assetsProduction environments interacting with mainnet blockchains and assets
AssetsTest assetsTest assetsReal assets
APIFull API access with the most limited rate limitsFull API access with limited rate limitsFull API access with increased rate limits
ExchangesLimited exchange integration support (only testnets)Limited exchange integration support (only testnets)All Fireblocks exchange integrations
FiatTestnet onlyTestnet onlyAll Fireblocks fiat integrations
DeFi/Web3Testnet protocols with WalletConnect Desktop integrationTestnet protocols with WalletConnect Mobile and Desktop integrationsFull support
(requires specific TAP implementation to enable)
Fireblocks NetworkN/AN/A.All Fireblocks Network connections are available
API Co-signerOnly Fireblocks provided API Co-SignerFireblocks-provided or self-hosted API Co-Signer.Self-hosted API Co-Signer
AMLN/AN/AMost assets supported via Chainalysis or Elliptic
TAPNon-editableFully editableFully editable
API User LimitUp to 5 UsersLimited to client settingLimited to client setting
SupportCommunity supportFull Support with Help Center accessFull Support with Help Center access
Mobile AccessN/AFireblocks mobile app to sign/authorize transactions and approve external connectionsFireblocks mobile app to sign/authorize transactions and approve external connection


Mainnet is a production-level blockchain network with cryptocurrency transactions being broadcasted, verified, and recorded. Mainnets have a base asset that can be used as funds in transactions or to pay network fees. All assets on Mainnets have a real-world monetary value.

A Mainnet workspace is a fully developed and deployed environment that allows you and your organization to conduct your real-world financial operations on the Fireblocks platform.

In Mainnet workspaces, you can securely:

  • Transfer digital assets
  • Add users
  • Create a Vault account or multiple
  • Whitelist new addresses
  • Connect to supported exchanges
  • Connect to other Fireblocks Network members
  • Configure MPC-CMP devices
  • Establish network connections


Moving to Mainnet workspaces

Warning: When testing new functions in Mainnet (production) environments, use small amounts first to confirm intended functionality before upscaling to larger amounts.


Testnet is a blockchain test network used by developers to run tests with the blockchain. Testnets operate on their own blockchains, separate from their associated Mainnet. Testnet assets have no monetary value, and many of them reset periodically.

A Testnet workspace is a testing-level environment that only allows you to use Testnet assets for integration and testing purposes. You can also perform many of the same actions you can in a Mainnet workspace without incurring real-world fees.

In the Fireblocks Console, the "Testnet Environment" badge appears at the top of the page to help you identify your Testnet workspace. See a list of Testnets supported by Fireblocks below:

Supported Testnets on Fireblocks
  • Arbitrum Testnet
  • Avalanche Testnet
  • Binance Smart Chain Testnet
  • CELO Testnet Alfajores
  • CELO Testnet Baklava
  • eCredits Testnet
  • Ethereum Testnet Goerli
  • Ethereum Testnet Sepolia
  • HOM Testnet
  • HT Chain Testnet
  • KUB Bitkub Testnet
  • RSK Smart Bitcoin Testnet
  • Smart BCH Testnet

Limitations of Testnet workspaces

The Testnet workspace will have certain conditions to protect you from losing real assets and compromising security while you test.

Testnet Limitations
  • Only Testnet assets and Testnet blockchains are supported, (e.g. Ethereum Goerli Testnet)
  • Simplified signing process:
    • Removes many security features in favor of simple setup and testing
    • No mobile signing application support
    • No client co-signer support
  • Limited exchange integrations - not all exchanges support Testnet blockchains and may not work as they would on Mainnet
  • Fiat integrations will only work on fiat test networks
  • DeFi/Web3 - Limited blockchain & Web3 dApp test network support
  • The Fireblocks Network is not available.
  • Transaction screening AML/KYT integrations are not available
  • Reduced API rate limits - Production-level load testing is not available

Considerations for managing Mainnet & Testnet workspaces

  • Aside from users you add to both workspaces, your Mainnet and Testnet are separate.
    Your Mainnet workspace will require its own vault accounts and asset wallets, exchange account and fiat account connections, policies, users, and more.
  • You must define the Mainnet workspace’s Transaction Authorization Policy (TAP) rules to work in accordance with various users, user groups, sources, destinations, and assets.
  • You must configure your Mainnet workspace to work with any API integrations and third-party accounts you want to carry over from your Testnet workspace.
    • This includes creating a new API key for and provisioning your API co-signer.


Parameters will change between workspaces/environments

Prodution-ready Mainnet parameters will likely be different from what you used in your Testnet workspace.


Configuration flexibility

You can add Fireblocks Console users, set your Admin Quorum, and connect to exchange accounts, fiat accounts, and Fireblocks Network members before or after you configure your API integrations.