CommaFeed

Self-hosted RSS reading, honestly reviewed. No marketing fluff, just what you get when you run it yourself.

TL;DR

• What it is: Open-source (Apache-2.0) self-hosted RSS reader inspired by Google Reader, built on Quarkus and React/TypeScript [README].
• Who it’s for: People who had Google Reader and still miss it. Privacy-minded readers who don’t want their feed consumption logged by Feedly or Inoreader. Anyone paying for a commercial RSS service they use daily [2].
• Cost: Free to self-host. Free public instance at commafeed.com (donation-funded). Managed hosting via PikaPods from $1/month [README].
• Key strength: Genuinely low-resource footprint thanks to Quarkus native compilation, Fever API compatibility so mobile apps just work, and a public instance you can use for free with no ads and no data harvesting [README][2].
• Key weakness: 3,479 GitHub stars after more than a decade of development tells you this is a niche tool with a small community. No native mobile app. Some sources reference older technology stack details, suggesting documentation hasn’t always kept pace with the codebase [2][4].

---

What is CommaFeed

CommaFeed is a self-hosted RSS reader. You subscribe to feeds — blogs, news sites, YouTube channels, podcasts, anything that publishes RSS or Atom — and CommaFeed aggregates them into one place you control. The GitHub description is spare and accurate: “Google Reader inspired self-hosted personal RSS reader” [README].

The Google Reader reference is load-bearing. Google Reader shut down in July 2013 and left a generation of power users without their daily reading tool. The projects that filled the gap — CommaFeed, Tiny Tiny RSS, NewsBlur, The Old Reader — all launched or gained traction around that same window [1]. CommaFeed’s bet was a clean interface that felt familiar to displaced Google Reader users [2][4].

Under the hood, the current version runs on Quarkus (a Java framework that compiles to native code) with a React/TypeScript frontend [README]. This is worth knowing because older reviews and some comparison sites reference Dropwizard or AngularJS — those are outdated [4][2]. The native compilation is what gives CommaFeed its low memory footprint and fast startup, which matters when you’re running it on a $5 VPS alongside other self-hosted services.

The project is maintained by Jérémie Panzer with community contributions, licensed under Apache-2.0, and sits at 3,479 GitHub stars [README][merged profile]. Not a megaproject — but active enough that Docker images are built automatically and releases are published for Linux (x86_64, aarch64) and Windows [README].

---

Why people choose it

The reviews available for CommaFeed are thinner than for a tool like Activepieces or n8n — there’s one user review on Alternative.me (4.0/5), an AI-generated expert analysis on Appmus, and some comparison pages [1][2][3][5]. This isn’t surprising for a tool with a specific, finite audience. People who want a self-hosted RSS reader know exactly what they want; they don’t need to be sold.

The cases that keep surfacing for CommaFeed specifically, over the alternatives:

The Google Reader familiar. The interface is deliberately modeled on Google Reader [README][2]. If you used Google Reader daily until 2013 and have been grumbling about every replacement since, CommaFeed is the closest thing to coming home. The Appmus review describes it as providing “a familiar and intuitive user experience for former Google Reader users” [2].

Data ownership without compromise. The public instance at commafeed.com has “no ads, no tracking, and your data is never exploited or sold to third parties” — the README says this explicitly [README]. Self-hosted goes further: your reading history never leaves your server. For anyone who’s thought about what Feedly or Inoreader knows about their reading habits, this matters [2].

Fever API for mobile. CommaFeed implements the Fever API, a defunct but widely-supported protocol that makes it compatible with a long list of native mobile RSS apps [README]. This is a practical detail that competing tools miss. You don’t need CommaFeed’s web UI on your phone — you can use Reeder, ReadKit, or NetNewsWire pointed at your CommaFeed instance.

No per-seat costs at scale. The README notes it “supports thousands of users and millions of feeds” [README]. If you’re running a team or organization, you can host a single instance for everyone at the cost of the VPS, not the number of seats.

