Miniflux

Self-hosted feed reading, honestly reviewed. No algorithmic noise, no tracking pixels, just articles from sources you chose.

TL;DR

• What it is: A minimalist, opinionated RSS/Atom/JSON feed reader written in Go, self-hosted, Apache-2.0 licensed [README].
• Who it’s for: People who want to read the internet on their own terms — without algorithmic feeds, without per-month SaaS bills, and without a bloated Electron app eating RAM. Works equally well for a developer running 200 feeds and a non-technical user who just wants to quit doom-scrolling Twitter for news [1][2].
• Cost savings: Feedly Pro runs ~$8/month ($96/year), Inoreader Plus ~$4–5/month. Miniflux self-hosted runs on a $5 VPS and costs nothing in licensing. The hosted Miniflux plan exists but pricing data wasn’t available in sources consulted.
• Key strength: Single Go binary, no Node.js, no Redis, no Elasticsearch — just the binary and a PostgreSQL database. Reviewers consistently cite speed and zero bloat [2][3].
• Key weakness: The minimalism is real — if you want algorithmic recommendations, social sharing features, or a polished mobile app from an app store, this isn’t it. Filter rules require regex, and the search can struggle at very high feed volumes [2].

---

What is Miniflux

Miniflux is a web-based RSS feed reader you run on your own server. The pitch is unusually honest about what it is and isn’t: the homepage literally says “No fancy features” and “Less is more” [homepage]. That’s not false modesty — it’s the design philosophy.

The project is developed by Frédéric Guillot and distributed under the Apache 2.0 license, which means you can use it commercially, modify it, and redistribute it without restriction [homepage]. At 8,933 GitHub stars it’s a respected project in the self-hosted community without being a marketing-funded growth story.

What it does: you add RSS, Atom, or JSON Feed URLs, Miniflux polls them on a schedule, and you read articles in a clean web interface. That’s the core. On top of that you get full-text fetching (it can pull the original article when a feed only shows summaries), privacy protections baked in at a level that goes well beyond typical readers, 25+ integrations with bookmark managers and notification services, a REST API, and webhook support [README].

The Go implementation matters more than it sounds. RSS readers are essentially long-running HTTP polling services — Go handles that cleanly, the binary is statically compiled with no external runtime dependencies, and the memory footprint is small enough that you can run Miniflux on a $5 VPS alongside other services without worrying about RAM [2][homepage].

---

Why people choose it

The pattern across all three reviews is the same: someone got tired of either commercial RSS SaaS costs/features or the complexity of heavier self-hosted alternatives, tried Miniflux, and found that stripping everything down to the essentials was exactly what they needed.

Escaping social media and algorithmic feeds. The XDA Developers piece [1] frames Miniflux not as a productivity tool but as a deliberate rejection of how social media controls news consumption. The author describes it as restoring control: “My appreciation for RSS feeds has returned, and I barely spend any time on social media.” The mechanism is direct — you subscribe to specific sources, Miniflux shows you everything they publish in reverse chronological order, nothing is boosted or suppressed. No algorithm, no sponsored content, no “you might also like.”

Replacing Feedly. Both [1] and [2] describe the same journey: Google Reader dies, they move to Feedly, Feedly’s free tier gets more restrictive, they look for alternatives. Miniflux resolves the cost problem (free to self-host) while removing features they didn’t want anyway — Feng from ofeng.org writes that he wanted “a simpler alternative without AI recommendations or excessive premium features” [2]. That’s the Miniflux target market exactly.

Performance. The Go implementation makes a practical difference at scale. Feng’s review [2] tested it with 100+ feeds: “the site speed is impressive as it is purely written in go.” Fetching and processing large feed collections happens in seconds, not the minutes you sometimes wait with PHP-based alternatives or RSS services running on shared infrastructure.

The privacy engineering is serious. Most RSS readers say “we respect your privacy.” Miniflux actually builds it into the content pipeline: tracking pixels removed, UTM parameters stripped, media proxied to prevent third-party tracking, Referrer-Policy: no-referrer enforced, external JavaScript blocked, YouTube played via youtube-nocookie.com with support for Invidious as an alternative player [README]. If you’re connecting your news consumption to a privacy threat model, the implementation here is unusually thorough.

