FreshRSS on Google Cloud Run

FreshRSS is a free, self-hosted, GPL-3.0-licensed RSS and Atom feed aggregator — a lightweight, multi-user "news reader" written in PHP that runs behind Apache and exposes the Google Reader and Fever APIs for mobile clients. This module deploys FreshRSS on Cloud Run v2 on top of the App_CloudRun foundation, which provisions and manages the shared Google Cloud infrastructure.

This guide focuses on the cloud services FreshRSS uses and how to explore and operate them from the Google Cloud Console and the command line. For the mechanics common to every Cloud Run application — service identity, ingress and load balancing, scaling and concurrency, CI/CD, Cloud Armor, IAP, Binary Authorization, VPC Service Controls, backups, and the deployment lifecycle — refer to the App_CloudRun foundation guide rather than repeating them here.

What FreshRSS costs on RAD, and how that compares

Running FreshRSS in your own Google Cloud project costs about US$90.17/month in Google Cloud charges, on top of a one-time 75-credit RAD module fee (67.5 credits — 10% lower — in a RAD-managed project). FreshRSS is a free, open-source, self-hosted RSS and Atom feed aggregator. If you deploy into a RAD-managed project, you can pause the whole thing for free and pick it back up later — see "Pause it for free" below.

FreshRSS is also available on GKE — see the GKE guide if you need Kubernetes-based orchestration; this guide covers the lower-cost Cloud Run option.

What you pay on RAD

	Own project	RAD-managed project
Module fee	75 credits (one-time)	67.5 credits (one-time, 10% lower)
Build time	~3–6 credits (one-time, per build)	~3–6 credits (one-time, per build)
Google Cloud running cost	~US$90.17/month, billed to your own Google billing account at list price	~41 credits/day (~US$4.10/day), metered hourly at list price plus RAD's margin

Default running cost in your own project

Resource	US$/month (Google list price, us-central1)
Cloud Run, 1x vCPU / 2 GiB (warm)	US$19.72
Cloud SQL for PostgreSQL, 1 vCPU / 3.75 GB, zonal, 10 GB SSD	US$51.02
NFS/cache file server (small VM)	US$13.43
Cloud NAT and networking	US$5
Cloud Storage (add-ons, backups)	US$1
Total	US$90.17

How it compares

There is no officially hosted/cloud version of FreshRSS to compare against, so the honest comparison is against self-managed infrastructure, not a competing SaaS.
A bare VPS sized to roughly 1 vCPU / 2 GiB — a Hetzner CPX22 (2 vCPU/4GB, ~US$24/mo), a DigitalOcean 2 vCPU/4GB Droplet (US$24/mo), or GCP's own Compute Engine e2-standard-2 (2 vCPU/8GB, ~US$49/mo) — usually undercuts RAD's sticker price; a VPS a size or two smaller would undercut it further.
What that lower price does not include is the admin's own time: patching the OS, rotating database backups, renewing TLS certificates and watching for downtime. RAD's managed Cloud SQL, Secret Manager and monitoring do that for you, which is the actual trade being made, not the sticker price.
RAD is not claiming to be cheaper than a bare VPS in cash terms — it usually is not. The case for RAD is what's managed for you.

Pause it for free: delete a RAD-managed project, restore it when you need it

If FreshRSS is running in a RAD-managed project, you can stop paying for it entirely without destroying it. Deleting that project first unlinks its billing, then asks Google to delete the project outright — Google's own 30-day recoverable soft delete. Unlike deleting the FreshRSS module on its own, this does not tear down Cloud SQL, any VM or the compute resource one by one: the whole project simply stops, and nothing is charged while it waits, because billing is already unlinked.

Restoring, within 30 days and only by the project's owner, asks Google to undelete the project and reattaches its billing account, then asks you to run Update on each deployment to confirm everything came back. Because nothing was individually destroyed, that Update finds the same resources already there — it is a check, not a rebuild, and an Update never charges the module fee again. This costs only a handful of build-time credits in total — roughly 5–10 credits, under US$1, for a typical 2–3-deployment chain. The 67.5-credit module fee is not charged again.

What this needs: you must own the project (not one RAD only manages billing for), you must restore it yourself within 30 days — after that Google deletes it for good — and restoring is admitted like creating a new project, so your purchased credit balance must still clear the tier's floor (100 credits for the sandbox tier most study/demo use fits). Google says most services are fully working again within 36 hours of a restore.

One real gap: nightly backups are written to a bucket inside the project, and that bucket has Cloud Storage's soft-delete explicitly turned off, so it is very likely gone as soon as you delete the project — even though the project itself is recoverable for 30 days. If you have customised FreshRSS and want to keep that work, copy a backup out (to Google Drive, or a bucket outside the project) before deleting. For a default install with nothing irreplaceable in it, this does not matter.

Pay only while you use it, the other way: delete and redeploy

If FreshRSS is in your own project (or more than 30 days have passed on a RAD-managed one), the way to stop paying is to delete the deployment and redeploy later when you need it again.

