The Quiet Rebellion of Open E-Readers

I was reading on my Kindle last week when it hit me: I dont own the books on this device. I own licenses that can be revoked. The device itself is locked down. I cant lend books freely. I cant read formats from my local library without jumping through hoops.

And Amazon knows exactly how long I spend on each page.

Thats when I discovered FreeInk, a project building something radically different: e-readers that you actually own.

What Is FreeInk

FreeInk is an open-source collective building the entire stack for e-paper readers: software, firmware, and hardware. Everything is open. You can pick it up, extend it, and make it your own.

Their flagship device, fig 1.0, is built on the ESP32-S3 with a GoodDisplay e-paper panel. It supports EPUB 2 and 3, has WiFi for book transfers, works with Calibre and KOReader Sync, and uses USB-C for charging.

Nothing fancy. Nothing locked down. Just a reader that lets you read.

Why This Matters

E-reading has become a walled garden problem. Kindle, Kobo, Apple Books: each is a closed ecosystem where the manufacturer controls what you can read, how you read it, and what data they collect while you read.

FreeInk flips this. Their firmware is open-source. The hardware design is published in KiCad. The case files are available for 3D printing. Even the battery is swappable.

Here is what that gives you:

• No DRM: Books you buy are books you own.
• Any format: EPUB, PDF, MOBI, CBZ. Load them via WiFi, USB, or microSD.
• No tracking: Nobody knows how long you spent on page 47.
• Repairable: Battery died? Swap it. Screen cracked? Replace it.
• Extensible: Dont like the UI? Change it. Want to add a feature? Build it.

The Technical Approach

What makes FreeInk interesting is how they have structured the firmware. They built a hardware-independent SDK that abstracts all the device-specific details: display controllers, waveforms, GPIO pins, bus speeds, touch controllers, frontlight.

The firmware calls one generic API and gets device-specific behavior. Adding a new device means creating a profile with configuration values. Not rewriting code.

They even compiled wolfSSL from source for TLS 1.3 support. This lets the reader sync with KOReader servers securely. Thats the kind of detail you only see when users are building for themselves.

The Real Win: Focus Reading

My favorite feature is something called Focus Reading. It bolds the front of each word to guide your eye and set your pace. Its based on research showing this technique improves reading speed and comprehension.

On a Kindle, you would need to wait for Amazon to decide this is worth building. On FreeInk, someone in the community just implemented it.

What Is Missing

FreeInk is not perfect. The screen is smaller than a Kindle Paperwhite. The processor is slower. Page turns are not quite as fast. There is no waterproofing. No cellular connectivity. No audiobook support.

But here is the thing: none of that matters for what this is. It is a reader. It reads books. It does not phone home. It does not lock your library. It does not treat you like a revenue stream.

Why I Am Excited

I have been thinking a lot about what it means to own technology. Not just possess it, but own it. Understand it. Modify it. Fix it.

FreeInk represents a quiet rebellion against the idea that devices should be black boxes we are licensed to use until they break or the company decides to kill support.

This is e-reading as it should be: you buy a book, you read a book. Nobody watches. Nobody tracks. Nobody can take it away.

The project is looking for sponsors and contributors. They are building hardware in the open, which is rare and hard and worth supporting.

I am going to build one. Not because it is better than a Kindle in every way, but because it is mine. And in 2026, that counts for something.

// share