Product overview

⚠️
Version 2 alpha — coming soon
These docs are an alpha preview of version 2, coming soon. Content and setup instructions may change before release.

io.finnet is built as a stack of products. io.sign is the core that everything else depends on. io.vault adds two products on top of io.sign: Treasury and Tokenisation. io.network is a side product that builds on all of them and connects to our private blockchain network.

This page summarises each product and how they depend on one another. Use the links to go deeper into each section.

io.sign

The core signing product. Every other product depends on it to produce threshold signatures.

io.vault

Digital asset custody built on io.sign. Provides Treasury and Tokenisation.

io.network

Tokenisation on our private blockchain network, integrated with our banking partners.

Platform basics

Quick startStand up io.sign locally for evaluation with Docker Compose.Deploying io.signChoose Mobile Signers or Virtual Signers with a self-hosted or io.finnet-managed backend.AuthenticationConfigure identity providers, JWT validation, and client sign-in.WebhooksDeliver io.sign event notifications to URLs you control.Supported blockchainsThe blockchains io.vault supports natively.Web consoleAn optional alpha console for debugging a self-hosted io.sign deployment.

How the products fit together

The products layer on top of each other. Each layer requires everything below it:

io.sign is required by everything. You cannot run any other product without it.
Treasury requires io.sign. You can deploy Treasury with io.sign alone, without Tokenisation.
Tokenisation requires io.sign and Treasury, plus Tokenisation itself.
io.network requires io.sign, Treasury, and Tokenisation.

io.sign

io.sign is the core signing product. It produces threshold signatures using Multi-Party Computation (MPC), and every other product relies on it to sign transactions and messages. io.sign returns a raw signature that you can broadcast yourself, or hand to io.vault to broadcast automatically.

Core, must-have product. Every other product depends on it.
Produces raw ECDSA and EdDSA signatures using threshold signing.
Distributes key shares across signers so no single party ever holds the full private key.
Supports human signers on their own devices and automated Virtual Signers.

Start with Get started with io.sign to choose a deployment, configure the service, and complete your first signing request.

io.vault

io.vault is the digital asset custody product built on io.sign. It holds keys, manages signers, and broadcasts signed transactions to the blockchain. io.vault provides two products: Treasury and Tokenisation.

Treasury

Treasury is the custody and asset management product. It manages vaults, signers, and signing policies, and broadcasts signed transactions on your behalf.

Requires io.sign.
Can be deployed with io.sign alone, without Tokenisation.
Manages vaults, signers, thresholds, and signing policies.
Broadcasts signed transactions to supported blockchains automatically.

Tokenisation

Tokenisation builds on Treasury to issue and manage tokenised assets.

Requires io.sign, Treasury, and Tokenisation itself.
Builds on Treasury's custody and signing capabilities to manage tokenised assets.

Learn more in the io.vault section.

io.network

io.network is a side product for financial institutions that want to modernise asset management through tokenisation on a private blockchain network. It integrates with our banking partners.

Requires io.sign, Treasury, and Tokenisation.
Runs on our private blockchain network.
Integrates with our banking partners.
Targets banks, investment firms, and other financial institutions.

Learn more in the io.network section.