Another entry in the "What Is a…" series, but this one comes with a confession. Most of these posts explain a VergeOS concept cleanly. This one starts with me ignoring it, and paying for it. The night my demo box became production It started innocently. After a call
I have a confession: I love a good TUI. Not the GUI, not the raw CLI: the TUI. The full-screen, keyboard-driven terminal app. k9s for Kubernetes, lazygit for git, htop for processes. The ones that make you feel like you're flying the plane instead of filling
Quick preface, so nobody mistakes this for a gap-filler: VergeOS already has AI capabilities built into the platform, its Private AI feature set. So this isn't "VergeOS can't do AI, here's a workaround." It's the opposite. The platform handles
Building a VergeOS Demo Box from eBay e-Waste There's a persistent myth that to really try enterprise hyperconverged infrastructure you need enterprise hardware — a rack, a SAN, two beefy servers, a five-figure quote. So people never get hands-on, and the software stays abstract. I wanted
I was chatting with George Crump — VergeIO's CMO, and someone who's been around storage and virtualization long enough to have watched the whole HCI story play out — and we got onto how much of my writing dives straight into the deep end: Kubernetes, reconcilers, firewall automation.
I wanted Rancher to provision a Kubernetes cluster directly onto VergeOS — clone the VMs, install RKE2, hand me a Ready cluster, no manual node-building. VergeOS ships an integration for exactly this: a Rancher UI extension and a docker-machine node driver, installed from their Helm chart repo. Almost all
The silent deploy The task was unremarkable: spin up a new VM from a recipe, attach it to the management network, hand it back. I asked Claude to do it. It ran vrg recipe deploy ubuntu-base --set name=metrics-02, watched the task complete, and reported success. Exit code
The result first $ curl -s --max-time 5 http://192.168.1.202/ | grep -o '<title>.*</title>' <title>VergeOS + Kubernetes: integration success</title> That hit a custom nginx pod on a single-node k3s cluster, through a LoadBalancer Service whose
The locked room I had an admin tier I was happy about: a VergeOS internal network for the management VMs — the jump host, the box with vrg installed, the handful of internal tooling boxes you don't want anywhere near the public network. Outbound internet for package updates, but
If you run a VergeOS cluster, you’ve probably moved between three control surfaces: * The WebUI for clicking around * The REST API for scripting * The Terraform provider for declarative infrastructure The Verge.io team has now shipped a fourth option: vrg. But the important story is not simply “VergeOS has
new VergeOS related content is coming very soon.. stay tuned!