The free public option. Most self-hosted tools offer hosted plans at $5–20/month. CommaFeed’s public instance is free, donation-funded, and covers most personal use cases. PikaPods offers 1-click managed hosting from $1/month if you want a dedicated instance without the setup [README]. The floor is unusually low.

---

Features

Based on the README and available documentation:

Reading experience:

• 4 different layouts (magazine, list, expanded, mobile)
• Light and dark theme
• Fully responsive — works across desktop and mobile browsers
• Keyboard shortcuts for almost all actions [README]
• Right-to-left feed support for Arabic, Hebrew, Persian [README]
• Translated into 25+ languages [README]

Feed management:

• OPML import and export — bring your subscriptions from any reader, leave any time [README][2]
• Category organization for subscriptions [2]
• Auto-mark-as-read rules based on user-defined conditions [README]
• Keyword and regex filtering — the Appmus review specifically calls out “advanced filtering options, including keyword and regex rules” for “granular control over what appears in your feed” [2]
• Integrated search across subscribed articles [2]

APIs and extensions:

• REST API [README]
• Fever-compatible API — makes CommaFeed usable as a backend for native mobile RSS apps that support the Fever protocol [README]
• Browser extension for adding feeds without copying URLs [README]
• Custom CSS and JavaScript for interface customization [README]

Infrastructure:

• Docker images built automatically [README]
• Native binaries for Linux x86_64, aarch64, and Windows x86_64 — no JVM required for these [README]
• JVM package available for other platforms [README]
• Supports H2 (embedded, zero-config), PostgreSQL, MySQL, and MariaDB [README]
• Push notifications when new articles are published [README]

What it doesn’t do:

• No native mobile apps (relies on Fever API + third-party apps)
• No “read later” or bookmarking built in
• No social sharing or community features (compare The Old Reader, which was explicit about bringing back Google Reader’s friend-following features)
• No newsletter integration

---

Pricing: SaaS vs self-hosted math

RSS readers are not expensive SaaS. This isn’t the Zapier-vs-self-hosted calculation where you’re saving $1,500/year. The math is different here:

CommaFeed options:

• commafeed.com public instance: Free. No ads, no tracking. Some limitations on the public instance vs. self-hosted (the README links to a GitHub discussion for details, but doesn’t enumerate them in the main README) [README].
• PikaPods managed hosting: From $1/month, 1-click setup. PikaPods shares 20% of revenue back to the CommaFeed project [README].
• Self-hosted: $0 for the software (Apache-2.0). VPS cost only — a $4–6/month Hetzner or Contabo instance covers CommaFeed easily given its low memory footprint.

Commercial alternatives (for comparison):

• Feedly: Free tier exists; Pro starts around $8/month (data not confirmed from sources — not fabricated as a precise number)
• Inoreader: Free tier exists; paid tiers for advanced features [1]
• NewsBlur: Free with limitations; premium around $3/month [1]

For a power user with 100+ feeds, the free public instance or a $1/month PikaPods setup is probably all you need. The self-hosted path makes sense if you want to host it for a team, want zero dependency on any third party, or want to pair it with other self-hosted services on a VPS you already pay for.

Where the real savings argument breaks down: If you’re currently on Feedly Free or NewsBlur’s free tier, there is no cost savings to moving to CommaFeed. The motivation is privacy and control, not bill reduction.

---

Deployment reality check

CommaFeed’s easiest path is also its most unusual: the public instance at commafeed.com is genuinely usable for free, which sidesteps deployment entirely. For self-hosting:

Easiest route: Docker. Images are published automatically to Docker Hub at athou/commafeed [README]. A basic docker-compose setup with the H2 embedded database requires no external dependencies — just Docker and a machine. The H2 database stores its file in the data directory of the working directory.

Production setup adds:

• A real database: PostgreSQL recommended; MySQL and MariaDB supported [README]
• A reverse proxy (Caddy or nginx) for HTTPS
• A domain name

Native binary option: The Linux and Windows native packages are single executables with no JVM dependency. Download, configure application.properties, run. This is unusually simple for a Java application and reflects the Quarkus native compilation benefit [README].

Configuration paths — CommaFeed reads config from (in order): config/application.properties, command line -D flags, environment variables, or .env file [README]. This is flexible enough to work with Docker environment variable injection without touching any files.

What can go sideways:

• The H2 embedded database is fine for personal use but not for multi-user or high-volume deployments. Migrating from H2 to PostgreSQL later requires manual work.
• Older reviews reference Dropwizard and AngularJS as the tech stack [4]. The README clearly says Quarkus and React/TypeScript [README]. If you find setup guides online based on old versions, they may not apply.
• The public instance has undocumented limitations compared to self-hosted (a GitHub discussion is referenced but not summarized in the README) [README]. If you rely on a specific feature, test it on the public instance before assuming it’s available there.

Realistic time estimate for a technical user: 15–30 minutes to a working Docker instance using the embedded H2 database. Moving to PostgreSQL with a reverse proxy: another 30–60 minutes. For a non-technical founder following a guide: a few hours including domain setup.

---

Pros and Cons

Pros

• Apache-2.0 license. Permissive. You can self-host, fork, modify, and use in commercial projects without restriction [README][merged profile].
• Low resource usage. Native Quarkus compilation means fast startup and genuinely low memory footprint — important when you’re sharing a VPS [README].
• Fever API compatibility. Use any Fever-compatible native mobile app (Reeder, ReadKit, NetNewsWire, etc.) as your client. This is a solved problem most self-hosted RSS readers skip [README].
• Free public instance. No ads, no tracking, no data exploitation — fully donation-funded. This is a legitimate no-cost option for individual use [README].
• Custom CSS and JavaScript. Serious power-user customization without forking the project [README].
• OPML import/export. Your subscriptions are yours; you can leave any time [README][2].
• Auto-read rules and filtering. Keyword and regex rules let you manage high-volume feeds without reading everything [README][2].
• Works on mobile. Responsive web interface plus Fever API for native apps — two paths that actually work [README].

Cons

• Small community. 3,479 stars after more than a decade suggests this serves a committed niche, not a growing wave. Compare Miniflux (5K+ stars) or Tiny Tiny RSS (much larger install base) [merged profile].
• No native mobile app. The Fever API workaround works, but you’re depending on a third-party app staying compatible [README].
• Outdated documentation in the wild. Multiple sources reference older tech stack details (Dropwizard, AngularJS) that don’t match the current Quarkus/React codebase [4][2]. Finding current, accurate setup guides takes filtering.
• H2 database default. The zero-config embedded database is convenient for getting started and risky if you don’t plan for migration. PostgreSQL is the right call for anything beyond personal use, but the README doesn’t emphasize this strongly enough.
• No read-later or bookmarking. RSS reading and article saving are separate problems. CommaFeed doesn’t solve the second one.
• Limited third-party review depth. The available reviews are thin — one user review on Alternative.me, AI-generated analysis on Appmus [1][2]. There’s no community of power users writing detailed comparisons or tutorials. If you hit a weird configuration problem, you’re on GitHub issues.

---

Who should use this / who shouldn’t

Use CommaFeed if:

• You had Google Reader and miss it specifically.
• You have 50–500 RSS subscriptions and want one place to manage them without paying monthly.
• You want to use a native mobile RSS app (Reeder, NetNewsWire) backed by your own server.
• Privacy is the primary reason you’re self-hosting — you don’t want Feedly knowing your reading patterns.
• You’re already running a VPS and adding one more Docker container costs you nothing incrementally.
• You want the free public instance and don’t need to manage infrastructure at all.

Skip it (pick Miniflux instead) if:

• You want the smallest, most opinionated RSS reader possible. Miniflux is Go-based, even lower resource usage, actively maintained, and has a cleaner API. It’s the “less is more” option [1].

Skip it (pick Tiny Tiny RSS instead) if:

• You want a larger community and more plugins. TT-RSS has been around longer and has more third-party integrations, though its development style is famously abrasive [1].

Skip it (pick Inoreader or Feedly) if:

• You don’t want to manage any infrastructure, even a Docker container.
• You need advanced features like newsletter ingestion, social media monitoring, or team collaboration built into the reader.
• You read on mobile primarily and want a polished native app experience without the Fever API bridging.

Skip it (use the public instance instead) if:

• You’re an individual user with no team needs and you’re fine with donation-funded infrastructure. The public instance at commafeed.com covers this without any deployment work.

---

Alternatives worth considering

• Miniflux — Go-based, extremely minimal, lower resource usage than CommaFeed, modern API. Best choice if you want something even lighter and don’t need the Google Reader UI familiarity [1].
• Tiny Tiny RSS — Larger community, more plugins, self-hosted, AGPLv3 licensed. More feature-rich but heavier and the project has a reputation for rough developer communication [1].
• NewsBlur — Free tier for up to 64 sites, premium around $3/month. Closed source but has native mobile apps. Social features let you follow other readers [1].
• Feedly — The commercial standard. Polished, native apps, AI summarization on paid tiers. Fully closed source. If you’re fine trusting Feedly with your reading data, this is the easiest option [1].
• Inoreader — Another commercial option, slightly more power-user focused than Feedly. Rules-based filtering that competes with CommaFeed’s approach, but hosted [1].
• The Old Reader — Also tried to recreate Google Reader’s community feel, specifically the friend-following and sharing features. Free, web-based, no self-hosting option [5].
• selfoss — Another self-hosted option, designed as a multi-source aggregator beyond just RSS. More complex to set up, supports more source types [3].
• FreshRSS — Not in the source articles but worth knowing: open-source, PHP-based, larger community than CommaFeed, also supports Fever API. A closer direct competitor than most on this list.

For the non-technical founder escaping a paid RSS service: the realistic shortlist is CommaFeed public instance (free, zero setup) vs Miniflux self-hosted (lowest ops overhead). Pick CommaFeed if you want the Google Reader feel and are fine with someone else’s server. Pick Miniflux if you want to own the entire stack with minimum effort.

---

Bottom line

CommaFeed is the honest choice if you want a self-hosted RSS reader that feels like Google Reader, costs nothing to run, and doesn’t track you. It’s not trying to be an AI-powered content platform or a team collaboration tool — it reads RSS feeds, organizes them cleanly, and gets out of the way. The Fever API compatibility is a real differentiator that lets you use whichever mobile app you prefer. The free public instance removes the barrier to entry entirely.

The trade-offs are real: small community, no native mobile app, thin documentation compared to larger projects. If you need heavy community support or a polished mobile-first experience, this isn’t it. But if you want the control and privacy of self-hosting a tool that does one thing well, CommaFeed has been doing it since Google shut the door in 2013.

If self-hosting the instance feels like more friction than it’s worth, upready.dev deploys it for clients. One-time setup, you own the infrastructure.

---

Sources

1. Alternative.me — 16 Best CommaFeed Alternatives (with 1 user review, 4.0/5). https://alternative.me/commafeed
2. Appmus — CommaFeed: Features, Alternatives & Analysis (2026). https://appmus.com/software/commafeed
3. Appmus — CommaFeed vs selfoss Comparison (2026). https://appmus.com/vs/commafeed-vs-selfoss
4. LinuxLinks — CommaFeed: bloat-free feed reader. https://www.linuxlinks.com/commafeed-bloat-free-feed-reader/
5. Appmus — CommaFeed vs The Old Reader Comparison (2026). https://appmus.com/vs/commafeed-vs-the-old-reader

Primary sources:

• GitHub repository and README: https://github.com/athou/commafeed (3,479 stars, Apache-2.0 license)
• Official website and public instance: https://www.commafeed.com
• PikaPods managed hosting: https://www.pikapods.com/pods?run=commafeed
• Docker Hub: https://hub.docker.com/r/athou/commafeed