OpenInfra Foundation

license

Apache-2.0(OSI)

source

public

core features withheld

no

Kata Containers is Apache-2.0 with its full source public, and the runtime, agent and Dragonball VMM all sit in one repository. The project sells no managed tier that could gate any part of it.

• https://api.github.com/repos/kata-containers/kata-containers recorded 2026-08-13

  Repo metadata - language Rust, license spdx_id Apache-2.0, default branch main, not archived, pushed 2026-08-13, 8,531 stars, 1,431 forks.

• https://api.github.com/repos/kata-containers/kata-containers/git/trees/main recorded 2026-08-13

  Untruncated default-branch tree, 32 entries. One LICENSE. src/ carries the whole product - runtime, runtime-rs, agent and the Dragonball VMM - with tools/, tests/, ci/ and docs/ beside it, and there is no ee/, enterprise/, commercial/ or proprietary/ path.

• https://cdn.jsdelivr.net/gh/kata-containers/kata-containers@main/LICENSE recorded 2026-09-29

  The file is the verbatim Apache License 2.0, opening "Apache License" and "Version 2.0, January 2004" and ending with the standard "limitations under the License." clause, with no added exceptions or terms.

• https://cdn.jsdelivr.net/gh/kata-containers/kata-containers@main/README.md recorded 2026-09-29

  The README states "The code is licensed under the Apache 2.0 license." and lists runtime, agent and Dragonball VMM as core components in the repository, with no separate paid edition named. Searched for enterprise, license key, commercial, pricing, paid and cloud-only: none.

• https://github.com/kata-containers/kata-containers recorded 2026-06-04

  Apache-2.0 license; lightweight VMs with container UX + VM isolation; v3.31.0 (May 19 2026)

• https://katacontainers.io/ recorded 2026-09-29

  The project site says "The code is hosted at GitHub under the Apache 2 license." and "stewarded by the Open Infrastructure Foundation". Searched the body for enterprise, commercial, pricing, paid and license key: none, and it offers no product or edition for sale.

• https://raw.githubusercontent.com/kata-containers/kata-containers/main/LICENSE recorded 2026-08-13

  The verbatim Apache License 2.0, complete and with no appended notices, exceptions or additional terms.

Kata Containers is adopted as Kubernetes infrastructure through its runtimeclass integration, with Baidu naming it in production across several cloud services. The project publishes no download, install or user count and ships as release tarballs and a Helm chart rather than a countable registry, so GitHub stars serve only as corroboration.

• https://api.github.com/repos/kata-containers/kata-containers recorded 2026-08-13

  Repo metadata - 8,531 stars, 1,431 forks, 99 watchers, pushed 2026-08-13, not archived. Corroborates an active specialist infrastructure project; adoption is not based on it.

• https://github.com/kata-containers/kata-containers recorded 2026-06-04

  standard implementation of lightweight VM containers; integrated runtime; 8k stars

• https://katacontainers.io/ recorded 2026-10-08

  The project site publishes no usage, download or deployment figure. It names one production user in prose - "Baidu is running Kata Containers in production to support Function Computing, Cloud Container Instances, and Edge Computing" - and otherwise asks operators to "Take the Kata Containers User Survey", which is the project asking for the number rather than reporting one.

• https://raw.githubusercontent.com/kata-containers/kata-containers/main/README.md recorded 2026-10-08

  Distribution is by release tarball and the kata-deploy Helm chart on Kubernetes, or build from source - no package-registry channel that would yield a countable download figure.

Kata Containers gives every workload VM-grade isolation through a pluggable hypervisor layer - QEMU, Cloud Hypervisor, Firecracker, Dragonball or StratoVirt - integrated with Kubernetes via a containerd shimv2 shim across x86_64, aarch64, ppc64le and s390x. Its cold start runs higher than the microVM and userspace frontier, putting it a step below Firecracker, which defines that frontier here.

• https://github.com/kata-containers/kata-containers recorded 2026-06-04

  lightweight VMs performing like containers with VM workload-isolation/security; integrated with Firecracker

• https://raw.githubusercontent.com/kata-containers/kata-containers/main/docs/design/architecture/README.md recorded 2026-09-29

  The architecture doc says each container creation goes through a VM boot: "The hypervisor creates and starts (_boots_) a VM using the" guest assets, and "The [agent](#agent) is started as part of the VM boot." before the workload is spawned.

• https://raw.githubusercontent.com/kata-containers/kata-containers/main/docs/design/virtualization.md recorded 2026-09-29

  The virtualization design doc compares hypervisors on start time, rating "| Startup Latency | Good | Excellent | Excellent | Best |" for QEMU, Cloud Hypervisor, Firecracker and Dragonball, and recommends "| Fastest startup time | Dragonball, Firecracker |".

• https://raw.githubusercontent.com/kata-containers/kata-containers/main/docs/how-to/what-is-vm-templating-and-how-do-I-use-it.md recorded 2026-09-29

  The VM templating how-to exists to cut that boot cost, saying it can help if you "care a lot about container" startup speed and that it "speeds up Kata Containers creation by as much as" 38.68 percent.

• https://raw.githubusercontent.com/kata-containers/kata-containers/main/docs/hypervisors.md recorded 2026-09-29

  The hypervisors doc lists supported VMMs including "|[Firecracker](#firecracker) | rust | `aarch64`, `x86_64` |" and "|StratoVirt | rust | `aarch64`, `x86_64` |" alongside QEMU, Cloud Hypervisor and Dragonball.

• https://raw.githubusercontent.com/kata-containers/kata-containers/main/README.md recorded 2026-09-29

  The README lists a runtime "providing a containerd shimv2 runtime implementation" and supported architectures including "| `s390x` | [IBM](https://www.ibm.com) Z & LinuxONE SIE |" and ppc64le.