2026.10.18
Profilarr: Self-Hosted Configuration Management for Radarr and Sonarr
Profilarr helps self-hosted media-server operators build, test, and sync Radarr and Sonarr configuration. Review its Docker, Arr-version, parser, proxy, and permission considerations before deployment.
What it is for
Profilarr is a configuration management platform for Radarr and Sonarr. It is aimed at self-hosted media-server operators who want to reduce repeated setup and keep configuration aligned across multiple Arr instances. The project is licensed under AGPL-3.0 and is presented as a self-hosted tool rather than a hosted service.
Its central workflow is to collect quality settings, Custom Formats, regular expressions, and media-management rules in one place, then test and deploy them. Users can link databases such as Dictionarry, TRaSH Guides, and Dumpstarr, or create and share their own database using the PCD template. This is particularly relevant to operators who maintain several instances or frequently adjust download-quality policies.
Known capabilities
For building configurations, Profilarr can group and order qualities, assign Custom Format scores per application, and manage naming conventions, media settings, quality definitions, and delay profiles. The README also describes local tweaks that persist across upstream updates through conflict handling.
For testing, regular expressions can be checked with embedded Regex101 test cases. Custom Formats can be evaluated against releases with a breakdown of which conditions pass or fail, while Quality Profiles can simulate release scoring and ranking for a movie or series. Custom Format and Quality Profile testing requires the separate parser service; linking, syncing, and other functions do not require it.
For deployment, Profilarr can sync configurations to multiple Arr instances, run automated searches with filters, selectors, and cooldowns, and bulk-rename files and folders with dry-run previews. Scheduled jobs cover sync, upgrades, renames, backups, and cleanup. Notifications are available through Discord, Telegram, Slack, ntfy, Pushover, Gotify, Apprise, and generic webhooks. Release v2.2.0 also added release-group filtering and release-date sorting in library views.
Constraints and deployment considerations
Check the host environment first. The README requires a Docker host with Linux kernel 3.17 or newer and explicitly says older Synology DSM installations using kernel 3.10 are not supported by Profilarr v2. The listed Docker platforms are linux/amd64 and linux/arm64. The Arr requirements are Sonarr v4/v5 and Radarr v5/v6; Sonarr v5 is still described as experimental in the README.
Release-channel choice also matters. latest tracks the newest stable release, while develop contains pre-release builds under testing and is not guaranteed stable. Exact version tags do not update automatically, and major-version tags remain within the selected major version. The README recommends keeping the profilarr and profilarr-parser images on the same channel, so mixing tags should be avoided.
Reverse-proxy and OIDC deployments require careful public-URL and callback configuration. The README also states that the runtime API key is not persisted to SQLite or bcrypt-hashed, and that it has full access. Operators should therefore assess secret handling, network exposure, and backup practices in their own environment. The supplied sources provide no independent security audit or performance measurements, so they do not support conclusions about security, capacity, or resource requirements.
Profilarr is best suited to users comfortable maintaining Docker services, working with Radarr/Sonarr configuration, and managing more than one instance or a complex quality policy. For a single lightly configured Arr instance, the operational overhead may provide less benefit. Adoption should follow an environment check covering kernel, Arr versions, proxy setup, persistent-volume permissions, and whether the parser service is actually needed.
Sources
Sources checked: 2026-10-18