Choosing your
deployment

SaaS, hybrid or on-premise.Same platform, same controls.

01 The decision

Deploy where it
suits you now

With most providers, choosing between a managed service and your own infrastructure is a decision you make once. Moving afterwards means replacing the platform, rebuilding the integrations around it and starting the audit again, so changing your mind costs more than the original implementation did. That is why the question stops being operational and becomes strategic, and why it takes so long to answer.

We have built the platform so that it does not have to work that way. It is the same system in all three configurations, with the same key architecture and the same controls, so where it runs is a setting rather than a commitment. Start wherever suits you now, and change it when your requirements change.

02 Configurations

Where the
platform runs

Runs in: Our environment
Live in: Days

We run the platform. You create your organisation, configure your policies and start moving assets, usually in days rather than quarters. There is no infrastructure to procure, no deployment project, and nobody on your side who has to keep it running at three in the morning.

What you accept

The platform runs in our environment, and you are relying on us to operate it and keep it available. That is a genuine dependency, even though it is an operational one and not a custodial one. Your keys, your policies and your operational data remain yours throughout, and so does the option to take them elsewhere.

03 Control

A scale, not separate products

Between the fully hosted platform and a fully sovereign one there are intermediate positions, and institutions land on them as often as on the ends.

SaaS Fully managed by us Low control
Self-hosted Signer Key components on client side Partial control
Managed Infrastructure Client infrastructure, The Vault management Medium control
On-premise Full infrastructure control Maximum control

Ease of use Quick deployment

Maximum security Full infrastructure control

04 Side by side

How they compare

The rows where the hosted option is the weaker answer are in the table as well. A technical buyer will find them either way, and it is better that they find them here.

	SaaS	Hybrid	On-premise
Time to first transaction	Days	Weeks	Up to months
Who runs it day to day	We do, fully managed	Shared: we run the platform, you run your signer	Your team, end to end
Where the platform runs	Our cloud	Our cloud, with your signer on your infrastructure	Entirely inside your perimeter
Where key shares live	Split between our cloud and your devices, never in one place	Split across our cloud, your infrastructure and your devices	On your infrastructure and your devices, we hold nothing
Who signs transactions	You and our co-signer, neither side can move funds alone	You and our co-signer, no transaction without infrastructure you control	Only you, every share stays under your control
Who holds operational data	We host it	We host it	You do, inside your perimeter
Team required on your side	None	A part-time infrastructure engineer	A dedicated infrastructure and operations team
Shape of the cost	Monthly subscription	Subscription plus your infrastructure	Capital and headcount
Changing later	Move to hybrid or on-premise	Move in either direction	Move back to SaaS or hybrid

05 Moving

What happens
when you move

Because it is the same platform in all three configurations, moving between them is a redeployment rather than a migration. Your policy configuration, roles and permissions, wallet structure, operational history and integrations travel with you. Your keys are not reissued. Your team does not relearn the system. The work you have already done with your auditors does not start again.

In practice we plan the move with you, stand the new environment up in parallel, test it against your live configuration, and cut over on a date you choose. We stay alongside your team through the first weeks afterwards.

What we will not pretend: if you are moving to your own infrastructure, you still have to build and run that infrastructure, and that is real work on your side. What we remove is the part where the platform, the integrations and the audit have to be built twice.

06 In practice

What institutions usually choose

Family offices and asset managers usually start on SaaS, because the decision chain is short and the operational requirements are clear. Banks and larger institutions more often begin with hybrid or on-premise, because parts of the system have to sit inside an existing perimeter. Payment businesses tend to choose by volume and by how deeply they need to automate. None of these are rules, and none of them are final.

If you are not sure which configuration fits, that is a reason to start rather than a reason to wait. Begin where it is fastest, and change it when you know more.

Get a tailored proposal Work out which fits you

Choosing your deployment

Deploy where it suits you now

Where the platform runs