You could run superchronic on your web server as a separate process, but you’ll run into problems if you scale up your machines to more than one instance since you’d then be running multiple instances of superchronic.
I setup Recurring scheduled tasks (like cron) - #25 by Brad for my SaaS website, https://legiblenews.com, which sends out an email once per day or per week depending on the users’ subscription settings. It runs one, and only one, superchronic machine instance and the website is running on 2 machine instances.
You could trigger a URL from something like How to set up reoccurring jobs with GitHub Actions if you want to jump through the hoops of setting up auth, etc. for the service and are OK with Github actions going down, not being exactly on-time, etc.