Feed all your interests from across the web.

Thinking of a feed reader, we usually picture the looks and features. And those are obviously a big part of it. But the other part, just as important, happens before anything reaches the screen: reliability, fetching and syncing content, treating the web with respect, and making sense of what people publish.

Feedstand is built to take both parts seriously. It is shaped more like a platform than just an app. A beautiful, customizable reader is one way to use it. It is also meant to be extended and connected to the other tools around it.

A reliable foundation

Most of a feed reader’s quality is decided in the background. Feedstand is built on a set of custom libraries for parsing, discovery, canonicalization, and change detection. These libraries have been thoroughly tested against millions of real-world feeds. They are open source, standalone, and available for anyone else building in this space.

Respect the web

A feed reader depends on other people’s servers, should behave like a good guest. That means scanning responsibly, fetching carefully, and avoiding unnecessary traffic when nothing has changed. The sites it depends on deserve that respect.

Built as a platform

The reader is one surface on top of a more flexible system. Extension, customization, and integration are built into the foundation from the very beginning. The goal is not to ship one opinionated app, but to create a platform that can grow into many different uses.

Not tied to one frontend

A good backend should work with more than one client, and a good reader should not depend on one backend forever. Compatibility with long-standing APIs like Google Reader and Fever keeps the system usable from other frontends and open to third-party readers. That kind of freedom matters more than polished lock-in.

Across devices

The interface should be available on the web, desktop, and mobile, with the same core experience across them. It should not be limited to one operating system or one form factor.

A good place to read

Feeds carry more than plain text. They can include code, media, galleries, and platform-specific embeds that need different handling once they arrive. A good reader should do its best to present that content clearly, with solid typography, proper code rendering, working audio and video players, and custom treatment where a generic article view is not enough.

Different content, different layouts

Blogs, newsletters, comics, social posts, and image-heavy feeds do not want the same layout. The presentation should match the material, whether that means a focused reading view, a denser browsing view, a timeline, or a gallery.

An interface you can shape

A reader gets used every day, so small interface choices matter. Themes, typography, density, how much interface stays on screen, and the ability to hide what you do not need should let the interface adapt to the person using it, not the other way around.

Privacy by default

A feed reader should not quietly expose more than it has to. Third-party assets can be proxied, tracking can be reduced, and the act of following sources should stay as much as possible inside the reader.

AI should stay optional

AI can be useful, but it should remain a tool, not the default way of reading. The basic act of following and reading feeds should work fully without it, and turning it off should mean off. When it is there, it should help with specific tasks, not stand between the reader and the sources they chose.

For the open web

The point is not only to pull content in, but to stay connected to the web that made feeds possible in the first place: open formats, open protocols, and direct ways to respond to publishers. Standards matter because they outlast products.