Remux

self-hosted media server with a Jellyfin-compatible API

---

Stream content from Stremio add-ons, local files, or WebDAV sources all through your existing Jellyfin clients.

Movies and shows come from Stremio add-ons or your own files. Music is handled separately through its own streaming pipeline.

Use your existing Jellyfin clients as-is: browse, search, and play.

Built in Rust for performance and low resource usage.

---

What makes it different from Jellyfin?

• Online sources or local files
  Stream from Stremio add-ons, a local path, or a WebDAV server

• Stremio-powered video
  Movies and shows come from Stremio add-ons

• Independent music pipeline
  Music is not tied to Stremio and is streamed from separate sources

• IPTV Support

• Dynamic libraries
  Build collections based on filters instead of folders or scans

• User management Including user data import from jellyfin servers to get you started

• Lightweight & fast
  Written in Rust with a focus on efficiency

• New dashboard
  A custom-built admin interface tailored for this workflow

• No backend plugins
  Simpler architecture (Jellyfin web UI theming still works)

• Local & WebDAV files
  Index and stream video, audio, or .strm files from a local path or WebDAV server

⚠️ Status

Remux is still in an early stage. Expect rough edges, missing features, and breaking changes. Run the image as follows

version: "3"
services:
  remux:
    image: ghcr.io/lostb1t/remux:latest # or nightly
    ports:
      - "3000:3000"
    volumes:
      /remux/data:/data

Development

Install cargo make

cargo install --force cargo-make

Build jellyfin web

cargo make jellyfin-web

Fetch/build all supported web clients (Jellyfin)

cargo make web-clients

run

cargo make dev

❤️ Support the Project

• ⭐ Star the repository on GitHub.
• 🤝 Contribute: Report issues, suggest features, or submit pull requests.
• ☕ Donate:
  • Ko-fi

AI policy

Important

Use AI as much as you want, but understand every line, verify it works, communicate as a human, and disclose significant AI-generated contributions.

We welcome contributions created with the help of AI tools such as GitHub Copilot, Claude, ChatGPT, Cursor, and similar assistants. AI is a tool; contributors remain responsible for everything they submit.

AI-assisted code is allowed

You may use AI to:

• Generate code
• Draft tests
• Research the codebase
• Suggest fixes and improvements
• Help write documentation

All contributions must still meet the project’s quality standards and pass review.

You are responsible for your contributions

Before submitting a pull request, you must:

• Understand the code you are submitting
• Be able to explain why it works
• Test your changes
• Review and edit any AI-generated content

Do not submit code you do not understand.

Communication must be human

When interacting with maintainers and reviewers:

• Write your own PR descriptions
• Write your own review responses
• Be prepared to discuss your changes

AI may help you draft a response, but maintainers expect to communicate with the contributor, not an AI assistant.

Disclose when AI was used

If AI was used to generate a significant portion of an issue, PR, or the code it contains, please say so in the submission. A short note in the PR description is enough — for example, "The initial implementation was drafted with Claude and then reviewed and edited by me."

Issues and pull requests that appear to be AI-generated but do not disclose it may be closed without review. Contributors who repeatedly submit undisclosed AI content, or who ignore this policy, may be blocked from contributing.

Keep It Human

We're grateful for all genuine contributions, whether AI-assisted or not. The key is human oversight and understanding. Thank you for helping keep Actual focused on what matter