I am still struggling to see how such a basic service is actually used? Is it just because it's (presumably?) a GUI to create the job(s), and a portion of people deploying services today are just not comfortable writing a cron entry, or a systemd timer unit?<p>In all the time I've seen this type of thing posted, I've seen one explanation that had the potential to make sense: an app that runs via "Functions As A Service" (if you call it 'server less', I will hit you, with the server it's running on).<p>But the explanation <i>given</i> was "oh we need this function (which is just a container running somewhere really) to "remain hot" so it responds quicker...<p>So it's not that they needed to run some job every $n minutes, that was a kludge work around. What they needed was either a FAAS platform that allows for minimal worker scaling (you know, like forking/threaded web servers have done for decades); or, and hold onto your hats here, I know it's a crazy idea: they needed a server that's always on.<p>I know that the author probably put a heap of effort into this tool, just as all the other "cron as a service" authors did - but I'm sorry, I just don't get it. At this rate, I will not be surprised when an un-ironic "printf as a service" is posted to "Show HN".