| Congratulations on the launch. I like the landing page and the justification for the lack of a free tier. Cronjobs are often set-and-forget tasks that a free tier can attract a lot of free users that are hard to turn into paying customer. A well-defined pricing structure with well-defined features can bring customers who settle-in for the long term. That said, I think you will be competing in an up-hill battle with competitors. - CI/CD systems: This is how I would personally setup my jobs. I can go as far as SSH-ing to a remote server, and execute a script there, assert a certain output in the stdout, and mark build as failed. CI/CD system can then alert whoever is responsible. I don't think extremely technical developers are your target audience. The right balance would be a UI that can make this easy. - Random polling: As other commenters mentioned, a loose scheduler can help those who want just want to casually spot-check stuff. - Granular schedules: One might need to run an indexer every 10 minutes Mon-Fri 08:00-17:00, and hourly in weekends. Instead of using two schedulers, it might be both financially and cognitively easier to have just one scheduler. - Add features to expect a certain output to mark the job as passed. This can be an HTTP status code, a certain regular expression, a time-out threshold, etc. Good luck on your ventures! |