containerd
containerd is an open-source, CNCF-governed container runtime that manages the full container lifecycle (image transfer, execution, storage, networking) for Linux and Windows hosts. It serves hyperscalers — Google GKE, AWS EKS/Fargate/Bottlerocket, and Azure AKS — plus Docker, Cloud Foundry, Balena, and VM-based runtime projects, all of which embed it as a default runtime under Kubernetes CRI.
- Company typePrivate
- Founded2015
- Headquarters—
- Headcount—
- GTM typeB2B
- OfferingSoftware
What containerd does
containerd is an open-source, industry-standard container runtime that manages the complete container lifecycle on a host system — image transfer and storage, container execution and supervision, low-level storage, and network attachments. It is built around a modular plugin architecture that supports multiple OCI-compliant snapshotters (overlayfs, native, btrfs, zfs, EROFS, devmapper, blockfile, fuse-overlayfs, nydus, overlaybd, stargz), a Runtime v2 shim API for third-party runtime authors, a Transfer Service for artifact movement between registries and stores, a Sandbox API for grouped-container lifecycles, Stream Processors for content-stream binaries, and built-in OpenTelemetry tracing since v1.6.0. Stable surface areas include a gRPC API (stable since v1.0) and a Go client SDK (stabilized at v2/client in v2.0). It is implemented as a daemon for Linux (amd64, arm64; Tier 2 ppc64le, riscv64, s390x) and Windows (amd64), and is the default runtime underneath Kubernetes CRI implementations across all three major hyperscalers — Google Kubernetes Engine, Amazon EKS / Fargate / Bottlerocket OS, and Azure Kubernetes Service — as well as Docker Engine, IBM Cloud Container Service, Cloud Foundry, Balena (edge), Kata Containers, Firecracker, and gVisor.
containerd has no commercial revenue model. It is licensed under Apache 2.0, distributed free of charge via GitHub releases, system package managers (apt-get, dnf, packaged as containerd.io by Docker), and embedded directly into managed Kubernetes services and operating systems. The project is owned and governed by the Cloud Native Computing Foundation (CNCF), a Linux Foundation non-profit, having been donated to CNCF by Docker in 2016 and graduating on February 28, 2019 as one of only a handful of CNCF graduated projects alongside Kubernetes, Prometheus, Envoy, and CoreDNS. Its primary "customers" are hyperscalers and platforms that embed it as a default runtime, while its served developers are the DevOps and platform engineering teams operating Kubernetes clusters at scale, plus infrastructure-tooling developers building higher-level orchestrators and specialized runtimes on top of the shim/snapshotter/Sandbox primitives. Release cadence is a 4-month cycle (April, August, December) aligned to Kubernetes, with LTS releases receiving at least two years of support — currently v2.3 (LTS through April 2028), v2.0 (LTS through March 2027), and v1.7 (LTS through September 2026).
containerd firmographics
Firmographics- Name
- containerd
- Legal name
- containerd Authors / Cloud Native Computing Foundation
- Website
- https://containerd.io
- Company type
- Private
- Founded year
- 2015
- Operating status
- Operating
- Short description
- containerd is an open-source, CNCF-governed container runtime that manages the full container lifecycle (image transfer, execution, storage, networking) for Linux and Windows hosts. It serves hyperscalers — Google GKE, AWS EKS/Fargate/Bottlerocket, and Azure AKS — plus Docker, Cloud Foundry, Balena, and VM-based runtime projects, all of which embed it as a default runtime under Kubernetes CRI.
- Ownership category
- akta.pro rank
containerd business model
Business model- GTM type
- B2B
- Offering type
- Software
- Cost components
- Personnel, Technology or R&D, Operations, Others
Revenue model
- Open Source Distribution: containerd is an open-source project distributed free of charge under the Apache 2.0 license. There is no commercial revenue model as the project is community-driven and maintained by contributors across multiple organizations with CNCF sponsorship.
Go-to-market motion1 record
Distribution channels4 records
Marketing channels4 records
containerd product offering
Product offeringCore offering
containerd is an industry-standard container runtime daemon available for Linux and Windows that manages the complete container lifecycle on its host system, including image transfer and storage, container execution and supervision, low-level storage, and network attachments. It supports the OCI Image and Runtime specifications, provides multi-tenant CAS storage for global images, and exposes a stable gRPC API and Go client for integration with Kubernetes and other orchestrators.
Product overview
containerd is a single unified container runtime product — an open-source daemon that manages the complete lifecycle of containers on a host system. The project provides the core containerd runtime along with supporting tools including the ctr CLI (for debugging), nerdctl CLI (for general-purpose use), and client SDK (Go). It is offered as a graduated CNCF project with long-term stable releases and supports integration with Kubernetes CRI, OCI-compliant runtimes (runc, Kata Containers, gVisor), and CNI networking plugins. No separate add-on modules, platform tiers, or sub-brands are offered — the product is containerd itself, distributed as versioned releases (LTS and regular) with tiered platform support across Linux, Windows, and various CPU architectures.
Differentiator
Problem solved
Functional benefit
Products and services
- containerd An industry-standard container runtime daemon for Linux and Windows that manages the complete container lifecycle including image transfer and storage, container execution and supervision, low-level storage, and network attachments. Supports OCI Image and Runtime specs, multi-tenant CAS storage, and integrates with Kubernetes CRI.
- nerdctl A containerd-compatible CLI tool that provides a stable, Docker-like user experience for interacting with containerd, intended for general-purpose container management rather than debugging (which ctr addresses).
Quantifiable outcome
- Graduated CNCF project status achieved February 28, 2019, recognized alongside Kubernetes, Prometheus, and Envoy
- +2 more outcomes
Companies that use containerd
Customer profileNamed customers10 records
Segments3 records
Ideal customer profiles3 records
containerd technology and API
TechnologyTechnology focussed Yes
API detail
- Has API
- Yes
- API docs
- API detail
Core technology
AI maturity
App detail
Integration4 records
Feature8 records
containerd partnerships and signals
Strategic signalPartnerships
Seven partnerships are on record, tiered core.
- Cloud Native Computing Foundation (CNCF)corecontainerd is a CNCF graduated project, managed and maintained under the CNCF governance framework. CNCF provides funding, infrastructure, and organizational support for the project's development and community growth.
- Google Cloud (GKE)coreGoogle Kubernetes Engine uses containerd as the default container runtime, with documentation and support for containerd on GKE.
- Amazon Web Services (Fargate, EKS, Bottlerocket)coreAWS uses containerd as the container runtime for Fargate, EKS, and the Bottlerocket OS, with extensive integration and support documentation.
- Microsoft Azure (AKS)coreAzure Kubernetes Service uses containerd as the default container runtime with official Microsoft documentation.
- DockercoreDocker Engine integrates containerd as its container runtime component, distributing containerd through official Docker package repositories.
- Open Container Initiative (OCI)corecontainerd implements OCI Image Spec and OCI Runtime Spec (runc), contributing to and supporting open container standards.
- Kubernetes SIG-Nodecorecontainerd maintains active collaboration with Kubernetes SIG-Node for CRI (Container Runtime Interface) development and integration testing.
Scale indicators3 records
Recent moves6 records
Expansion highlights5 records
containerd competitors and assessment
Company assessmentBroad incumbents
- Red Hat OpenShift: Enterprise Kubernetes distribution that historically defaulted to CRI-O but increasingly supports containerd. OpenShift is a competing platform whose runtime choice influences containerd's enterprise penetration.
- Kubernetes: The container orchestration platform that consumes containerd via the CRI. Kubernetes is both the dominant upstream consumer of containerd and the system whose evolution determines containerd's roadmap.
Emerging players
- Kata Containers: VM-based container runtime that integrates with containerd via the Runtime v2 shim. Aims to provide hardware-isolated containers and competes at the isolation layer while relying on containerd for orchestration.
- gVisor: Google's application kernel for containers that runs as an OCI-compatible runtime under containerd. Competes at the sandboxing/isolation layer for security-sensitive workloads.
- Firecracker: AWS's microVM technology that integrates with containerd through the Runtime v2 shim for lightweight VM-based container isolation. Powers AWS Fargate and Lambda.
Others
- BuildKit: Docker's next-generation build tool that produces OCI images consumed by containerd. Complementary in the container lifecycle (BuildKit builds, containerd runs), sharing Moby/Docker governance heritage.
Direct peers
- Podman: Red Hat's daemonless container runtime that provides a Docker-compatible CLI. While Podman focuses on rootless and developer use cases rather than being a Kubernetes CRI runtime, it competes with containerd for container lifecycle management in non-cluster contexts.
- CRI-O: CNI/CRI-O is the primary alternative container runtime specifically built for Kubernetes. Used by OpenShift and other Kubernetes distributions, it competes directly with containerd in the Kubernetes CRI runtime layer.
- runc: The OCI runtime reference implementation that containerd uses as its default low-level runtime. Highly complementary — containerd orchestrates and runc executes — but they occupy the same container runtime stack with overlapping governance under OCI.
- Docker / Moby: Docker originally created containerd in 2015 and donated it to CNCF. Docker Engine still embeds containerd as its runtime component, making them both collaborators and adjacent product offerings — Docker provides the developer-facing UX while containerd is the underlying runtime.
Market position
Strengths5 records
Weaknesses5 records
Competitive moat5 records
Key highlights7 records
Customer concentration
containerd social profiles
Digital presencecontainerd compliance and trust
Trust signalCompliance2 records
containerd financial estimates
Financial estimateRevenue estimate
Valuation estimate
containerd leadership team
Management profileNumber of profiles
containerd funding detail
Funding detailFunding overview
Funding rounds
Investors
Funding detail is available on the Subscription and Enterprise plan.Contact sales →
containerd M&A and investment
M&A and investmentM&A
Investments
M&A and investment is available on the Subscription and Enterprise plan.Contact sales →
Frequently asked questions about containerd
What does containerd do?
containerd is an industry-standard container runtime daemon available for Linux and Windows that manages the complete container lifecycle on its host system, including image transfer and storage, container execution and supervision, low-level storage, and network attachments. It supports the OCI Image and Runtime specifications, provides multi-tenant CAS storage for global images, and exposes a stable gRPC API and Go client for integration with Kubernetes and other orchestrators.
Is containerd a public or private company?
containerd is a private company. It is classified as nonprofit foundation owned and is currently operating.
When was containerd founded?
containerd was founded in 2015.
How does containerd make money?
One revenue line is on record: open Source Distribution.
Who are containerd's main competitors?
Broad incumbents on record are Red Hat OpenShift and Kubernetes. Emerging players are Kata Containers, gVisor and Firecracker. BuildKit is listed as an others. Direct peers are Podman, CRI-O, runc and Docker / Moby.
Does containerd have an API?
Yes. containerd provides a gRPC API (stable from v1.0) and a Go client API (stable from v2.0). The gRPC API is the primary product offering and maintains backward compatibility without major version jumps. The Go client package (github.com/containerd/containerd/v2/client) enables developers to integrate containerd into their projects, supporting operations such as connecting to the daemon, pulling images, creating containers, creating tasks, and managing container lifecycle. The API minor version increments independently from the main containerd version. The gRPC API is documented for Linux and Windows platforms. Developer documentation is at github.com/containerd/containerd.