Codebase quality. Feng’s [2] review notes the application follows a clean architecture: CLI → daemon → worker pool → feed scheduler → HTTP server. He concludes: “you don’t need to comment too much when code is properly organized.” For self-hosters who might want to understand what’s running on their server, or who fear picking up unmaintainable open-source code, this matters.

---

Features

Feed handling

• RSS 1.0/2.0, Atom 0.3/1.0, JSON Feed 1.0/1.1 support [README]
• OPML import/export for moving your subscription list between services [README]
• Full-text fetching: downloads and extracts original article content using a local Readability parser when feeds publish summaries only [README]
• Custom scraper rules via CSS selectors for sites where the default extraction fails [README]
• Podcast and video enclosure support — YouTube videos play inline [README]
• Custom rewriting rules and regex filters to include or exclude articles by pattern [README][2]
• Automatic favicon fetching [README]

Privacy and security

• Pixel tracker removal [README]
• Tracking parameter stripping (UTM, fbclid, etc.) [README]
• Media proxy to prevent third-party tracking [README]
• No telemetry, no advertising [homepage]
• Blocks external JavaScript [README]
• Content sanitization before rendering [README]
• HTTP/2 can be disabled optionally to reduce fingerprinting [README]
• Custom user agent and proxy support [README]

Interface

• Responsive design — desktop, tablet, and mobile [README]
• PWA — can be added to home screen without an app store download [README]
• Keyboard shortcuts for fast navigation [README][3]
• Six themes: light/dark/system × serif/sans-serif [README]
• Custom CSS and JavaScript for personal tweaks [README]
• Available in 20 languages [README]

Integrations and API

• 25+ third-party integrations: Wallabag, Instapaper, Pocket, Readwise Reader, Notion, Telegram, Discord, Slack, Ntfy, Pinboard, Linkding, Karakeep, and more [README]
• Webhooks for real-time notifications [README]
• REST API with client libraries in Go [README]
• Fever and Google Reader API compatibility — lets you use existing mobile RSS apps like Reeder, NetNewsWire, or FeedMe as a front-end [README][docs]
• Bookmarklet for subscribing from any browser [README]

Deployment

• Single Go binary, statically compiled, no external runtime [homepage]
• Docker image available [README]
• RPM and Debian packages [homepage]
• PostgreSQL as the only dependency [README][3]
• Cloudron installation option [docs]

---

Pricing: SaaS vs self-hosted math

There’s no subscription or commercial edition. Miniflux is Apache 2.0 — zero licensing cost [homepage].

Miniflux hosting (managed option): Miniflux.app lists a /hosting.html page suggesting a managed option exists, but pricing data was not available in the sources consulted for this review. Check the official site for current figures.

Self-hosted:

• Software: $0
• VPS: $5–10/month (Hetzner, Contabo, DigitalOcean)
• PostgreSQL: bundled in a docker-compose setup or $0 on a self-managed instance
• Your time: minimal after initial setup

Commercial alternatives for comparison:

Service	Free tier	Paid tier
Feedly	100 feeds, 3 feeds per board	Pro ~$8/month, $96/year
Inoreader	150 feeds, ads	Plus ~$4–5/month
NewsBlur	64 feeds, 10/month visits	Premium ~$36/year
Feedbin	None	~$5/month, $55/year

Note: these figures are from training data and subject to change; verify at each vendor’s pricing page.

For a user running 50–200 feeds, self-hosting Miniflux on a $6/month Hetzner VPS costs $72/year flat, with no per-feed limits, no read-count limits, no “upgrade to unlock search” walls. Against Feedly Pro that’s a saving of ~$24/year for the software alone — but if you’re already running other services on that VPS (and most self-hosters are), the marginal cost of adding Miniflux is essentially zero.

The math is less dramatic than the Zapier replacement case — RSS reader SaaS isn’t as expensive as workflow automation SaaS. The real argument for self-hosting Miniflux isn’t primarily financial; it’s data ownership, privacy, and no vendor risk.

---

Deployment reality check

Reviewers’ experience here is consistently positive because the deployment surface is genuinely small.

What you need:

• A Linux VPS or home server (256MB RAM is functional, 512MB+ recommended with several hundred feeds)
• PostgreSQL (version 15+ recommended; bundled in the default Docker Compose setup)
• A domain and reverse proxy (Caddy or nginx) for HTTPS — technically optional, practically essential if accessing over the internet
• Docker and docker-compose, or the ability to install a Debian/RPM package directly

