IVMIA orchestrates workloads across every virtualization, container, and bare-metal platform your team runs. Each plugin translates IVMIA's normalized workload model into the platform's native API — so a VM moves from VMware to Proxmox, a container lifts from Docker to Kubernetes, or a Windows 11 desktop gets rebuilt on an Incus host, all through the same orchestration surface.
The virtualization platforms IVMIA treats as peer targets — any workload can start on one and migrate to another.
libvirt-API. Full VM lifecycle, storage-pool orchestration, snapshots, live-migration between libvirt hosts, and the reference target for cross-platform conversions.
Proxmox REST-API. VM and LXC lifecycle, HA-group awareness, storage-backend modeling (ZFS / Ceph / LVM / NFS), backup integration that dovetails with VaultSync.
vSphere REST-API + SDK. Host / cluster / DRS awareness, vMotion orchestration, VMDK snapshot & clone. Coexists with vCenter — IVMIA does not require replacing it.
WMI + PowerShell remoting. VM lifecycle, live-migration, VHDX snapshot, checkpoint management, and Cluster Shared Volume awareness for failover-cluster deployments.
VBoxManage + SDK. Covers the labs, developer workstations, and training environments where VirtualBox persists — so those workloads are visible to the same orchestrator as the datacenter fleet.
Incus REST-API. System-container and VM orchestration, cluster awareness, storage-pool modeling. The go-to target when a team wants container density with VM isolation.
Container workloads treated as first-class citizens, not an afterthought.
Docker Engine API + Compose-file parsing. Container lifecycle, volume orchestration, network modeling, and the bridge between a Compose project and an IVMIA-managed workload.
Podman REST-API + systemd-unit integration. Quadlet awareness, pod orchestration, and rootless-namespace modeling.
Kubernetes API-server integration. Treats namespaces / Deployments / StatefulSets as IVMIA workloads, mediates cross-cluster migration, and coordinates persistent-volume movement with VaultSync.
Physical servers and workstations managed through the same orchestrator as the virtualized fleet — so “rebuild this machine” and “migrate this VM” are the same workflow.
Covers RHEL / Rocky / Alma / Ubuntu / Debian / SUSE / Arch. Inventory, config drift, workload definition, and P2V / V2P conversion paths.
WMI + WinRM. Windows 11 desktops and Windows Server fleets treated as IVMIA workloads — including P2V capture and restore on any supported hypervisor target.
SSH + MDM-aware plugin. Workstation inventory, config posture, and integration with the VaultSync mobile / workstation source plugin for backup and restore.
Treats EC2 instances and EKS workloads as IVMIA targets so the same lift-and-shift surface covers on-prem and AWS.
Azure Resource Manager integration for VM and AKS workloads, paired with VaultSync's Azure Blob target.
GCE VM + GKE cluster plugin for teams with cross-cloud orchestration requirements.
OCI compute + OKE integration, paired with VaultSync's native OCI Object Storage target.
Every platform plugin implements IVMIA's workload-model interface: inventory, lifecycle, snapshot, migrate, telemetry. That is what lets a workload defined once be started on any supported platform and moved between them — and it is what connects IVMIA to VaultSync (backup), NIVMIA (network state), and OpenUTM (policy) without a separate integration layer.
IVMIA plugins are what make “we're moving off VMware” or “we're consolidating on Proxmox” a scheduled migration instead of a multi-quarter project.
Back to All Products Talk to Us