Seerr doesn't download torrents from JF, it adds a request to either Sonarr or Radarr (which grabs the torrent from an indexer, adds it to your torrent client, then when it finishes, moves it appropriately, and let's JF know that there is something new, and tells Seerr that it finished)

You basically set up a regular *arr stack then put Seerr on top of that. As long as you set up the underlying *arr stack correctly, then you should be able to minimally touch it and everything should be fairly good on its own. I open my underlying stack about once a month to clear out any weird issues, but I could go longer if I wanted.