Skip to main content

Fully Managed TinyTinyRSS
as a Service

Deploy TinyTinyRSS as a fully managed service starting at €9/mo. Get automated backups, SSL, updates, support and monitoring included.

Tiny Tiny RSS is an open-source feed reader for RSS, Atom, and JSON Feed, running on PHP and PostgreSQL. After original maintainer Andrew Dolgov retired the project infrastructure on 1 November 2025, the community fork at github.com/tt-rss/tt-rss became the canonical 2026 source. We run the current community-maintained main branch.

Free 7-day trial  99.9% Uptime SLA  No credit card  Cancel anytime

Free 7-day trial  99.9% Uptime SLA
No credit card  Cancel anytime

TinyTinyRSS

TinyTinyRSS

STARTING AT

€9/month
Automated Backups
Monitoring
Automated Updates
Auto SSL

USAGE

Unlimited
Human Support
Custom Domains
Terminal Access
File Manager Access
Deploy in your region 21 locations worldwide
GermanyFinlandNetherlandsUKSwedenUnited StatesCanadaSingaporeJapanAustraliaBrazilSouth Africa+9 more →
TinyTinyRSS Preview Image

ABOUT THE SOFTWARE

What is TinyTinyRSS

Tiny Tiny RSS is an open-source web-based feed reader, originally created by Andrew Dolgov in 2005. It parses RSS, Atom, and JSON Feed sources, stores articles in PostgreSQL, and runs a separate update daemon to keep feeds fresh in the background. It is licensed under GPL-3.0-or-later.

The project is built in PHP, with a Dojo Toolkit frontend and a documented JSON API. It supports multi-user mode, fine-grained per-feed filters, full-text article extraction via the af_readability plugin, and a plugin architecture used by the community to add Fever-API compatibility, Google Reader API emulation (FreshAPI), and SSO integrations. The native Android client is published at github.com/tt-rss/tt-rss-android.

Andrew Dolgov ("fox") announced his retirement on 3 October 2025 and dismantled the original infrastructure on 1 November 2025. The project lives on under contributor supahgreg at github.com/tt-rss/tt-rss, which is the canonical source in 2026. MySQL support was removed on 28 April 2025; PostgreSQL is now the only supported database. There is no semantic version — Docker images are SHA-tagged from the main branch.

FEATURES

What TinyTinyRSS does

Tiny Tiny RSS reads feeds. What separates it from lighter readers is depth: a working plugin ecosystem, multi-user support, full-text extraction, programmable filters, and a documented API that mobile clients have been writing against for over a decade.

Multi-user mode

Run a shared instance for a team. Each user gets isolated feeds, filters, and OPML import. Set SINGLE_USER_MODE="false" in config.

Full-text extraction

The built-in af_readability plugin fetches full article text for feeds that publish summaries only. Per-feed toggle.

PostgreSQL search at scale

The af_psql_trgm plugin enables trigram-indexed search across hundreds of thousands of articles without slowing the UI.

JSON API for automation

Documented endpoints for fetching unread counts, marking articles, importing OPML, and triggering plugin hooks. Used by mobile clients and scripts.

Filter engine

Match articles by title regex, source, age, or content. Trigger actions: tag, label, mark read, publish, or invoke a custom plugin hook.

Fever and Google Reader APIs

Built-in Fever plugin works with Reeder and Fiery Feeds; the community FreshAPI plugin adds Google Reader compatibility for NetNewsWire, Unread, and others.

Share by URL

Publish a curated feed publicly without exposing your account. Per-user public feed, per-category RSS, or per-article share URLs.

Plugin architecture

Drop a PHP class into plugins.local/ to extend. Active community plugins cover SSO, image-proxy privacy, Mercury full-text, and chat notifications.

WHAT'S ALWAYS INCLUDED

Every app. Fully managed.
Nothing extra to pay for.

Every app you deploy includes the full managed service — security, backups, updates, and support from day one.

Automatic updates and patches

Apps run the latest stable version. Security patches applied silently, with rollback if needed.

Daily off-site backups

Multiple daily backups in redundant off-site locations. One-click restore if anything goes wrong.

24/7 uptime monitoring

Continuous monitoring with instant alerting. We respond before you notice.

SSL, firewall, DDoS protection

Auto-renewing SSL, hardened firewall rules, DDoS mitigation on every deployment.

Performance and scaling

We monitor resource usage continuously. When your app needs more headroom, we flag it and upgrade with your explicit approval.

Dedicated engineering support

Real engineers on chat. DNS, SMTP & migration help. All included in €9.

