Harbor: a Tauri and Rust desktop client for the Stremio addon protocol that ships no content
A Custom Stremio Client Built for Adventure!
At a glance
- What is it?
- Harbor is an MIT-licensed desktop media player for the open Stremio addon protocol, built on Tauri with a Rust core. It hosts, indexes and bundles no media: you bring your own addons and sources, and the maintainers suggest building it yourself.
- Who is it for?
- Choose Harbor if you already use Stremio addons and want an open, hackable desktop client with a native player, a stream ranking engine, watch parties, DVR and a theme engine, and you are comfortable building it from source.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 5 days 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 17, 2026, and from our analysis. They are not legal advice.
DEEP OPEN-SOURCE ANALYSIS
A different player for the Stremio ecosystem, not a competitor
Harbor is a desktop media player and a client for the open Stremio addon protocol. The README is emphatic about what that means and does not mean: Harbor hosts, indexes and ships no media, and bundles no content addons. You bring your own addons and sources. It is built on Tauri with a React frontend and a Rust core, and it is MIT licensed.
The intended user already uses Stremio and wants a different flavour of client on the desktop, one with features like a native player, a stream ranking engine, Wikidata integration, watch parties, picture-in-picture, DVR, Live TV, anime support and a theme engine. The README repeatedly positions Harbor as not a Stremio competitor but a different player for the same ecosystem, and even urges users to support Stremio directly and use its official apps on mobile and TV.
That framing is unusually careful, and it reflects the legal shape of the project. Harbor is code that speaks a protocol; the content comes from whatever addons and sources the user has already chosen. The README states plainly that contributors are not responsible for what a user does with it or which addons they use, and directs people to follow the laws of their jurisdiction.
The stream engine and native player are the reasons to switch
The substance behind Harbor is in its player and its handling of streams. The README lists a native player, a stream ranking engine that orders the results an addon returns, and picture-in-picture, DVR and Live TV as first-class features. It works on Cinemeta out of the box and gets richer with a free TMDB key, which is the pattern throughout: functional with public metadata, better when you supply your own keys.
The Rust core is where the performance-sensitive work lives, with the React and Tauri layer providing the UI. That split is a deliberate architecture choice: Tauri produces a smaller desktop footprint than an Electron app by using the system webview, and the Rust core handles the parts that benefit from a native language. The repository is a pnpm workspace with a `harbor-core/` package and a `src-tauri/` directory, confirming that division.
Features like watch parties, a theme engine and anime support signal a project aimed at enthusiasts who want to customize their viewing setup rather than a minimal viewer. The README's tone, a passion project addressing bugs promptly as scope permits, sets expectations accordingly: this is a community effort, not a commercial product with a support contract.
Running the web build or building the desktop app
Harbor has two build targets, a browser build of the Vite and React UI and the full Tauri desktop app. The README notes official Linux `.deb`, `.rpm`, Flatpak and AppImage builds are maintained in a separate repository, and strongly recommends building your own from source because the bundled releases are unsigned.
The fastest way to see the web UI is Docker Compose, which the repository provides:
docker compose upThat builds the image from the included Dockerfile and serves the Vite/React web UI on port 1420, with no Rust or Tauri toolchain needed for the browser build. For a local development setup with the source, the `package.json` scripts define the flow:
pnpm run setup
pnpm run dev`pnpm run setup` fetches the binaries, libmpv, mpv and fonts the player needs, and `pnpm run dev` starts the Vite dev server. Building the desktop app uses the Tauri toolchain through `pnpm run tauri`, and the README's Linux system build is `pnpm run tauri:build:linux-system`. The project pins pnpm 11.9.0 via corepack, which the Dockerfile makes explicit, so matching that pnpm version avoids install drift.
Unsigned releases and the build-it-yourself recommendation
The clearest limitation is one the README raises itself, repeatedly and in capital letters: the bundled releases do not include Windows or macOS code signing or certification, because it is a free project, so opening them triggers OS security prompts. The maintainers highly recommend building your own Harbor from the latest source to avoid those popups.
That is an honest disclosure, but it is a real barrier. A user who wants a signed, double-click-to-run desktop app will find friction here: either accept the OS warnings on unsigned bundles or set up the Tauri toolchain and build it themselves. For a technical audience that is acceptable; for a general audience it is a meaningful hurdle.
The second limitation is inherent to what Harbor is. It ships no content and no addons, so out of the box it is a player with public metadata and nothing to play until you add your own Stremio addons and sources. That is a deliberate design and legal stance, not a gap to be fixed, but it means Harbor is only as useful as the addons the user already has. The README also notes the project is sometimes slowed by contributors' timezones, so fixes and update rollouts can take time.
Against the official Stremio desktop app
The direct alternative is Stremio's own official desktop application, which the README actively encourages people to support and use. The official app is signed, maintained by the company behind the protocol, and is the reference client the ecosystem is built around.
Harbor's difference is that it is an independent, open-source client offering a different feature mix, the stream ranking engine, watch parties, a theme engine, DVR, Live TV and the rest, on a Tauri and Rust base, for users who want to customize or tinker in ways a reference client does not expose. The cost is the unsigned builds, the community-paced support, and the build-it-yourself recommendation. Choose the official Stremio app if you want a signed, supported client and do not need Harbor's extra features. Choose Harbor when you want an open, hackable desktop player for the same addons, are comfortable building from source, and value features like the ranking engine and theme system over the convenience of a signed binary. The two are complements: Harbor is a different player for an ecosystem the README explicitly asks you to keep supporting.
MIT, self-built updates, and what to set up first
Harbor is MIT licensed, and the README goes further than most, stating you are free to sell, reuse or profit off of it. For a project that positions itself as an open concept rather than an entity, that permissiveness is consistent, and it means anyone can fork Harbor or ship a derivative without restriction beyond attribution.
Maintenance leans on the self-built model. Because the recommended path is building from source and the official signed-free Linux packages live in a separate builds repository, keeping current means either tracking that builds repo or rebuilding from the latest source when it is available, which the README suggests doing. Updates flow through an update endpoint the maintainers push to, subject to their testing and timezones.
The concrete first step is to get a source of content and metadata configured, since Harbor ships neither. Add your own Stremio addons and sources, and supply a free TMDB key to enrich the metadata beyond the default Cinemeta, then decide between the Docker web build for a quick look and a full Tauri build for the native player and its DVR, PiP and Live TV features. If you use a bundled release instead of building, expect the unsigned-app OS prompts the README warns about.
Editorial conclusion
Choose Harbor if you already use Stremio addons and want an open, hackable desktop client with a native player, a stream ranking engine, watch parties, DVR and a theme engine, and you are comfortable building it from source. It is the wrong choice if you want a signed, supported, double-click app, since the bundled releases carry no Windows or macOS signing and the maintainers recommend building your own, or if you expect content included, since Harbor ships no media and bundles no addons. Before using it, add your own Stremio addons and sources and a free TMDB key, then pick the docker compose web build for a quick look or a full Tauri build for the native player features.
Frequently asked questions
Does Harbor include movies or streaming addons?
No. The README states Harbor hosts, indexes and ships no media and bundles no content addons; you bring your own addons and sources. It works on Cinemeta metadata out of the box and is richer with a free TMDB key.
Why does Harbor recommend building it yourself?
Because the bundled releases do not include Windows or macOS code signing, since it is a free project, so opening them triggers OS security prompts. The README highly recommends building your own from the latest source to avoid those popups.
What is Harbor built with?
The README says Harbor is built on Tauri with a React frontend and a Rust core. The repository is a pnpm workspace containing a harbor-core package and a src-tauri directory, and a Docker path serves the Vite/React web UI without the Rust toolchain.
Community notes