A redeploy costs the module fee again, plus the builds: roughly 75 + ~3–6 credits (~US$7.95) in your own project, or 67.5 + ~3–6 credits on a RAD-managed one.

Deleting only saves money once FreshRSS would otherwise sit unused long enough to clear that redeploy cost against its own running cost: roughly about 3 days or more idle in your own project (against its ~US$90.17/month Google Cloud bill), or about 2 days or more idle in a RAD-managed project (against its ~41 credits/day).

Most of FreshRSS's running cost is the database and the shared file/cache VM. They stop only when nothing else in the project uses them, so deleting this app while something else shares the project saves only this app's own compute share of the total above.

Keep data first: nightly backups go to a bucket inside the deployment and are deleted with it, so copy the latest backup out before deleting if you want to keep it.

Lab sessions and Managed Environments

Lab sessions, for training: a trainer runs a session for a class. Each participant gets the app in their own Google Cloud project for 15 minutes to 24 hours, within an allowance the trainer sets. Either the trainer funds every place, or each participant pays for their own. Everything is deleted when the session ends and unused credits go back to the trainer.
Managed Environments, for consultancies: a partner runs the app for a client from a ring-fenced wallet it funds, and settles with the client directly. If the wallet runs low, billing pauses and the data is kept, so nobody receives an unexpected charge. At the end the partner hands the project over and the deployments become the client's own.
Credits can be bought in more than 20 currencies, including XAF, XOF, NGN, GHS, KES and ZAR, by card, bank transfer or mobile money.

Sources (8 October 2026): Google Cloud Billing Catalog API list prices; radmodules.dev/pricing for RAD's own fees and daily-credit estimates; Google's project delete/restore docs for the pause/restore mechanics.

1. Overview

FreshRSS runs as a PHP/Apache container on Cloud Run v2. The deployment wires together a focused set of Google Cloud services:

Capability	Google Cloud service	Notes
Compute	Cloud Run v2	PHP/Apache service on port 80, 1 vCPU / 2 GiB by default, one instance kept warm (`min_instance_count = 1`)
Database	Cloud SQL for PostgreSQL 15	Required — the entrypoint installs with `--db-type pgsql`
Persistent storage	NFS (Filestore / self-managed)	Mounted at `/var/www/FreshRSS/data`; holds config, per-user state, feed cache. No GCS bucket
Cache	Redis (optional)	Off by default; FreshRSS does not require it
Secrets	Secret Manager	Auto-generated `FRESHRSS_ADMIN_PASSWORD`; database password
Ingress	Cloud Run URL / Cloud Load Balancing	Default `run.app` URL; optional external HTTPS load balancer + custom domain

Sensible defaults worth knowing up front:

PostgreSQL 15 is the supported engine. The container entrypoint hardcodes --db-type pgsql and the db-init job is Postgres-only; the schema is created by FreshRSS's own installer on first boot.
NFS is enabled by default (enable_nfs = true) and mounted at /var/www/FreshRSS/data. FreshRSS writes its generated config (data/config.php), per-user state, cached articles, and favicons there — without a persistent volume this state is lost on every cold start or redeploy.
FRESHRSS_ADMIN_PASSWORD is generated automatically and stored in Secret Manager. It seeds the default admin account (and its API password for mobile clients) on first install.
One instance is kept warm by default (min_instance_count = 1, max_instance_count = 1). It must stay at least 1: feed refresh runs as an in-container cron (CRON_MIN = */15) that exists only while an instance does — see the pitfalls table.
max_instance_count = 1. A single instance owns the in-container refresh cron and the file-based session/cache state; running more than one without care duplicates feed refreshes.
The container listens on port 80 (Apache), not 8080.
BASE_URL is set from the predicted service URL at plan time and corrected at runtime from CLOUDRUN_SERVICE_URL, so FreshRSS's self-referencing links and the / → setup redirect resolve on the real Cloud Run host.

2. Google Cloud Services & How to Explore Them

All commands assume PROJECT and REGION are set. Service and resource names are reported in the deployment Outputs.

A. Cloud Run — the FreshRSS service

FreshRSS runs as a Cloud Run v2 service that autoscales by request load between the minimum and maximum instance counts. Each deployment creates an immutable revision; traffic can be split across revisions for safe rollouts.

Console: Cloud Run → select the service for revisions, traffic, logs, and metrics.

CLI:

gcloud run services list --project "$PROJECT" --region "$REGION" \
  --filter="metadata.name~freshrss"
gcloud run services describe <service-name> --project "$PROJECT" --region "$REGION"
gcloud run revisions list --service <service-name> --project "$PROJECT" --region "$REGION"

See App_CloudRun for scaling, concurrency, execution environment, and traffic splitting.

B. Cloud SQL for PostgreSQL 15

FreshRSS stores all application data (feeds, subscriptions, articles, categories, users) in a managed Cloud SQL for PostgreSQL 15 instance. The service connects privately through the Cloud SQL Auth Proxy over a Unix socket; no public IP is exposed. On first deploy the db-init Job creates the application database and user, and FreshRSS's own installer creates the schema.

