Keep Nigerian data onshore.
Keep your global tools.
Onshore swaps BVNs, NINs, account numbers and payment details for tokens. Your logs, AI and support tools keep working, and the real values stay in Nigeria.
The CBN’s June 2026 circular says payments transaction data generated in Nigeria must be “stored and managed in Nigeria” from 1 January 2027.
Read the circularMoving 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.
Tokenize once. Use it everywhere.
Your systems hold a token. The value stays encrypted in Nigeria, behind a policy.
BVN, NIN, NUBAN and +234 phone numbers, 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 Nigeria, 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 BVN.
Point your OpenAI-compatible client at the gateway. Prompts go out with tokens, and the customer gets real values back.
In your language, in a few lines.
Eight SDKs, a web component and a REST API. Pick yours.
import { VaultClient } from "@onshore/sdk";
const vault = new VaultClient({
baseUrl: "https://vault.onshore.ng",
serviceAccountId: process.env.ONSHORE_SA_ID!,
keyId: process.env.ONSHORE_KEY_ID!,
privateKey: process.env.ONSHORE_PRIVATE_KEY!,
});
// Store the BVN. Keep the token.
const [{ token }] = await vault.tokenize("v_live_ng01", [
{ field: "bvn", value: "22123456789", subject_ref: "cust_1042" },
]);
// A policy decides what comes back.
const [reveal] = await vault.detokenize("v_live_ng01", [token!], "Ticket 88213");
console.log(reveal.decision, reveal.value);Token refresh, batching and retries are handled for you. Detokenize fails closed.
token tok_bvn_7Hq2xP9LmA4c reveal masked *******6789
Built to fit your stack.
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.
Hosted in Nigeria, or inside your walls.
It’s the same software either way. Fintechs can use the hosted service, and banks can run it in their own data centre with their own HSM.
- Two separate planes, and the control plane’s database role cannot read vault data
- Five key shares, and any three unseal the key service
- Internal traffic runs over mutual TLS
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.