If you are self-hosted in Polaris land, I think we primarily schedule things through the MS SQL job scheduler. Since there are other jobs already there, it gives you the advantage of consolidating all of your scheduled stuff into one place.
We do have a few things that we update outside of SQL jobs (including things like the bib dedupe queue) and those are typically managed through Hangfire, again because it is the defacto standard in Microsoft .NET land and has a lot of robustness for handling failures, etc.
