NewKernhaven 2026.4 adds Verification of Payee for SEPA payments.Verification of Payee is here.Read more →
Partners Now working with four institutions across Europe →

The real-time core European banks build on.

Kernhaven pairs an immutable ledger with an event-driven integration layer. Launch products in weeks, run 24/7 without maintenance windows, and deploy on-prem or in any cloud.

  • Built on .NET & open standards
  • EU data residency
  • DORA-ready by design
Instant Saver v2.1Promoted to production · 09:14

Trusted by banks and lenders across Europe

4partner institutions
3European countries
24/7posting, no end-of-day batch window
< 25 msp99 posting latency

Product tour

One console for product, operations and engineering.

Everything your teams need to run a bank on Kernhaven, from launching a product to tracing a single posting.

Launch products without a release.

Product teams define rates, tiers, fees and limits in versioned templates. Simulate the impact on a staging tenant, then promote to production with four-eyes approval.

  • Versioned product templates
  • Simulation before go-live
  • Four-eyes approval workflow
Products / SavingsInstant Saver
v2.1 · Draft
CurrencyEUR
AccrualDaily
CapitalisationMonthly
WithdrawalsUnlimited
Balance tierRate (AER)Change
€0 – €10,0002.10%—
€10,000 – €50,0002.35%+0.10
Above €50,0002.50%+0.15
Run simulationSubmit for approval

Why Kernhaven

Modern banking without the big-bang risk.

01

Launch in weeks, not years

Products are configuration, not code. Define a new savings account or loan on a staging tenant and promote it to production the same week.

02

Always on

No end-of-day batch freeze. Interest, fees and balances update continuously, so customers see the truth at any hour.

03

Migrate step by step

Run Kernhaven alongside your legacy core. Move one product or one segment at a time, with reconciliation built in.

04

Lower cost of ownership

One codebase for every client, standard .NET skills, and container-based deployment your team already knows.

05

AI-ready data

Every change is a structured event. Stream it to fraud models, analytics or your data lake without touching the core.

Architecture

Strong where it must be. Flexible everywhere else.

Money movements are posted in a single ACID transaction to an append-only ledger. Everything around the core reacts to events, so integrations never slow down a payment.

  • Immutable double-entry ledger — every posting is permanent and auditable.
  • Transactional outbox — events are never lost and never published for a failed transaction.
  • API-first — REST and event streams for every capability.
  • Deploy anywhere — Kubernetes on-prem, Azure, AWS or a sovereign EU cloud.
Kernhaven architecture: channels call the API, the core posts to the immutable ledger, and the outbox publishes events to downstream consumers.Channels · Mobile · Web · Branch · Open BankingAPI Gateway · OAuth2 / OIDCKERNHAVEN CORE · ACIDCustomersDepositsLendingPaymentsImmutable ledgerOutboxEvent stream · Kafka / RabbitMQFraud & AMLReportingNotificationsData lake

Progressive migration

Replace your core one wave at a time.

No big-bang weekend. Kernhaven runs next to your legacy core until the last product has moved.

2–4 weeks

Discover

We map your products, data and integrations, and agree a migration plan with clear go/no-go criteria for every wave.

Month 2–4

Coexist

Kernhaven goes live next to your legacy core. New products launch on Kernhaven first while both ledgers are reconciled automatically.

Month 4+

Migrate in waves

Existing portfolios move one product or segment at a time. Every wave is rehearsed, validated and reversible.

When ready

Decommission

Once the last wave is complete, the legacy core is retired and its run costs disappear from your budget.

Compliance & resilience

Made for European regulation.

We design for the rules our clients live under, so your compliance and risk teams start from a strong position.

DORA

ICT risk controls, incident logging and exit strategies supported by design.

GDPR

EU data residency, data minimisation and right-to-erasure workflows.

PSD2 / PSD3

Open Banking APIs and strong customer authentication integration.

EBA outsourcing

Audit and access rights, sub-outsourcing transparency and exit plans in every contract.

Works with your stack

Open standards. No lock-in.

Kernhaven runs on the infrastructure and tooling your teams already use.

KKubernetes
PPostgreSQL
SSSQL Server
AKApache Kafka
RRabbitMQ
MAMicrosoft Azure
AAWS
GCGoogle Cloud
OOpenTelemetry
KKeycloak
GGrafana
HVHashiCorp Vault

FAQ

Questions banks ask us.

Can't find what you are looking for? Talk to our team.

How long does a typical implementation take?

A greenfield launch on Kernhaven typically takes four to six months from contract to first customer. Progressive migrations from a legacy core are planned in waves, with the first wave live in around six months.

Can Kernhaven run alongside our existing core?

Yes. Coexistence is how we recommend migrating. Kernhaven runs in parallel, starting with new products or a single segment, while automated reconciliation keeps both ledgers in step.

Where is our data hosted?

Wherever you choose: in your own data centre, in your Azure, AWS or Google Cloud tenant, or in an EU sovereign cloud. Customer data never leaves the European Economic Area unless you decide otherwise.

How do you support DORA compliance?

We provide ICT risk documentation, incident reporting hooks, audit and access rights, sub-outsourcing transparency and a tested exit strategy as part of every contract.

What skills does our team need?

Kernhaven is built on .NET, PostgreSQL and Kubernetes. Most bank IT teams already have these skills, and we offer training and certification for engineers and operations staff.

How is Kernhaven licensed?

Annual subscription based on the number of active accounts and modules, with implementation services priced separately. There are no per-transaction fees.

See Kernhaven in action.

Book a 30-minute walkthrough. We will launch a live product on the platform, from configuration to first posting.