Inkwell: RSS reader application designed for e-ink devices.

What it does

Inkwell is a self-hosted RSS and Atom reader optimized for e-ink devices, particularly Kindles. It serves articles as static HTML formatted for the built-in browser on e-readers. The application pre-processes feeds by extracting article content and transcoding embedded images so that devices download only ready-to-render bytes from local disk. Users can browse feed listings, read individual articles, and manage a read-later queue directly from their e-ink device.

Who it is for

Inkwell targets people who own e-ink devices like Kindles and want to read RSS feeds without relying on cloud services or external applications. The software appeals to users comfortable running their own infrastructure and those who prefer reading long-form content on e-ink screens. It suits individuals who want direct control over their data and feed sources.

Pricing

The site does not show prices.

How it stands out

Most RSS readers prioritize smartphones and tablets with color screens. Inkwell reverses this approach by building specifically for e-ink hardware and their constraints. The application handles the technical work of image transcoding and content extraction in advance, so the e-reader device performs minimal processing when fetching articles. Installation options include building from source or running under Docker, with support for reverse proxies and access control. The tool allows authentication via a gateway without requiring typing on the device itself, reducing friction during setup. Documentation covers installation, self-hosting, configuration, and device-specific behavior.

What a founder should check

A competitor should verify the current landscape of e-ink-optimized feed readers. Most established RSS services (Feedly, Inoreader, The Old Reader) added e-reader support as secondary features rather than primary design goals, which may leave room for a specialized alternative. Check switching costs for existing users—whether they have built up years of read history, custom feeds, or OPML exports that would be painful to migrate away from a self-hosted solution.

Also examine the moat around Kindle browser limitations and the broader e-ink device ecosystem. Kindle browsers have specific rendering quirks; a reader must stay current with those constraints across device models. Verify whether sufficient demand exists among technical users for self-hosted RSS infrastructure, especially since cloud-based readers remain free or low-cost and require no setup.

Thinking of building something like this?

Every launch here is a competitor to somebody's idea. If yours is close, check it against the market before you build: the Full Check names the rivals, the prices and the gaps.