Talos Linux will no longer be exclusively an operating system designed around Kubernetes. Sidero Labs has announced Talos Hypervisor, a KVM-based virtualization layer built directly into Talos that will allow virtual machines to run without deploying KubeVirt or using Kubernetes to manage them. The project is also preparing direct execution of OCI containers outside Kubernetes, particularly for edge environments. The first alpha version is expected to be demonstrated in October, with general availability planned for December 2026.
The key points about the new Talos Hypervisor in 20 seconds
- Talos Linux will add a native KVM-based hypervisor for running virtual machines.
- Sidero Labs has chosen not to use KubeVirt or require Kubernetes to manage VMs.
- Talos will also be able to schedule OCI containers directly, particularly for edge deployments.
- The hypervisor will be open source under MPL-2.0.
- The announcement coincides with Yardi Systems’ acquisition of Sidero Labs.
The move is particularly interesting because it challenges one of the approaches that has gained ground in recent years: using Kubernetes as a common platform to manage both containers and virtual machines.
Sidero Labs has chosen another path. Instead of putting virtualization inside Kubernetes, it wants Talos Linux itself to manage both types of workloads.
The company argues that deploying Kubernetes solely to run virtual machines introduces unnecessary complexity for some infrastructure operators. That is Sidero Labs’ assessment, rather than an inherent limitation of KubeVirt, which remains a valid option for organizations that specifically want to manage VMs as Kubernetes resources.
Talos is trying to solve a different problem.
Talos wants to become a virtualization platform too
Talos Linux was created around a distinctive philosophy: reduce the operating system running Kubernetes to the bare essentials.
It does not have a traditional administration environment with SSH, an interactive shell or a package manager. Configuration is handled through an API protected with mutual TLS (mTLS), the operating system is immutable, and updates are atomic.
Until now, Kubernetes has effectively been the reason for that architecture to exist.
Talos Hypervisor changes that relationship.
Virtualization will be integrated directly into the operating system using KVM (Kernel-based Virtual Machine), the virtualization technology built into the Linux kernel. Virtual machines will be able to run and be managed on Talos without requiring a Kubernetes cluster.
| Traditional Talos | New Talos model |
|---|---|
| Kubernetes as the primary workload | Kubernetes, VMs and containers |
| Containers managed by Kubernetes | Containers can also run without Kubernetes |
| Talos as a Kubernetes OS | Talos also acts as a hypervisor |
| Talos API for node management | One API for managing the host |
| No SSH or interactive shell | Immutable model remains |
| Kubernetes required for workloads | Some workloads can run without Kubernetes |
Virtual machines will use standard technologies on top of KVM, while containers will continue to use images compatible with the Open Container Initiative (OCI). Sidero Labs emphasizes this point to argue that the new platform will not introduce a proprietary workload packaging format.
There is also an important distinction from what Talos can already do today.
Talos can already run inside a virtual machine hosted on platforms such as KVM, Proxmox, VMware, Hyper-V or Xen. The project’s documentation has long included instructions for these environments.
Talos Hypervisor reverses that relationship: Talos itself will now be able to host virtual machines.
The alternative to KubeVirt removes Kubernetes where it is not needed
KubeVirt makes it possible to bring virtual machines into Kubernetes and manage them through resources and tools from the Kubernetes ecosystem.
It makes sense when an organization wants a Kubernetes-centric operating model while retaining workloads that still need virtualization.
Sidero Labs believes that approach does not fit every scenario.
If a company only needs to run several VMs, deploying Kubernetes to achieve that means maintaining additional components and expertise that may add little value to that particular use case.
Talos Hypervisor is intended to remove that dependency.
A virtual machine will be able to run on Talos using KVM without Kubernetes being involved in its lifecycle. At the same time, another Talos node can continue operating as part of a conventional Kubernetes cluster.
Different workloads could potentially coexist on the same platform.
Conceptually, the proposal resembles the convergence pursued by other infrastructure platforms, although Sidero Labs starts from a different foundation: a minimal, immutable operating system managed entirely through APIs.
The company argues that this can reduce the number of systems that need to be patched, audited and administered when an organization operates both Kubernetes and a traditional virtualization platform.
That claim will need to be tested once the software is mature enough and real production deployments emerge. Reducing the number of components does not automatically make infrastructure simpler: distributed storage, virtual networking, migration, high availability, backups and VM lifecycle management remain complex problems regardless of the hypervisor being used.
Those areas will be an important technical test for Talos Hypervisor.
Containers will also be able to run without Kubernetes
The second development is almost as interesting as native virtual machines.
Talos will be able to schedule containers directly without Kubernetes.
At first glance, that may seem unusual for an operating system historically described as “a modern OS for Kubernetes.” But there are environments where deploying an entire cluster to run a handful of containers creates more infrastructure than necessary.
Edge computing is an obvious example.
An organization may operate hundreds or thousands of remote locations where it only needs to run one or a few services. An industrial node, retail location, telecommunications site or remote facility does not necessarily need a complete Kubernetes control plane.
Sidero Labs wants Talos to run those containers directly, with Talos Omni managing the fleet.
Omni is Sidero Labs’ management plane for centrally managing Talos machines and Kubernetes clusters. The company offers it both as a service and for self-hosted deployments, including isolated environments.
The broader direction is therefore more significant than simply adding a hypervisor.
Talos is attempting to evolve from a Kubernetes-specialized operating system into a common infrastructure layer for Kubernetes, virtual machines and standalone containers.
That also changes the market in which it competes.
Until now, its most obvious comparisons were Kubernetes-focused operating systems and distributions. With an integrated hypervisor, it starts moving closer to the territory occupied by virtualization and private-cloud platforms.
Sidero Labs plans to publicly demonstrate the alpha version during TalosCon in Amsterdam on October 15–16, 2026. General availability is planned for December.
Until then, many of the claimed benefits should be treated as design goals and vendor statements rather than capabilities proven at scale in production environments.
Sidero Labs has been acquired by Yardi
The technical shift comes alongside a corporate development that will probably be watched as closely as the hypervisor itself.
Yardi Systems has acquired Sidero Labs. The companies announced the deal on September 14, although financial terms have not been disclosed.
Yardi is a U.S. enterprise software company particularly associated with the real-estate industry and has more than 10,000 employees, according to its own figures. Until now, it has not been a particularly prominent name in the cloud-native community.
Sidero Labs says it will continue operating as a standalone company within Yardi and that the acquisition will provide additional resources for Talos development.
For the community, the particularly sensitive question is the future of open source.
The company says Talos Linux will remain available under MPL-2.0, and Talos Hypervisor will also be open source. Its current website also states that the community edition will not be restricted by the arrival of new enterprise offerings.
There is an important distinction: Talos Linux and the new hypervisor are presented as open source under MPL-2.0, while Talos Omni uses BSL 1.1, according to Sidero Labs’ current information.
The acquisition does not itself mean that licensing or governance will change. There is also no current evidence that Yardi intends to close Talos.
However, it is understandable that an open-source community will closely watch what happens after an acquisition.
The most meaningful evidence will not only be the commitments made on announcement day, but the decisions that follow: open development, community contributions, feature availability, licensing and the relationship between community and enterprise editions.
The roadmap should provide some answers relatively soon.
Talos Hypervisor is expected to arrive first as an alpha in October, with Sidero Labs targeting general availability in December. If the approach works as intended, Talos will no longer answer only the question of how to run Kubernetes on a minimal operating system.
Its proposition will be considerably broader: use the same operating system to decide when Kubernetes is actually needed and when a virtual machine or container can run perfectly well without it.