Infrastructure That Tells the Truth

For those that want the plan not the buzzwords.

What I Do

I design and deploy infrastructure that works—securely, efficiently, and without vendor bloat.

Most of my work centers around helping small businesses, clinics, and lean operations modernize the systems they depend on. Whether it’s stabilizing a failing network, securing legacy equipment, or building visibility into data that’s been ignored for years, I bring a practical, full-stack approach shaped by over two decades in IT.

  • Secure edge deployments with pfSense or VyOS
  • Network visibility and threat detection using Suricata and OpenSearch
  • HIPAA-conscious infrastructure for small healthcare teams
  • Remote access solutions that prioritize encryption and auditability
  • Lightweight dashboards and logging pipelines for real-time insight
  • General systems cleanup and integration, especially where internal IT has hit a wall

I stay focused on the projects I can do right. If you’re unsure where your problem fits, I’ll take a look—and if it’s not in my wheelhouse, I’ll say so.

How I Work

I don’t run a call center. I’m not backed by a sales team. I’m a full-stack infrastructure engineer who’s been hands-on with every layer of the IT stack—from dial-up era routers to telco-scale network operations to modern open-source observability.

I’ve built systems that are still in use 10+ years later. I’ve untangled disasters left by outsourced vendors. I’ve worked for Silicon Valley giants and rural telcos alike, and the lesson is always the same: do it right, or do it twice.

When I take on a client, I’m not guessing. I build exactly what’s needed—lean, secure, and future-ready. I use tools that I trust and support systems that I design. If I didn’t build it, I’ll audit it. If I can’t stand behind it, I won’t sell it.

I take on only as many clients as I can personally support. That means when you call, you're not routed through layers—I pick up. And when alerts come in, they go to me, not into a queue.

You get clarity, documentation, security, and a direct line to someone who knows your system inside and out.

If you're looking for a quick fix or the cheapest option, I'm not it.
If you're looking for someone who will own the outcome and build it right—we should talk.

About Me

I’ve been working in IT, networking, and infrastructure for nearly three decades. What started with a natural talent for breaking down language into patterns turned into a lifelong obsession with systems—both human and machine.

I got my professional start in the early 90s, building and fixing computers when the internet still made noise. By 2001, I was fully immersed in the rural telecom world—supporting dial-up users, configuring Cisco 3640s, and keeping critical infrastructure running when “centralized support” meant you had to know everything, because no one else could.

For 14 years, I worked at a rural telecom NOC serving over 20 independent telcos. I wore every hat: Linux admin, routing engineer, software developer, system integrator, crisis manager. I built internal tools to manage DOCSIS, SIP, Calix FTTH, and SS7 log pipelines—tools that are still in use today.

Later, I joined Elastic as a support engineer, where I worked directly with large enterprises and high-scale infrastructure teams. The experience sharpened my understanding of advanced tooling, observability, and scalable systems. But after leaving Elastic, I dipped into freelance consulting and hit a wall—while I knew the technology inside and out, I quickly realized I didn’t fully understand what smaller teams and businesses actually needed from it.

I wasn’t interested in guessing. So I got back to the roots of it—what it really takes to support everyday operations in the places that don’t have enterprise budgets or dedicated teams. I took on my current role: an all-hats NOC position that puts me on the front lines, handling everything from residential internet issues to hospital networks, municipal systems, and small business fire drills. Phone calls. Field tickets. Late-night problems no one else wants to own.

And that’s where I finally found it. The common threads. The real needs. The things that never make it into spec sheets but make or break a business.

That’s the perspective Dangerous Metrics is built on—deep technical understanding *and* a firsthand grasp of what the people behind the systems actually deal with day to day.

Dangerous Metrics is my answer to that.

I’m still that all-hats engineer at heart. I’ve worked inside telecoms, startups, NOCs, and frontline support desks. I’ve built everything from custom monitoring platforms to VPN mesh backbones to PBX systems that talk back. I know what it means to be the one on call, the one digging through logs, the one fixing what the prepackaged tools missed.

This isn’t theory. It’s lived experience.
And when I take on a client, I bring all of it with me.

Who I Help

[Target audiences: clinics, small manufacturers, rural telco, small MSPs, etc.]

Contact

[Basic instructions, or embed form if desired. Or just display your email for now.]

Email: contact [at] dangerousmetrics.com