Tinkerbell
Tinkerbell is an open-source bare metal provisioning and management platform (infrastructure automation) hosted by the Cloud Native Computing Foundation that orchestrates hardware workflows using container-based, cloud-native patterns.
- Workflow-driven bare metal provisioning and lifecycle management (infrastructure automation)
- Composable microservices for handling hardware metadata, workflow orchestration, and image deployment (infrastructure services)
- Cloud-native, container-based execution model for provisioning actions (containerized operations)
- Hardware management tailored for data center and edge environments (infrastructure management)
- Integration with cloud-native ecosystems for managing physical servers with software-defined workflows (cloud-native infrastructure)
More About Tinkerbell
Tinkerbell is an open-source bare metal provisioning and lifecycle management platform (infrastructure automation) designed to apply cloud-native, container-based patterns to physical server management. Originating in the context of large-scale hardware operations and now hosted by the Cloud Native Computing Foundation (CNCF), it targets the problem space of automating the full lifecycle of physical machines, from initial provisioning through reconfiguration and reprovisioning, using declarative workflows and microservices rather than manual or ad hoc tooling.
The Tinkerbell stack consists of modular components (infrastructure services) that work together to manage bare metal at scale. A workflow engine (orchestrator) executes provisioning steps as containers, allowing each action—such as disk partitioning, Operating System (OS) installation, firmware configuration, or network setup—to run as an isolated container image (containerized operations). A metadata service (configuration management) stores and exposes information about hardware inventory and per-machine configuration, while complementary services handle Dynamic Host Configuration Protocol (DHCP), PXE, and image handling where applicable (network boot and imaging). These components are designed to be composable so that operators can integrate Tinkerbell with existing data center and automation ecosystems.
Tinkerbell applies concepts from cloud-native architecture, such as microservices, APIs, and container orchestration (cloud-native infrastructure), to the bare metal domain. Workflows are defined declaratively, which enables repeatable, version-controlled provisioning pipelines and reuse of workflow definitions across environments. Because actions are implemented as containers, teams can build and maintain custom workflows using their existing container tooling and Continuous Integration and Continuous Deployment (CI/CD) systems, while still targeting physical hardware.
Enterprises typically use Tinkerbell in data centers and edge environments where they maintain physical server fleets and want to align hardware management with their cloud-native software operations (infrastructure operations). Common use cases include automated onboarding of new servers, redeploying machines between roles, enforcing standard images and configurations, and integrating hardware lifecycle events with higher-level platforms and schedulers. Tinkerbell’s design supports multi-tenant or multi-environment use through its API-driven, microservices-based approach.
From a taxonomy perspective, Tinkerbell fits into bare metal automation, infrastructure provisioning, and cloud-native infrastructure management. It interoperates with container ecosystems by executing provisioning logic as containers and exposing APIs that can be called from other automation platforms or orchestration layers (integration and extensibility). For enterprise technical stakeholders, Tinkerbell provides a programmable, workflow-oriented system for managing physical infrastructure with patterns aligned to modern cloud-native practices, offering a path to unify Infrastructure-as-Code (IaC) approaches across both virtual and physical compute.