BuildKit
github.com
- Free plan
- Windows
- macOS
- Linux
- API
- Self-hosted
What BuildKit is
BuildKit is a free toolkit for turning source code into build artifacts in a repeatable way. It consists of the buildkitd daemon and buildctl client, and uses LLB, a binary format for expressing process dependency graphs. Build definitions can come from Dockerfiles or other frontends that convert them to LLB. BuildKit supports concurrent dependency resolution, instruction caching, cache import and export, nested jobs, multiple output formats, and automatic garbage collection. It can run builds without root privileges and supports OCI (runc) and containerd worker backends. Results can be exported as images, local directories, tarballs, Docker tarballs, or OCI tarballs. The daemon exposes a gRPC API through a Unix socket by default, with TCP sockets also available. Binaries are listed for Linux, macOS, and Windows. The unofficial macOS Homebrew formula does not include buildkitd; the project gives Lima in a Linux virtual machine as one way to run it. BuildKit is licensed under Apache-2.0.
Who it suits
BuildKit suits developers and build-platform teams that need configurable, cache-aware artifact builds. Its frontends, worker backends, and output options are relevant to projects integrating build execution into their workflows.
Good to know, and what to watch
- Supports concurrent dependency resolution and instruction caching.
- Imports and exports build caches.
- Can execute builds without root privileges.
- Exports images, directories, and several tarball formats.
- Binaries are listed for Linux, macOS, and Windows.
- Unofficial Homebrew formula omits the buildkitd daemon.
- GitHub Actions, S3, and Azure Blob cache options are marked experimental.
Plans
Every plan and priceBuildKit (Apache License 2.0)
Free plan
Getting started
- Open the BuildKit repository on GitHub
- Download the binary for Linux, macOS, or Windows
- Start the buildkitd daemon
- Use buildctl to define and run builds
- Connect through the default gRPC socket or a TCP socket
- On macOS, use a Linux VM such as Lima when the Homebrew formula is insufficient
Limits to check
The free Apache-2.0 plan is perpetual and has no charge. On macOS, the unofficial Homebrew formula does not include buildkitd, so running the daemon requires another route such as Lima in a Linux virtual machine.
The Club's review
BuildKit is an open-source engine for producing repeatable build artifacts, suited to developers and platform teams who want control over container build pipelines. Its broad frontend, worker, and output support is compelling, but the separate daemon and macOS setup make it less turnkey than a hosted service.
Overview
BuildKit separates the buildkitd daemon from the buildctl client. Builds are represented in LLB, a vendor-neutral format for process dependency graphs that supports concurrent execution and cache reuse. Docker Engine 23.0 and later use Buildx and BuildKit by default for docker build, so many Docker users encounter it as part of their existing workflow rather than as a separate tool. The project is licensed under Apache-2.0 and identifies users including Moby, Docker, Tekton Pipelines, Gitpod, Dagger, and Depot.
Key features
Extensible, cache-aware builds
Frontends translate build definitions into LLB; Dockerfiles and other LLB languages are supported. Concurrent dependency resolution, instruction caching, and cache import and export help reduce repeated work. Cache exporters include inline, registry, local directory, and GitHub Actions. The GitHub Actions, S3, and Azure Blob cache options are experimental, so workflows that depend on them carry more uncertainty than those using the established exporters.
Build results can be exported as images, local directories, tarballs, Docker tarballs, or OCI tarballs. That range is useful when a pipeline needs more than a container image, while automatic garbage collection helps manage accumulated build data. Nested build jobs, pluggable architecture, and distributable workers give teams further room to shape their build pipelines.
Workers, permissions, and isolation
The daemon supports OCI (runc) and containerd workers, and BuildKit can execute without root privileges. Its default security model limits API access to the BuildKit state directory and prevents application and frontend containers from accessing the host system, privileged system calls, or external devices directly. Those controls make it suitable for builds involving untrusted sources, though they do not remove the operational responsibility of running and configuring the daemon.
API and integrations
The daemon exposes a gRPC API, using /run/buildkit/buildkitd.sock by default, and can also listen on TCP sockets. The project lists integrations and users across Docker, Moby, Tekton Pipelines, Docker buildx, Gitpod, Dagger, and other projects. This makes BuildKit a natural fit for teams extending existing container or CI infrastructure rather than seeking a self-contained hosted build service.
Pricing
BuildKit is free under the Apache-2.0 license: the BuildKit plan costs nothing, with perpetual, worldwide, non-exclusive, no-charge, royalty-free terms. There are no paid tiers or plan quotas to weigh. The trade-off is operational rather than financial: teams run the daemon and client within their own build environment.
Platforms
BuildKit supports Linux, Windows, and macOS, with binaries for all three, as well as API and self-hosted use. The macOS caveat matters: the unofficial Homebrew formula does not include the buildkitd daemon. The project gives running it in a Linux VM through Lima as an example, which adds setup compared with using Docker Engine 23.0 or later, where BuildKit is enabled by default for docker build. Windows containers and rootless mode are supported.
Who it's for
BuildKit suits developers and platform teams that need configurable, cache-conscious builds, multiple output formats, or integration with existing container and CI tooling. Its free, permissively licensed distribution is attractive for self-hosted pipelines, and the ability to run without root privileges is useful where build permissions need to be constrained. It is a weaker fit for readers who want a managed build service or a straightforward macOS installation without a separate daemon setup.
Pros and cons
- Broad build flexibility: Dockerfiles and other LLB frontends, multiple worker backends, and several output formats support varied pipeline designs.
- Reusable work: Concurrent dependency resolution, instruction caching, and cache import and export can avoid rebuilding unchanged work.
- Useful isolation controls: Rootless execution and default host-access restrictions help limit what builds can reach.
- Self-managed operation: The daemon-and-client architecture puts setup and operation on the team rather than offering a hosted workflow.
- Mac setup hurdle: The unofficial Homebrew formula omits the daemon, so macOS users need another way to run it, such as a Linux VM.
- Experimental cache choices: GitHub Actions, S3, and Azure Blob cache options are marked experimental, a concern for pipelines that rely on them.
Alternatives
- Dagger is worth considering for teams that want a freemium option with a free Individual plan for one user and 1,000,000 monthly events, plus a one-month run history and community support.
- Garden may suit readers seeking a freemium option with a free tier, while its Enterprise plan includes secrets management, RBAC, and self-hosting.
- Jib is a free alternative focused on open-source container building tools for Java.
- ko is a free open-source container image builder for Go.
- Tilt is a free, Apache-2.0-licensed option.
- Cloud Native Buildpacks Pack offers a free CLI and Go library, with no paid plans.
- Depot is a paid alternative with a Developer plan at $20 a month, billed monthly, including one user and build-minute allowances.
- Kaniko is a free option for building container images from Dockerfiles, distributed as container images.
Browse more options in Container Build Tools and Container Engines.
Verdict
Choose BuildKit if you need a free, flexible engine for self-managed container builds, especially when cache reuse, multiple frontends, or constrained execution matter. Its strongest reason to choose it is the control its extensible architecture gives a build pipeline. Look elsewhere if you want managed builds or a simpler macOS installation: the daemon remains yours to run, and Homebrew does not supply it.
The verdict
BuildKit provides a configurable build engine with multiple frontends, worker backends, and output formats. macOS users should note that the unofficial Homebrew formula does not include the daemon.
Questions people ask
What does BuildKit cost?
BuildKit is free under the Apache-2.0 plan: free, perpetual, worldwide, non-exclusive, no-charge, and royalty-free.
Which systems can run BuildKit?
BuildKit supports Linux, Windows, and macOS, with API and self-hosted deployment options. Binaries are available for all three systems.
Can BuildKit build images without root privileges?
Yes. Rootless execution is supported, and image building is available.
What outputs can a build produce?
Build results can be exported as images, local directories, tarballs, Docker tarballs, or OCI tarballs.
How does BuildKit expose its API?
The daemon uses a gRPC API and listens at /run/buildkit/buildkitd.sock by default. TCP sockets can also be used.
What the maker publishes
- Adopters
- The project lists Moby and Docker, img, OpenFaaS Cloud, Tekton Pipelines, Docker buildx, Gitpod, Dagger, Depot, and other projects as users. source
- API
- The daemon listens on a gRPC API at /run/buildkit/buildkitd.sock by default and can also use TCP sockets. source
- Architecture
- BuildKit is composed of the buildkitd daemon and the buildctl client. source
- Binaries
- The latest BuildKit binaries are available for Linux, macOS, and Windows. source
- Build features
- Features include concurrent dependency resolution, instruction caching, cache import and export, multiple output formats, and automatic garbage collection. source
- Cache backends
- Cache exporters include inline, registry, local directory, and GitHub Actions cache; the README marks GitHub Actions, S3, and Azure Blob cache options experimental in its contents list. source
- Core features
- Key features include automatic garbage collection, extendable frontend formats, concurrent dependency resolution, instruction caching, cache import/export, nested build jobs, distributable workers, multiple output formats, pluggable architecture, and execution without root privileges. source
- Docker availability
- The README says Docker Engine 23.0 and later use Buildx and BuildKit by default for docker build. source
- Execution
- BuildKit supports execution without root privileges. source
- Extensible builds
- BuildKit uses frontends to convert build definitions into LLB, and supports Dockerfiles and other LLB languages. source
- Host isolation
- With the default daemon configuration, the BuildKit API does not allow access to the host filesystem outside the BuildKit state directory, and application and frontend containers cannot access the host system, run privileged system calls, or access external devices directly. source
- Integrations
- The repository lists Moby and Docker, Tekton Pipelines, Docker buildx, Gitpod, Dagger, and other projects as BuildKit users. source
- Integrations
- BuildKit documentation lists integrations or usage with Podman, nerdctl, Kubernetes, Docker buildx, GitHub Actions cache, S3 cache, Azure Blob Storage cache, and OpenTelemetry. source
- Latest release
- The repository’s releases page lists v0.33.1 as the latest release dated September 30, 2026. source
- License
- The repository identifies its license as Apache-2.0. source
- License
- BuildKit is distributed under the Apache License, Version 2.0, which grants perpetual, worldwide, non-exclusive, no-charge, royalty-free copyright rights subject to the license terms. source
- LLB
- BuildKit builds use a binary intermediate format called LLB for defining process dependency graphs, and LLB is concurrently executable, efficiently cacheable, and vendor-neutral. source
- macOS limitation
- The README says the unofficial Homebrew formula for macOS does not include the buildkitd daemon and gives Lima in a Linux VM as an example way to run it. source
- Outputs
- Build results can be exported as images, local directories, tarballs, Docker tarballs, or OCI tarballs. source
- Platforms
- The buildctl client is available for Linux, macOS, and Windows, while buildkitd is available for Linux and Windows. source
- Platforms
- The buildctl client is available for Linux, macOS, and Windows, while the buildkitd daemon is available for Linux and Windows. source
- Purpose
- BuildKit converts source code into build artifacts efficiently and repeatably. source
- Purpose
- BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner. source
- Security model
- BuildKit describes itself as secure by default and usable with untrusted sources. source
Checked against the maker's pages on 30 Sept 2026.