Telegram-Stremio is a self-hosted media server built with FastAPI, MongoDB, and PyroFork that turns Telegram channels into a private streaming library watched in Stremio or Nuvio.

What it is

Telegram-Stremio is a self-hosted media server that lives in the Stremio addon ecosystem, built with FastAPI, MongoDB, and PyroFork, and licensed under GPL-3.0. It streams Telegram files straight into Stremio or Nuvio, and it replaces manual, bot-command-driven handling of Telegram media with a web panel that requires no coding and almost no bot commands. The project is written in Python and is organized around a Stremio addon that serves your Telegram channels as a streaming library.

The concrete problem it solves is that Telegram files are not a media library: they lack posters, descriptions, seasons, and episodes, and they are not permanent streaming links. With Telegram-Stremio, forwarding a movie or episode to a channel instantly produces a permanent, no-expiry streaming link with posters, descriptions, seasons, and episodes, just like a real streaming app. For multi-user sharing, it adds subscriptions, access tokens, and an admin panel; the companion TeleStremio Android app covers the single-user, phone-hosted case.

Key capabilities

• The server stack is FastAPI for the web layer, MongoDB for the database, and PyroFork for the Telegram client.
• Forwarding a movie or episode to a channel turns it into a permanent, no-expiry streaming link with posters, descriptions, seasons, and episodes.
• A web settings page and admin panel cover logs, restart, and update, so almost no bot commands are needed.
• Auto catalogs and custom catalogs are supported, along with private, exclusive, and searchable catalogs.
• Special channels include an anime channel, a global search channel, an announcement channel, and a skip channel.
• Subscriptions and access tokens provide access control for multi-user deployments.
• Filename rules cover movies, TV shows, split files such as .001 and .002, combined or season-pack files, and subtitles with language name and code support.

Who uses it and how

• Self-hosters run the full server on a VPS with Docker and MongoDB, which the README recommends for 24/7 multi-user streaming with subscriptions, access tokens, and the admin panel.
• Users who want free always-online hosting without a VPS deploy on Hugging Face, and the README also documents a Heroku path.
• Single users install the TeleStremio Android app to run the same idea on a phone with no VPS, no Docker, and no MongoDB, using Tailscale for remote access; that app is limited to one user, on-demand live search, Cinemeta Popular and Top Rated catalogs, and uptime while the phone is on.
• Content workflows include organizing channels, adding files by forwarding with filename rules, adding files manually, and adding subtitles by filename or manually; the README gives Goa trip, lectures, and One Piece as manual-add examples.
• Groups that share a library use multi-user access tokens, subscriptions, and a public URL out of the box on the server, while the app is intended for personal, single-user viewing.

Getting started

First-time setup runs through config.env and the web settings page, after which the README offers three deployment routes: VPS with Docker and MongoDB (recommended), Hugging Face, or Heroku. The TeleStremio Android app is the no-server alternative for phone-hosted use.

How it compares

The facts do not name any similar tools, so Telegram-Stremio stands alone in this registry. The README's only internal comparison is between the TeleStremio Android app and the full self-hosted server: the app is single-user, phone-hosted, and on-demand, while the server adds a full indexed database, auto and custom catalogs, requests, subscriptions, tokens, an admin panel, analytics, backups, announcements, MediaFlow proxy, and RPDB or Fanart, with 24/7 uptime.

When to use it — and when not to

A self-hoster must operate MongoDB and a VPS or Docker host, and must take on subscriptions, tokens, and admin duties, while the TeleStremio app avoids that infrastructure but caps the library at on-demand live search and runs only while the phone is on. Anyone who does not want to run that infrastructure, or who only needs single-user phone viewing, should choose the app over the full server. The facts give no other limiting signals: the licence is GPL-3.0, open issues stand at 1, and the last push is 2026-09-15.