Proof in production
Two systems we built and run.
Two production platforms designed, built, and operated end to end — backend, frontends, infrastructure, data pipelines, content. Everything the offer promises already runs here.
One pattern at a time.
Narrower cases — each takes one production pattern or one decision and shows it concretely, at the scale it actually runs.
Batch service & lifecycle visibility
Background work as production engineering: every batch job has a visible lifecycle, prioritization, and idempotent semantics.
View case →
Integration testing → DB-per-test, real layers
Behaviour verified by simulating real usage, freezing the resulting database, and replaying it through the same code that runs in production.
View case →
Structured Data → Knowledge Surfaces
Turn entities, relationships, and classifications into useful pages, graphs, and explanations. AI enriches typed fields. It does not write prose.
View case →
MVC monolith → REST API + modern frontend
Migrating a long-running ASP.NET MVC application to a REST API + Next.js frontend, page by page, never big-bang.
View case →
Legacy MVC replacement: gradual extraction or controlled twin?
A synthetic case study. NaboWorks A/S, a 12-year-old ASP.NET MVC service marketplace, and the modernization decision a System Report has to answer before any code is written. Detailed reference document for the companion sample report.
View case →