About
Heroic recoveries make great stories but terrible operations. I design for Monday mornings, not war rooms.
I'm Matthias. Senior infrastructure engineer, based in Arizona. 25+ years in healthcare IT, hybrid environments, and the kind of systems that break at 3 AM on a holiday weekend.
I spent 10 years as the sole IT leader for MomDoc, one of Arizona's largest OB/GYN practices. Took the organization from peer-to-peer networking and paper charts to a fully integrated VMware datacenter across 21 sites, 80 clinicians, and 250+ employees. No external consultants for the entire tenure. Led full EHR adoption in 2005. Deployed iPad-based VDI for 200+ providers in 8 weeks in 2011, years before it became an industry standard.
After that, six years as Senior Cloud Architect at a cloud service provider. VMware and Azure hybrid environments. Veeam immutable backup architecture. Senior escalation point for downstream MSPs and the CEO's primary technical advisor.
Four generations of medicine in my family, all in Arizona's East Valley. Spanish bilingual.
I take on projects that interest me: stabilization, migration, recovery architecture. Everything goes back to your team with documentation they can actually use. 90% of my engagements end with a clean handoff, not a retainer.
Fragile, undocumented, held together by one person's memory. That's exactly the kind of problem I solve. Find me on LinkedIn or call (480) 666-1693.

Sole IT leader for a 21-site, 250-employee healthcare organization. Paper charts to fully integrated VMware datacenter. Early EHR. HIPAA from day one.
VMware and Azure hybrid environments. Senior escalation point for downstream MSPs. Evaluated emerging technologies before market adoption.
iPad-based VMware Horizon View for 200+ providers in 2011. Built the proof of concept over a weekend. Became an industry standard years later.
Designed and deployed Veeam immutable repositories for ransomware-resistant data protection across production client environments.
Every script should eliminate more work than it creates. If it needs babysitting, it's not automation.
Hardening shouldn't require a dedicated initiative. It should be how things are built from the start.
If the person who built it leaves and the system breaks, the system was never really finished.
The goal is a team that doesn't need me after I leave. If you're still calling me six months later, I didn't do my job.
with on-site availability for cutovers.
and enterprise procurement ready.
know the cost before you commit.
available across major time zones.