Selected Works

[ // ] — CASE LIBRARY

Every deployment below shipped, measured, and is still running. Open a card for the brief, the architecture and the outcome.

Eleven disconnected ERPs across four countries collapsed into one Odoo 18 estate.

Sector ManufacturingScale 3,400 seatsYear 2025

Challenge: Eleven legacy ERPs, four fiscal regimes, and month-end close taking nine days across parallel spreadsheets nobody trusted.
Approach: A single canonical data model, staged dual-run migration with reconciliation gates, and a custom multi-company consolidation engine on Odoo 18.
Stack: Odoo 18 EE · PostgreSQL 16 · Kafka · dbt · Kubernetes
Outcome: Month-end close 9 days → 31 hours. 41.2M records migrated with zero downtime. Licensing cost down 34%.

Sub-40ms fraud inference on a streaming feature platform with full model auditability.

Sector BankingLatency P99 34msYear 2025

Challenge: Fraud decisions ran overnight in batch, so losses were discovered a day late and analysts could not explain a single score to a regulator.
Approach: A streaming feature store with point-in-time correctness, a model registry with signed artefacts, and per-decision SHAP traces persisted for audit.
Stack: Flink · Feast · Triton · MLflow · Terraform · EKS
Outcome: P99 inference 34ms. Fraud loss down 41%. Every decision reproducible and explainable to the regulator, on demand.

A dual-region Kubernetes platform carrying 2.1M daily shipment events.

Sector LogisticsThroughput 2.1M / dayYear 2024

Challenge: A single-region monolith could not survive a regional outage, and freight tracking degraded precisely when volume peaked.
Approach: Active-active across two regions, an event mesh with idempotent consumers, and progressive delivery so a bad release could never reach all traffic.
Stack: Kubernetes · Istio · NATS · Terraform · OpenTelemetry
Outcome: 99.98% availability sustained through two live regional failover drills. MTTR down to 6.4 minutes. Cloud spend down 38%.

One WCAG 2.2 AA portal replacing 26 departmental front doors.

Sector PublicServices 26 unifiedYear 2024

Challenge: Twenty-six departmental portals, twenty-six identity systems, and citizens abandoning applications they could not complete.
Approach: A shared design system, one federated identity layer, and a service framework where each department ships its own journey without forking the platform.
Stack: TypeScript · React · tRPC · OIDC · PostgreSQL
Outcome: Application completion up 62%. WCAG 2.2 AA verified by external audit. Mean task time cut from 14 minutes to 4.

[ 01 — 04 ] DEPLOYMENTS ON RECORD Request the full case library ↗

DEPLOYMENTS0

ENGINEERS0

AVG. TENURE0

RETENTION0

We will connect you with the operators who run these systems today.

[ // ] — INQUIRY

Open a channel

A principal engineer reads every inquiry and replies within one business day.

odyntiq://inquiry-terminalChannel secured · TLS 1.3