Skip to main content
NEXCLARA

Deployment and sovereignty

Your infrastructure should not become your dependency

A hosting objection should never decide the fate of a project. That is why portability here is a property of the architecture, not a commercial undertaking.

Deployment and sovereignty

Four modes, one codebase

Moving from one mode to another is a configuration change, not a rewrite.

  • Shared — See this mode in detail

    At NEXCLARAOn your side

    Data resides At NEXCLARA

    NEXCLARA infrastructure, certified European hosting, logical isolation verified continuously.

    Microfinance, smaller banks

  • Dedicated — See this mode in detail

    At NEXCLARAOn your side

    Data resides At NEXCLARA

    Instance and database reserved for your institution alone. Physical isolation, no longer merely logical.

    Strict security policy

  • On your premises — See this mode in detail

    At NEXCLARAOn your side

    Data resides On your side

    Your data centre or private cloud. Data never leaves your perimeter.

    Large accounts, demanding committees

  • Hybrid — See this mode in detail

    At NEXCLARAOn your side

    Data resides On your side

    Processing on your side, technical supervision with no personal data at all.

    A frequent compromise

What makes this possible

No dependency on any proprietary service

A platform built on one vendor's proprietary services cannot be deployed anywhere else. The opposite choice was made from the first line of code, and it is verified automatically on every change.

Standard components

Standard relational database, containers, S3-compatible storage. No proprietary extensions, no exclusive managed service.

Externalised configuration

Changing host means changing environment variables, not changing code.

Runs on a closed network

The platform starts and operates with no mandatory outbound network access. Every external dependency is optional and degradable.

Diagnostics without data access

Supervising an installation never requires access to the personal data it processes. Technical logs are exportable without them.

Security arrangements

What protects the data you entrust

WAMU institutions are subject to precise requirements: a security policy approved by the governing body, a named security officer, an IT risk map, continuity plans tested in real conditions, incident notification. The architecture answers these requirements piece by piece.

Encryption

In transit and at rest, across all data and backups.

Institution isolation

One institution's data can under no circumstances be read by another. Isolation is applied at three levels: database, application and audit. No query executes without an institution context.

Audit log

Every decision and every access leaves a tamper-evident trace, usable as-is in inspection.

Reversibility

You retrieve your data in standard formats, through a documented and tested procedure. Leaving is never a negotiation.

Banking outsourcing

The file your regulator expects

Circular no. 04-2017/CB/C of the WAMU Banking Commission

In the WAMU, any draft outsourcing contract must be submitted for prior review to the General Secretariat of the Banking Commission before it takes effect. That step sits between commercial agreement and deployment, and it regularly catches solutions designed elsewhere off guard.

What we hand you

  • The responsibility matrix, establishing that the bank remains responsible for the credit decision.
  • Data location, the applicable jurisdiction and the associated guarantees.
  • The full subcontracting chain, with each party's role and certifications.
  • The continuity plan, its recovery objectives and its restoration tests.
  • The audit rights of the bank and of the regulator, and how they are exercised.
  • The reversibility plan: formats, timescales and assistance to retrieve your data.
Back to top