The kind of infrastructure I like to keep close.

What runs

I maintain a small set of personal infrastructure because it teaches different lessons from building polished software.

• A home lab for storage, media, experiments, and services that are better owned than rented.
• Home automation for the useful kind of invisible technology: lights, sensors, routines, and the occasional reminder that convenience needs boundaries.
• Networking and device management because unreliable foundations make every other system feel worse.
• Validator infrastructure as part of a long-running interest in blockchain networks and Web3 communities.

What does not belong here

No IP addresses. No topology diagrams. No private endpoints. No operational details that turn curiosity into attack surface.

The point is the shape of the work: I like systems that have to keep running after the fun part of building them is over.

Why it matters

Maintaining infrastructure changes how you think. It makes trade-offs concrete. Reliability, privacy, cost, power, backups, and security stop being abstract nouns and become things that interrupt your evening if you ignore them.