What you don’t need:

• Node.js, npm, Redis, Elasticsearch, RabbitMQ — none of these. One binary, one database [homepage].

Jamie Phillips [3] documented a standard Docker Compose setup with a PostgreSQL Alpine container, noting that the compose file handles automatic admin account creation and database migrations — you don’t run ALTER TABLE scripts manually. The XDA review [1] walked through installation steps including repository setup and firewall configuration, describing it as straightforward within an existing home lab.

What can go sideways:

The filter system requires regex knowledge — the reviewer from ofeng.org [2] notes this as a genuine limitation: “Filtering and blocking rules require regex knowledge and only filter titles.” If you want to filter by content body or use plain-text keyword matching without regex syntax, you’re either learning regex or going without filters.

Search at scale is the other limitation Feng flags [2]: at very high feed volumes, the full-text search (PostgreSQL-backed) “may struggle with large feed volumes, potentially conflicting with the minimalist philosophy.” For most users — say, under 500 feeds — this won’t be an issue. If you’re aggregating thousands of feeds, test the search performance before committing.

Mobile experience is a PWA, not a native app. You add it to your home screen and it behaves like an app, but it’s the web interface. For many users this is fine; for users who want iOS or Android push notifications out of the box, you’ll need to wire up one of the notification integrations (Ntfy, Pushover, Telegram, etc.) yourself [README].

Realistic time estimate: 20–45 minutes for a developer on a fresh VPS. For a non-technical user following a guide: 1–3 hours including domain, HTTPS, and troubleshooting. The Docker Compose path is the easiest; the binary-only path is minimal but requires you to manage a systemd service yourself.

---

Pros and cons

Pros

• Apache 2.0 license. Genuinely permissive — commercial use, modification, redistribution, all fine. No “Fair-code” restrictions, no commercial tier required [homepage].
• Single binary deployment. No Node, no Redis, no Elasticsearch. Just the binary and PostgreSQL. This is the correct level of complexity for an RSS reader [2][homepage].
• Go performance at scale. 100+ feeds processed in seconds. The architecture is clean and reviewers with technical backgrounds note it explicitly [2].
• Privacy engineering that actually works. Tracking pixel removal, UTM stripping, media proxying, external JS blocking, and Referrer-Policy headers — all on by default, none requiring configuration [README].
• Fever and Google Reader API compatibility. You keep your existing mobile RSS app (Reeder, NetNewsWire, FeedMe, etc.) as the front-end and just point it at your Miniflux instance [README][docs].
• 25+ integrations. Connects to every major bookmark manager (Wallabag, Linkding, Readwise, Pocket, Instapaper), notification service (Telegram, Ntfy, Pushover, Discord), and link archiver you’d want [README].
• Full-text fetching. Pulls original article content for feeds that only publish summaries — key for staying in one reading environment [README].
• No telemetry, no advertising. The homepage says it, the README means it [homepage].
• Keyboard-driven interface. Fast navigation without touching the mouse — appreciated by reviewers who want efficient reading workflows [README][3].

Cons

• Regex-only filtering. The content filtering system requires regular expression knowledge. Plain keyword filtering isn’t available, which is a real barrier for non-technical users [2].
• Search performance degrades at very high feed volumes. PostgreSQL full-text search is adequate for most use cases but hits limits when you’re aggregating hundreds of feeds with years of history [2].
• No native mobile apps. The PWA works, but it’s not the same as a purpose-built iOS or Android app. Push notifications require separate integration setup [README].
• Truly minimalist UI — for better and worse. If you want read-time estimates, AI summaries, or saved article recommendations, there’s nothing here. The “No fancy features” positioning is accurate and non-negotiable [homepage].
• Solo maintainer project. Miniflux is developed by Frédéric Guillot. There’s no company behind it, no funding announcement, no 10-person team. This is fine until it isn’t — evaluating the bus factor is reasonable for a tool you’d make central to your daily information consumption.
• No multi-user access controls. If you want to run a shared Miniflux instance for a team with per-user permissions and admin oversight, the feature set is limited. It has basic multi-user support but not role-based access controls.

---

Who should use this / who shouldn’t

Use Miniflux if:

