Industry 01Financial Services

Financial Services.

Hikari Blue operates in financial services where the regulatory load is the design constraint, not the compliance afterthought. Every system we ship is audit-defensible by architecture, to DORA, NIS2, GDPR, and the EU AI Act, in parallel.

Operated for Banks · Asset managers · Insurers Regulatory baseline DORA · NIS2 · GDPR · EU AI Act Geography EU · US · cross-border

What makes this sector hard

Regulation is no longer a downstream control. It is the architecture brief.

Five structural pressures shape every engagement we accept in financial services. They are not problems to solve once. They are the operating reality every system we ship must survive in production.

  • 01

    DORA and NIS2 in parallel, on the same platform

    Both regulations enter active enforcement on overlapping perimeters. The platform must answer ICT risk obligations and operator-of-essential-services obligations from the same evidence chain. Built once, audited twice.

  • 02

    AI Act applied to credit decisioning, KYC, claims, fraud

    Most existing decisioning systems were not designed to emit per-decision evidence. The retrofit cost is structurally underestimated until the first regulator letter arrives.

  • 03

    Legacy core, modern customer surface

    Mainframe, COBOL, packaged banking suites coexisting with mobile-first customer experience. The seam between the two carries most of the operational risk, and most of the cost of change.

  • 04

    Cross-border data residency without business friction

    EU sovereignty rules, US frameworks, APAC variations. The system must keep data where the regulator says, while letting decisions flow where the business needs.

  • 05

    Senior architects on regulated environments are scarce

    The number of engineers who have shipped a system that survived a DORA-grade audit can be counted in three digits per market. Hiring is not a strategy. Mobilizing is.

How we operate here

Signature engagements in financial services.

Four engagement types we accept in financial services. Each is signed by a named partner and carries audit posture as a design property, not as a delivery checklist.

  • DORA & NIS2 architecture mapping

    Six to ten weeks. We map the platform against both regulations simultaneously, identify the shared evidence surface, and design the single audit chain that defends both, without two parallel programs.

    Signed by Franck Ohrel

  • AI risk framework on decisioning

    Eight to sixteen weeks. We design the evaluation, logging, model registry and kill-switch layer for credit, KYC, claims or fraud decisioning. EU AI Act-ready evidence by architecture.

    Signed by Xavier de Maillard

  • Banking core modernization

    Twenty-four to forty-eight weeks. Strangler-pattern replacement of legacy banking core under continuous observability, with reversibility at every step. No big-bang migration.

    Signed by Xavier de Maillard

  • Senior operator reinforcement

    Six to twenty-four weeks. Calibrated senior architects mobilized inside your team: sized to the outcome, planned exit, transfer of ownership engineered from day one.

    Signed by Rémi Claverie

Solutions mobilized here

Where the Hikari Blue Solutions land in financial services.

Bring the regulator question

Before the next audit cycle,
map the evidence surface.

Thirty minutes with a senior partner. We listen to your real DORA, NIS2 and AI Act perimeter, then we tell you what is engineered, what is hand-stitched, and what we would attack first.

Book a 30-minute working session Or write directly to the founding partner