Imagine this: you buy a house, sign the deed, move in. Then you discover the foundation is owned by a corporation that won’t let you see its blueprints. They can add doors you don’t know about. They can lock rooms you thought were yours. That’s your computer. Every single one of them.
You obsess over which operating system to use. You debate Linux vs. Windows vs. macOS. You care about app permissions, encryption, VPNs. But the very first code that runs on your machine—the boot firmware—is a black box. You can’t audit it. You can’t change it. And you can’t be sure it’s not lying to you.
Most people have never heard of coreboot, Libreboot, or Canoeboot. They don’t know that the firmware on their motherboard is often a proprietary blob with no public source code. They don’t know that Intel’s Management Engine or AMD’s PSP can run code before the OS even loads. They don’t know that their “personal computer” is anything but personal.
Then there’s Canoeboot.
It’s a fork of Libreboot, maintained by the same developer, Leah Rowe. But Canoeboot draws a line in the sand. It removes every single binary blob from coreboot. Every. Single. One. That means no microcode updates, no vendor firmware, no unsigned code. The result is a boot firmware that is fully auditable, understandable, and controllable by the user. It’s the closest thing to a computer that actually belongs to you.
But here’s the tension that most people miss: this radical purity comes at a cost. Canoeboot supports fewer motherboards than Libreboot. It won’t run on the latest hardware. It demands older, often slower machines. The trade-off is real—and it’s the same trade-off that has haunted free software since the beginning: freedom versus compatibility.
Most projects choose compatibility. They accept binary blobs because they want users. They want adoption. They want impact. Canoeboot says no. Better to have a fully free system that few people use than a compromised system that everyone uses.
That’s a hard position. It’s also the only honest one.
I’ve been using a Canoeboot-compatible ThinkPad X200 for a year. It’s slow. It’s old. But every time I press the power button, I know exactly what happens. I can read the entire boot flow. I can modify it. I can rebuild it. There is no secret. There is no backdoor. That feeling of ownership is addictive—and it’s something the industry has stolen from us.
Leah Rowe, the developer behind both Libreboot and Canoeboot, doesn’t mince words. She’s called binary blobs a “security risk” and a “freedom issue.” She’s taken the radical step of splitting her own project because she believes that even a “pragmatic” acceptance of blobs is a betrayal of the core idea of free software. Whether you agree with her or not, you have to admit she’s consistent.
And that consistency exposes an uncomfortable truth: most of us aren’t willing to make the same sacrifice. We want freedom, but we also want convenience. We want privacy, but we also want the latest hardware. We want control, but we want it to be easy. We want our computers to be ours, but we aren’t willing to pay the price.
That’s why Canoeboot matters. It’s not a product. It’s a mirror. It shows us what we’ve given up. The next time you install a new OS or tweak a privacy setting, ask yourself: what’s running before my OS even starts? If you can’t answer that question, you don’t own your computer.
Canoeboot is the fix. And it’s not for everyone. But it’s for anyone who is tired of being lied to.
FAQ
Q: What exactly is Canoeboot and how is it different from Libreboot?
A: Canoeboot is a fork of Libreboot by the same developer. The difference is that Canoeboot removes all binary blobs from coreboot, while Libreboot accepts some blobs for hardware compatibility. Canoeboot is stricter about freedom, but supports fewer devices.
Q: Is Canoeboot safe to use on my daily driver?
A: It depends on your hardware. Canoeboot supports a limited set of older motherboards, mostly Intel-based ThinkPads from the Core 2 Duo era. If you have compatible hardware, it's stable and fully auditable. But don't expect modern features like UEFI or fast boot times.
Q: Doesn't rejecting all binary blobs make the project irrelevant?
A: That's the common criticism. But Canoeboot's value isn't in market share—it's in demonstrating what a fully free system looks like. It serves as a proof of concept and a moral benchmark. If you value absolute control over your hardware, it's the gold standard.