AIOStreams: One Stremio Addon That Funnels Every Source Through Your Own Filter Rules
AIOStreams consolidates multiple Stremio addons and debrid/usenet services - including its own suite of built-in addons and a native Usenet streaming engine - into a single, highly customisable super-addon.
At a glance
- What is it?
- AIOStreams is a self-hosted TypeScript addon that merges other Stremio addons, its own built-in scrapers, and debrid or Usenet services into one stream list. It is aimed at people who already run a debrid account and want one configuration instead of six.
- Who is it for?
- Adopt AIOStreams if you already pay for a debrid service and are tired of keeping Torrentio, Comet and MediaFusion configured separately, or if you want Usenet results inside Stremio without a second client. Skip it if you only ever stream from one source, or if you want a stable tagged release: the published builds are nightly-dated, so pin the Docker image digest rather than a version string.
- Can I use it commercially?
- Yes, with strict conditions. AGPL-3.0 is a network copyleft licence: if people use a modified version over a network, for example as a hosted service, you must offer them its source code under the same licence.
- Is it still maintained?
- Yes. The repository last received commits 1 day ago.
- What is it written in?
- Mainly TypeScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on September 15, 2026, and from our analysis. They are not legal advice.
DEEP OPEN-SOURCE ANALYSIS
The problem is addon sprawl, not a missing scraper
Stremio users who care about stream quality end up installing several addons at once. Torrentio covers one set of indexers, Comet another, MediaFusion a third, and each one has its own configuration page, its own API key fields, and its own idea of how to sort results. The README frames AIOStreams as a response to exactly this: instead of juggling multiple addons with different configurations and limitations, the project fetches from all configured sources and then deduplicates, filters, sorts and formats them before presenting a single list. The audience is therefore narrow and specific. It is not someone who wants a stream to appear. It is someone who already has opinions about which release group wins, which resolutions to hide, and which debrid service to prefer, and who is tired of expressing those opinions five times. The README divides this audience explicitly into a casual user who wants a simple unified list and a power user who wants to fine-tune every aspect of the results. Both are served by the same pipeline; the difference is how many rules they write into it.
What actually happens between a Stremio request and the stream list
AIOStreams presents itself to Stremio as a single addon, with a manifest that the README says is generated dynamically. That detail matters more than it looks. Because the manifest is produced at request time rather than shipped as a static file, the addon can reflect the current set of sources and their current capabilities without the user reinstalling anything, and the README cites this as the reason you always get the latest addon updates without reconfiguring. Behind the manifest sits a pipeline: configured sources are queried, their results are merged, duplicates are removed, filters are applied, the survivors are sorted, and the formatted output goes back to Stremio. The README states that streams, catalogs, metadata, subtitles and addon catalogs are all supported, so the merge is not limited to the stream endpoint. Sources come from three places. First, external addons added by URL, with the README claiming that if it works in Stremio it works here, plus an addon marketplace that lists 80 or more community addons and can apply your debrid keys to compatible ones automatically. Second, a built-in suite hosted alongside your instance, including Knaben, Zilean, AnimeTosho, Torrent Galaxy, EZTV, NekoBT, SeaDex, TorBox Search, Easynews Search, Stremio GDrive and a Library addon for browsing your debrid or Usenet library. Third, connectors to things you already run: Bitmagnet, Jackett, Prowlarr, NZBHydra2, and generic Newznab or Torznab endpoints. Services are configured once in the Services tab and, per the README, applied to every compatible addon, which is the mechanism that removes the repeated credential entry.
Running it: Docker, the Services tab, and the Usenet decision
The repository publishes Docker images under both viren070/aiostreams on Docker Hub and ghcr.io/viren070/aiostreams/aiostreams, and the README's badge configuration queries a registry stats endpoint for both names, so either registry is a supported path. A deployment therefore starts with a container run or compose file pointing at one of those image names, followed by opening the configuration page and working through the tabs. The Services tab is where debrid and Usenet credentials go: Real-Debrid, AllDebrid, Debrid-Link, Premiumize, TorBox, EasyDebrid, PikPak, Offcloud, Seedr and put.io are named for debrid, and the Usenet side lists the built-in engine, Easynews, NzbDAV, AltMount, Stremio NNTP and StremThru Newz. The Addons side is where you either browse the marketplace or paste a custom addon URL, and where you categorise what you added. One constraint is stated plainly in the README rather than buried: built-in addons that search for torrents require a debrid service. They are not usable on their own. For Usenet there is a second decision. The README says results can be streamed by the built-in engine, by external tools such as NzbDAV or AltMount, natively by Stremio itself, or through TorBox on its Pro plan, and it points to a separate Usenet guide for the details. Choosing the built-in engine means supplying your own NNTP provider; choosing an external tool means running that tool as well. The README does not lay out the trade-offs between those four paths, which is the thinnest part of the supplied material.
Where the consolidation breaks down
The centralisation that makes AIOStreams useful is also its main failure mode. Every query passes through your instance, so if the container is down, unreachable from your network, or slow, Stremio shows nothing regardless of how healthy the upstream addons are. A single addon that aggregates many is a single point of failure by construction, and the README does not describe caching, retry behaviour, or what happens when one source times out while others respond. That is a gap worth probing before you move your whole setup onto it. There is a second limitation in the built-in addons specifically: the torrent-searching ones are gated behind a debrid service, so a user with no debrid account gets none of the built-in value and is left with the aggregation layer over external addons. A third issue is release cadence. The three most recent releases listed are all nightly builds dated the same day, within roughly twenty minutes of each other. Nightly builds are how the project ships, and the README's own framing of dynamic manifests assumes you are willing to track that. Anyone who needs a frozen, auditable artefact has to pin an image digest instead of a version tag. Finally, the automatic application of debrid keys to compatible marketplace addons is convenient and worth understanding before you enable it: your credentials are being handed to third-party addon endpoints by your instance, and the README does not enumerate which addons receive them.
Compared with running Torrentio or Comet directly
The obvious alternative is to keep using a single scraping addon such as Torrentio or Comet on its own, configured through its own web form. The difference is architectural, not cosmetic. Torrentio and Comet each own their indexer list and their own sorting logic; you choose from what they decided to query, and your filtering options are limited to the knobs that addon exposes. AIOStreams inverts that. It treats those addons as inputs, adds its own scrapers and your self-hosted indexers alongside them, and puts the deduplication, filtering and sorting in a layer you control. The practical consequence is that switching indexers no longer means switching addons, and two addons returning the same release collapse into one entry. The cost is operational: you now run a service, keep it updated, and accept that its availability bounds your streaming. A second alternative, for Usenet specifically, is to skip AIOStreams' engine and use NzbDAV or AltMount as the streaming layer, which the README itself lists as supported paths. That keeps the Usenet machinery in a separate, independently maintained project, at the price of one more container and one more thing to configure.
Licence and the cost of staying current
AIOStreams is licensed AGPL-3.0. For a self-hoster running the container for personal use, the practical effect is limited: the licence's network-copyleft obligations attach when you modify the software and let others interact with it over a network, at which point you are expected to offer those users the corresponding source. Running an unmodified image for yourself does not trigger that. If you fork it, rebrand it, or host it for other people, read the licence text rather than a summary; nothing here is legal advice. Maintenance cost is the more immediate concern. The project is active, with the last push dated 2026-09-10 and nightly releases the day before, so the code moves. That means the upgrade path is continuous rather than punctuated: you either follow nightlies and absorb occasional breakage, or you pin a digest and fall behind on addon compatibility fixes. There is no published LTS or stable channel in the supplied material, and the README does not describe a migration process between versions. Budget for reading release notes before each bump, and keep your configuration somewhere you can restore it, because the whole value of the instance lives in that configuration rather than in the code.
Editorial conclusion
Adopt AIOStreams if you already pay for a debrid service and are tired of keeping Torrentio, Comet and MediaFusion configured separately, or if you want Usenet results inside Stremio without a second client. Skip it if you only ever stream from one source, or if you want a stable tagged release: the published builds are nightly-dated, so pin the Docker image digest rather than a version string. Before committing, verify three things on your own instance: that your debrid provider is on the supported list, that your indexer speaks Newznab or Torznab if you plan to use Usenet, and that the built-in usenet engine is actually reachable from your network, since the README offers NzbDAV, AltMount, Stremio's own NNTP support and TorBox Pro as alternatives when it is not.
Community notes