NeutArr¶

NeutArr is DUMB's default backlog-search automation service. It continuously searches for missing or upgraded content in your Arr applications. It periodically triggers searches in Radarr, Sonarr, Lidarr, and Whisparr to find better quality releases or fill gaps in your library.

Overview¶

NeutArr integrates with your Arr stack to automate the hunt for:

• Missing content - Movies, TV episodes, or music not yet downloaded
• Quality upgrades - Better releases that meet your quality profiles
• Cutoff unmet - Content below your configured quality cutoff

DUMB supports multiple NeutArr instances, allowing you to run separate hunters for different Arr configurations (e.g., one for Decypharr-linked services and one for NzbDAV-linked services).

Service relationships¶

Default ports¶

Additional NeutArr instances must use unique ports.

Automation in DUMB¶

DUMB auto-populates NeutArr with Arr instances that opt in.

1. Set use_neutarr: true on the Arr instances you want NeutArr to manage.
2. (Optional) Set core_service on the NeutArr instance to filter which Arr instances it pulls in.

Example Arr instance:

"radarr": {
  "instances": {
    "Decypharr": {
      "enabled": true,
      "core_service": "decypharr",
      "use_neutarr": true,
      "port": 7878,
      "config_file": "/radarr/decypharr/config.xml"
    }
  }
}

Example NeutArr instance filter:

"neutarr": {
  "instances": {
    "Decypharr": {
      "core_service": ["decypharr", "nzbdav"]
    }
  }
}

With that filter in place, the NeutArr instance only receives Arr entries whose core services overlap the NeutArr instance. If core_service is left blank on a NeutArr instance, it can receive all Arr instances with use_neutarr: true. For deeper behavior details, see Core Service Routing.

Configuration settings in dumb_config.json¶

Below is a sample configuration for NeutArr within the dumb_config.json file:

"neutarr": {
  "instances": {
    "Default": {
      "enabled": false,
      "core_service": "",
      "process_name": "NeutArr",
      "repo_owner": "I-am-PUID-0",
      "repo_name": "NeutArr",
      "release_version_enabled": false,
      "release_version": "latest",
      "branch_enabled": false,
      "branch": "main",
      "suppress_logging": false,
      "log_level": "INFO",
      "port": 9705,
      "auto_update": false,
      "auto_update_interval": 24,
      "clear_on_update": false,
      "exclude_dirs": [
        "/neutarr/default/config"
      ],
      "platforms": [
        "python"
      ],
      "command": [
        "/neutarr/default/venv/bin/python",
        "main.py"
      ],
      "config_dir": "/neutarr/default",
      "config_file": "/neutarr/default/config/general.json",
      "log_file": "/neutarr/default/config/logs/neutarr.log",
      "env": {
        "NEUTARR_CONFIG_DIR": "/neutarr/default/config",
        "NEUTARR_PORT": "{port}"
      }
    }
  }
}

Configuration key descriptions¶

• enabled: Whether to start this NeutArr instance.
• process_name: Display name used in logs and the frontend.
• repo_owner / repo_name: GitHub repository to pull from.
• release_version_enabled / release_version: Use a tagged release if enabled.
• branch_enabled / branch: Use a specific branch if enabled.
• suppress_logging: If true, disables log output for this service.
• log_level: Logging verbosity (e.g., DEBUG, INFO).
• port: Port the NeutArr web UI is exposed on.
• auto_update: Enables automatic self-updates from GitHub.
• auto_update_interval: How often (in hours) to check for updates.
• clear_on_update: Clears build artifacts or cache during updates.
• exclude_dirs: Prevents specific directories from being affected by updates.
• platforms: Required runtime (typically python).
• command: The command used to launch NeutArr.
• config_dir / config_file: Where configuration files are stored.
• log_file: Path to the NeutArr log file.
• env: Environment variables passed at runtime.

Multi-instance support¶

DUMB supports running multiple NeutArr instances to work with different Arr configurations. The default config ships with a single Default instance.

Each instance maintains its own:

• Configuration directory
• JSON config files
• Web UI port
• Log output

NeutArr web UI¶

NeutArr provides a web interface for:

• Configuring which Arr services to monitor
• Setting search intervals and limits
• Viewing hunt status and history
• Manual search triggers

Access the UI at http://<host>:<port> or through the DUMB frontend's embedded service UI feature.

Tips¶

• Start with conservative search intervals to avoid rate limiting from indexers.
• Use separate NeutArr instances when you have Arr services connected to different download clients.
• Monitor logs via the DUMB frontend or from the log_file path defined for each instance.
• NeutArr respects your Arr quality profiles, so configure those first.

Resources¶

• NeutArr GitHub Repository