Documentation menu

Start here / choose a topology

Requirements and deployment modes

Choose the smallest useful private stack and understand where Docker, Plex, storage, and optional providers fit.

Baseline requirements

Use an authorized exact Omakase Plus private release on a trusted server with:

  • Debian 12 or 13, or a compatible Docker host;
  • Docker Engine and the Compose plugin;
  • a local filesystem for Omakase data and SQLite;
  • an Omakase-managed library path;
  • an existing Plex server or the bundled Plex profile;
  • ffprobe inside the release image;
  • HTTPS and owner authentication before access extends beyond loopback;
  • independent backups for Omakase data, secrets, and Plex configuration.

Rootless Docker is not currently a supported target because media ownership and optional device or network handling differ.

Compare the modes

ModeBest forNetwork requirementStart posture
Import-onlyMedia already on diskNo torrent traffic or VPNRecommended first install
Real-DebridAn existing provider account and provider-backed libraryProvider API and established storage adapterOptional adapter
qBittorrent + GluetunExplicit local BitTorrent useHealthy tunnel, kill switch, and shared network namespaceEnable only after import proof

Existing server or Proxmox

An existing Docker server is the shortest route. Keep code, mutable data, imports, and the managed library in separate paths. If Plex already exists, map the Omakase library into the path Plex sees.

For a trusted personal Proxmox node, an unprivileged Debian LXC can run the compact stack. Docker in an LXC requires Proxmox nesting and keyctl. Use a QEMU VM when stronger isolation, live migration, or untrusted users matter.

Never make the container privileged or disable AppArmor just to make Docker work.

Existing or bundled Plex

With existing Plex, Omakase needs the base URL, a token stored outside source control, and the exact Plex-visible paths for Anime and Anime Movies.

The bundled profile uses the official Plex image. Keep the Plex database on a local filesystem with working file locks. The example binds Plex to loopback until you deliberately choose a trusted LAN route.

A safe adoption sequence

  1. Install the exact release and restrict the secret file.
  2. Render Compose before startup.
  3. Start Omakase with existing or bundled Plex in import-only mode.
  4. Run Doctor.
  5. Import synthetic, owned, or otherwise authorized media.
  6. Verify identity, subtitles, Plex metadata, and playback.
  7. Capture and test rollback.
  8. Connect AniList if wanted.
  9. Add Real-Debrid or the local torrent lane only when its legal, network, and recovery boundaries are understood.

Continue with the existing Docker server or Proxmox container guide.