Truly open
Full schematics, PCB layout, and firmware sources published under open hardware licenses. No NDAs, no blobs where we can avoid them, no mystery silicon.
// open hardware · open firmware · open future
FreeWork drops into your existing Framework 13 chassis and replaces the mainboard with something radical: a board you can study, modify, and rebuild — with pluggable compute modules from Raspberry Pi to a MiSTer-compatible FPGA.
// why freework
Full schematics, PCB layout, and firmware sources published under open hardware licenses. No NDAs, no blobs where we can avoid them, no mystery silicon.
When the compute module you rely on ages out, swap it — not the whole board, and definitely not the whole laptop. The carrier stays; the compute evolves.
Design your own module, respin the carrier, add the port you always wanted. Every design file exists so you can change it.
// pluggable compute
FreeWork is a carrier: display, battery, keyboard, expansion cards, and power are handled on-board. The CPU — or FPGA — lives on a pluggable module.
Run a fully documented ARM platform in a premium laptop chassis. Great mainline Linux support, a massive community, and hardware you can actually reason about.
A module built around an FPGA compatible with the MiSTer project. Cycle-accurate classic computers, consoles, and arcade cores — in a laptop you carry every day.
The module connector is fully specified and openly documented. RISC-V board? Microcontroller cluster? If you can route it, you can boot it.
// hardware
Specifications describe the current design target and may evolve during prototyping.
// retro corner
The FPGA module targets compatibility with the MiSTer-FPGA project — the gold standard for cycle-accurate recreations of classic hardware. Slot it in and your Framework 13 becomes an Amiga, a Genesis, an arcade cabinet… on original-accurate silicon logic, not software emulation.
// roadmap
Carrier board bring-up: power, display, keyboard, and the module connector validated on first-revision hardware.
Small batch for developers and contributors — firmware hardening, module ecosystem work, and real daily-driver testing.
Finalized design files published, production run organized with and for the community.
// get involved
FreeWork needs hardware hackers, firmware developers, FPGA core wranglers, and daily-driver testers. Repository and community links are coming soon — check back as the project boots up.