onshore
Early accessOpen source, with packs for 18 countries

Keep customer data in its country.
Keep your global tools.

Onshore swaps national IDs, account numbers and payment details for tokens: NI numbers in the UK. Your logs, AI and support tools keep working, and the real values stay in the country they belong to.

Vaultv_live_gb01GBUnited Kingdom
FieldToken
NI numberAB 12 34 56 C
Sort code and account12-34-56 12345678
Phone07700 900123
Emailsam@example.com
Made-up data · encrypted in United Kingdom
DetectionProtecting
Refund of £1,250.50 to GB82 WEST 1234 5698 7654 32 failed. My NI number is AB 12 34 56 C
NI number0.97Tokenized
IBAN0.99Tokenized
Amount0.93Tokenized
Who sees this NI number?support-agents@v3
PersonGetsResult
Support agent•• •• •• 56 CMasked
Fraud analystAB 12 34 56 CReal value
Data teamtok_uk_nino_7Hq2…Token only
Contractor—Denied
Purpose requiredApproved networks200 reveals an hour
Audit log Log intact
09:41:07Ada O.Revealed NI numbera41f…
09:40:52Tom H.Viewed masked IBAN7c02…
09:38:15svc-loansTokenized 240 valuese9b1…
09:36:44Priya S.Reveal refused03dd…
09:31:02Lucas M.Published policy v35fa8…

Moving the database is the easy part. The data keeps leaving.

Data centres solve where your database lives. Your logs, chatbots, helpdesk and analytics still send customer identifiers abroad, every day. That’s the gap Onshore closes.

Real UK identifiers are leaving.
United Kingdom
Abroad
uk_nino=AB 12 34 56 C
12-34-56 12345678
07700 900123
sam@example.com
Any country

Pick a country. Setup does the rest.

Onshore asks where your company is, then fills in the vault’s country, that country’s data types, the laws to track, the time zone and the formats. No country is assumed, and you can change any of it.

  • 15 country packs, plus one for names, cards and emails everywhere
  • Each law shows its source and the date we last checked it
  • Office hours, daily reports and usage follow your own time zone
  • The console speaks English and French
Where is your company?
First-time setup Filled in from your answer. Change anything.
Vault countryUnited Kingdom · data stays here
Country packsEverywhereUnited Kingdom
Data typesNational Insurance numberNHS numberSort code and account
Laws to trackUK GDPR
Time zoneEurope/London
Formats21/11/2026 · £1,250.50 · +44
Console languageEnglish · English and French
$ rv init --country gb
The vault

Tokenize once. Use it everywhere.

Your systems hold a token. The value stays encrypted in its country, behind a policy.

Explore the vault
Local formats

NI numbers, Aadhaar, CPFs, Emirates IDs, BVNs, IBANs and more, with tokens that can keep the shape your systems expect.

Detection

Finds identifiers you didn't plan for in free text and JSON, and you can add data types of your own.

Keys held in the country

Use the bundled key service, or connect your own HSM. A sealed key service means nothing gets decrypted.

Vaultv_live_gb01GBUnited Kingdom
FieldToken
NI numberAB 12 34 56 C
Sort code and account12-34-56 12345678
Phone07700 900123
Emailsam@example.com
Made-up data · encrypted in United Kingdom
Try it

Paste a line. Watch what would leave the country.

Country
Input
What leaves United Kingdom2 found
Hi, my refund still hasn't arrived. My NI number is tok_uk_nino_5ZkS0nxFT1 and you can call me on tok_phone_ZtBiE3Ut58.
NI number × 1Phone × 1Runs only in this page, with a simplified preview of each country’s pack. Please use made-up data.
How it works

From raw value to proof, in five steps.

01

Plug in where data flows

Call an SDK, drop in a form, or put the proxy, log processor or AI gateway in the path. You can start with one flow and add others later.

Ways in
SDK or API
Secure form
HTTP proxy
Log pipeline
AI gateway
Support tool
One engine, in each country
02

Find what's sensitive

Field rules catch what you know about. The detection engine catches the rest in free text and JSON. New rules start in Watch only, so nothing changes until you decide.

DetectionProtecting
Refund of £1,250.50 to GB82 WEST 1234 5698 7654 32 failed. My NI number is AB 12 34 56 C
NI number0.97Tokenized
IBAN0.99Tokenized
Amount0.93Tokenized
03

Lock it up and hand out a token

The value is encrypted on its own, in the vault’s country, and a token takes its place. That token can travel to your database, your vendors and your dashboards.

From value to token
Value2345 6789 0124
Stored2345 6789 0124
Token00000000000000
Master key held by the key service, or your HSM. Never in the database.
04

Decide who gets what

When someone needs the real value, a policy checks who, what, when and why. The answer is the value, a mask, the token or no.

Who sees this NI number?support-agents@v3
PersonGetsResult
Support agent•• •• •• 56 CMasked
Fraud analystAB 12 34 56 CReal value
Data teamtok_uk_nino_7Hq2…Token only
Contractor—Denied
Purpose requiredApproved networks200 reveals an hour
05

Keep the proof

Every decision adds an entry to a hash-chained log. Your reports are built from those entries, so you can trace each number back to what happened.

Audit log Log intact
09:41:07Ada O.Revealed NI numbera41f…
09:40:52Tom H.Viewed masked IBAN7c02…
09:38:15svc-loansTokenized 240 valuese9b1…
09:36:44Priya S.Reveal refused03dd…
09:31:02Lucas M.Published policy v35fa8…
Stop the leaks

One engine. Every exit.

Each module wraps the vault and detection around one leak. Turn on only the ones you need, and watch before you enforce.

