RSS-proxy vs osmos::feed
A side-by-side comparison of two self-hosted rss & news readers options — licensing, setup difficulty, resource needs, and what each one replaces.
| Feature | RSS-proxy | osmos::feed |
|---|---|---|
| Deploy effort | Under-an-hour setup | Read-the-docs project |
| Health score | 20 · At risk | 14 · At risk |
| Category | RSS & News Readers | RSS & News Readers |
| License | MIT | MIT |
| Language | TypeScript | TypeScript |
| Setup difficulty | Medium | Easy |
| Min. RAM | 256 MB | 32 MB |
| Deployment | docker | source |
| GitHub stars | ★ 1,923 | ★ 989 |
| First released | 2019 | 2021 |
| Replaces | Feedly | Feedly |
What are RSS-proxy and osmos::feed?
RSS-proxy
RSS-proxy is an open-source tool that generates RSS, Atom, or JSON feeds from websites that do not offer them, by analyzing page markup to detect article lists. It runs as a self-hosted service via Docker; its successor project is feedless.
- Creates feeds from any page
- JSON and Atom output
- Self-hosted aggregation
osmos::feed
osmos::feed is a tool that turns a list of feeds into a self-hosted static RSS reader website using GitHub Actions. It requires no server and rebuilds the reader on a schedule.
- Static site RSS reader
- Runs on GitHub Actions
- No server required
RSS-proxy vs osmos::feed: key differences
Both projects are written in TypeScript. Osmos::feed is the lighter option, starting around 32 MB of RAM against 256 MB for RSS-proxy. RSS-proxy is the more established project (first released 2019), while osmos::feed arrived in 2021. RSS-proxy lists first-class Docker deployment; osmos::feed does not.
Why pick each one
Choose RSS-proxy if…
- Released under the MIT license
- First-class Docker support for quick deployment
- Active community (1.9k GitHub stars)
- Written in TypeScript
Choose osmos::feed if…
- Released under the MIT license
- Easy to set up — beginner-friendly
- Written in TypeScript
- Tiny footprint — runs in 32 MB RAM
Frequently asked questions
Is RSS-proxy or osmos::feed better?
Neither is universally better. RSS-proxy has the larger community, while osmos::feed is simpler to set up (easy difficulty). Choose based on the comparison table above and your own setup.
Are RSS-proxy and osmos::feed free and open-source?
Yes. RSS-proxy is licensed under MIT and osmos::feed under MIT. Both can be self-hosted at no software cost.
Can I run RSS-proxy and osmos::feed with Docker?
RSS-proxy: yes. osmos::feed: check the project docs for container support.
Which is lighter on resources, RSS-proxy or osmos::feed?
osmos::feed has the smaller minimum footprint at 32 MB of RAM, compared to about 256 MB for RSS-proxy. Real-world usage depends on library size, user count, and enabled features.