Compute & Hyperconvergence
Six generations of virtualization. One enduring commitment to running too many VMs.
Pawsitively Innovating Tomorrow, Yesterday.
Enterprise-grade ambition. Home-lab-grade budget. A fiercely independent technology laboratory advancing the frontiers of automation, infrastructure, and strategically scheduled naps.

CHMALABS is a proudly independent technology laboratory where complex infrastructure meets simple curiosity—and occasionally a cat walking across a keyboard.
We explore self-hosting, systems engineering, automation, and observability with the conviction that anything worth doing is worth containerizing, monitoring, documenting, and eventually rebuilding from scratch.
At CHMALABS, we leverage cutting-edge, cloud-native, feline-driven synergies to maximize purrformance, minimize accountability, and proactively disrupt systems that were working perfectly fine.
Through strategic innovation, aggressive automation, and the occasional unauthorized nap, we empower our infrastructure to achieve five-nines availability, nine-lives resiliency, and zero measurable responsibility when neither is achieved.
Because at CHMALABS, we don't just think outside the box. We sit in it, automate it, containerize it, and then knock it off the table.
Six virtualization platforms. Thirteen years. Countless rebuilds. Still no change control.
The humble beginning. One machine, several virtual ones, and entirely too much confidence.
Windows Server virtualization grew into clustered infrastructure. Redundancy entered the chat.
vSphere management and enterprise-grade infrastructure. Now with more consoles.
Hyperconverged infrastructure, where compute and storage learned to share.
Formerly Azure Stack HCI. On-premises infrastructure with cloud ambitions.
Today's lab foundation. Same curiosity. Better containers. Rebuilds still available on demand.
Platform sequence reflects CHMALABS history; individual migration dates are intentionally omitted.
From enterprise infrastructure to automation and observability: systems we've built, operated, explored, or occasionally had to rebuild.
Six generations of virtualization. One enduring commitment to running too many VMs.
Cloud resources, clusters, and container workloads across more platforms than the budget requested.
Automating repeatable work and inventing exciting new failure modes in the process.
Graphs, traces, logs, and alerts that explain why a service stopped being optimistic.
Certificates, access controls, networks, and workflows with very serious-looking approvals.
Data pipelines, self-hosted media, and enough storage to require a separate meeting.