onshore
Editions and deployment

One product. Every country you serve.

Every edition runs the same containers. Start free in one country, link installs across countries with Enterprise, or let us run it for you in Onshore Cloud.

Self-hosted · open sourceSource release planned

Free

One country, on your own servers.

  • Every product: vault, detection, logs, AI, proxy, files
  • One install keeps data in one country
  • Passwords with authenticator codes or passkeys
  • Community support
$ rv init --country de
Self-hosted · licensedEarly access

Enterprise

Several countries, one console.

  • Everything in Free
  • Link an install in each country you serve
  • Single sign-on (SAML, OIDC), SCIM and LDAP
  • Offline licence, and support from us
$ rv init --country in --join rvj_… --primary https://onshore.yourco.example
Hosted by OnshorePlanned

Cloud

We run it, in the countries you choose.

  • A region in each country, run by us
  • Single sign-on, SCIM and LDAP included
  • Region not open yet? Join its waitlist, and set it up in a click when it opens
  • Same software as self-hosted
Sign up and pick your countries in the console.
Several countries

Link an install in each country.

Your console makes a single-use join code, valid for a day and tied to one country. The new install joins with it, then sends a signed report every minute. Your console can ask it to create a vault, and it does so in its own country.

countsYour consolePrimary install · United KingdomGermany3 vaultsNigeria2 vaultsIndia4 vaultsBrazil1 vaultRed dots: customer values. They stay in the install’s country.
Crosses the border
  • Vault names and settings
  • Counts: values found, reveals, refusals
  • Instructions such as “create a vault”
Never crosses
  • Customer values
  • Encryption keys
Signed reports, every minute
  • Germany reported · 3 vaults · 12,480 values found in 7 days
a server in India

What’s not built yet

  • One sign-in across installs. People sign in to each install for now.
  • Sending access rules from one install to the others.
  • One audit view across installs. Each install keeps its own.

Linking has been tested end to end on one machine, not yet across countries.

Ways to run it
Docker Compose today

Single server

Free or Enterprise

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

High availability

For banks on Kubernetes

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

Onshore Cloud

Run by us, per country

  • A region in each country we open
  • A primary site and a separate standby site
  • Encrypted backups kept in the same country
  • One vault per organisation and country
Install

A few commands to a working install.

Tell the installer your country and it picks the pack, time zone and formats. It 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
StandardA fintech or lender 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, per install. 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.