Work
Selected work.
Client names stay private; the engineering doesn't. Each case study covers the problem, how the system was built, and what changed.
01Healthcare SaaS
Rebuilding a healthcare SaaS platform without stopping it
A long-lived PHP application rebuilt as Next.js portals, a .NET API and mobile apps on Terraform-managed Azure, with every subscriber carried across.
- Clients
- Portals
- API
- Data
Next.js · React · TypeScript · Tailwind CSS · .NET · +8
02Data & integration
A file ingestion pipeline that runs itself
Partner files collected from FTP and landed in cloud object storage by containerized Python jobs: versioned, monitored and pleasantly boring.
- Partner FTP
- Ingest job
- Landing zone
- Consumers
Python · Docker · Container jobs · Azure Blob Storage · FTP · +2
03Regulated enterprise
A zero-secret platform for a regulated enterprise
Containerized APIs on Kubernetes with managed identity everywhere, end-to-end tracing, and pipeline templates teams reuse instead of reinventing.
- Clients
- Ingress
- API pods
- Data & queues
Kubernetes (AKS) · Docker · .NET · Entra ID · Managed identity · +3
04Industrial manufacturing
A fast, findable web presence for an industrial manufacturer
A modern marketing site that loads instantly, ranks for what buyers search for, and turns spec-sheet browsing into quote requests.
- Buyers
- Edge
- Site
- Inquiries
Next.js · React · TypeScript · Tailwind CSS · Structured data · +2
Have a system that should be on this page?
Start a project