Deployment

Our cloud, your servers, or the source.

Same software in all three. The difference is who operates it, where keys live, and how you pay. Most operators start on cloud and move to self-hosted when their licence requires it; setup fees carry over.

01 · White-label cloud

We run it, under your brand

Dedicated instance on EU dedicated servers (Hetzner, Falkenstein or Helsinki). Backups, upgrades, monitoring and 24/7 on-call included in year one. You get the admin; we get the pager.

Best for: first launch, token projects, payment companies. Not available for Custody.

02 · Self-hosted

We install on infrastructure you control

Bare metal or your cloud account (AWS, Hetzner, OVH, Azure). We have no standing access; support sessions use time-limited credentials you issue. Keys never leave your perimeter. Updates and support at 20% of licence per year.

Best for: licensed brokers, banks, anyone with a data-residency rule.

03 · Source code

Full repositories, your engineers

Everything in self-hosted plus the code, the build pipeline and infrastructure definitions. 90 days of onboarding for your team. Optional update stream at 15% per year; you may fork and diverge.

Best for: groups with an in-house engineering team and a long horizon.

Side by side

What changes between the models.

	White-label cloud	Self-hosted	Source code
Who operates	BitPolaris	You, with our on-call	You
Where	EU dedicated servers	Your bare metal or cloud	Your bare metal or cloud
Keys	Encrypted in the instance (HashiCorp Vault)	Entirely in your perimeter	Entirely in your perimeter
Our access	Operational, logged	None standing; session credentials you issue	None
Updates	Included; you approve windows	20% of licence / yr, you approve windows	Optional 15% / yr update stream
Custody block	Not available	Available	Available
Time to launch	Fastest — environments exist	+1–2 weeks for install and key ceremony	+ onboarding; launch on your schedule
Pricing	Setup + monthly	One-time licence + annual support	One-time perpetual licence
Exit	90 days notice, full data export	Perpetual; support optional	Perpetual

Regions & residency

Where it can run.

Cloud instances are EU by default. Self-hosted goes wherever your licence requires. Data residency, backup location and support hours are written into the order.

Cloud · EU

Hetzner Falkenstein (DE) or Helsinki (FI).

Backups to the other site. GDPR processor agreement included.

Self-hosted · EU

Any provider.

Reference installs on Hetzner, AWS Frankfurt, OVH.

Self-hosted · GCC

AWS Bahrain and UAE, Oracle Dubai, on-premise.

Arabic UI and RTL supported.

Self-hosted · Türkiye

Local providers or on-premise for data-localisation requirements.

TRY fiat rails live.

Self-hosted · other

Singapore, Switzerland, UK on request.

Sanctions screening on all deployments.

Moving between models

Start on cloud. Move when you need to.

A cloud-to-self-hosted migration is two weeks and a planned weekend. Your setup fee is credited against the licence.

01
Week 1
Your infrastructure provisioned with our installer. Staging restored from a cloud snapshot.
02
Week 2
Key ceremony on your side; new custody addresses announced to users with a sweep plan.
03
Week 3
Dress rehearsal: full restore to your production, read-only, reconciled against the chain.
04
Cutover
Trading paused for under an hour, usually a Sunday 02:00 local. DNS switch, final sweep, reopen. Cloud instance kept read-only for 30 days, then destroyed with a certificate.

Not sure which model?

Tell us your licence status and where your users are. We recommend one and explain why.

Talk to sales Compare prices