Skip to content

Dependent services

These services provide databases, mounted files, or metadata to another application. The dependencies you need depend on that application's configuration and installed layout.

At a glance

Supporting services need to match the workflow that uses them. A running unrelated instance is not a substitute for the intended dependency.

flowchart TD
    A["Choose a core workflow"] --> B["Check its required dependencies"]
    B --> C["Start the matching database or provider"]
    C --> D["Start the matching mount if required"]
    D --> E["Verify the core application connection"]

Dependent Service Index

Service Description Required By
CLI Battery Standalone metadata and Trakt layer for stable/older CLI Debrid releases CLI Debrid layouts that still use the standalone service
Phalanx DB Distributed metadata store for CLI Debrid CLI Debrid (optional but often used)
PostgreSQL Shared database engine for required and optional service backends Riven, Zilean, pgAdmin, TPA, mediastorm, migrated services, optional Metrics history
rclone Mounts Debrid/Usenet WebDAV storage CLI Debrid, stable Riven, InfiniDysk, Decypharr external-rclone mode
Zurg Debrid-backed WebDAV provider for use with rclone CLI Debrid, Riven

How they work

Dependency Startup requirement
Dev CLI Battery Runs before CLI Debrid only when its installed layout needs the standalone API. DUMB skips the managed Battery process for a recognized embedded layout.
PostgreSQL Starts before applications configured to use its managed databases.
rclone Makes a configured WebDAV source available as local files. The source service must be ready first.
Zurg Exposes Debrid content to an rclone instance configured to use Zurg.

A disabled dependency can prevent its consumer from becoming ready even if the consumer's own process starts. Check both logs when diagnosing startup failures.