Skip to main content

Rackmount Modular Framework Server

The Rackmount Modular Framework Server is a community project to design 3D-printable rack-mount enclosures for Framework Laptop mainboards, enabling their reuse as homelab servers, Kubernetes clusters, and NAS devices1. Started by n3rding in May 2022, the project has inspired multiple community builds including Andy Clemenko's 6-node "BladeRunner" cluster and Fady's "FrameCluster" 10-node design1.

Motivation​

The Framework mainboard is attractive for homelab use because of its small size, low power consumption, modular I/O (via expansion cards), and upgradeability — when a user upgrades their Framework Laptop, the old mainboard can be repurposed as a server instead of becoming e-waste1. Laptop-class CPUs offer good performance-per-watt compared to older Xeon servers, making them suitable for home NAS, Kubernetes clusters, and learning environments1.

n3rding's Original Design​

n3rding's design criteria1:

  • Printable on a standard 200×200 mm print bed
  • Modular bays that users can rearrange
  • Compatible with existing Framework expansion cards
  • Support for 19" 1U, 10" 1U, and vertical "cluster/blade" mounting
  • Standardized module front/middle/rear sections to minimize reprints

The 17" (19" rack) front unit comprises 3 bays: two identical mainboard bays (left and right) and a middle section for 2.5" drives or 1U power supplies1. Each bay is split into three parts — the front 44 mm, plus middle and rear sections — so changing the front layout doesn't require reprinting the entire bay1.

Technical Challenges​

n3rding identified several key challenges1:

  • Power — The board requires USB-C PD negotiation, not a simple 12V supply
  • Power button — The onboard button is tiny and impractical for rack use; requires an interface board for the header
  • Cooling — Framework mainboards draw air top/bottom and exhaust sideways (90°), unlike traditional servers that flow front-to-back
  • Networking — The WiFi M.2 slot can accommodate 1G or 2.5G Ethernet cards; 10G requires the full PCIe slot via riser
  • Storage — M.2 2230 to 5× SATA port cards exist but are reportedly flimsy; USB-C to SATA is an alternative
  • No IPMI — No remote management capability without additional hardware
  • No ECC RAM — Intel Framework mainboards don't support ECC memory

Community Builds​

Andy Clemenko's "BladeRunner" (2023)​

Andy Clemenko built a 6-node Framework cluster for Kubernetes, documented in two YouTube videos12:

  • 2-node prototype — Built first as a proof of concept
  • 6-node "BladeRunner" — Housed in a shoebox-sized enclosure, powered by two 6-port USB-C PD power supplies
  • Cooling — No heat issues reported with all heatsinks oriented vertically and vented out the top1
  • Networking — Used Framework's 2.5 GbE expansion cards (one per node)1
  • Power — Used 6-port 65W USB-C PD chargers (2 units for 6 nodes)1
  • Use case — Kubernetes cluster

Fady's "FrameCluster" (2025)​

In December 2025, community member Fady posted a high-density 10-node 3D-printable rackmount design for 10" or 19" racks1. Framework VP nrp praised the design as "awesome" with "very high density"1. Files were published on MakerWorld with F3D source files for customization1.

AstraLuma's Build (2023)​

AstraLuma built a smaller cluster using modified Framework reference case designs, adding Ethernet card cutouts and improved airflow1. Software challenges were encountered with Realtek-based Ethernet cards on Debian, requiring the realtek-firmware package1.

Power Solutions​

Power delivery is a recurring challenge since Framework mainboards require USB-C PD1:

SolutionDescriptionLimitations
Framework power brickOne per board, mounted on bladeSimple but bulky for multi-node
Multi-port USB-C PD charger6–10 ports at 65W eachMay reset all ports when new device connects1
1U rackmount USB-C hube.g., Bravour 10-port 65WPurpose-built for rack use1
Server PSU + PD negotiation12V server PSU with USB-PD chipRequires custom electronics1
PicoPSU with PD adapterUSB-PD to ATX for drives + fansLimited drive count1

Cooling Considerations​

The thread identified that Framework mainboard cooling is fundamentally different from traditional servers1:

  • Framework fans intake from top/bottom and exhaust sideways
  • Traditional servers push air front-to-back across the heatsink
  • Stacking boards vertically (as in a blade configuration) requires careful attention to avoid fans working against each other
  • Andy Clemenko reported zero heat issues with vertical heatsink orientation and top ventilation1
  • 3D-printed enclosures should use PETG or ASA rather than PLA due to heat concerns1
  • BIOS setting "Standalone mode" disables chassis intrusion LED blinking1

Networking Options​

MethodSpeedInterfaceNotes
Framework 2.5 GbE card2.5 GbpsExpansion card slotSimplest; Realtek driver issues on some Linux distros1
M.2 2230 Ethernet (WiFi slot)1–2.5 GbpsInternal M.2 E-keySaves expansion card slots1
PCIe riser + full NIC10 GbpsInternal M.2 with riserBest performance; thermal and space challenges1
Thunderbolt 4 networking40 GbpsTB4 cable between boardsPoint-to-point only; no TB switches exist1
USB Ethernet dongle1–5 GbpsUSB-CCheap and simple1

Footnotes​

  1. Rackmount Modular Framework Server — Framework Community (n3rding et al., May 2022 – March 2026) ↩ ↩2 ↩3 ↩4 ↩5 ↩6 ↩7 ↩8 ↩9 ↩10 ↩11 ↩12 ↩13 ↩14 ↩15 ↩16 ↩17 ↩18 ↩19 ↩20 ↩21 ↩22 ↩23 ↩24 ↩25 ↩26 ↩27 ↩28 ↩29 ↩30 ↩31 ↩32

  2. BladeRunner - Framework Laptop Cluster - k8s shoe box — Andy Clemenko (YouTube, March 2023) ↩