Ross ROSS = Recommend OSS · open-source software intelligence for agents

Kata Containers

Kata Containers is an open source project and community working to build a standard implementation of lightweight Virtual Machines (VMs) that feel and perform like containers, but provide the workload isolation and security advantages of VMs. https://katacontainers.io/ observed · 2026-08-28

github.com/kata-containers/kata-containers · Rust · Apache-2.0 (permissive) observed · 2026-08-28

Health v2 · maintenance only

99/100

  • Activity 99
  • Release rhythm 98
  • Longevity 100
How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.

  • gap_med: 28
  • age_days: 3191
  • days_rel: 12
  • days_push: 7
  • n_releases_24m: 28

Full methodology

Adoption not part of the score

8606 stars · 1448 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded

Kata Containers is an open source container runtime that builds lightweight virtual machines which plug seamlessly into the container ecosystem, offering container-like performance with VM-grade hardware isolation. It supports multiple hypervisors (QEMU, Cloud-Hypervisor, Firecracker) and integrates with Docker, containerd, CRI-O, and Kubernetes via OCI and CRI standards.

Use cases

  • run untrusted workloads in Kubernetes with stronger isolation
  • sandbox multi-tenant containers on a shared cluster
  • get VM-level kernel isolation without sacrificing container performance
  • secure CI/CD build jobs with hardware-enforced isolation
  • replace nested containers inside full VMs with lightweight VMs
  • isolate network, memory, and I/O per container workload

When to choose

  • you need stronger workload isolation than shared-kernel containers provide
  • you run multi-tenant Kubernetes clusters and want sandboxed pods
  • you want OCI/CRI compatibility so existing container tooling keeps working
  • you need hardware-enforced isolation using VT-x, ARM Hyp, or confidential computing extensions

When to avoid

  • your host lacks hardware virtualization support (no KVM)
  • you need maximum container density and startup speed with minimal overhead
  • you only run trusted first-party workloads where shared-kernel isolation suffices
  • you target non-Linux hosts, since Kata requires a Linux host with a hypervisor

Facets

application · maturity stable

container-runtime security container-orchestration security cloud-computing cloud self-hosted lightweight-vms oci-runtime qemu firecracker cloud-hypervisor hardware-virtualization workload-isolation cri sandboxed-containers virtualization containers devops linux docker kubernetes

2 sources

Member repositories

RepositoryRoleHealth v2
kata-containers/kata-containersmain99
kata-containers/runtimemirror10

For agents

markdown · JSON · MCP: product_card(name="kata-containers/kata-containers")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem