Refeed

Open-source RSS aggregation, honestly reviewed. Minimal hype, just what you get when you run it yourself.

TL;DR

• What it is: MIT-licensed, self-hosted RSS reader with a modern web UI, mobile apps via React Native/Expo, and a handful of bookmark management features you won’t find in most alternatives.
• Who it’s for: Privacy-conscious readers escaping Feedly or Inoreader who want something visually cleaner than FreshRSS and more opinionated than Miniflux — and don’t mind being early to a small project.
• Cost savings: Feedly and Inoreader both charge $3–8/mo per person for their paid tiers. Refeed self-hosted runs on a cheap VPS for roughly $5–10/mo, with no per-seat or per-feed pricing.
• Key strength: Timed Bookmarks — an opinionated feature that auto-expires saved articles, keeping your reading list honest. Newsletter-to-RSS ingestion via a custom email address is also genuinely useful.
• Key weakness: 176 GitHub stars at time of writing. No third-party reviews in the wild. Website was unreachable during research. This is early-stage software backed by a single developer, not a battle-tested platform.

---

What is Refeed

Refeed is an open-source RSS reader built by Michael Kremenetsky. The pitch from the README is simple: “with Refeed, you can easily organize and read your favorite websites, blogs, and news sources in one place.” There’s no elaborate marketing angle, no “AI-first” positioning, no enterprise tier. It’s an RSS reader [README].

The technology stack is modern — Next.js, tRPC, React, React Native, Expo, Tailwind CSS, Prisma, and Supabase for the database layer [README]. That’s not a vintage PHP project you’ll be duct-taping together; it’s a TypeScript monorepo built with Turborepo that includes both a web interface and a React Native mobile app. That’s more platform coverage than several of the more popular alternatives in this space.

What makes Refeed different isn’t the core RSS reading — it’s the opinionated features layered on top. The Timed Bookmarks concept (bookmarks that delete themselves after a preset duration) is an unusual design choice that forces you to either act on saved articles or watch them expire. Whether that’s useful or annoying depends entirely on how you manage your reading backlog.

One important caveat up front: this project has 176 GitHub stars. The website returned a fetch error during research. No third-party reviewers have written about it. The assessment below is based on the README, the merged project profile, and context from the broader self-hosted RSS space [1][2][3][4]. Treat this review accordingly.

---

Why people choose it (and why you might)

Nobody is choosing Refeed because it’s the established option — they’re choosing it because the established options have visible problems that Refeed attempts to address.

The self-hosted RSS space is dominated by FreshRSS, Miniflux, and Tiny Tiny RSS. FreshRSS wins on features and third-party client compatibility, but its default interface is widely described as dated, and the configuration surface is wide [1][2][4]. Miniflux markets aggressively on minimalism, which is a polite way of saying it does less [1]. Tiny Tiny RSS has a devoted following but is notorious for having a development team that can be hostile to newcomers [1].

Reviewers across the self-hosted RSS space consistently repeat the same complaints about hosted services like Feedly and Inoreader: privacy concerns (a lot can be inferred about you from your feed subscriptions), the risk of features getting paywalled or the service shutting down, and interfaces that have grown bloated with algorithmic recommendations that nobody asked for [2][4]. One XDA reviewer put it plainly: “I wouldn’t have to worry about sudden shutdowns, forced UI changes, or features getting locked behind a paywall” [4].

Refeed targets the same audience — people who want the clean hosted-service experience but without the data collection — but takes a different bet than FreshRSS or Miniflux. It prioritizes a modern web stack and unique bookmark management over maximum feature parity with the RSS protocol’s full extension surface. If you’ve looked at the FreshRSS interface and found it overwhelming, or at Miniflux and found it too stripped-down, Refeed is trying to sit in the middle.

The newsletter-to-RSS feature is the other draw. Refeed gives you a custom email address — you subscribe to newsletters with it, and Refeed converts those newsletters into RSS items inside your feed [README]. That’s a real capability that most self-hosted RSS readers don’t offer natively, and it addresses a genuine pain point: newsletters are the modern equivalent of RSS, and they don’t play nicely with standard aggregators.

---

Features

Based on the README and the merged profile:

Reading and organization:

• Web-based RSS feed reader with full content fetching — articles render inside Refeed, not just as headline links [README]
• Fullscreen reading mode to eliminate interface chrome [README]
• Mark read on scroll — articles auto-mark as read while you scroll through them [README]
• Filters — auto-remove content matching keywords, authors, or publication dates before it hits your feed [README]
• Bookmark Folders — organize saved articles into folders for retrieval [README]

The distinctive features:

• Timed Bookmarks — bookmarks automatically delete after a user-set duration. The design intent is forcing you to act on saved articles or let them expire, keeping your reading list free of years-old deferred articles [README]
• Newsletter ingestion — custom email address for newsletter subscriptions; Refeed converts incoming newsletters into RSS items accessible directly in the reader [README]
• Notes — jot down thoughts per-article with named note types (“Inspiration”, “To-Do”, “Deep Dive”) [README]

Platform:

