Introducing Zyvor AI Labs: Building Open Infrastructure for the Post-VMware Era

Susant Sahani — Mon, 10 Aug 2026 07:56:20 +0000

Enterprise infrastructure is changing.

VMware licensing changes, rising public-cloud costs, Kubernetes adoption, growing AI workloads, and increasing infrastructure complexity are forcing organizations to rethink how they operate compute infrastructure.

At Zyvor AI Labs, we're building an open infrastructure platform for that transition.

Our goal is straightforward:

Give enterprises the freedom to migrate, run, secure, automate, and operate workloads without becoming locked into another infrastructure vendor.

Meet HyperSDK

At the center of Zyvor is HyperSDK, our infrastructure modernization and orchestration platform.

We don't see infrastructure modernization as simply converting a VMware virtual machine into another disk format.

The lifecycle is much bigger:

Discover → Assess → Migrate → Validate → Operate → Secure → Automate

HyperSDK brings together technologies for virtualization, migration, Kubernetes, networking, automation, AI infrastructure, and operational intelligence.

hyper2kvm: VMware to KVM migration

hyper2kvm is focused on migrating virtual machines toward KVM-based infrastructure.

Migration can involve much more than converting a VMDK to QCOW2.

The guest operating system must still boot correctly afterward.

hyper2kvm addresses areas such as:

Disk conversion
VirtIO preparation
Windows migration readiness
Boot-path remediation
initramfs repair
GRUB repair
Post-conversion validation

Our goal is to make VM migration repeatable and automatable rather than treating every VM as a manual project.

GuestKit: Know before you migrate

One of the biggest migration risks is discovering a problem after cutover.

That's why we built GuestKit.

GuestKit provides offline VM disk intelligence so infrastructure teams can inspect guest disks before booting or migrating them.

It can help answer questions such as:

Is this VM likely to boot after migration?
Are the necessary drivers present?
Is the bootloader healthy?
What migration blockers exist?
What should be fixed before cutover?

GuestKit works with common virtual disk formats including QCOW2, VMDK, and RAW.

This becomes especially valuable when assessing hundreds or thousands of machines ahead of a migration wave.

Zeus OS: Virtual machines on Kubernetes

Containers aren't replacing every enterprise VM.

A large number of organizations need to operate both.

Zeus OS is our visual infrastructure operating layer around Kubernetes and KubeVirt.

We're building it to make Kubernetes-based virtualization practical for infrastructure teams managing both traditional VMs and modern containerized workloads.

Machina: KVM operations

After migration, someone still needs to operate the infrastructure.

Machina focuses on KVM and libvirt management, VM lifecycle operations, provisioning, automation, and day-two infrastructure management.

The objective is to make open virtualization infrastructure easier to operate at enterprise scale.

PacketWolf: Network intelligence

Modern infrastructure isn't only about compute.

Understanding how workloads communicate is equally important.

PacketWolf focuses on network intelligence and security, connecting workload and process activity with network behavior.

We're working with technologies including eBPF, Cilium, and Hubble to provide deeper infrastructure-level visibility and policy automation.

HyperCluster: Kubernetes lifecycle

HyperCluster focuses on Kubernetes cluster lifecycle automation.

That includes workflows around:

Preflight validation
Deployment
Scaling
Upgrades
Cluster operations
Infrastructure teardown

Running Kubernetes is easy to demonstrate.

Operating it consistently across real environments is much harder.

That's the problem HyperCluster is intended to address.

Aether: Workload portability

Infrastructure teams shouldn't have to redesign an application every time its runtime changes.

Aether explores a portable model for deploying and operating workloads across environments such as:

Kubernetes
KubeVirt
Podman
Bare metal

The broader principle is simple:

Applications should be portable. Infrastructure should remain a choice.

Forge: AI infrastructure

AI is becoming another major infrastructure workload.

Forge focuses on operating enterprise AI and GPU infrastructure, including areas such as:

GPU placement
Utilization
Governance
Cost visibility
Networking
AI infrastructure operations

AI workloads shouldn't require organizations to abandon everything they already know about infrastructure engineering.

Infrastructure should belong to the customer

One principle influences nearly everything we're building at Zyvor:

Infrastructure should belong to the customer, not the infrastructure vendor.

An enterprise should be able to decide where a workload runs according to its own requirements.

That might be:

KVM
Kubernetes
KubeVirt
Private cloud
Public cloud
Bare metal
Edge infrastructure
Hybrid environments

The infrastructure platform should help organizations make those choices.

It shouldn't remove them.

VMware exit is only the beginning

A lot of conversations today start with:

"How do we move away from VMware?"

That's an important question.

But migration is only the first part.

After migration, organizations still need:

Virtual machine lifecycle management
Networking
Observability
Security
Automation
Disaster recovery
Cost visibility
Windows workload support
Kubernetes integration
AI infrastructure management

Moving a VM solves a migration problem.

Operating the next infrastructure platform solves a much larger one.

That's why we're building Zyvor as an infrastructure platform rather than only a VM conversion utility.

Why open infrastructure?

We believe the next generation of enterprise infrastructure will increasingly be built around open technologies such as:

Linux
KVM
Kubernetes
KubeVirt
libvirt
eBPF
Cilium
Containers
Open APIs

These are already powerful building blocks.

The opportunity is making them easier to deploy, integrate, migrate to, and operate as one coherent infrastructure environment.

That's what we're working on at Zyvor AI Labs.

What we'll publish on DEV

This will not just be a product announcement channel.

We'll share technical engineering content covering topics such as:

VMware to KVM migration
Windows VM migration
KubeVirt
Kubernetes infrastructure
KVM and libvirt
eBPF
Cilium and Hubble
Offline VM inspection
Boot troubleshooting
Infrastructure automation
Network intelligence
AI infrastructure
Architecture deep dives
Lessons learned while building HyperSDK

If you're working on virtualization modernization, VMware migration, Kubernetes infrastructure, or open infrastructure, we'd love to hear about the problems you're running into.

What part of the post-VMware infrastructure stack do you think still needs the most work?

Explore Zyvor AI Labs:
https://zyvor.dev

HyperSDK: Open infrastructure for migration, virtualization, Kubernetes, networking, automation, and AI infrastructure.

DEV Community: Zyvor AI Labs