Kata Containers

license

Apache-2.0(OSI)

source

public

governance

open community (OpenInfra Foundation)

core-gated

ungated

Fully Apache-2.0, source public, vendor-neutral open-foundation governance, no managed-tier gating from the project itself.

• 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://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.

• 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://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://katacontainers.io/ recorded 2026-08-13

  "The Kata Containers community is stewarded by the Open Infrastructure Foundation... The code is hosted at GitHub under the Apache 2 license." The site offers documentation, releases, mailing lists and a user survey, and sells no product, subscription or supported edition of its own.

Established CNCF/OpenInfra-adjacent container-runtime project integrated into Kubernetes runtimeclass deployments; broad but operator-concentrated infrastructure adoption rather than a mass per-user count. No clean download or user figure could be verified, and the ~8k GitHub stars only corroborate rather than carry the level. Level 3 reflects specialist infrastructure reach. The absence of a numeric reach is deliberate: katacontainers.io publishes no download, install, cluster or user count anywhere - what it publishes instead is a running user survey asking operators to self-report, plus one named production deployment (Baidu, for Function Computing, Cloud Container Instances and Edge Computing) - and the project ships as release tarballs and a kata-deploy Helm chart rather than through a countable package registry, so there is no channel to band on.

• 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-08-13

  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://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; the level does not rest on it.

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

  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.

VM-grade isolation with OCI and Kubernetes compatibility and pluggable hypervisors; very strong isolation but higher cold-start than the microVM and userspace frontier-definers, so 4. Five hypervisors are pluggable - QEMU, Cloud Hypervisor, Firecracker, Dragonball and StratoVirt - with QEMU the best-supported for NVIDIA GPUs and confidential computing, and the runtime ships as a containerd shimv2 shim with an in-VM agent across x86_64, aarch64, ppc64le and s390x. That places it one rung below Firecracker, which defines the 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/README.md recorded 2026-08-13

  Lightweight VMs "that feel and perform like containers, but provide the workload isolation and security advantages of VMs", on x86_64/amd64, aarch64, ppc64le and s390x. Core components are a containerd shimv2 runtime (Go and Rust), an in-VM agent, and the optional built-in Dragonball VMM.

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

  Five supported hypervisors - Cloud Hypervisor, Firecracker, QEMU, Dragonball and StratoVirt - selected per runtime through a configuration file. QEMU is the only one with GPU, Intel TDX and AMD SEV-SNP support, and is where the project focuses its GPU runtimes.