Services Overview¶

DUMB is composed of multiple services that work together to provide a complete automated media management system. Services are categorized into:

• DUMB Services: Required for system orchestration and user interaction
• Core Services: Manage Debrid content orchestration or media playback
• Dependent Services: Required by one or more core services to function
• Optional Services: Enhance or simplify workflows but are not required

How the Services Work Together¶

DUMB is built as a collection of microservices that communicate over internal APIs and shared paths. Below is an example flow:

1. Platform Infrastructure

   • DUMB API coordinates and manages all service interactions
   • DUMB Frontend provides the web interface for managing and viewing services

2. Debrid Orchestration & Content Management

   • Riven Backend, CLI Debrid, Plex Debrid, and Decypharr each serve as a Debrid orchestrator: requesting, managing, and monitoring content acquisition workflows
   • These core services integrate with providers like Trakt, Seerr, and Debrid APIs to manage what content gets fetched
   • NzbDAV provides a WebDAV endpoint and download client integration for NZB workflows
   • Sonarr/Radarr/Lidarr/Whisparr manage media queues and organize content from download clients
   • Prowlarr manages indexers and syncs them to the Arrs
   • NeutArr automates backlog and quality-upgrade searches across the Arr stack

3. Media Playback

   • Plex is the core service that hosts and serves collected content to users
     • It relies on symlinked or mounted content made available through rclone/Zurg from the other core services
   • Jellyfin and Emby can be used as alternatives to Plex for library playback

4. Storage & Retrieval

   • rclone mounts remote Debrid storage for local access
   • Zurg provides WebDAV access to debrid downloads

5. Metadata & Caching

   • CLI Battery and Phalanx DB serve as local or distributed metadata stores
   • Zilean caches metadata and exposes a Torznab-compatible indexer for scraping optimization

6. Database Layer

   • PostgreSQL stores metadata for Riven, Zilean, and pgAdmin
   • pgAdmin is a GUI for exploring PostgreSQL databases

Quick Reference¶

Tips¶

• Use the onboarding UI to enable only the services you need
• Services will auto-start in dependency order
• Logs and errors can be viewed in the DUMB Frontend

Service Categories¶

• DUMB Services
• Core Services
• Dependent Services
• Optional Services