A self-hosted feed aggregator daemon with a pluggable filter and output system for processing and distributing RSS/Atom articles.
Feedpushr is a self-hosted feed aggregator daemon that collects articles from RSS/Atom feeds, processes them through a customizable filter chain, and pushes them to various outputs like HTTP endpoints, email, or external services. It solves the problem of automating content distribution and curation by providing a flexible, extensible pipeline that users control entirely on their own infrastructure.
Developers, sysadmins, or content curators who need to automate the aggregation and distribution of feed content, especially those preferring self-hosted solutions with custom processing rules.
Developers choose Feedpushr for its simplicity as a single binary, its extensibility via plugins and expressions, and its full self-hosting capability, giving them complete control over their feed processing workflow without relying on third-party services.
A simple feed aggregator daemon with sugar on top.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Deploys as a standalone executable with an embedded database, eliminating complex dependencies, as shown in the installation options using Docker or direct download.
Supports custom filters and outputs via compiled Go plugins, allowing tailored workflows, with examples like Twitter integration available in the contrib directory.
Offers a REST API with OpenAPI documentation, a web UI, and a CLI, providing multiple ways to manage feeds and outputs, as detailed in the features section.
Uses a custom expression language to route articles based on tags, title, or metadata, enabling precise automation, documented in the EXPRESSION.md file.
Creating custom outputs or filters requires Go programming and compiling plugins, which can be a barrier for non-developers, as admitted in the plugins section.
Core outputs are basic (e.g., stdout, HTTP, email), and advanced services like Twitter depend on external plugins that may lack maintenance or documentation.
Setting up involves multiple environment variables, authentication files, and expression syntax, leading to a steeper initial setup compared to simpler aggregators.