onshore
Early accessBuilt for the CBN’s 1 January 2027 data rule

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.

Vault Made-up data
FieldToken
BVN22123456789
NIN70123445412
NUBAN0123456789
Phone+2348031234567
DetectionProtecting
Transfer of N250,000 to 0123456789 failed. My BVN na 22123456789
BVN0.97Tokenized
NUBAN0.91Tokenized
Amount0.93Tokenized
Who sees this BVN?support-agents@v3
PersonGetsResult
Support agent*******6789Masked
Fraud analyst22123456789Real value
Data teamtok_bvn_7Hq2…Token only
Contractor—Denied
Purpose requiredApproved networks200 reveals an hour
Audit log Log intact
09:41:07Ada O.Revealed BVNa41f…
09:40:52Tunde B.Viewed masked NUBAN7c02…
09:38:15svc-loansTokenized 240 valuese9b1…
09:36:44Musa K.Reveal refused03dd…
09:31:02Ngozi E.Published policy v35fa8…
Until the CBN rule starts
 

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 circular

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 identifiers are leaving the country.
Nigeria
Abroad
bvn=22123456789
acct 0123456789
+2348031234567
nin=70123445412
The vault

Tokenize once. Use it everywhere.

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

Explore the vault
Nigerian formats

BVN, NIN, NUBAN and +234 phone numbers, 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 Nigeria

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

Vault Made-up data
FieldToken
BVN22123456789
NIN70123445412
NUBAN0123456789
Phone+2348031234567
Try it

Paste a line. Watch what would leave the country.

Input
What leaves Nigeria4 found
Good morning. Transfer of tok_amt_tjuYVdE5eg to tok_nuban_Ma53pkMBSA failed. My BVN na tok_bvn_fMmfx0QnU5, email tok_email_LGguq0mZgp
Amount × 1NUBAN × 1BVN × 1Email × 1Runs only in this page, using a simplified preview of detection. 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 Nigeria
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
Transfer of N250,000 to 0123456789 failed. My BVN na 22123456789
BVN0.97Tokenized
NUBAN0.91Tokenized
Amount0.93Tokenized
03

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.

From value to token
Value22123456789
Stored22123456789
Token00000000000
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 BVN?support-agents@v3
PersonGetsResult
Support agent*******6789Masked
Fraud analyst22123456789Real value
Data teamtok_bvn_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 BVNa41f…
09:40:52Tunde B.Viewed masked NUBAN7c02…
09:38:15svc-loansTokenized 240 valuese9b1…
09:36:44Musa K.Reveal refused03dd…
09:31:02Ngozi E.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 BVNs in them don't.

On the way to your log vendor
level=error msg="transfer failed" nuban=0123456789
level=info user=cust_1042 bvn=22123456789
level=warn phone=+2348031234567
Free text

Tickets and chats, cleaned as they arrive.

DetectionProtecting
Transfer of N250,000 to 0123456789 failed. My BVN na 22123456789
BVN0.97Tokenized
NUBAN0.91Tokenized
Amount0.93Tokenized
Secure components

Collect a BVN without it touching your code.

Your page
Your BVN
221234
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 BVN.

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

Explore the gateway
Inside NigeriaYour app and Onshore
My transfer to 0123456789 failed. BVN na 22123456789.
Sorry about that. I can see the transfer to 0123456789 failed, and I have logged it against BVN 22123456789.
At the model providerWhat it receives and returns
My transfer to tok_nuban_Qa81 failed. BVN na tok_bvn_7Hq2.
Sorry about that. I can see the transfer to tok_nuban_Qa81 failed, and I have logged it against BVN tok_bvn_7Hq2.
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 "@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);
Node.js

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

Package
@onshore/sdk
Output
token  tok_bvn_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
OIDC and SAML
Keys
OpenBao
Keys
PKCS#11 HSMs
Audit
Your SIEM
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 mapMade-up data
Flow score
50%
Open work
2
Payment logsCore ledgerSupport copilotLog vendorGermanyData warehouseIrelandDR siteLagosModel 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 BVN?

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 BVNa41f…
09:40:52Tunde B.Viewed masked NUBAN7c02…
09:38:15svc-loansTokenized 240 valuese9b1…
09:36:44Musa K.Reveal refused03dd…
09:31:02Ngozi E.Published policy v35fa8…
Deployment

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
your server
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.