Civo Bare Metal
Civo Bare Metal is alpha functionality introduced in the Konstruct 0.7 line. Interfaces and workflows may change between releases. Bare-metal clusters managed by Konstruct are priced per the pricing page — while in alpha, this capability is available without any upcharge.
Civo Bare Metal brings your own data center into Konstruct. Racked servers become discoverable hardware, hardware becomes Kubernetes clusters, and those clusters become first-class Konstruct clusters — with the same GitOps catalog, application delivery, environments, and templates you use everywhere else.
Powered by Colony
Under the hood, Civo Bare Metal is powered by Colony, the Civo bare-metal Kubernetes provisioning platform. Colony is a product in its own right — a self-hosted, declarative, CRD-native operator that takes servers from PXE boot through OS installation to running Kubernetes, with no hosted service dependency and full air-gap support.
Konstruct surfaces Colony's capability as an optional feature set. You can run Colony standalone with kubectl and GitOps tooling (Colony documentation), or let Konstruct drive it from the UI and manage the resulting clusters alongside your cloud fleet.
What you get
The Civo Bare Metal section of the Konstruct navigation adds four areas:
| Area | What it does |
|---|---|
| Dashboard | At-a-glance view of your bare-metal estate across sites |
| Hardware | Discovered physical servers (assets), their lifecycle state, and readiness for provisioning |
| Private clusters | Kubernetes clusters running on your bare metal, managed by Konstruct |
| Sites | The physical locations where your infrastructure runs, connected with a pairing code |
How the pieces fit
- Connect a site — a site is a physical location (a data center, a hall, an edge location). Connecting one pairs the Colony control plane at that location with your Konstruct control plane.
- Discover hardware — servers at the site are discovered via their BMC (Redfish/IPMI) and network-boot (PXE), becoming assets ready for provisioning.
- Create clusters — provision Talos Linux, K3s, or CivoStack clusters onto discovered hardware, then manage them in Konstruct like any other cluster: GitOps catalog, apps, environments, RBAC.
When to use it
- Public cloud exodus — moving workloads from hyperscalers onto your own hardware without giving up self-service platform ergonomics
- Data sovereignty — keep infrastructure, data, and the control plane entirely on premises; air-gapped operation is supported
- Edge and multi-site — each physical location is a site; one Konstruct control plane manages many
- Full cloud experience — CivoStack clusters bring the Civo cloud platform stack (Cilium, distributed storage with Mayastor and Ceph, ingress, monitoring) to your metal