Self-host FreshRSS for your private feed inbox.
FreshRSS keeps subscriptions, unread state and feed history in your own reader. VibeNest launches a prepared adapter on your subdomain with free SSL and persistent storage.
Personal feed state
Keep subscriptions, filters, unread state and saved articles in an instance that belongs to one user or admin.
VibeNest-ready adapter
The adapter uses the official FreshRSS image, port 80, persistent data/extensions volumes and feed refresh cron defaults.
Public smoke passed
The smoke deploy reached running and the public URL opened the FreshRSS installation screen, not a VibeNest fallback.
Deploy FreshRSS in one click
- 1. Launch the adapter VibeNest opens the deploy flow with the FreshRSS adapter repo and branch pre-filled.
- 2. Confirm hardware Use a free or paid server slot so the RSS reader has RAM, CPU and persistent storage.
- 3. Finish setup When deploy finishes, open FreshRSS and complete the first installation screen on your VibeNest subdomain.
A self-hosted RSS reader with your own feed history
FreshRSS collects articles from blogs, release feeds and news sources into one web reader. Subscriptions, categories, read state, favourites and filtering rules remain in your instance instead of being tied to a hosted feed account.
It suits larger or long-lived feed collections because it includes feed refresh jobs, importing and exporting, user management and an extension ecosystem. The VibeNest adapter preserves both application data and extensions while applying a sensible refresh schedule.
Complete installation once
Open the installer immediately, select the bundled database option for this lightweight recipe, create the administrator and finish setup so nobody else can claim the first account. Import an OPML file or add feeds manually, then verify scheduled refreshes and back up the persistent data volume.
Source, VibeNest recipe and live proof
Original open-source project
Review the upstream source, release notes and AGPL-3.0 license before you deploy or update the app.
Original GitHubVibeNest-ready recipe
Adapter uses the official FreshRSS image, port 80, persistent data/extensions volumes and feed refresh cron defaults. The container healthcheck was removed because the setup flow made path checks misleading; VibeNest validates the public URL instead.
Deploy repositoryPublic deployment proof
Public URL returned HTTP 302 to /i/ and then HTTP 200 with <title>Installation · FreshRSS: step 1</title>, FreshRSS cookie and Apache headers.
Open live deploymentFrequently asked questions
Is FreshRSS open source? +
Yes. FreshRSS is open-source software. VibeNest launches it through a small adapter that keeps upstream intact and adds deploy-safe defaults.
Why should I run my own FreshRSS instance? +
Feeds, subscriptions and reading state are personal. Your own instance keeps that state under your VibeNest project instead of a shared account.
Does FreshRSS fit the free tier? +
The adapter passed a VibeNest free-tier smoke deploy. Large feed lists or aggressive refresh intervals may need a paid hardware slot.
Does it need persistent storage? +
Yes. The adapter stores FreshRSS data and extensions on persistent volumes so subscriptions and read history survive redeploys.
What was fixed for VibeNest? +
The adapter uses the official FreshRSS image on port 80 and persistent volumes. A misleading container healthcheck was removed, then the public URL opened the real FreshRSS installation UI during smoke.
Deploy your private RSS reader
Start with a tested FreshRSS adapter, then keep subscriptions and reading history under your own VibeNest project.
Deploy FreshRSS