About / the operator behind the systems

I work where
systems meet reality.

I'm DrOSAlchemist, an AI/ML and network systems engineer. My work lives at the intersection of model infrastructure, Kubernetes, networking and security: the pieces that make a platform useful after the demo is over.

I like problems that cross boundaries. A model needs a GPU, a scheduler needs a capacity contract, a service needs a name and an address, and every change needs a way to be seen and reversed. Connecting those details is where reliable systems take shape.

This site is a working notebook: selected engineering projects, field notes and ideas about building infrastructure that stays understandable under pressure.

KubernetesAI / ML infrastructureGPU schedulingDNS & IPAMCloud networkingPlatform securityObservabilityGitOps
DrOSAlchemist GitHub profile avatar
DR OS / SYSTEMS PRACTICEProfile image via GitHub
01

Make the system legible

Good automation exposes intent, ownership and failure modes instead of hiding them behind a button.

02

Design for the day after launch

Operations, observability and rollback are part of the architecture, not cleanup for later.

03

Secure the seams

Identity, policy and network boundaries matter most where components meet.