Miniflux
A minimalist, blazing-fast RSS reader - one Go binary on managed Postgres, your feeds on your own box.
One-click deploy, from $13/mo on a Miget plan.
Miniflux is the RSS reader for people who just want to read: a clean, keyboard-driven, distraction-free UI with no recommendations, no tracking, and no upsell. It is a single statically-linked Go binary, so it boots instantly and idles in about 50 MB.
Everything lives in Postgres - feeds, entries, read state, API keys - which makes this template one of the catalogue’s cleanest deploys: the app container is disposable, and the managed Postgres is the only thing holding state.
It speaks the Google Reader and Fever APIs, so the mobile clients you already like (Reeder, NetNewsWire, FeedMe) connect straight to your instance. Full-text fetching, feed rules, and integrations (Wallabag, Pocket, webhooks) come built in.
Upstream project: Miniflux
#what you get
- Single Go binary - starts instantly, idles around 50 MB
- Google Reader and Fever API compatibility for mobile clients
- Full-text article fetching, keyboard shortcuts, dark theme
- Feed filters, rules, and integrations (Wallabag, webhooks, more)
- All state in managed Postgres - the app is stateless
- Apache-2.0, no telemetry, no feed-count limits
#topology
| Service | Role | Public |
|---|---|---|
| miniflux | reader + API (stateless, :5000) | yes |
| db | managed Postgres (feeds + read state) | no |
#miget sizing
// this stack needs
1.1 GiB RAM · 5 GB disk · 2 services
The binary barely registers; the Hobby plan is plenty. Postgres holds everything, so size disk to how many feeds and how much history you keep.
Hobby - recommended fit
$13/mo
1 vCPU · 2 GiB · 50 GiB disk
Headroom for your own apps: 2 GiB at $19/mo
Professional - production
$22/mo
1 vCPU · 2 GiB · 10 GiB disk
Dedicated resources, production SLOs - plan details
One Miget plan is a fixed pool of compute - the whole stack (managed databases included) deploys inside it, and anything left over runs your other apps. No per-service or per-seat math.
#vs. the managed service
What the hosted equivalents charge, against the flat Miget plan this stack fits on. Prices as of June 2026, sources linked.
| Service | Plan | Monthly | What you get |
|---|---|---|---|
| Miniflux on Miget ★ | 2 GiB plan | $13 | this whole stack, flat - no usage meters, and room left for your own apps |
| Feedly | Pro | ~$7 | $7/mo; higher tiers cap sources |
| Inoreader | Pro | ~$8 | ~$7-9/mo |
Same money as a hosted reader, with no source caps and your history in a Postgres you control.
#vs. other PaaS
Estimated monthly cost of running this exact stack (1.1 GiB RAM, 5 GB disk, 2 containers) elsewhere, from published June 2026 rates.
| Platform | Est. monthly | Notes |
|---|---|---|
| Miget ★ | $13 flat | compose stacks first-class: one deploy, dedicated vCPU, managed Postgres/Valkey, volumes and TLS all included in the plan |
| Heroku | ~$56 | no volumes; nothing between 1 GB ($50) and 2.5 GB ($250) dynos - 2 GB containers cost far more than shown |
| DO App Platform | ~$19 | no persistent volumes - stateful containers need managed DBs/Spaces (base $5 Spaces included here) |
| Render | ~$15 | per-service instances (0.5 GB $7, 2 GB $25) - every container is its own paid service |
| Railway | ~$12 | usage-based ($10/GB RAM-mo); vCPU billed separately at $20/vCPU-mo on top |
| Fly.io | ~$7 | cheapest sticker price - but burstable shared CPUs (1/16 core; dedicated vCPUs cost ~2-3×), no compose deploys (one app per container, manual wiring), managed DBs billed extra |
Estimates assume RAM fully allocated at published on-demand rates - and sticker price isn't the whole comparison: the cheaper rows buy burstable shared CPUs, per-service wiring instead of a compose deploy, and managed databases billed separately. Heroku and DO App Platform have no persistent volumes at all - stateful stacks like this one need workarounds there.
#deploy it
On Miget
- Create a Compose Stack in app.miget.com pointing at the templates repository
- Set the stack path to
miniflux -
Set the required variables:
ADMIN_USERNAME / ADMIN_PASSWORD, first admin, created on first bootBASE_URL, the app’s https domain, set after first deploy
- Deploy. Miget layers
compose.miget.yaml(RAM, privacy, volumes, managed services) automatically
Locally first?
Every template is portable, vanilla Docker Compose - the Miget overrides are ignored locally:
git clone https://github.com/deployable-sh/stacks
cd miget-compose-templates/miniflux
docker compose up -dSame files, same behavior. The template README covers connection strings and scaling notes.
#faq
What does this save vs Feedly or Inoreader?
Feedly Pro is $7/month and Inoreader Pro is roughly $7-9, both capping sources and feeds at higher tiers. Miniflux self-hosted is $7/month flat with no source limit, no ads, and your reading history in a Postgres you control.
Can I keep using my phone’s RSS app?
Yes. Miniflux exposes both the Google Reader and Fever APIs, so clients like Reeder, NetNewsWire, and FeedMe sync against your instance the same way they would against a hosted service.
Is it really just one container plus a database?
Yes. There is no Redis, no worker, no queue - one Go binary and Postgres. Migrations run on start, so deploys and rollbacks are trivial.
Ship Miniflux today
One compose stack, 1.1 GiB of RAM, from $13/month flat, and it runs on your laptop with the same files.