Use cases / Commercial, merchant and non-interest banks
Your data centre. Your HSM. Our software.
Banks can self-host the same software as the hosted version, using Docker Compose, with a Helm chart for Kubernetes in early access, connected to their own HSM and databases. The control stays with you and so does the evidence.
What changes
Today
With Onshore
Where it runs
A vendor's cloud you have to assess
Inside your own network and change process
Keys
Held by a provider
In your HSM over PKCS#11, or your own OpenBao
Staff access
Broad database access for many teams
Masked by default, with a reason on every reveal
Audit requests
Weeks of log gathering
A hash-chained record and signed exports
What you'd use
Questions
Can it run without the internet?+
Self-hosted installs use an offline licence, so the product itself does not need to phone home. Modules reach only the destinations you configure.
Does it connect to our identity provider?+
OIDC and SAML single sign-on are built. Early access installs should be tried against your provider first.
What about older core banking APIs?+
The proxy reads XML and SOAP and keeps envelopes intact.
Start with one leak.
Tell us which flow worries you most. We'll show you what it would take to keep it onshore.