Application hosting

Hosting FreshRSS

A self-hosted feed reader that gathers updates from RSS sources. A container deployment can use SQLite or an external database.

Min vCPU
Not specified
Min memory
Not specified
Min storage
Not specified

Understand the setup

Check runtime, storage and installation requirements before choosing a server.

See requirements

Budget your resources

Allow room for the operating system, database and your actual workload.

Open resource planner

Build your shortlist

Compare plan details and review which requirements still need checking.

Explore plans

Must have

Installation requirements

  • A container image compatible with the host CPU architecture.
  • Persistent application data and a configured database.

Recommended

Planning guidance

No further general recommendations are published for this version.

Capacity depends on your workload

The installation documentation does not define a universal hardware minimum. Feed count, refresh frequency and retained articles affect resource use.

We only compare what providers publish. A RAM figure alone can't confirm compatibility or production capacity.

Deploy with

Supported paths

  • Docker container
  • Docker Compose

The host must provide

Runtime

SQLite
Built-in option
PostgreSQL or MySQL/MariaDB
Optional external database

Storage

Persistent data

Keep application data and any external database persistent. Back up configuration and feed data before replacing the container.

Step by step

Plan a FreshRSS deployment

  1. Choose a release

    Use a versioned release for controlled upgrades rather than the rolling edge image.

    Official instructions
  2. Configure refresh

    Set the refresh schedule and verify database connectivity and persistent mounts.

    Official instructions

Security

Before you go public

  • Replace database example passwords.
  • Keep internal-host access restrictions unless a specific trusted feed requires an exception.

Cost

Beyond the server price

  • Budget for retained articles, database storage and backups.

Matching plans

Explore hosting options

Vultr

Vultr Optimized Cloud Compute (CPU Optimized) · 4 vCPU / 8 GB

4 vCPU
8 GB RAM
75 GB Storage
6 TB Transfer
  • Dedicated vCPU (AMD EPYC)
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

  • A container image compatible with the host CPU architecture.This prerequisite has no comparable published plan field.
  • Persistent application data and a configured database.This prerequisite has no comparable published plan field.
Vultr

Vultr Optimized Cloud Compute (CPU Optimized) · 8 vCPU / 16 GB

8 vCPU
16 GB RAM
150 GB Storage
7 TB Transfer
  • Dedicated vCPU (AMD EPYC)
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

  • A container image compatible with the host CPU architecture.This prerequisite has no comparable published plan field.
  • Persistent application data and a configured database.This prerequisite has no comparable published plan field.
Vultr

Vultr Optimized Cloud Compute (General Purpose) · 1 vCPU / 4 GB

1 vCPU
4 GB RAM
30 GB Storage
4 TB Transfer
  • Dedicated vCPU (AMD EPYC)
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

  • A container image compatible with the host CPU architecture.This prerequisite has no comparable published plan field.
  • Persistent application data and a configured database.This prerequisite has no comparable published plan field.
Vultr

Vultr Optimized Cloud Compute (General Purpose) · 16 vCPU / 64 GB

16 vCPU
64 GB RAM
320 GB Storage
8 TB Transfer
  • Dedicated vCPU (AMD EPYC)
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

  • A container image compatible with the host CPU architecture.This prerequisite has no comparable published plan field.
  • Persistent application data and a configured database.This prerequisite has no comparable published plan field.
Vultr

Vultr Optimized Cloud Compute (General Purpose) · 2 vCPU / 8 GB

2 vCPU
8 GB RAM
50 GB Storage
5 TB Transfer
  • Dedicated vCPU (AMD EPYC)
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

  • A container image compatible with the host CPU architecture.This prerequisite has no comparable published plan field.
  • Persistent application data and a configured database.This prerequisite has no comparable published plan field.
Vultr

Vultr Optimized Cloud Compute (General Purpose) · 4 vCPU / 16 GB

4 vCPU
16 GB RAM
80 GB Storage
6 TB Transfer
  • Dedicated vCPU (AMD EPYC)
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

  • A container image compatible with the host CPU architecture.This prerequisite has no comparable published plan field.
  • Persistent application data and a configured database.This prerequisite has no comparable published plan field.
Vultr

Vultr Optimized Cloud Compute (General Purpose) · 8 vCPU / 32 GB

8 vCPU
32 GB RAM
160 GB Storage
7 TB Transfer
  • Dedicated vCPU (AMD EPYC)
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

  • A container image compatible with the host CPU architecture.This prerequisite has no comparable published plan field.
  • Persistent application data and a configured database.This prerequisite has no comparable published plan field.
WP Engine

Essential — 1 site

1 Websites
10 GB Storage
25,000 visits/month Visits
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

  • A container image compatible with the host CPU architecture.This prerequisite has no comparable published plan field.
  • Persistent application data and a configured database.This prerequisite has no comparable published plan field.

Want the full monthly bill? Use the hosting cost calculator. It keeps unknown charges visible.