WHY MANAGED

Why teams pick managed TinyTinyRSS

On 1 November 2025, original maintainer Andrew Dolgov dismantled the tt-rss.org infrastructure. Every existing self-hosted instance pointing at the old Gitea repo now has a stale source. The new community fork is the canonical source — and the migration is one of three operational shifts that make managed hosting the path of least resistance.

We run the current community-maintained main branch from github.com/tt-rss/tt-rss. Every new deployment pulls a SHA-tagged Docker image we have already validated against our PostgreSQL build. When the maintainer publishes a notable fix, we test it on staging, apply it to your instance during your low-traffic window, and note it in your account log. You do not need to track the fork, watch the Discussions tab, or rebuild your own image.

Tiny Tiny RSS is opinionated about its install path. The project's own documentation states that Docker is the only fully-supported method and non-Docker installs receive "best effort" community support. The update daemon is a separate persistent PHP process that does not detach from the terminal and requires careful systemd or supervisor setup. The upstream defaults are also conservative: session cookies expire at 24 hours, the daemon runs two workers, and login activity gates feed updates after 30 days. None of these defaults are wrong for a single-user home install. None of them are right for a team.

REVIEWS

Hear from customers ​like you​​​​​​​

Successful businesses and professionals around the world rely on DANIAN every day

USE CASES

Three teams who run TinyTinyRSS on DANIAN

These are representative team types we set up most often. Each starts with the same flat €9 plan.

6-PERSON OSINT CONSULTANCY

Tracking 800 advisory feeds across three languages

Tracks ~800 feeds: national CERT advisories, OFAC bulletins, regional news in Russian, Mandarin, and Farsi, and CVE databases. Runs in Germany for stricter local data-protection regimes. af_readability enabled globally; FreshAPI exposes a Google Reader endpoint so analysts read on Reeder for iOS. SSO via auth_remote chained to Keycloak. 90-day searchable retention; six named users on multi-user mode.

SOLO SECURITY RESEARCHER

CVE triage with Slack alerts on critical hits

Monitors NVD recent-CVE feeds, GitHub Security Advisories, vendor PSIRT feeds, and 30+ infosec-researcher blogs. ~120 feeds, ~400 articles per day. Filter rules tag critical hits; a small custom plugin POSTs matching articles to a Slack webhook on the HOOK_ARTICLE_FILTER event. Built-in Fever plugin powers Reeder on iOS for triage. Single-user mode behind HTTP basic auth.

12-REPORTER REGIONAL NEWSROOM

Source list under press-shield rules in Stockholm

Tracks ~450 feeds: government press, court filings, competitor outlets, FOIA-watch sites. Runs in Stockholm under press-shield considerations. Multi-user with Keycloak SSO; auth_remote bridges credentials. "Share by URL" publishes curated public feeds for the politics desk. Daily OPML backup via update.php. 12 editorial accounts, 180-day retention.

COMPARISON

Four ways to run TinyTinyRSS

Tiny Tiny RSS sits in the small set of self-hosted apps with no direct SaaS equivalent — Inoreader and Feedbin are the closest, but neither offers the plugin extensibility or multi-user team mode TT-RSS includes. The cost math comes out differently than people expect once you cross three or four seats.

 PATH1 SEAT5 SEATS 10 SEATSOPERATIONS ON YOU
1. Proprietary SaaS
Inoreader Pro (annual)
$7.50/mo~$37.50/mo~$75/moZero. SaaS handles everything. No plugins, no full-text extraction, no custom filters at TT-RSS sophistication.
2. Self-host on a VPS
€24/mo production-class VPS
€24/mo + ~2h/mo€24/mo + ~3h/mo€48/mo + ~5h/moYou install Docker, run the official compose, configure systemd, manage SSL, monitor the daemon, apply patches, schedule backups.
3. Home server
Synology DS923+ or similar NAS
€700 + €8/mo€700 + €8/mo€700 + €8/moYou handle network exposure, ISP outages, hardware failures, off-site backups, and the daemon's idle behaviour.
DANIAN Managed TinyTinyRSS€9/mo€9/mo€9/moZero on your side. Backups, updates, monitoring, SSL, daemon supervision, PostgreSQL tuning — all included.

VPS costs assume a production-class instance suitable for sustained PHP-FPM and PostgreSQL workloads. Home-server hardware amortised over 3 years plus electricity. Inoreader pricing reflects per-seat list price on annual billing as of May 2026; bundled Team SKUs may differ.

BY INDUSTRY

TinyTinyRSS for specific industries

