Make bare metal flow.
The six lines flow, above and below without constancy. — the I Ching
K8s made applications cloud-native; Kurrent makes compute cloud-native.
Kurrent is a cloud-native, stateless bare-metal delivery paradigm. It carries "stateless" down to the physical compute layer: a compute node (Device) holds no persistent state, and identity (Worker), system and data are granted by the network and the control plane. Its unit of scheduling is not the application but the system itself — a system belongs to an identity, not to a machine. A device starts as soon as it is connected to the network, and compute flows between bare-metal nodes like current. See the manifesto.
Storage is NVMe-oF-first: an in-kernel NVMe/TCP target exports system disks, with TLS 1.3 on a single port 4421 shared by the firmware and kernel boot stages. DHHC-1 credentials follow the Worker and are issued at disk creation on nvmet backends; the root path uses the full NQN from the disk record. iSCSI (stgt/lio) remains as a compatibility backend.
Deploy a control plane and join storage nodes in minutes — see Deployment on the documentation site. The kurrent CLI ships prebuilt binaries on Releases for Linux amd64/arm64 and Windows amd64.
The documentation site covers deployment, system disk customization, operations, troubleshooting, and reference material: CLI reference, API reference, architecture overview.
A device joins the pool on first boot; after binding a Worker, creating a system disk and setting the default disk in the Web UI, it boots. One Worker can carry multiple system disks and switch between them in the menu. System Disk Customization and First Delivery cover image preparation and the first boot. Cold boot is verified on Debian 12/13, Ubuntu 24.04/26.04, Fedora 44, AlmaLinux 10.2 and openSUSE Leap 16.0; see the distribution matrix for details, and the verification set does not limit which distributions can boot.
The boot-chain firmware is built by the companion repository Kurrent Firmware: Kurrent makes compute stateless, the firmware repository makes boot firmware stateless. Build and deployment steps are documented in Firmware Build and Deployment.
The direction is a cross-platform, cross-architecture cloud-native meta-protocol: one stateless semantics across bare metal and hypervisors. The vision lives in the Manifesto; concrete directions are in the ROADMAP (中文: about/zh/ROADMAP.md).
Issues, Discussions and pull requests are welcome. AI may write the syntax, but architecture must be understood by a human; read AI_POLICY.md before submitting.