• You’re paying for Feedly, Inoreader, Feedbin, or similar and want to eliminate the bill while keeping the reading habit.
• You’re consuming news through Twitter/X, LinkedIn, or Reddit algorithmic feeds and want to switch to curated, source-direct reading without the noise [1].
• You’re a developer or home-lab operator comfortable with Docker Compose and a VPS — the deployment is genuinely easy.
• Privacy is part of your threat model. The built-in tracker removal and media proxying are substantive, not cosmetic.
• You already use a mobile RSS app (Reeder, NetNewsWire, FeedMe) and want a self-hosted back-end — the Fever/Google Reader API compatibility is the right answer here [README][docs].
• You want a stable, low-maintenance service. Go binaries don’t break on apt upgrade, and the single-dependency architecture means fewer moving parts.

Skip it (use a commercial reader) if:

• You need push notifications on mobile without configuring Ntfy or Telegram yourself.
• You want AI-generated summaries or article recommendations — Feedly and Inoreader offer these, Miniflux doesn’t and won’t.
• You’re not comfortable with the command line and don’t have a technical person to do a one-time setup.

Skip it (use FreshRSS instead) if:

• You need a proper multi-user instance with user management and per-account permissions. FreshRSS is more mature for shared deployments.
• You want a larger plug-in ecosystem or a more featureful UI while staying self-hosted. FreshRSS is more configurable; Miniflux is more opinionated.

Skip it (use Tiny Tiny RSS instead) if:

• You were previously on TTRSS and liked its extensibility through plugins — Miniflux has no plugin system [3].

---

Alternatives worth considering

• FreshRSS — PHP-based, more features, proper multi-user support, larger plug-in ecosystem. More complex to maintain. The pragmatic choice if Miniflux feels too stripped down.
• Tiny Tiny RSS (TTRSS) — long-running project, extensible via plugins, self-hosted. Jamie Phillips used it before switching to Miniflux [3]. Heavier than Miniflux, PHP/PostgreSQL stack.
• Feedly — the most polished commercial alternative. Pro tier at ~$8/month gets you AI features and better organization. Appropriate if you want zero maintenance and don’t mind the bill.
• Inoreader — slightly cheaper than Feedly, more power-user-focused with better filtering on paid tiers. Still closed-source SaaS.
• Feedbin — clean, fast, developer-friendly hosted reader. ~$5/month. Not open source, but respected in the indie web community.
• NewsBlur — open source and self-hostable, but the hosted tier is the primary use case. More social features than Miniflux.
• Readwise Reader — not an RSS reader in the traditional sense, but if you want a combined read-later + RSS + newsletter inbox with AI summaries, it competes for the same attention. Significantly more expensive.

---

Bottom line

Miniflux is what happens when someone builds exactly the tool they want and has the discipline to not add anything else. It reads RSS feeds. It does it fast, privately, and reliably, on hardware you control, with no SaaS subscription and no algorithm deciding what you see. The Apache 2.0 license means you can run it, modify it, or embed it in a commercial product without permission or fees.

The trade-offs are real: no fancy mobile apps, no AI features, regex-only filtering, and a solo maintainer. But for the target use case — replacing a commercial RSS reader bill, escaping algorithmic news feeds, or building a privacy-respecting information diet — Miniflux is hard to beat. The total setup time is an afternoon, the ongoing maintenance is close to zero, and the marginal VPS cost for someone already self-hosting anything else is effectively nothing.

If the setup is the blocker, that’s exactly what unsubbed.co’s parent studio upready.dev handles for clients. One-time deployment, you own the stack.

---

Sources

1. Samir Makwana, XDA Developers — “This self-hosted RSS reader finally got me off social media for news” (Dec 28, 2025). https://www.xda-developers.com/this-self-hosted-rss-reader-finally-got-me-off-social-media-for-news/
2. Feng, ofeng.org — “RSS reader in golang — Miniflux review” (Sep 15, 2023). https://ofeng.org/posts/best-self-host-rss-reader/
3. Jamie Phillips, phillipsj.net — “Self-Hosted RSS Using Miniflux” (Dec 27, 2020). https://www.phillipsj.net/posts/self-hosted-rss-using-miniflux/

Primary sources:

• GitHub repository and README: https://github.com/miniflux/v2 (8,933 stars, Apache-2.0 license)
• Official website: https://miniflux.app
• Documentation: https://miniflux.app/docs/index.html
• Hosting page: https://miniflux.app/hosting.html