P1, D3 and D4

Running It

You run it, so it has to be runnable. Corlayr is software you deploy, which means the unglamorous half matters as much as the ledger: how it goes out, how you know it is healthy, how it upgrades without a weekend, and how your existing book gets onto it without a cutover.

Infrastructure as codeExpand and contractDual-run migration

Deployment.

PieceWhat you get
Container imagesSigned, versioned, and the same image in every environment.
Infrastructure as codeThe topology as a definition you keep in your own repository and review like any other change.
Standalone migrationsDatabase migrations run as their own job rather than on application boot.A migration that runs on boot runs once per replica and races itself. Separating it is the difference between a deploy and an incident.
Expand and contractSchema changes land in two steps, so a release and a rollback are both ordinary.
Secure defaultsA hardening guide and a deployment checklist, with the defaults already set the safe way.
Support bundleA redacted diagnostic bundle you can send us without sending customer data.

Alerting on invariants, not on CPU.

Metrics, traces and structured logs are table stakes. What is worth saying is what the system alerts on: ledger imbalance detected is an alert here, and so is a reconciliation that stopped reporting a heartbeat.

A platform that only tells you about memory tells you that the machine is fine while the books are wrong.

  • ledger.trial_balance_zero, continuously, against the live book rather than at month end.
  • ledger.balances_match_replay, so a balance that has drifted from its entries is found by the system and not by a customer.
  • audit.chain_intact and audit.anchors_agree, so tampering is detected rather than assumed impossible.
  • ops.job_heartbeats, because a check that silently stopped looks exactly like one that keeps passing.

Migrating on without a cutover weekend.

Opening balances and history import through the same API everything else uses. Then both systems run in parallel and are reconciled against each other daily, so the decision to switch is made on evidence rather than on a date in a plan.

LiveInstruction, outbound transferManual
What triggered it
SourceOfficer, admin portalRail webhook, M4
ActorA. Patelsystem
Recorded asmanual_bookingprovider_event
The resulting ledger entry
DebitClient wallet, Northwind
CreditSettlement, safeguarded
Amount24,500.00EUR

Identical entry, either way

What it guarantees.

Each of these is enforced rather than intended, and each is something you can sit down and try to break on a call. We would rather you did.

  • Migrations run as their own job, never on application boot, so replicas cannot race each other through the same schema change.
  • Expand and contract means every schema change is rollback-safe by construction rather than by care.
  • The system alerts on its own invariants, so an imbalance is an alert rather than a discovery.
  • A dual run reconciles the old book against the new one daily, so the switch is a decision rather than a leap.

Tell us what you run on today.

Migration is the part of a core banking change that actually goes wrong, and the conversation is more useful early than late.