• Web interface (Next.js)
• Mobile apps via React Native and Expo — meaning both iOS and Android are covered [README]
• Self-hosted via Docker [README]; Supabase handles the database layer

What’s notably absent:

• No mention of Fever API or compatible API for third-party clients like Reeder or NetNewsWire
• No documented plugin or extension system comparable to FreshRSS extensions [1][2]
• No WebSub (PubSubHubbub) support mentioned for real-time feed updates [1]
• No comics/media-specific view

---

Pricing: SaaS vs self-hosted math

Refeed has no cloud tier and no commercial pricing. It’s MIT-licensed software you run yourself or don’t run at all. There’s no managed hosting option to buy into.

Feedly for comparison:

• Free: 100 sources, 3 feeds
• Pro: pricing not confirmed from available sources — data not available from research materials
• Feedly AI tiers run higher; exact figures unavailable from sources consulted

Inoreader for comparison:

• Free tier exists with limitations
• Paid tiers add features like filters, search, and rules — exact pricing data not available from sources consulted

What reviewers actually say about cost: the XDA reviewers who wrote about FreshRSS [2][4] and the selfh.st survey [1] don’t frame hosted RSS as expensive the way Zapier is expensive — RSS readers top out around $10–15/mo per person for the priciest tiers. This is a privacy and control argument as much as a cost argument.

Self-hosted Refeed:

• Software: $0 (MIT license) [README]
• VPS: $5–10/mo (Hetzner, Contabo, or DigitalOcean)
• Supabase: free tier for personal use, or self-hosted Supabase adds complexity

The savings math here is less dramatic than replacing a Zapier bill. You’re saving $5–15/mo if you were paying for Feedly or Inoreader, which over a year is $60–180. The real argument is control and privacy, not raw dollars.

---

Deployment reality check

The README’s install path has two options: clone and run locally with pnpm, or use Docker [README]. The Docker path is documented in setup/SELFHOSTING.md in the repo.

What the setup requires:

• Supabase — either the hosted platform or a self-hosted Supabase Docker instance [README]. This is non-trivial. Self-hosting Supabase involves running multiple containers (PostgreSQL, GoTrue for auth, PostgREST, Kong, and others). If you use the hosted Supabase free tier, you’re trading self-hosting purity for simplicity.
• Running the schema SQL manually in the Supabase SQL editor [README]
• Running pnpm db:push to push Prisma schema
• Environment variables configured via .env

What can go sideways:

• The Supabase dependency is the biggest friction point. Unlike FreshRSS or Miniflux which bundle their own PostgreSQL via docker-compose, Refeed externalizes auth and database to Supabase [README]. If you want a fully self-contained deployment, you’re orchestrating Supabase Docker alongside Refeed. That’s a more complex setup than competitors offer.
• No third-party reviewers have written about their Refeed deployment experience. There’s no community troubleshooting archive to draw on if something breaks.
• 176 GitHub stars means the project is not under significant external testing pressure. Bugs that would surface quickly in a widely-used project may persist quietly here.

Realistic time estimates: for a technical user familiar with Docker and Supabase — probably 1–3 hours. For someone who has deployed Docker containers before but hasn’t touched Supabase — 3–6 hours including understanding the Supabase setup. For a non-technical founder with no server experience — this is not a project to attempt alone.

The mobile app (React Native/Expo) adds a note of optimism here: if you get it running, you’ll have both a web interface and native mobile apps without setting up anything additional [README]. That’s better platform coverage than FreshRSS (which relies on third-party apps) or Miniflux (which promotes its PWA) [1].

---

Pros and Cons

Pros

• MIT license. You can self-host, fork, or embed it without restrictions [README]. Same freedom as FreshRSS, better than Miniflux’s license on the managed hosted tier.
• Timed Bookmarks. A genuinely novel approach to reading list management. If you’ve ever opened Pocket or Instapaper to find 400 articles you’ll never read, this is a direct response to that problem [README].
• Newsletter-to-RSS ingestion. A custom email address that converts newsletters into feed items is not a standard feature in any of the established self-hosted alternatives [1][README]. This alone might justify the setup overhead for heavy newsletter subscribers.
• Modern tech stack. Next.js, tRPC, Prisma, Supabase is a developer-legible, maintainable foundation — not legacy PHP [README]. Easier to fork and modify if you have TypeScript skills.
• Native mobile apps. React Native + Expo means iOS and Android apps built from the same codebase. FreshRSS and Miniflux rely on third-party clients for this [1][README].
• Full content fetching. Articles render in full inside the reader, not just as headlines linking out [README].

Cons

• 176 GitHub stars. This is not a community-battle-tested project. FreshRSS, Miniflux, and Tiny Tiny RSS have years of production deployments behind them [1]. Refeed is very early.
• No third-party reviews exist. Zero independent assessments to cross-check. Every claim in this review traces back to the README or the broader RSS market context.
• Website was unreachable during research. A single developer project whose website goes down during research is a reliability signal worth factoring into a long-term decision.
• Supabase dependency complicates self-hosting. Full self-hosted deployment requires running or connecting to a Supabase instance, which is more operationally complex than competitors that use a single PostgreSQL container [README][1].
• No third-party client API documented. No Fever API, no Google Reader API, no FreshRSS API compatibility. If you want to use Reeder, NetNewsWire, or any desktop RSS client as a front-end, Refeed won’t support it [README vs 1].
• No plugin or extension system. FreshRSS has a community extension catalogue; Refeed has none mentioned [1][README].
• Single-developer project with no visible team or company backing. Contact is a personal email address (michaelkremenetsky@refeed.dev) [README]. There’s no indication of commercial backing or a founding team.

