Jeremy Brown @virtetc

@alphafox I would start with a 1.2GB HDD. You will never run out of space.

@______punished #BeenThereDoneThatGotTheTShirt

I hear stories like this from peers all the time. I often tell them to still go for it. Make a better wheel. Find some way to differentiate yourself—even if it’s simply providing a different customer experience. There’s a reason why you often see a Walgreens just across the street from a CVS and there is a reason why this works. Plus, you never know, someone you see as a competitor today might get bought and blown up (e.g. VMware/Broadcom) and the field opens up.

Key things I’d love your take on: - The “honest UI” that only offers operations that actually work on each hypervisor - Cross-hypervisor migration handling disk formats properly - The API-first design (visible REST calls + easy “Copy as curl” in the UI) - How the simulated telemetry/alarms/tasks feel in the dashboard - Overall, is this direction useful for people doing heterogeneous or exit projects? Technology Preview, so real feedback appreciated.

@grok what do you think of the vOpsCentral demo at demo.vopscentral.com? One web console that talks native to ESXi (no vCenter), Hyper-V, Proxmox, KVM, XCP-ng, and SimpleVM. Agentless, with cross-hypervisor migration and a guided live migration wizard. Trying to kill the “juggle six different consoles” problem after VMware changes. Demo has no signup — just pick small/medium/large simulated fleet and explore.

@anupamrjp Thinware vOpsCentral One console, supports all major hypervisors (ESXi, Hyper-V, SimpleVM, KVM, Proxmox and XCP-ng). Try the fully functional interactive demo at: demo.vopscentral.com

@anupamrjp simplevm.com Enterprise virtualization for everyone. SimpleVM is a free forever type-1 hypervisor.

@sflorimm vopscentral.com Platform-agnostic virtualization management.

Excellent framing — KVM really is the common foundation across so many modern platforms. vOpsCentral treats SimpleVM (Thinware’s KVM-on-Rocky) and generic KVM as first-class citizens with full live-migration compatibility between them, while also managing the other four platforms in the same console. It’s built for exactly these hybrid realities with accurate disk-format handling for powered-off any-to-any moves. Interactive demo: demo.vopscentral.com Have you looked at unified management options for mixed KVM + other hypervisor estates?

@kestra_io vOpsCentral pairs nicely. Built with an API-first model every action includes the API hint on screen. No need to spend countless hours reading API documentation—the console trains you. Full interactive demo available now: demo.vopscentral.com Feedback welcome.

Had another conversation today reminiscing about the “good ole days” when you could actually buy a software license and own it. I’m more convinced than ever that demand for that model is far greater than the current software industry wants to admit. Thinware is reaffirming our commitment to perpetual-first licensing. Buy it. Own it. Use it forever. No lock-in. If this sounds refreshing—or forign—let’s talk. I’d value your perspective. #PerpetualLicensing #SoftwareOwnership #CostControl #OnPrem

The exit planning conversations are definitely heating up. One angle that doesn’t always get enough attention early enough is the ongoing management cost after the move. You solve the licensing problem but can inherit a new one: tool sprawl and constant context switching across whatever mix of platforms you end up with. Teams that plan for a lighter, unified management layer from the start tend to spend a lot less time fighting their tools once everything is live. What part of the post-exit operational model are you thinking about most right now — migration itself or the day-to-day management burden afterward?

Solid advice on the migration side — controlled waves, proper dependency mapping, and rollback planning are exactly right. The piece that often gets underestimated is what happens after the workloads land or in a partial infrastructure ship: you now have a heterogeneous estate and the management surface area explodes. Different UIs, different “gotchas,” and constant context switching just to answer simple questions like “can I safely live-migrate this or is it cold-only here?” How are you handling day-to-day operations and visibility once the Proxmox side is live alongside any remaining platforms?

This is the part that doesn’t get enough airtime. The licensing hit is real, but the downstream effect is often even more painful — extra layers, new appliances, and processes that feel deliberately more complicated than they need to be. When you’re already running (or moving to) a mixed estate, every additional bit of complexity multiplies the daily drag. A lighter approach that still gives you clear visibility across platforms without forcing another heavy manager in the middle can remove a surprising amount of that overhead. What specific part of the new licensing or management stack is eating the most time for your team right now?

One of the quieter but most expensive parts of post-VMware exits is the sudden management surface area explosion. You go from one (admittedly awesome) console to juggling standalone ESXi hosts, Proxmox web UIs, Hyper-V Manager, libvirt/virsh sessions, and whatever storage or backup tools each platform brings. Every context switch carries risk — different terminology, different “what actually works here” rules, and constant mental overhead figuring out whether a workload can move without downtime or whether a disk format conversion will even succeed cleanly. The practical cost shows up in migration waves and daily ops: time lost to format guesswork, failed live-migration attempts because clustering prerequisites weren’t fully met, and the general drag of never quite knowing the real boundaries of each platform without testing in production. vOpsCentral grew directly out of running these mixed estates. One modern web console that talks straight to each platform’s native API (SimpleVM, KVM, standalone ESXi, Hyper-V, Proxmox, XCP-ng). It reports capabilities honestly instead of offering options that will fail, handles powered-off any-to-any VM conversion with proper format awareness, and ships a guided wizard that actually configures the firewall, SSH trust, and readiness checks needed for live migration on plain KVM/Proxmox hosts — instead of leaving you with a 20-step wiki. It’s not about forcing everything into one tool overnight. It’s about cutting the tool sprawl so the team can spend more time on actual workloads and less time fighting the management layer. What’s the single biggest source of operational drag or context-switching pain you’re seeing in your environment right now? Fully interactive demo (real simulated fleet, no install): demo.vopscentral.com

Climbing costs are pushing lean teams and MSPs to look for genuinely predictable alternatives. Reducing both licensing surprises and management overhead is a big part of regaining control. Thinware SimpleVM was designed as a free-forever Type-1 KVM hypervisor with intuitive web management and broad hardware support—aimed at teams that want capability without the complexity or recurring cost tax. simplevm.com

Scale like this really drives home why honest workload assessment and phased execution matter so much. The operational and financial stakes are enormous. Thinware SimpleVM’s unlimited scalability, live migration, automated HA failover, and web management on a hardened KVM base can serve as a straightforward on-prem foundation for teams that want to reduce complexity without introducing new licensing variables. simplevm.com

Powerful example. The renewal email as catalyst is something we see constantly, and the shift to $0 licensing with full control changes the economics and the peace of mind. For organizations looking for a similarly predictable, no-surprise foundation without having to adopt a full stack, Thinware SimpleVM offers a free-forever Type-1 KVM option focused on exactly that simplicity and sovereignty. simplevm.com

Renewal calls really do accelerate the conversation for a lot of teams. The appeal of removing the ‘hostage pricing’ variable is huge. One approach Thinware has taken with SimpleVM is eliminating that variable entirely—free forever, no subscriptions, with enterprise features like live migration and web-based management so teams can focus on operations instead of licensing roulette. simplevm.com

Exactly—treating every workload the same in wave one is where a lot of hidden friction shows up later. Solid assessment and prioritizing low-uncertainty systems first makes the whole transition more predictable. For teams that want a clean, licensing-surprise-free Type-1 KVM foundation with straightforward web management and easy VMware v2v paths, Thinware SimpleVM was built with exactly that in mind. simplevm.com