Fusion Hosting

How Fusion works

Fusion subscribes to RSS and Atom feeds, retrieves new entries, groups sources, tracks unread state, stores bookmarks, and provides search through a responsive web interface. Feed auto-discovery can help locate a site’s published subscription address, while keyboard shortcuts support a fast reading workflow. The progressive web app can be installed by compatible browsers without a separate native application package.

The catalogue sets one generated password and persists /data. Fusion also offers Fever API compatibility for selected third-party readers and optional OIDC configuration upstream, but the standard package does not provide OIDC credentials or configure a Fever username. Feed availability, article content, update frequency, and enclosure access remain dependent on publishers and remote servers.

Key Fusion features

A single password protects the standard hosted reader. This is not a multi-tenant account system with separate private libraries for unrelated users. Fever-compatible clients require their own configuration and may support only the subset of behaviour exposed through that API. The hosted package includes the server, not paid mobile clients, provider accounts, or publisher subscriptions.

RSS feeds can move, disappear, publish malformed XML, omit full article text, or block frequent retrieval. Fusion cannot expand a summary into the full article unless the feed or linked source makes that content available through supported behaviour. Users should export or otherwise retain important subscription lists before large reorganisations.

Fusion vs Feedly

Fusion is a compact self-hosted RSS reader centred on unread state, bookmarks, search, groups, shortcuts, PWA access, and Fever API compatibility. Feedly is a managed cloud news reader with source discovery, web and mobile access, cross-device synchronisation, boards, team workflows, and higher-tier research or intelligence capabilities. Both aggregate feeds but target different service expectations.

Feedly may suit readers or organisations that want provider-maintained clients, discovery, collaboration, and managed synchronisation. Fusion is appealing when a focused personal reader and local control matter more. It does not include Feedly’s commercial discovery ecosystem, native app account, enterprise administration, or intelligence features.

Who uses Fusion

Individuals follow blogs and publications without relying on social timelines, researchers group sources by project, and technical readers keep release feeds or industry news in one queue. Bookmarks and search help preserve useful entries after the unread count is cleared, while keyboard navigation supports rapid review of a large daily list.

Fusion is not a content-licensing service, paywall bypass, permanent web archive, or guarantee that every feed contains complete articles. A feed reader reflects what publishers distribute. Users should respect subscription terms, keep account credentials private, and retain a separate OPML or source list for recovery and migration.

Self-hosting Fusion: requirements and cost

Fusion resource use grows with feed count, refresh activity, article retention, search index size, bookmarks, enclosures, simultaneous readers, and unreliable sources that time out or retry. PostgreSQL and MariaDB are Not required in the catalogue template; Fusion uses its own data directory. Text feeds are light, while many high-frequency sources or media enclosures create more network and storage activity.

On AvaHost, Fusion uses Plan 1 at €2. The hosted Fusion package includes one-click deployment, a custom domain with automated HTTPS, automatic application updates, and scheduled backups. The standard package provides one generated password. OIDC, Fever-client credentials, native reader apps, publisher accounts, paid subscriptions, content rights, and complete full-text retrieval are not included. Keep an independent subscription export and test important feeds after publishers or the application change.