Kubernetes · Talos Linux
Talos Linux is the immutable, API-driven functioning scheme purpose-built for Kubernetes. No SSH, no shell, no bundle manager. Just the binaries needed to run your fleet, from naked metal element to the edge.
Free & Enterprise
One codebase. Two ways to run it.
Talos Linux is liberated and open origin under MPL-2.0. Talos Enterprise Linux is the identical OS. What the endeavor tier adds is proof, indemnity, and person to call: the assurance, compliance evidence, and assistance that safety and procurement teams need to sign off.
Open origin · MPL-2.0
Talos Linux
Free, forever
- Immutable, API-driven OS for Kubernetes
- No SSH, no shell, no bundle manager
- Minimal assault surface, minimal CVEs
- CIS-hardened, mTLS, SELinux, trusted boot
- Community assistance · 10,200+ GitHub stars
Enterprise licence · MPL-2.0New
Talos Enterprise Linux
$1,000 per node per twelvemonth · 10-node minimum
- Fleet administration alongside Omni, included
- 24/7/365 assistance alongside CVE SLAs
- FIPS 140-3 compliant builds
- Schematic-specific SBOMs & curated VEX, for your exact build
- Signed build attestation
- Commercial IP indemnity
- Built for NIS2 & CRA compliance
Trusted by endeavor phase teams
In manufacturing throughout regulated, sovereign, and mission-critical environments.
Why Talos Linux
Infrastructure that can’t drift, and can’t be logged into.
Most fleets are held together by hand, and the gaps are anywhere they break. Talos removes the gaps by design, the identical throughout all collection and all site.
Minimal
Minimal by design
Fewer than 50 binaries, fair adequate to run Kubernetes. Minimal assault surface, minimal CVEs.
API-only
No SSH, no shell
Every node communication goes through a secured gRPC API alongside mutual TLS. Nothing to log into.
Immutable
Read-only & ephemeral
Nothing is written to disk at runtime, nothing persists between reboots. A reboot returns the node to its declared state.
Declarative
One YAML, entire machine
The complete device province is defined declaratively. No configuration-management tools to maintain.
Atomic
Unified lifecycle
OS and Kubernetes upgrade together as one atomic, rollback-safe image. The identical toggle from day zero on.
Hardened
Secure by default
mTLS on all API access, CIS guidelines applied out of the box, SELinux and trusted footwear included.
Talos Enterprise Linux
Clear the safety review. Keep the open-source OS.
Everything Talos Linux does, affirmative Omni fleet management, the audit evidence, indemnity, and reply times that get an open-source OS through endeavor procurement. Built for NIS2 and CRA.
Compliance
FIPS & regulatory fit
FIPS 140-3 compliant builds and a posture built for the frameworks auditors ask about.
- FIPS 140-3 compliant builds
- NIS2 & CRA-aligned posture
- CIS benchmark alignment
Supply chain
Artifacts safety teams demand
Evidence tied to the exact depiction you run, traceable rear to source.
- Schematic-specific SBOM per release
- Curated VEX, not auto-generated noise
- Signed build attestation
- OCI-compatible distribution
Support
24/7/365, alongside targets
The group who wrote the code, not a tier-1 helpdesk.
- CVE SLAs alongside reply targets by severity
- Direct admission to Sidero engineering
- Dedicated Slack channel
- Upgrade & immigration assistance
Legal
Commercial IP indemnity
The contractual safety procurement expects from a business vendor.
- IP indemnification for Talos Linux
- Formal assistance agreement, SLA-backed
- Audit-ready documentation
- Security-questionnaire support
Adopted in the open
- ~1Mdownloads / year
- 109k+registered clusters
- 10,200+GitHub stars
- 330+contributors
In the community’s words
“I'm consistently being blown distant by the amount of engineering that has gone into Talos Linux for operating k8s effortlessly and securely.
It's insane to think that there was a period all of this had to be manually wired up. As much as I don't akin drinking an idiosyncratic company's koolaid, so far this one's lit.”
“Talos is so nice and uncomplicated to oversee whenever compared to having to oversee the two k3s and the presenter OS.
To create it equal better, deploy a self-hosted case of Omni to oversee the Talos nodes. Gives you a nice interface to grip rolling out config patches, rolling Talos and k8s updates, scaling up and down, and integrating alongside infrastructure providers to automatically provision machines.”
Fleet management
When prepared to oversee a fleet, Omni builds on talosctl
When the fleet outgrows manual lifecycle management, Omni takes complete provisioning, upgrades, config, and backups throughout all collection from one place. It additionally schedules containers immediately on Talos at single-node border sites, alongside no Kubernetes collection required, managed through the identical fleet plane.
Talos Omni · origin accessible · BSL 1.1 · SaaS or self-hosted
Cluster statusRunning
Control planes3 / 3 ready
Talos version1.14.0
Kubernetes1.37.0
Edge containers, no clusternew
DeploymentSaaS · self-hosted
Built in the open
Open origin since day one. In manufacturing since 2020.
Talos Linux is and stays open origin under MPL-2.0. The endeavor tier adds assurance and assistance on top. It doesn’t near the code or move capabilities rearward a wall.
- Talos LinuxMPL-2.0forever
- Talos Omnisource availableBSL 1.1
- CNCFSilver member