1
Step 1Open the server Apps tab
Select your VPS, open the Apps tab, and start a new app deployment. Keep sensitive server details hidden before capturing or sharing screenshots.
Back to all templates
Sonarr
Application512MB+ RAM
PVR for Usenet and BitTorrent - TV show management and automation
pvrtv-showsautomationarr-stack
Deploy Sonarr in 3 Steps
1
Connect Your VPS
Add your server credentials to Server Compass
2
Select Sonarr
Choose from our template library
3
Deploy & Configure
Fill in settings and click Deploy
No Docker knowledge required
Step-by-step deployment guide
Deploy Sonarr on a VPS with Server Compass
Use the Sonarr template in Server Compass to deploy a self-hosted TV show management and automation server with persistent config, TV, and downloads volumes on your VPS, then verify the Sonarr web UI in a browser.
About 7 minutesBrowser verified
2
Step 2Choose an app template
Click New App and choose the template deployment path so Server Compass can load the built-in catalog.
3
Step 3Search for Sonarr
Use the template picker search to find Sonarr in the Server Compass template catalog.
4
Step 4Select the Sonarr template
Choose the Sonarr template. Server Compass fills the Sonarr image, host port, published server URL, and persistent config, TV, and downloads volumes.
5
Step 5Review the Sonarr settings
Confirm the app name and compose services. In this run, the app was named sonarr-demo and used host port 8989.
6
Step 6Deploy Sonarr
Review the generated environment values, confirm the port is available, and click Deploy Now.
7
Step 7Watch the deployment progress
Keep the deployment modal open while Server Compass uploads the compose file, pulls the Sonarr image, starts the container, and verifies the stack.
8
Step 8Confirm Sonarr is running
After deployment finishes, return to the Apps tab and confirm the Sonarr app is marked Running with its application URL available.
9
Step 9Open Sonarr in the browser
Open the application URL in a browser. The Sonarr web UI confirms the site is reachable.
After Sonarr Opens
- Configure authentication, indexers, download clients, and root folders before using Sonarr for production TV automation.
- Mount real TV and downloads directories before adding production series and download clients.
- Add a domain and HTTPS before exposing the TV automation server to users.
- Configure users, libraries, metadata providers, and remote access settings before production use.
- Back up the Sonarr config volume before relying on the server for production automation.
Sonarr deployment questions
What does the Sonarr template deploy?
It deploys the LinuxServer Sonarr container with persistent config, TV library, and downloads volumes mounted at /config, /tv, and /downloads.
Which port did the tutorial use?
The tutorial used host port 8989, which maps to the Sonarr web server on container port 8989.
Why does the guide stop at the first-run web UI?
The tutorial verifies the clean first-run web UI because real library paths, users, metadata providers, and remote access settings depend on the production server.
Should this become a blog post?
No. The deployment guide should live on the Sonarr template detail page and be linked from the reusable template deployment docs page.
Why Self-Host Sonarr?
Sonarr is a PVR for Usenet and BitTorrent that automatically downloads and organizes your TV shows. Self-hosting gives you a fully automated media pipeline that works 24/7 on your server, monitoring for new episodes and downloading them automatically.
Automatic TV show monitoring and downloading
Quality profiles for managing storage vs quality trade-offs
Calendar view showing upcoming episodes
Integrates with download clients and media servers
Rename and organize files according to your naming scheme
Sonarr vs Alternatives
Sonarr vs Manual downloads
Manual searching is tedious. Sonarr automates the entire process — monitoring, downloading, renaming, and notifying your media server.
Sonarr vs SickChill
SickChill is outdated. Sonarr has a modern API, active development, and better integration with the Arr stack.
Sonarr vs Medusa
Medusa is functional but less maintained. Sonarr has a larger community, more frequent updates, and better API support.
Why Deploy Sonarr with Server Compass?
Server Compass deploys Sonarr with persistent configuration and connects it to your media server stack. Pair with Prowlarr and Radarr from our template library for a complete automated media pipeline.
Download Server CompassAfter Deployment
After deploying Sonarr with Server Compass, complete these steps to finish setup
1
Configure download clients
2
Add indexers
3
Add TV series to monitor
Need help? Check out our documentation for detailed guides.
Sonarr FAQ
Common questions about self-hosting Sonarr
How do I deploy Sonarr with Server Compass?
Simply download Server Compass, connect to your VPS, and select Sonarr from the templates list. Fill in the required configuration and click Deploy. The entire process takes under 3 minutes.
What are the system requirements for Sonarr?
Sonarr requires a minimum of 512MB RAM. We recommend a VPS with at least 1024MB RAM for optimal performance. Any modern Linux server with Docker support will work.
Can I migrate my existing Sonarr data?
Yes! Server Compass provides volume mapping that allows you to import existing data. You can also use standard Sonarr backup and restore procedures.
How do I update Sonarr to the latest version?
Server Compass makes updates easy. Simply click the Update button in your deployment dashboard, and the latest Sonarr image will be pulled and deployed with zero downtime.
Is Sonarr free to self-host?
Sonarr is open-source software. You only pay for your VPS hosting (typically $5-20/month) and optionally Server Compass ($29 one-time). No subscription fees or per-seat pricing.
Ready to Self-Host Sonarr?
Download Server Compass and deploy Sonarr to your VPS in under 3 minutes. No Docker expertise required.
Download Server Compass