---

Who should use this / who shouldn’t

Use Refeed if:

• You’re a developer comfortable with TypeScript monorepos and want a modern-stack RSS reader you can actually fork and modify.
• The Timed Bookmarks feature solves a real problem you have — your reading list is a graveyard of saved articles you never return to.
• You subscribe to a lot of newsletters and want them consolidated into a single feed interface without cluttering your email inbox.
• You’re willing to be an early user of unproven software and can tolerate rough edges.

Use FreshRSS instead if:

• You want third-party client compatibility (Reeder, Fluent Reader, NetNewsWire) via Fever or Google Reader API [1][2][4].
• You want the most feature-complete, community-vetted self-hosted option with years of production use behind it [1].
• You want Docker-only deployment with no external service dependencies [2][4].

Use Miniflux instead if:

• You want the absolute minimal, lowest-resource RSS aggregator with a clear and honest minimalist philosophy [1].
• You’re comfortable paying a small managed hosting fee and want zero maintenance overhead [1].

Use CommaFeed instead if:

• You want something between FreshRSS’s complexity and Miniflux’s minimalism with a slightly more modern UI and easy import from existing feeds [3].

Skip all self-hosted options if:

• You’re non-technical and don’t have someone to handle a one-time server deployment for you. The Feedly free tier covers the basics well enough not to justify the operational overhead.

---

Alternatives worth considering

The self-hosted RSS space is more crowded than many people realize. From the sources surveyed:

• FreshRSS — the default recommendation for most self-hosting newcomers. Feature-rich, multi-client compatible, SQLite or PostgreSQL, strong community [1][2][4]. The interface looks dated but it works reliably.
• Miniflux — aggressively minimal. Go binary, PostgreSQL, Fever API. Opinionated in the opposite direction from Refeed — no extras, just feeds [1].
• Tiny Tiny RSS — full-featured with an extensive plugin catalogue, but the community is famously unwelcoming to beginners [1].
• CommaFeed — positioned between FreshRSS and Miniflux; one self-hoster specifically cited it as having “a combination of easy install and slightly more modern UI options” compared to FreshRSS [3].
• Feedly (hosted) — if self-hosting is more overhead than it’s worth and privacy isn’t a top concern. The free tier covers 100 sources.
• Inoreader (hosted) — similarly capable, closed source, subscription pricing.

For a non-technical founder evaluating RSS options, the realistic self-hosted shortlist is FreshRSS or Miniflux — both have years of community support and documented deployment guides. Refeed is a more interesting project technically, but the risk profile is much higher for anyone who needs their tools to just work.

---

Bottom line

Refeed is a genuinely interesting RSS reader idea with a modern codebase, two compelling differentiating features (Timed Bookmarks and newsletter ingestion), and a technology stack that makes it approachable for TypeScript developers who want to fork it. What it doesn’t have is a community, documentation beyond the README, a working website at research time, or any third-party validation that the deployment experience is smooth. 176 GitHub stars is a small signal, and the Supabase dependency makes the self-hosting path more complex than competitors that ship a single docker-compose file. If you’re a developer looking for a project to run and possibly contribute to, it’s worth trying. If you’re a non-technical founder who just wants reliable self-hosted RSS, FreshRSS or Miniflux are lower-risk choices with years of production use behind them. Refeed is a project to watch, not yet one to bet your daily reading workflow on.

If you want help evaluating whether Refeed or one of its more established alternatives is the right fit to deploy — that’s exactly what upready.dev does for clients.

---

Sources

1. Ethan Sholly, selfh.st — “Self-Hosting Guide to Alternatives: Feedly, Inoreader” (Nov 14, 2024). https://selfh.st/alternatives/rss-readers/
2. Sumukh Rao, XDA Developers — “I brought my news feed back from the dead thanks to this self-hosted RSS reader” (Jun 23, 2025). https://www.xda-developers.com/brought-news-feed-back-self-hosted-rss-reader/
3. Andrew Allen, Double A Reviews — “Four self-hosted services that I’ve found surprisingly useful” (Jan 29, 2025). https://double-a-reviews.beehiiv.com/p/four-self-hosted-services-that-i-ve-found-surprisingly-useful
4. Dhruv Bhutani, XDA Developers — “I self-hosted my own RSS reader to keep up with the news” (Mar 8, 2025). https://www.xda-developers.com/i-self-hosted-my-own-rss-reader-to-keep-up-with-the-news/

Primary sources:

• GitHub repository and README: https://github.com/michaelkremenetsky/refeed (176 stars, MIT license)
• Official website: https://refeedreader.com (unreachable at time of research)