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.
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.
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
Tokenize once. Use it everywhere.
Your systems hold a token. The value stays encrypted in its country, behind a policy.
NI numbers, Aadhaar, CPFs, Emirates IDs, BVNs, IBANs and more, with tokens that can keep the shape your systems expect.
Finds identifiers you didn't plan for in free text and JSON, and you can add data types of your own.
Use the bundled key service, or connect your own HSM. A sealed key service means nothing gets decrypted.
Paste a line. Watch what would leave the country.
From raw value to proof, in five steps.
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.
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.
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.
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.
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.
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.
Whatever the proxy can’t read in full, it doesn’t forward.
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.
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.
Hi, I’m Sarah Johnson, 34. My card 4111 1111 1111 1111 was charged £1,250.50 twice. Email me at sarah@example.com.
Hi, I’m Emma Clarke, 34. My card card ending 1111 was charged £1,250.50 twice. Email me at [EMAIL_1].
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.
In your language, in a few lines.
Eight SDKs, a web component and a REST API. Pick yours.
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);Token refresh, batching and retries are handled for you. Detokenize fails closed.
token tok_uk_nino_7Hq2xP9LmA4c reveal masked *******6789
Built to fit your stack.
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.
- Vault names and settings
- Counts: values found, reveals, refusals
- Instructions such as “create a vault”
- Customer values
- Encryption keys
- 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.
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
When they ask who saw what, show the record.
See audit and evidenceThe residency map lists every system and vendor, and each flow's status.
Types caught per destination, before and after protection.
A timeline with the person, reason and result of each access.
Hash-chain verification and signed daily checkpoints.
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.
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
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
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
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.