The number has to be
right to the cent.
In finance, a computation settles a trade, sizes a risk, or closes a book — and a regulator can ask you to retrace exactly how it was produced, years later. Most of it runs on models that drift and reconciliations that don't quite close. We serve financial services with software, not cranes : deterministic settlement + risk + reconciliation compute on Heisen, model-risk verification, and the Maxor Sentinel tamper-evident ledger. Same input, same result, to the cent, immutable. The firm owns the trade ; we make the compute behind it provable.
To the cent
Reconciliation that closes — deterministic compute
SR 11-7
Model-risk management posture
Tamper-evident
Maxor Sentinel immutable ledger
Sovereign
Canada-built, data stays in your control
Six exposures across the compute + the ledger.
Financial risk is model + record risk before it's market risk : a model the regulator won't accept, a reconciliation that won't close, a ledger an auditor can't trust. The exposures below are what deterministic, audit-grade software + a tamper-evident ledger exist to control — the software half of a financial operation done to the standard.
Non-reproducible model output
A risk or valuation model that gives a different number on re-run can't pass model-risk review (SR 11-7). Heisen is deterministic — same input, same result, with inputs + version pinned for the regulator's replay.
Reconciliation that won't close
When positions, cash, and trades don't reconcile to the cent, the break hides risk + invites a finding. Deterministic reconciliation closes the balance and pinpoints the break, every run.
Tamperable audit record
A mutable ledger is a fraud + compliance exposure — an auditor can't trust what could be edited. Maxor Sentinel is a tamper-evident, hash-chained ledger — the record an auditor can verify wasn't altered.
Model-risk non-compliance
SR 11-7 + OCC 2011-12 mandate model validation + governance. A model without a reproducible, documented basis fails the exam. We build the verification + documentation posture in from the start.
Settlement error
A settlement computed wrong is a financial + counterparty-trust loss. Deterministic settlement compute returns the same, correct result every run — to the cent, audit-trailed.
Data sovereignty + control
Trade + client data on a foreign-controlled platform is a sovereignty + privacy exposure. Heisen is Canada-built + sovereign — the data + the compute stay in the firm's control, deployable in its environment.
Software-first. The compute + the ledger.
Financial services is a software engagement for us — deterministic compute, model-risk verification, immutable ledger, reconciliation. Six concrete fits.
Deterministic settlement + risk compute
Settlement, valuation, and risk compute that's reproducible to the cent — the number the firm can defend to a counterparty and a regulator, version-pinned for replay.
Model-risk verification (SR 11-7)
Model validation + governance built to the SR 11-7 / OCC 2011-12 posture from kickoff — reproducible, documented, exam-ready, not reconstructed at review.
Tamper-evident immutable ledger
Maxor Sentinel — a hash-chained, tamper-evident ledger for trades, positions, and audit events. The record an auditor can verify wasn't altered.
Reconciliation to the cent
Deterministic reconciliation across positions, cash, and trades — the balance closes, the break is pinpointed, every run. No silent drift.
Audit-trailed compliance record
Maxor Audit — every computation + event attributable, contemporaneous, and reproducible. The exam file generated as the work happens.
Embeds into your core / risk stack
Heisen embeds by API into your existing core-banking / risk / treasury stack — the deterministic + immutable layer alongside your systems, data residency intact.
Financial Services in the field
From sector context to the lifts we engineer — a look at where this work happens.
The standards we work to.
We build the software to the model-risk + security + data-integrity standards your firm is examined against. The trading + investment decisions are the firm's — we build the deterministic, provable compute behind them.
Model risk management
The supervisory guidance on model risk. Our software is built to its validation + governance posture — reproducible, documented, exam-ready.
Trust services criteria
The trust-services standard for security, availability, and confidentiality. Our software-development + operations posture is built SOC 2-aligned.
Information security management
The ISMS standard. Our software keeps trade + client data secure + resident under an ISO 27001-aligned posture.
Data-integrity principles
Attributable, Legible, Contemporaneous, Original, Accurate + Complete, Consistent, Enduring, Available. The financial record holds to ALCOA+ for the exam.
Fundamental review of the trading book
Where market-risk capital is computed, FRTB governs. Our deterministic risk compute produces the reproducible, defensible numbers FRTB IMA expects.
Canadian privacy law
The Canadian privacy framework. Our software keeps client data compliant + resident, with sovereignty by default.
Software only. No cranes, no rigging here.
Financial services is a pure software engagement. Our three crane-lift pillars don't apply — the value is entirely in the deterministic compute + the immutable ledger. Here's how each pillar applies, honestly, including where it doesn't.
Sealed plans + emergency response
Not applicableHeavy crane lifts don't apply to a financial-services software engagement — there's no crane pick in our scope here. The engagement is entirely the deterministic compute + the tamper-evident ledger.
Distribution + training + implementation
Not applicableWith no crane lift in scope, CRANEbee lift simulation doesn't apply to this sector. Our modeling value is the deterministic settlement + risk compute, not a crane study.
Distribution + advisory + training
Not applicableMurlink rigging doesn't apply to a pure software engagement — there's no physical handling in our scope for financial services.
Deterministic engineering platform
The whole engagement. Deterministic settlement + risk + reconciliation compute on Heisen, model-risk verification (SR 11-7), and the Maxor Sentinel tamper-evident ledger + Maxor Audit. Reproducible to the cent, immutable, audit-trailed. Sovereign, Canada-built, data residency intact. Heisen embeds into your core / risk stack by API.
Financial software that passes the exam.
For financial services, the engagement is the software — anchored on Heisen, backed by the Maxor Sentinel ledger. We build deterministic, audit-grade software : same engineering posture, same team kickoff to go-live, sovereign by default. A model that returns the same number on re-run and a ledger an auditor can verify wasn't altered. Engineered in Canada, owned by you.
Heisen — our deterministic intelligence layer — is optional on any build: embed it or not, your call. Either way it plugs into a fresh custom app or your existing third-party software via API.
Deterministic settlement + risk platform
Settlement, valuation, and risk compute reproducible to the cent — the number the firm defends to a counterparty and a regulator, version-pinned for the SR 11-7 replay.
Maxor Sentinel immutable ledger
A hash-chained, tamper-evident ledger for trades, positions, and audit events — the record an auditor can verify wasn't altered, sovereign and resident.
Reconciliation + compliance record
Deterministic reconciliation that closes to the cent + an audit-trailed compliance record — the break pinpointed, the exam file generated as the work happens.
Scope your financial-services engagement.
Tell us the function, the models, and the model-risk + audit obligation. A senior lead responds within one business day with a scoped engagement and a path to first deliverable.