Your whole custody platform, inside your own private network
Wallets, policies, approvals and MPC signing all run on your servers, with no exposure to the public internet. Signing nodes are spread across clouds and regions, so there is no single point of failure and no third party in the loop.
Architecture
Everything runs where your security team can see it
Calls Fystack over private IPs
Wallets, payouts
Limits, approvals
In your region
AWS account A, Frankfurt
GCP project B, Netherlands
Azure account C, Paris
Fystack has no access to your keys, data or transactions
Shared by every customer
Run and controlled by the vendor
Vendor region, cross-border
Same API, same key servers
Your keys and data sit with a third party
Why self-host
Custody without a third party in the room
No public ingress
The API, console and signing nodes sit on private IPs. There is no endpoint on the internet for an attacker to find.
MPC across clouds and regions
Signing nodes run in separate cloud accounts and regions over a private mesh. Losing one provider does not stop signing, and one node on its own holds only a useless key share.
Fystack has no access
Keys, data and transactions never leave your infrastructure. We can't see them, so we can't leak them.
Data stays in your region
Pick the regions your licence requires. Wallet data, audit logs and key shares never cross a border you didn't choose.
No volume caps
Unlimited wallets and transactions. Your costs don't jump when you have a good month.
The full platform, not just signing
Multi-chain wallets, policy engine, approval workflows, audit trails, REST API and SDKs. Plug in your own KMS or HSM.
Built for regulated teams
Simple answers to the questions your regulator asks
Where exactly are the keys?
Split into key shares on MPC nodes in your own cloud accounts or data centers. The full key never exists anywhere.
Where does customer data live?
In your database, in the regions you choose. Nothing is copied to a vendor cloud.
Who else can access it?
Nobody outside your organisation. Fystack has no access to your keys, data or transactions.
What happens if a cloud provider goes down?
Signing nodes run across providers and regions, so the remaining nodes keep signing.
Who it's for
For teams that can't hand their keys to someone else
Banks & Neobanks
Offer digital asset custody inside the same boundary as your core banking systems.
Payment Institutions & EMIs
Run stablecoin settlement and payouts without routing funds through a vendor cloud.
Licensed Exchanges & Brokers
Hot wallet operations at any volume, with keys in infrastructure you are licensed to operate.
Custodians & Trust Companies
Own the full custody stack your clients and auditors expect you to control.
Corporate Treasury
Hold and move digital assets with the same controls and approvals as the rest of treasury.
Tokenization Platforms
Issue and manage tokenized assets with keys that never leave your environment.
Compared
Self-hosted vs typical cloud custody
| Fystack self-hosted | Typical cloud custody | |
|---|---|---|
| Where it runs | Your private network | Vendor cloud, public internet |
| Key shares | All on your infrastructure | Partly held by the vendor |
| Data location | Your chosen regions | Vendor's regions |
| Vendor access | None | Part of every transaction |
| Volume and wallets | Unlimited | Caps and overage fees |
| Single point of failure | Nodes across clouds and regions | Vendor uptime |
Deployment
From pilot to production on your own servers
Run the pilot
One command spins up the full stack on a server you own.
Place your MPC nodes
Spread signing nodes across the cloud accounts and regions you choose.
Lock down the network
Keep everything on private IPs behind your VPN. No public ingress.
Connect your app
Call the REST API or SDKs from inside your network and go live.
Deploy On-Prem or Your Favorite Cloud





Bring custody inside your own walls
Tell us about your licence, regions and infrastructure. We'll help you design a deployment your security team and regulator are both happy with.