Skip to main content
Talos Director is in Limited Availability. Limited Availability customers receive full production support and work directly with Sidero Labs engineering during onboarding. General availability is planned for January 2027, and the console is changing quickly until then, so details on these pages may differ from what you see.To request access, visit siderolabs.com/getdirector.
Talos Director runs on standard x86-64 servers with hardware virtualization, with no hardware specific to Talos Director. The table below lists the platforms it runs with, in three columns:
  • Validated platforms are in production use today.
  • Supported platforms work and are covered by support, but have not yet carried production workloads.
  • Roadmap items are planned and not yet available.

​
Hosts

Each host needs hardware virtualization (Intel VT-x or AMD-V) and an IOMMU enabled in firmware. Zero-touch onboarding needs a Redfish-capable BMC that can boot the server once over UEFI HTTP. Servers without one can be onboarded by booting the Talos Linux image from an ISO or USB. See How a server becomes a host. Hosts in the same compute cluster share storage. Live migration and High Availability both depend on every host in the cluster being able to open a VM’s disks. See Storage Pools.

​
Migrating from VMware

Converting a VM from vCenter needs guest credentials, a VM with no existing vCenter snapshots, and VirtIO drivers and the QEMU guest agent installed in the guest. Scheduled and automatic cutover, which keep the VM running during the copy, also require VMware’s Virtual Disk Development Kit (VDDK), uploaded from your VMware entitlement. Cold conversions do not. See What Happens During a Migration.

​
Availability

Talos Director is in Limited Availability. Limited Availability customers receive full production support and direct engineering engagement during onboarding. General availability is planned for January 2027.