onshore
Deployment

Same software. Your choice of home.

Every part ships as a container, so the hosted and self-hosted versions are the same product. Pick what your risk team and your budget can live with.

Planned for early access

Hosted

For fintechs and smaller institutions

  • We run it in Nigerian data centres
  • A primary site and a separate standby site
  • Encrypted backups kept in Nigeria
  • One vault per tenant
Docker Compose today

Self-hosted

For teams with their own infrastructure

  • Runs on one server to start
  • Your PostgreSQL, or a bundled one
  • Offline licence
  • A pass or fail report for your change ticket
Helm chart in early access

Self-hosted HA

For banks on Kubernetes

  • Several vault API replicas
  • External PostgreSQL with a replica
  • Your HSM for keys
  • Ready for your own review
Install

A few commands to a working install.

The installer writes your settings, sets up key shares and finishes with a report you can attach to a change ticket.

your server
Sizing
ProfileForServersEach server
PilotProof of concept14 vCPU, 16 GB RAM, 200 GB SSD
StandardFintech or MFB in production1 app + 1 database replica8 vCPU, 32 GB RAM, 500 GB SSD
HABanks3 app nodes + PostgreSQL primary and replica + HSM8 vCPU, 32 GB RAM each

Starting points from our reference design. Your traffic may need something different.

Start with one leak.

Tell us which flow worries you most. We'll show you what it would take to keep it onshore.