A feed reader is not a regulated tool, but the teams that build their workflow around one often face regulatory pressure on what they read and where they store it. Three industries put substantive demands on the deployment — and on the operator running the instance.

Analysts tracking sensitive sources work under access-logging and source-confidentiality constraints. A SaaS feed reader leaks the reading list — and therefore the investigation — to a third party. Self-hosting solves the leakage problem only if the operator runs encryption-at-rest, isolated authentication, and access-controlled logging.

We set ENCRYPTION_KEY on first deployment so feed passwords stay encrypted in PostgreSQL. SSO via auth_remote means analyst accounts live in your existing identity provider, not in the TT-RSS user table. DAEMON_UPDATE_LOGIN_LIMIT is raised to 365 days so feeds keep refreshing for analysts on rotation. We tune the daemon to four workers and DAEMON_SLEEP_INTERVAL to 60 seconds for breaking-news desks.

Typical scale: 200 to 1,000 feeds per analyst, with CVE-heavy operators seeing 50 to 200 vendor advisories per day. CERT advisories, OFAC bulletins, GHSA, and vendor PSIRT feeds are the common foundation; regional language coverage adds another 100 to 300 feeds per active language.
Reporters' source lists are working notes. Under press-shield laws in many jurisdictions, the list itself can be discoverable, so where the reader runs and who can see the logs matters. A regional desk hosting its reader on a U.S.-cloud SaaS is one subpoena away from disclosure it cannot push back on.

We deploy in the region your operation legally sits in: a Swedish newsroom in Sweden, a French one in France, a regional desk in New York or Toronto. Multi-user mode is standard, with SSO chained to your editorial identity provider so press credentials drive feed access, not a separate TT-RSS password. The built-in Share by URL function turns one curated category into a public feed for the politics desk without exposing the rest of the instance.

We set retention to match your archive policy: 180 days, one year, or open-ended. A regional newsroom commonly tracks 300 to 600 feeds; reporters star or save 10 to 50 articles per shift. Government press feeds, court-filing RSS, competitor outlets, and FOIA-watch sites are the typical foundation.
Client privilege makes a research list confidential by default. A SaaS reader stores that list — and the reading patterns behind it — on a third party's infrastructure, with access logs the firm does not control. For firms operating under Schrems II-style restrictions on U.S.-cloud processing, self-hosting is the policy answer, not a preference.

We deploy in your home jurisdiction with single-tenant isolation. ENCRYPTION_KEY is set; SSL is enforced; DISABLE_LOGIN_FORM pairs with SSO so authentication runs through the firm's identity provider. Feeds are tagged by client matter — court filings (PACER for U.S. matters, Court of Justice press feeds, national gazette RSS), regulator bulletins, legal-tech blogs.

Retention runs seven years to match conflicts-check requirements. A 50-attorney firm with 10 active research seats commonly tracks 150 to 300 feeds across 30+ matter tags. Filter rules route articles to per-matter labels automatically based on docket numbers or counterparty names.

FAQ

Frequently asked questions

Everything teams ask before signing up — answered straight, without sales speak.

Three groups: technical setup, migration, and how DANIAN works as a service.

01

Technical and configuration

Yes. Export OPML from your current reader (most have a one-click export), then in TT-RSS go to Preferences → Feeds → OPML → Import. Large OPMLs occasionally fail with error code 7 on malformed entries.
Yes via two paths. The built-in fever plugin gives you a Fever-API endpoint that Reeder 5, Fiery Feeds, and lire support natively. For NetNewsWire, Unread, and other Google Reader-compatible clients, we install the community FreshAPI plugin so you get a /api/greader.php endpoint. We turn both on by default.
Yes. We deploy with SINGLE_USER_MODE="false" and create the admin account on first boot. Each user has isolated feeds, filters, preferences, and OPML. User admin lives at Preferences → Users. Pair it with auth_remote or auth_oidc for SSO; we configure either against your identity provider on request.
Per-feed credentials. Right-click the feed → Edit feed → Authentication. Feed passwords are stored encrypted in PostgreSQL when ENCRYPTION_KEY is set. We set ENCRYPTION_KEY on first deployment, so credentials are encrypted from the start without any extra step on your side.
Yes — the af_readability plugin uses Fivefilters Readability.php to fetch the full article and inline it in the feed item. Per-feed toggle. For sites where readability fails (BBC is a known case), we install the mercury_fulltext plugin which calls a Mercury Parser endpoint for those feeds specifically.
PostgreSQL handles a TT-RSS instance with 1,000 to 2,000 feeds and several hundred thousand articles without difficulty. We enable af_psql_trgm by default for trigram-indexed search; we tune autovacuum thresholds for the article table's small-insert pattern; we partition archive tables on instances past 1M articles.
Yes — for production, the daemon must run persistently to refresh feeds. The official wiki recommends a systemd unit. We run it as a supervised process with automatic restart on crash, log to a structured journal, and alert on consecutive failures. You do not see this; it is part of the platform.
Yes if they live in plugins.local/ (the convention for non-core plugins). We track which third-party plugins you have installed and test them against new TT-RSS builds before rollout. If a plugin breaks against a new release, we pin you to the prior build, notify you, and wait for the plugin update.

