EDIT: I was told in another sub that my original comment below wasn’t all that correct I’ll leave it for posterity, but the response I received was:
““Duck Streams” is just a renamed AIOStreams configuration using the first available public instance.
i.e. the QuickStart tool installs a preconfigured AIOStreams (+AIOMetadata) configuration with its name changed to “Duck Streams”.
You don’t typically use the bootstrapper together with AIOStreams. While the bootstrapper sets up individual addons in Stremio directly, the addons need to be added separately into the AIOStreams configuration too.
You can certainly use the bootstrapper, and then install AIOStreams as an addon separately, but ideally you’d either remove the standalone addons or remove AIOStreams after once you’ve decided; otherwise, you’re sending wasted requests to the addons that are duplicated in AIOStreams and in Stremio directly.
If you plan to use AIOMetadata, avoid the bootstrapper entirely. Just use Cinebye + install AIOMetadata to stremio. (the quickstart tool does this for you)”
Original Comment Below >>>
@Miki I saw somewhere you talking about trying to deep dive into the “Full” Bootstrapper config options and it set me down a path lol
I don’t have direct config answers, but I started researching conceptually how to get the most out of Bootstrapper, AIOStreams, and even Duck Streams. Here’s what I’ve come up with so far, let me know if you think you could add anything to it:
I think I’m starting to visualize this; please tell me if I’m grasping this correctly.
AIOStreams:
• GitHub - Viren070/AIOStreams: One addon to rule them all. AIOStreams consolidates multiple Stremio addons and debrid services into a single, highly customisable super-addon.
• A Stremio addon that acts as an aggregator/wrapper, combining, filtering, and sorting results from multiple other addons.
• Provides a unified interface and enhanced output management; effectively a single point of failure if it goes down, even if underlying addons are still available.
• Supports shared “templates” of advanced configurations; can be created using AIO tflix Builder—a separate community tool.
• Designed to be managed and tweaked incrementally over time.
Bootstrapper:
• GitHub - DryKillLogic/stremio-account-bootstrapper: Bootstrap your Stremio account
• An automated script that rapidly configures a Stremio account with a predefined set of popular addons.
• Automates initial setup and overwrites existing Stremio configuration.
• Not intended for ongoing, in-place tweaking as changes generally require re-running the bootstrap process (effectively a wipe and reinstall).
Ultimately, these tools are complementary: a bootstrapper can be used to install a clean baseline, after which AIOStreams can be installed and used to manage, filter, and refine addon output over time.
Both approaches still rely on the same underlying providers/services, the difference is how results are installed, surfaced, and maintained, not the sources themselves.
So, basically, I would use the “Full” Bootstrapper preset (installing the full stack of providers, indexers, and debrid-enabled addons) expecting AIOStreams to sit on top of that, not replace it by…
• Run the Bootstrapper (Full preset) first and confirm playback works normally.
• Install AIOStreams afterward as an additional addon.
• Import an AIOStreams template (or build my own) that targets the addons the Full preset already installed.
• Hide the raw source addons in the UI and let AIOStreams control the user interface.
Note on the new Duck Streams: Duck Streams fits in as an upstream source addon: it provides streams, but doesn’t manage or aggregate other addons. In a Full Bootstrapper setup—or just installed after Bootstrapper and before AIOStreams—Duck Streams can simply be included as one of the inputs AIOStreams aggregates and ranks alongside the other installed source addons.
Have I got it?