See all products
Log redaction

Your logs can leave. The IDs in them don't.

On the way to your log vendor
level=error msg="refund failed" iban=DE89370400440532013000
level=info user=cust_1042 aadhaar=234567890124
level=warn ssn=123-45-6789
Free text

Tickets and chats, cleaned as they arrive.

DetectionProtecting
Refund of £1,250.50 to GB82 WEST 1234 5698 7654 32 failed. My NI number is AB 12 34 56 C
NI number0.97Tokenized
IBAN0.99Tokenized
Amount0.93Tokenized
Secure components

Collect an ID number without it touching your code.

Your page
National ID number
AB 12 3
Frame served by your vault
What your code gets
// waiting…
HTTP proxy

Swap one URL. Protect the traffic behind it.

JSONFormsXMLSOAPMultipartHeadersQuery strings

Whatever the proxy can’t read in full, it doesn’t forward.

AI gateway

The model answers. It never sees the ID.

Point your OpenAI-compatible client at the gateway. Prompts go out with tokens, and the customer gets real values back.

Explore the gateway
Inside the countryYour app and Onshore
My refund to GB82 WEST 1234 5698 7654 32 failed. NI number AB 12 34 56 C.
Sorry about that. I can see the refund to GB82 WEST 1234 5698 7654 32 failed, and I have logged it against AB 12 34 56 C.
At the model providerWhat it receives and returns
My refund to tok_iban_Qa81 failed. NI number tok_uk_nino_7Hq2.
Sorry about that. I can see the refund to tok_iban_Qa81 failed, and I have logged it against tok_uk_nino_7Hq2.

Hide each value the way the task needs.

A token, a placeholder, a natural stand-in name, or a range. Stand-ins are swapped back in the reply from a sealed map kept in the vault’s country.

Hide values as
The customer writes

Hi, I’m Sarah Johnson, 34. My card 4111 1111 1111 1111 was charged £1,250.50 twice. Email me at sarah@example.com.

The model receives

Hi, I’m Emma Clarke, 34. My card card ending 1111 was charged £1,250.50 twice. Email me at [EMAIL_1].

The customer gets back

Sorry, Sarah. I’ve flagged the duplicate charge of £1,250.50 and we’ll email sarah@example.com when it’s refunded.

Natural text. Stand-in names are swapped back in the reply, from a sealed map kept in-country. Choose per kind of value: names, ages, amounts, cards, emails and more.

SDKs

In your language, in a few lines.

Eight SDKs, a web component and a REST API. Pick yours.

Developer overview
server.ts
import { VaultClient } from "@onshorehq/sdk";

const vault = new VaultClient({
  baseUrl: "https://vault.gb.onshorevault.com",
  serviceAccountId: process.env.ONSHORE_SA_ID!,
  keyId: process.env.ONSHORE_KEY_ID!,
  privateKey: process.env.ONSHORE_PRIVATE_KEY!,
});

// Store the ID number. Keep the token.
const [{ token }] = await vault.tokenize("v_live_gb01", [
  { field: "national_id", value: "AB123456C", subject_ref: "cust_1042" },
]);

// A policy decides what comes back.
const [reveal] = await vault.detokenize("v_live_gb01", [token!], "Ticket 88213");
console.log(reveal.decision, reveal.value);
Node.js

Token refresh, batching and retries are handled for you. Detokenize fails closed.

Package
@onshorehq/sdk
Output
token  tok_uk_nino_7Hq2xP9LmA4c
reveal masked  *******6789

Built to fit your stack.

Logs
OpenTelemetry
Logs
Fluent Bit
Logs
Vector
AI
OpenAI-compatible APIs
Support
Freshdesk
Support
Zoho Desk
Support
Salesforce
Support
Intercom
Sign-in
SSO, SCIM and LDAP
Keys
OpenBao
Keys
PKCS#11 HSMs
Audit
Your SIEM
Several countries

One console. Every country.

Run an install in each country you serve and link them. Each keeps its customers’ data at home and reports only names, settings and counts, signed, every minute.

See the editions
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

Enterprise, in early access. People still sign in to each install, and access rules are set per install for now.

Residency map

Nobody can tick a flow green. It has to earn it.

See every system and vendor that holds your data. Each flow’s status comes from what Onshore actually sees, and one leak sends a verified flow straight back to red.

  • Flows appear by themselves when a route sees traffic
  • Anything you declare is labelled as declared, in every report
  • Scores track both flows and data volume, so a big leak can’t hide
Residency mapVault in the UK · made-up data
Flow score
50%
Open work
2
Payment logsCore ledgerSupport copilotLog vendorGermanyData warehouseIrelandDR siteManchester, UKModel providerUnited States
Core ledger to Data warehouse:Leaking
Evidence

When they ask who saw what, show the record.

See audit and evidence
Where is the data?

The residency map lists every system and vendor, and each flow's status.

What still flows abroad?

Types caught per destination, before and after protection.

Who saw this person's ID number?

A timeline with the person, reason and result of each access.

Can you prove the log wasn't altered?

Hash-chain verification and signed daily checkpoints.

Audit log Log intact
09:41:07Ada O.Revealed NI numbera41f…
09:40:52Tom H.Viewed masked IBAN7c02…
09:38:15svc-loansTokenized 240 valuese9b1…
09:36:44Priya S.Reveal refused03dd…
09:31:02Lucas M.Published policy v35fa8…
Editions

Open source. Run it anywhere.

The same software in every edition. Start free in one country, link countries with Enterprise, or let us run it in Onshore Cloud.

Compare the editions
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.
Use cases

Made for the teams holding the data.

Start with one leak.

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