Shared service
One instance serves several institutions, with isolation applied at three levels. It is the default mode, the fastest to go live and the least costly.
Who it is for
The institution profile this mode is the right choice for, not the list of those that could make do with it.
- Microfinance institutions and networks of branches.
- Smaller banks with no dedicated operations team.
- Any institution starting out that wants to try the platform before settling the hosting question.
How it works
What is actually in place in this mode, and who operates it.
- One instance, several institutions
The platform runs on NEXCLARA infrastructure, on certified European hosting. Each institution has its own context, configuration and data.
- Three-level isolation
Database, application and audit. No query executes without an institution context: a query without context returns nothing, rather than everything.
- Continuous verification
Automated cross-institution access attempts run on every change to the platform, and block release if any succeeds.
What it means for your operations
What this mode asks of your IT team, and what it spares them.
- No infrastructure to mobilise on your side, and no operations skill required.
- Updates are applied by NEXCLARA, with no intervention and no maintenance window to negotiate.
- Supervision, backups and restoration are operated by NEXCLARA, with periodic restoration tests.
What it does not allow
What this mode does not allow. A deployment mode is chosen on its limits as much as on its promises.
- Isolation is logical, not physical. A security policy requiring hardware separation calls for the dedicated mode.
- Data resides at NEXCLARA. A policy that rules this out calls for on-premises deployment.
When it is the right answer
You want to decide quickly, without mobilising an IT team, and your security policy accepts outsourced hosting with a certified European provider.