onshore
Use cases / PSPs, switches, mobile money operators and fintechs

Keep your stack. Bring the data home.

Nigeria's central bank wants payment data stored in the country from 1 January 2027, and data protection laws from Saudi Arabia to Brazil set conditions on sending personal data abroad. Moving your database is the visible part. The harder part is what flows out of it every day, in every country you operate in.

What changes
Application logs
Datadog receives account numbers in error messages
Datadog receives tokens, and debugging still works
KYC onboarding
National IDs pass through your web app and database
A secure frame collects them, and you store a token
Analytics events
Segment and warehouses collect phone numbers
Events carry stable tokens that still join up
Vendor APIs
Each integration needs rewriting
The proxy swaps values on the way through
What you'd use
Questions
Do we still need to move our database?+

Usually, where a local rule requires it. Onshore handles the identifiers and the flows around that database, and the rest of your data still needs a home in the country.

We operate in several countries. One install or many?+

One per country whose data must stay home. With Enterprise, a single console links them, and each install reports only names, settings and counts.

How long until it's protecting traffic?+

Each module starts in Watch only. You see what it would catch before it changes anything.

Start with one leak.

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