Pick a route

You do not need every project. Start with the outcome you want and add another ship only when it solves a real problem.

• I want the complete automation stack

  Use Plundarr. Maraudarr generates one docker-compose.yml, one .env, and the configuration directories for your selected services.

  Plundarr quick start

• I only need PIA WireGuard configuration

  Use Privateerr. It runs the official PIA manual-connection scripts and writes files that Gluetun or another WireGuard client can consume.

  Privateerr quick start

• Plex already works; I want the backstage tools

  Use Duplex for Kometa, ImageMaid, PATTRMM, Tautulli, Notifiarr, and controlled container updates.

  Duplex overview

• I need a platform-specific route

  Choose Linux Docker, Synology Container Manager, or TrueNAS Apps. The stack stays Compose-based while storage and permissions change by platform.

  Choose a harbor

A sane first voyage

1. Decide where downloads, libraries, and application state will live.
2. Confirm the Docker user can read and write those locations.
3. Generate Plundarr with only the services you actually plan to configure.
4. Edit .env before starting containers.
5. Start the VPN lane first and validate it before adding indexers and managers.
6. Add requests, playback, dashboards, and maintenance tools in layers.

Tip

A smaller working stack is easier to reason about than a 20-container stack where every web UI is asking for its first-run setup at once.

Before you launch

• Docker Engine and Docker Compose v2 are available.
• Host paths exist and have the intended owner/group.
• The chosen host ports are free.
• The Docker subnet does not overlap your LAN, VPN, or another Compose project.
• Secrets are in an ignored .env, never in docker-compose.yml.
• You have a backup plan for config/, not just the media library.