Dedicated service
Instance and database reserved for your institution alone, on NEXCLARA infrastructure. Isolation becomes physical, without you having to operate anything.
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.
- Mid-sized banks whose security policy rules out sharing.
- Institutions with a security committee demanding on environment separation.
- Institutions wanting hardware separation without taking on operations.
How it works
What is actually in place in this mode, and who operates it.
- One instance per institution
Service and database are dedicated. No other institution's data passes through the same instance.
- Same codebase, different configuration
Moving from shared to dedicated changes not one line of code: it is a parameterised deployment operation.
- Dedicated backups and restoration
Backups are encrypted, retained in the same jurisdiction, and restoration is tested periodically on your instance.
What it means for your operations
What this mode asks of your IT team, and what it spares them.
- No operations burden on your side: NEXCLARA runs the instance.
- Update windows can be negotiated with your teams, which is not possible in shared mode.
- Infrastructure cost is higher than shared and reflected in the price.
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.
- Data still resides at NEXCLARA. A policy forbidding this calls for on-premises deployment.
- Dedication changes nothing about outsourcing obligations: the file for the Banking Commission is still required.
When it is the right answer
Your security committee refuses sharing, but your institution does not wish to take on running another platform.