Console: SQL → select the instance for connections, backups, flags, metrics.

CLI:

gcloud sql instances list --project "$PROJECT"
gcloud sql instances describe <instance-name> --project "$PROJECT"
gcloud sql connect <instance-name> --user=<db-user> --database=<db-name> --project "$PROJECT"

The instance name, database, user, and password secret are in the Outputs. See App_CloudRun for the connection model, backups, and password rotation.

C. Persistent storage (NFS)

FreshRSS's data directory (/var/www/FreshRSS/data) is backed by an NFS volume (enable_nfs = true), which holds the generated config, per-user state, cached articles, and favicons. This module declares no GCS bucket — feed content is kept in PostgreSQL and the NFS data dir.

Console: Filestore → Instances (managed NFS), or Compute Engine → VM instances (self-managed NFS server).

CLI:

gcloud filestore instances list --project "$PROJECT"
# Confirm the mount inside the running revision:
gcloud run services describe <service-name> --region "$REGION" \
  --format='value(spec.template.spec.volumes)'

See App_CloudRun for the NFS server model and GCS Fuse options.

D. Redis (optional cache)

Redis is disabled by default (enable_redis = false) and FreshRSS does not require it. It is exposed as a forwarded option for parity with sibling PHP modules; leave it off unless you have a specific reason to enable it.

Console: Memorystore → Redis (if using a managed instance).
CLI:
```
redis-cli -h <redis-host> ping
```

E. Secret Manager

One application secret is generated automatically: FRESHRSS_ADMIN_PASSWORD, which seeds the default admin account and its API password on first install. The database password is managed separately by the foundation.

Console: Security → Secret Manager.

CLI:

gcloud secrets list --project "$PROJECT" --filter="name~freshrss"
gcloud secrets versions access latest --secret=<secret-name> --project "$PROJECT"

See App_CloudRun for injection and rotation details.

F. Networking & ingress

The service is reachable at its run.app URL by default (public ingress). An external HTTPS load balancer with a custom domain, Cloud CDN, and Cloud Armor can be layered on; ingress settings and VPC egress control connectivity.

Console: Cloud Run (service URL); Network services → Load balancing.

CLI:

gcloud run services describe <service-name> --region "$REGION" --format='value(status.url)'
gcloud compute addresses list --project "$PROJECT"

See App_CloudRun.

G. Cloud Logging & Monitoring

Container logs flow to Cloud Logging; Cloud Run and Cloud SQL metrics flow to Cloud Monitoring, with optional uptime checks and alert policies.

Console: Logging → Logs Explorer; Monitoring → Dashboards / Alerting.

CLI:

gcloud run services logs read <service-name> --project "$PROJECT" --region "$REGION" --limit 50

3. FreshRSS Application Behaviour

First-deploy database setup. The db-init Job runs using postgres:15-alpine. It connects through the Cloud SQL Auth Proxy and idempotently creates the application database and user and grants privileges. The job is safe to re-run.
First-boot install. The container's platform-entrypoint.sh resolves the DB host, then drives FreshRSS's own cli/do-install.php (creates data/config.php and the schema) and cli/create-user.php (creates the admin account from FRESHRSS_ADMIN_PASSWORD), then chains the upstream entrypoint. The install is idempotent — it is skipped once data/config.php exists on the NFS volume.
Feed refresh cron. The upstream image starts an in-container cron (CRON_MIN = */15) that actualizes subscribed feeds every 15 minutes. This runs only while an instance is alive — which is why min_instance_count defaults to 1. At 0, Cloud Run reaps the idle instance and refreshes stop until the next request wakes the service.
Admin credential. The default login is admin with the generated FRESHRSS_ADMIN_PASSWORD; the same value is set as the API password used by Google Reader / Fever API mobile clients. Change it in the FreshRSS UI after first login — rotating the Secret Manager value alone will not re-set an already-installed account.
Health path. The startup probe is a TCP check on port 80; the liveness probe is an HTTP GET on /i/, which returns a literal 200 and renders from the database (/ answers with a 302 redirect, which a load-balancer health check rejects). FreshRSS also serves an unauthenticated /status JSON endpoint suitable for uptime checks. Allow a generous first-boot window while the installer creates the schema.
Base URL. BASE_URL is set to the predicted Cloud Run URL at plan time and corrected at runtime from CLOUDRUN_SERVICE_URL. Verify the running revision:
```
gcloud run services describe <service-name> --region "$REGION" --format='value(status.url)'
```

Inspect job execution:

gcloud run jobs list --project "$PROJECT" --region "$REGION"
gcloud run jobs executions list --job <job-name> --project "$PROJECT" --region "$REGION"

4. Configuration Variables

Variables are grouped exactly as they appear on the deployment platform. Only settings specific to or notable for FreshRSS are listed; every other input is inherited from App_CloudRun with its standard behaviour.