RSS-Bridge Hosting

1. Open your pod using any access protection configured for it. RSS-Bridge itself has no user-registration wizard to complete.
2. Find an available bridge, fill in its source-specific fields and preview the result. Choose an Atom or other reader-compatible output and copy that feed URL into your feed reader.
3. If the bridge you need is not enabled, PikaPods instructs you to edit config/whitelist.txt over SFTP to allow additional bridges. Follow the bridge names and configuration guidance, then restart the pod after changing its configuration.

The bridge-access guide also documents the newer enabled_bridges configuration and the legacy whitelist file used in PikaPods' instructions. Enabling a bridge does not guarantee the source website permits access.

No. PikaPods sets up and runs RSS-Bridge for you, including OS and app updates and HTTPS. You won't touch Docker or a server. Your files and database stay accessible if you ever want to move them elsewhere.

The generated Atom or Media RSS feed can be subscribed to from a compatible web, phone or desktop feed reader. Use the generated feed URL, not just your pod's home page. No dedicated RSS-Bridge mobile app is needed; reader apps and services may have their own subscriptions.

A bridge whitelist controls which bridges can run, not who may access the pod. Upstream supports HTTP Basic and URL-token authentication in its configuration. If access protection is enabled, your reader must support it on every feed request. Keep access tokens and private feed URLs secret; simply subscribing to a feed does not make an otherwise public instance private.

There is no required RSS-Bridge cloud account. Some individual bridges require a source-service account, API key or other configuration, and those providers can impose charges and limits. A hosted pod also does not automatically supply separate services that a particular bridge may depend on.

Websites can block server requests, change their pages or require login, causing a bridge to stop working. There is no guarantee for every site or social network. Feeds are refreshed when requested after their cache expires, rather than continuously collected in the background; see the caching FAQ.

Set up incremental backups to S3 in your pod settings for automatic nightly snapshots, or download your files and database yourself. We keep whole-server backups for server failures, but they aren't a per-pod restore service, so your own backup is what protects your data.

You can use RSS-Bridge instead of RSS.app. PikaPods runs it for you, and you can move your files and database elsewhere.

RSS.app is a hosted service that creates feeds for you, with plans and a dashboard. RSS-Bridge uses community-maintained bridges, which you enable in a whitelist over SFTP. When a site changes, a bridge may stop working until it's updated, so it takes more upkeep. In return, you keep control of the instance and your feeds.

No. You add prepaid credit and your pods are billed by the hour from that balance, rounded up to full hours. There are no contracts or minimum terms: delete a pod anytime and billing stops. Optional automatic top-ups keep your pods running without manual payments.

You do. And you're in full control. If you ever want to download, migrate, edit or delete your data, just enable file and database access for your pod and it will be right there.