How It Actually Gets Installed
Mobile RASP SDK Integration:
One SDK. Zero Disruption.
No API redesign. No change to how your app looks or feels. No slowdown your users will notice. Three pieces, none of them touching what you've already built.
What You Actually Install.
The SDK
A small piece of code added to your existing Android and iOS app. It watches the device and the session — it doesn't ask for new dangerous permissions, and it doesn't change a single screen your users see.
The Backend
Hosted by us on SaaS, or run in your own cloud account (BYOC) or your own data centre (on-premise). It checks and scores what the SDK reports, without needing you to redesign your existing APIs or business logic.
The Dashboard
One place for your team to see what's being caught, investigate a case, and pull the signed evidence record — without digging through logs across five different tools.
What Won't Change.
You don't rewrite your existing endpoints or business logic. The SDK adds signed evidence to a session; verification happens alongside your app, not by tearing out what's already working.
No new screens, no new permission pop-ups, no extra taps for your users. Protection runs quietly in the background — your customers keep the exact experience they already know.
The SDK is built to be light — it checks the device and reports signals without slowing down app launch, screen transitions, or the transaction itself.
Start on our SaaS, or keep everything in your own cloud account or data centre. With BYOC and on-premise, your data residency and access rules stay exactly as your compliance team already set them.
SaaS, Your Cloud, Or Your Data Centre.
The SDK is the same in all three. What changes is where the backend runs and who operates it.
We host it. You integrate the SDK.
Live within 24 hours of the signed agreement. The only work on your side is the SDK integration, and we support it in real time. One flat monthly price, on the cost page.
It runs in your cloud account.
The backend is deployed in your own cloud account, so data stays in your environment. We deploy it with your team. Priced by a written quote.
It runs in your data centre.
The full stack is hosted on your own infrastructure, for teams that need everything inside their own walls. Priced by a written quote.
Three Steps. Not a Project.
Add the SDK to your Android and iOS app — a standard library integration, not a rewrite.
On SaaS we provision your tenant, live within 24 hours of the signed agreement. For BYOC or on-premise, we deploy the backend in your environment with your team.
The dashboard goes live. Your team sees real signals from day one, and we support the integration in real time.
This also satisfies the data-residency and access-control expectations behind DPDP Rule 6 and RBI's security rules — on BYOC and on-premise, because the data never has to leave your own environment in the first place.
Integrating the Consent Manager.
Using the DIMEAI Consent Manager for Data Fiduciaries? Its own guide covers the business API, the browser widget, the Android and iOS consent panel, the tenant dashboard and offline verification.
Ask Your Engineers to Ask Ours.
Bring your technical team. We'll walk through exactly what changes on your side — which is almost nothing.
Frequently asked questions
How long does NonaShield SDK integration take?
The standard integration is four steps: initialise the SDK, enrol the device, call onUserLogin, and optionally run a payment check. The integration guide walks through each platform.
Which platforms does the SDK support?
Android, iOS and React Native from one Kotlin Multiplatform SDK.
Do customers have to change their login or payment flow?
No. The SDK works alongside your existing flow. Business calls go through the NonaShield HTTP client so the security headers attach automatically.