I run what I ship.
Monitoring, incident response, and the unglamorous upkeep that keeps software honest. Shipping is the start of a system’s life, not the end of it — so I stay on to run what I built, or to steady what someone else did. One engineer, business hours, and an escalation path we agree up front.
What's included
What you get
Metrics, logs, and traces through one stack; alerting wired to symptoms rather than noise; and the same infrastructure-as-code I build with, so recovery is reproducible instead of heroic.
Doota Mail — built to be run, not just shipped
An ingest path that never drops mail, idempotent consumers, and a one-command IaC deploy in CI — the operational shape I bring to client systems. The details live with the case study.
I take on a small number of projects at a time.
Tell me what you're building and where it hurts. I'll say honestly whether I'm the right person for it.