KIWI NG

KIWI NG is a command-line builder for creating bootable, reproducible Linux images. It reads an image description and package repositories, prepares a root tree, and turns that tree into one or more artifacts, such as disk images, ISO files, or containers. Outputs can target virtual machines, cloud platforms, removable media, and specialized deployments. Descriptions can specify metadata, repositories, packages, users, storage, target configuration, and image types; overlays, archives, and scripts allow further customization. Documented package managers include apk, apt, dnf4, dnf5, microdnf, pacman, and zypper. Tested and supported distributions listed by the project include Fedora, CentOS Stream, openSUSE, Ubuntu, Debian, and Arch Linux. KIWI NG is daemonless, supports multi-architecture builds, and uses a local cache backend. It is free under the GPL-3.0 license, with installation available through a distribution package manager, Open Build Service, or pip. The build host needs a recent Linux distribution, Python 3.9 or newer, Git, and at least 15 GB of recommended free disk space. QEMU can optionally boot and inspect results.

KIWI NG offers a description-driven way to build varied Linux image types, with customization and multiple distribution options. Plan for the Linux, Python, Git, and disk-space requirements, and consider matching the build host to the target distribution.

KIWI NG suits Linux users and teams who need to produce reproducible images for virtual machines, cloud platforms, removable media, or containers. It assumes familiarity with command-line workflows and Linux build environments.

KIWI NG is a daemonless, command-line builder for reproducible Linux images. It is best for administrators, appliance makers, and engineering teams that need one versioned recipe to produce several deployment formats.

Overview

KIWI NG turns an image description and package repositories into a prepared root tree, then converts that tree into one or more bootable artifacts. A description directory, using config.xml or a .kiwi file, can define metadata, repositories, packages, users, storage settings, and target-system configuration. Keeping those choices in a versioned description makes the build repeatable and reviewable rather than dependent on an interactive setup.

The same prepared tree can feed multiple image types, which is useful when a team wants a shared baseline for different environments. Build customization supports overlays, archives, scripts, and imported CA certificates. That flexibility covers appliance-specific changes, but it also means configuration discipline remains your responsibility.

Key features

• Broad output range: Generate images for virtual machines, cloud platforms, removable media, containers, and specialized deployment targets. Disk, ISO, and container artifacts are supported, with qcow2 given as a virtual-machine disk example. This is a strong fit for teams shipping one Linux base into several environments.
• Explicit, versioned recipes: Packages, repositories, users, metadata, and storage are declared in the image definition. The approach suits reproducible infrastructure and source-controlled release processes better than ad hoc image assembly.
• Distribution and package-manager coverage: Officially tested distributions include Fedora, CentOS Stream, openSUSE, Ubuntu, Debian, and Arch Linux. Documented package managers include apk, apt, dnf4, dnf5, microdnf, pacman, and zypper, giving mixed-distribution teams room to standardize their workflow.
• Daemonless and multi-architecture: KIWI NG builds without a resident daemon and supports multi-architecture builds. Its cache backend is local, so caching is straightforward but centered on the build host rather than a stated shared cache service.
• Optional image inspection: QEMU can boot and inspect generated images. It is an optional virtualization environment, useful for checking results before deployment without making virtualization a prerequisite for every build.
• Installation and distribution choices: Install through a distribution package manager, the Open Build Service, or Python's pip. Source code, GitHub releases, and RPM packages are also linked for teams that prefer different supply paths.

Pricing

KIWI NG is free: the KIWI NG plan costs nothing. There are no paid tiers, trial period, seat charges, or usage quotas stated, and the project is licensed under GPL-3.0. That makes it suitable for individual administrators and organizations that can operate their own Linux build infrastructure. The cost is operational rather than subscription-based: you provide the build host, storage, and maintenance.

Platforms

KIWI NG runs on Linux and is self-hosted. The project lists Fedora, CentOS Stream, openSUSE, Ubuntu, Debian, and Arch Linux among officially tested build hosts, with minimum versions defined in its documentation. A recent Linux distribution, Python 3.9 or newer, and Git are required, with at least 15 GB of recommended free disk space. The documentation recommends matching the build host's distribution, and keeping it near the target image's major version, because builds depend on distribution tools and behavior. That constraint matters when a team wants to build several distributions from one machine.

Who it's for

Choose KIWI NG for Linux administrators, appliance developers, and platform teams that need bootable, reproducible images across virtual machines, cloud, removable media, and containers. It is particularly appropriate when image definitions belong in version control and one root tree must yield several artifacts.

Look elsewhere if you need a graphical workflow, a managed build service, or a broad non-Linux build host matrix. KIWI's command-line model and distribution-sensitive requirements favor teams comfortable maintaining Linux tooling and build descriptions.

Pros and cons

Pros

• One recipe, many artifacts: A prepared root tree can become disk, ISO, or container outputs, reducing duplicated image definitions.
• Detailed customization: Overlays, archives, scripts, package repositories, storage settings, and CA certificates support appliance-level tailoring.
• Open-source operating model: GPL-3.0 licensing, self-hosting, and a free plan avoid recurring per-seat or usage fees.
• Multiple support channels: An open kiwi-images mailing list and Matrix room provide community contact.

Cons

• Linux-only hosting: Windows and macOS users need a separate Linux environment.
• Host matching is consequential: Distribution tools and behavior can make a mismatched build host unsuitable for a target image.
• Local caching only: The stated cache backend is local, which may limit sharing and reuse across builders.
• Resource and tooling overhead: Python, Git, a recent distribution, and roughly 15 GB of free space are practical prerequisites before the first build.

Alternatives

Container Build Tools is the broader category to browse when you are comparing image and container workflows.

• Buildah is a free Linux and self-hosted command-line option with no paid tiers or usage limits stated; choose it when container-focused tooling is the priority.
• BuildKit is free across Linux, macOS, Windows, and self-hosted setups; pick it when cross-platform availability matters more than KIWI's distribution-image scope.
• Dagger offers a free Individual plan for one user with 1,000,000 monthly events, one month of run history, and community support, plus a paid Team plan at $50; choose it for pipeline orchestration with a hosted-style usage model.
• ko is a free open-source Go container image builder; choose it for a focused container build workflow.
• Open Build Service is free GPL software with a reference server and self-installation option; pick it when package and distribution build infrastructure is the central need.
• Tilt is a free Apache-2.0 open-source tool for Linux, macOS, and Windows; choose it when your priority is a cross-platform development workflow.
• Amazon EC2 is a paid cloud service with a free tier for new customers offering up to $200 in credits for six months; pick it when you need rented compute rather than a local image builder.
• Pack is a free CLI and Go library with no paid plans listed; choose it for Cloud Native Buildpacks-based application images.

Verdict

KIWI NG is a strong choice for Linux teams that want source-controlled, reproducible images and multiple deployment artifacts from one description. Its free GPL-3.0 model and broad distribution and output support are the main reasons to choose it. Look elsewhere if Linux-only, distribution-matched hosts and a command-line build process do not fit your operating model.