# Supported hardware

> What Rasputin runs on, what has actually been booted, and what is only expected to work.

<!-- Canonical: https://rasputin.geekdojo.com/docs/hardware/ — raw-markdown mirror for agents and LLMs. -->

Rasputin runs on **a Raspberry Pi, or any UEFI amd64 box**. That is the whole
claim, and it is a claim about how the images are built — not a promise that
every machine has been tried.

So this page keeps two things apart:

- **Runs on** — what the image supports by construction. The arm64 image boots
  via the Raspberry Pi bootloader; the amd64 image is an upstream kernel booted
  by GRUB over UEFI, so it wants a 64-bit UEFI machine with a wired Intel or
  Realtek NIC. No legacy BIOS, and no wireless.
- **Tested on** — machines that have actually run it. This is a record, not a
  promise. Hardware missing from it is not hardware that failed; it is hardware
  nobody has tried.

**The firewall is the exception.** It is a separate x86-only image on its own
release cadence, and it stays narrower than the node claim — an Intel N100 box
is the reference and the only target. See
[Getting started](../getting-started/) for where it fits.


## Nodes

| Hardware | Arch | Status | Where that comes from |
| --- | --- | --- | --- |
| Raspberry Pi 4 | `arm64` | tested | 23 compute nodes in a BitScope ER24A rack, OS 2026.07.2-dev.101 |
| Raspberry Pi 5 | `arm64` | tested | Control-plane node, provisioned 2026-07-07 |
| Compute Module 4 | `arm64` | tested | 2 nodes on a Turing Pi 2, stock OS 2026.07.6, no image changes |
| Compute Module 5 | `arm64` | untested — should work | Same SoC as the Pi 5, and its device tree ships in the image — but no CM5 has ever been booted. Treat it as untested. |
| LattePanda Mu + Lite Carrier | `amd64` | tested | Primary development bench |
| CWWK x86-p5-n100 | `amd64` | tested | Firewall reference hardware |

## Carrier boards

Multi-node carriers Rasputin has been run on, and whether it drives their baseboard management controller.

| Carrier | BMC backend | Status | Where that comes from |
| --- | --- | --- | --- |
| BitScope ER24A Edge Rack — Six CB04B cluster blades, 24 Raspberry Pi slots | `bitscope` (RS-485 serial, one manager reaches all 24) | tested | 23 nodes enrolled in 44 minutes; 24/24 online in 121 seconds. Power and serial-over-LAN. BitScope has been dormant for years — this is validation evidence, not a buying recommendation. |
| Turing Pi 2 — Four compute-module slots, board rev 2.5.1, BMC firmware 2.3.2 | `turingpi` (REST over HTTPS with certificate pinning, mDNS discovery) | tested | Two CM4 nodes provisioned and running, and power control driven from the control plane against the board itself. Shipped 2026.07.6. Serial-over-LAN is declined on purpose — this board exposes no console the backend can honestly serve, so it errors rather than faking one. |