Moka

From request to play, on your own server.

Moka is a self-hosted media server for films, shows and music. Ask for a title and it is found through your indexers, downloaded by your client, filed in your library and ready to play in the browser.

Development preview: it runs, it is unfinished, and it changes often.

Sintel 2010 Example request
  1. Requested Waiting for someone to approve it.
  2. Wanted Approved. Looking for a release that fits your quality profile.
  3. Searching Asking your indexers right now.
  4. Sent to client A release was picked and handed to your download client.
  5. Downloading Your download client is fetching it.
  6. Importing Download finished. Adding it to your library.
  7. In library Ready to play.

One program, one path

Moka covers the whole way in one place: a catalog to browse, requests with approval, release search with quality profiles, downloads through your own client, import into tidy folders, and a player in the browser with subtitles.

Each title is one thing that moves through visible states, so the request, the download and the file you play are the same object seen at different moments. When Moka decides something for you, it says why: which release it took, why it skipped the others, why a video is being converted.

Moka ships with no content sources. You connect your own download client and indexers.

Why it exists

Moka started as a personal project. I wanted my own setup to feel like one program instead of several, and to understand every choice it made.

It is still personal, but I would rather build it in the open than finish it alone. While it is in development the code is public, so you can follow along, run it, and tell me where it falls short. Ideas, criticism, bug reports and questions are all welcome in the issues.

Works with what you already run

Moka is not here to replace your stack. It can sit next to it, take over one part, or simply watch. And you can stop using it whenever you like: the library is plain folders with readable names, and imports hardlink or copy, never move.

Jellyfin
Keep watching there. After each import Moka refreshes just that folder, and it brings back what people watched.
Radarr
Moka can sit in front of it: approved requests go to Radarr, and every film Radarr has shows up in Moka to watch.
Prowlarr
Bring in the indexers you already set up there in one step, or let Prowlarr keep them in sync.
qBittorrent, Transmission, SABnzbd
Your download client stays yours. Moka adds downloads under their own category and follows them to the end.
Request and subtitle apps
Apps that talk to Radarr or Sonarr can connect to Moka with an API key and get the usual webhooks after an import.

Where it stands

Works today

  • Films and shows, from request to play
  • Whole seasons, and new episodes as they air
  • Release choice with quality profiles, explained for every release
  • Playback in the browser, converted with FFmpeg only when needed
  • Subtitles inside or next to the file, styled ones included
  • Existing film and show folders brought in as they are

Coming next

  • Music downloads and playback (catalog and album requests work)
  • Ebooks and audiobooks
  • An API that existing phone and TV apps can connect to
  • A first release

Try it, then tell me what broke.