Regulated compliance software
A platform moving off a .NET monolith without stopping
An eight-year-old backend of about 1,800 source files and 95 controllers, moving onto a
modern API and front end with the Strangler Fig pattern. No rewrite, no downtime, no
feature freeze. Old and new run side by side in the same cluster under a written contract
for who is allowed to change what. Cutover is per customer: an administrator moves one
tenant onto the new stack, and one call moves them back. Around twenty feature areas
crossed over in six weeks.
378 API endpoints
24 route modules behind the seam
~2,670 automated tests
GitOps delivery on Kubernetes
Multi-site service operations
An operations platform where the hard part was the accounting
A single-page front end over serverless functions, bridged to the ERP the business already
ran on. The screens were the easy half. Every amount is handled in integer cents from end
to end. Publishing a record is idempotent, so a retry cannot create a duplicate or charge
twice. Invoices from the accounting system are reconciled against operational records, and
anything that will not match goes to an itemised review queue instead of being rounded
into a total that looks fine.
46 serverless functions
73 database migrations
364 automated tests
Investment screening
A screening tool that refuses to invent a number
Long PDFs in; a filled screen and a spreadsheet out that lines up row for row with the
workbook the team already uses. Nine deterministic checks, with no model involved, run
over every extracted figure. Three of them exist because we hit that exact error once. A
figure we could not find stays visibly missing, with the reason, rather than becoming a
zero that someone forwards to a committee.
nine deterministic cross-checks
no model in the checking path
