Tinkerbell

Paid APILinuxSelf-hosted

What Tinkerbell is

Tinkerbell is an open-source engine for provisioning and managing bare metal infrastructure. Its core stack includes Tink, Smee, Tootles, and Hook, with optional power and boot services and a Cluster API provider. A workflow pairs hardware with a template and is managed as a Kubernetes custom resource. Templates sequence tasks such as streaming an image to disk, writing files, and partitioning disks, while actions can use any container image available to the worker. Smee supplies DHCP and TFTP and serves iPXE and the initial installation image. Tootles exposes hardware metadata over HTTP, including an AWS EC2-compatible format. Rufio manages baseboard controllers and can run one-off machine actions. Deployment options are Kubernetes, a standalone binary, and Docker Compose. Production documentation recommends Kubernetes 1.26 or later. The stack requires Layer 2 networking or a DHCP relay, and workers need iPXE support.

Who it suits

Tinkerbell suits infrastructure teams provisioning dedicated physical servers through declarative, API-centric workflows. It also fits Kubernetes users needing a bare-metal provider for Cluster API.

What it does well

Open-source bare metal provisioning engine
Workflow templates define sequential infrastructure tasks
Supports Kubernetes, binary, and Docker Compose deployment
Provides DHCP, TFTP, and iPXE boot services
Cluster API provider supports bare-metal clusters

What to know first

Production setup recommends Kubernetes 1.26 or later
Requires Layer 2 networking or DHCP relay
Target workers must support iPXE boot
Quick-start path requires public internet

Limits

The documented minimum stack allocation is 2 vCPUs, 4 GB RAM and 300 MB disk. Workers need about 2 GB RAM for HookOS and a workflow, with actual memory depending on action images; the Vagrant and Libvirt quick start does not support air-gapped or proxied environments.

Getting started

Choose Kubernetes, standalone binary or Docker Compose deployment
For production, prepare Kubernetes 1.26 or later
Provide Layer 2 networking for DHCP or configure a DHCP relay
Prepare workers with iPXE network-boot support
Allocate at least 2 vCPUs, 4 GB RAM and 300 MB disk for the stack
Define hardware and templates as workflow custom resources

Verdict

Tinkerbell provides modular services for network booting, hardware metadata, machine control, and workflow execution. Its deployment and networking prerequisites should be checked before adopting it for physical infrastructure.

Questions

Is Tinkerbell free?

Yes. It is offered as open-source software.

Which deployment options are available?

The installation guide documents Kubernetes, a standalone binary and Docker Compose.

What does production deployment require?

The documentation recommends Kubernetes 1.26 or later for production.

What networking does the stack need?

Smee's DHCP service requires Layer 2 networking, or a configured DHCP relay in the deployment environment.

Can it create Kubernetes clusters?

Yes. Its Cluster API provider lets Tinkerbell act as a bare-metal provider for cluster creation and management.

Where can users get support?

The project directs users to its documentation, GitHub organisation and the #tinkerbell channel in the CNCF Slack workspace.

Facts from Tinkerbell's own pages

BMC management: Rufio manages baseboard management controllers and can execute one-off actions to bring physical machines to a desired state. · tinkerbell.org, 5 Oct 2026
Cluster API integration: Tinkerbell provides a Cluster API infrastructure provider that lets it serve as a bare-metal provider for Cluster API. · tinkerbell.org, 10 Oct 2026
Community support: The project directs users to its documentation, GitHub organization, and the #tinkerbell channel in the CNCF Slack workspace for help and participation. · tinkerbell.org, 5 Oct 2026
Core stack: The core stack consists of Smee, Tootles, Hook, and Tink. · tinkerbell.org, 10 Oct 2026
Custom actions: Actions can use any container image available to the worker. · tinkerbell.org, 5 Oct 2026
Deployment options: The installation guide documents Kubernetes, a standalone binary, and Docker Compose; Kubernetes is recommended for production use. · tinkerbell.org, 10 Oct 2026
Kubernetes integration: The Cluster API provider lets Tinkerbell act as a bare metal provider for Kubernetes cluster creation and management. · tinkerbell.org, 5 Oct 2026
Metadata: Tootles exposes hardware metadata over HTTP and can provide it in an AWS EC2 compatible format. · tinkerbell.org, 5 Oct 2026
Minimum resources: The architecture page lists minimum stack resources of 2 vCPUs, 4 GB RAM, and 300 MB disk. · tinkerbell.org, 10 Oct 2026
Network boot: Smee provides DHCP and TFTP services and serves iPXE and the initial installation image. · tinkerbell.org, 5 Oct 2026
Network requirement: The stack requires Layer 2 networking for its DHCP server, or a DHCP relay configured to forward traffic to the stack. · tinkerbell.org, 10 Oct 2026
Optional hardware management: Optional PBnJ and Rufio services communicate with baseboard management controllers. · tinkerbell.org, 10 Oct 2026
Production setup: The documentation recommends Kubernetes for production and specifies Kubernetes 1.26 or later as a prerequisite. · tinkerbell.org, 5 Oct 2026
Provisioning model: It uses an API-centric, declarative configuration and automation approach inspired by the Kubernetes community. · tinkerbell.org, 10 Oct 2026
Purpose: Tinkerbell is a bare-metal provisioning engine maintained by the Tinkerbell Community. · tinkerbell.org, 10 Oct 2026
Resource requirements: The documented minimum stack resources are 2 vCPUs, 4 GB RAM, and 300 MB disk, and target worker machines must support iPXE network boot. · tinkerbell.org, 5 Oct 2026
Setup limitation: The quick-start guide says its Vagrant and Libvirt path requires public internet and does not support air-gapped or proxied environments. · tinkerbell.org, 10 Oct 2026
Stack components: The core stack includes Tink, Smee, Tootles, and Hook, with optional power and boot services and a Cluster API provider. · tinkerbell.org, 5 Oct 2026
Support: The community page directs users to documentation, GitHub for bugs and feature ideas, and the CNCF Slack #tinkerbell channel for discussion. · tinkerbell.org, 10 Oct 2026
Target hardware: A target worker must support iPXE network boot and needs about 2 GB RAM to load HookOS and run a workflow; actual memory needs depend on action container images. · tinkerbell.org, 10 Oct 2026
Templates: Templates contain sequential tasks and actions, including actions such as streaming an image to disk, writing files, and partitioning disks. · tinkerbell.org, 5 Oct 2026
Workflow execution environment: HookOS is a lightweight in-memory operating system used to run Tink Worker and execute workflows. · tinkerbell.org, 10 Oct 2026
Workflow management: Workflows combine hardware and a template, are defined as Kubernetes custom resources, and are managed by tink-controller. · tinkerbell.org, 10 Oct 2026
Workflow model: A workflow combines hardware and a template for execution and is managed as a Kubernetes custom resource. · tinkerbell.org, 5 Oct 2026

Where Tinkerbell stands on Freedom251

OS Deployment Software#26 of 29
Bare Metal as a Service (BMaaS) Software#11 of 12
Bare Metal Provisioning Software#26 of 28