02

Migration and onboarding

We can activate your app on your own custom domain/subdomain. Examples: mydomain.com, anyword.mydomain.com.
Or, on our randomized free subdomain. Example: 963.apps.danian.cloud
If you wish to use a custom domain/subdomain, select that option when ordering your app (or notify us later). We will send you the required DNS records and if needed, our tech team will modify them for you.
21 datacenter locations across six continents. You choose the region at provisioning. Application data sits in the region you choose; pick whichever is closest to your users or matches your data-residency preference.
Yes. Request a region migration from the dashboard and we run the move in the background. The system emails you when the migration completes; total transfer time depends on data volume but typical instances finish in a few hours. There is no extra charge for a region change.
Yes. Full data export is available at any time, in a portable format you can bring to any infrastructure.

03

Billing, support, and platform

€9 covers everything we do for that app: hardware in the region you choose, daily off-site backups with one-click restore, automatic security patches and version upgrades, 24/7 monitoring, SSL and firewall, and engineering support on Email/LiveChat. There are no setup fees or hidden line items. For more info see our Pricing page.
If you decide to continue, we charge €9/app/month from day 8. If you don't, the trial ends and you can export your data. No card is required for the trial, and we never auto-charge you without explicit consent.
No. The €9/month is flat regardless of how many users log into your app. Add 5 users or 50; the price doesn't change.
24/7 Live chat and email support, both staffed by engineers who run the systems. We handle DNS configuration, SMTP setup, app integrations, performance tuning, troubleshooting, and migration help. Response time is typically under an hour. There is no tier system — every customer gets the same support.
Yes. Cancel from the dashboard. We don't charge a cancellation fee, we don't lock data, and we will export your data to you on request before deletion. data to you on request before deletion.
Every customer instance is backed up daily to a separate region from the primary. We test restores. You can request a restore at any backup point within the retention window — usually 7 days for daily backups.
Your application data sits in the region you choose at provisioning — 21 datacenter locations across six continents. Account-level data (billing, account email, support ticket history) is processed centrally. Application data region is picked by you, per app.
99.9% uptime SLA on every app, every tenant. Service credits are documented at danian.co/service-level-agreement. The status page is located at status.danian.co.
When your tenant approaches the resource ceiling — the base tier holds 1 vCPU/RAM, 30 GB storage — we notify you. Resource upgrades happen with your explicit consent; we will not upgrade your tenant or charge you without it.
We wait. We don't suspend the app or delete your data on the first failed charge. We email you, you fix the card on file, and we continue.
Invoices can be downloaded from the billing dashboard in PDF the day each charge succeeds. EU VAT is added where applicable and the VAT-reverse-charge regime applies for VAT-registered businesses with a valid number.
150+ open-source apps across automation, team chat, file sync, analytics, AI, password management, email marketing, dev tools, project management, smart home, CMS, and federated social. See the full catalog →
Yes. Every instance comes with a web-based terminal and a file manager in your DANIAN management dashboard. Useful for managing your data and customizations.
Resources scale with your usage. If your app needs more vCPU, RAM, or storage, we add it — and we ask first before any change to your plan. €9 is the floor; resource-heavy workloads may price higher, but you'll always know in advance.
Yes. We have both a Partner program and an Affiliate program available. Anybody can sign up.
No contract. No minimum commitment. Cancel anytime from the dashboard with one click. The 7-day free trial requires no credit card. After the trial converts to paid, you can still cancel at any month without notice or penalty.

DEPLOY IN YOUR REGION

21 datacenter locations on six continents

Pick the region closest to your users.

United States, Germany, Finland, Singapore, Australia, Brazil, Canada, Netherlands, UK, Spain, Italy, France, Sweden, Malaysia, India, Japan, Mexico, Poland, South Korea, Chile, South Africa and more coming soon

Global Reach Map

Try managed TinyTinyRSS for 7 days

No card. Cancel from the dashboard.