Must have
Installation requirements
- A container image compatible with the host CPU architecture.
- Persistent application data and a configured database.
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 requirementsBudget your resources
Allow room for the operating system, database and your actual workload.
Open resource plannerBuild your shortlist
Compare plan details and review which requirements still need checking.
Explore plansRecommended
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
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
-
Choose a release
Use a versioned release for controlled upgrades rather than the rolling edge image.
Official instructions -
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
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.
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.
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 High Performance (AMD) · 12 vCPU / 24 GB
12
vCPU
24 GB
RAM
500 GB
Storage
12 TB
Transfer
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.
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.
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.
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.
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.
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) · 1 vCPU / 2 GB
1
vCPU
2 GB
RAM
25 GB
Storage
4 TB
Transfer
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) · 16 vCPU / 32 GB
16
vCPU
32 GB
RAM
300 GB
Storage
8 TB
Transfer
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) · 2 vCPU / 4 GB
2
vCPU
4 GB
RAM
50 GB
Storage
5 TB
Transfer
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.