[jmeyer2k]

The landing page looks good. The UI screenshots are a little small and hard to read on my screen, but overall, the design is great.

You might also want to consider explicitly stating the value proposition: how will I save money/time/etc by using your service?

One possible use case that you might be missing are recurrent tasks that I want to ensure are run. For example, for my service, https://pagecheck.app, I run tests every 30 minutes or so and I want to make sure those tests succeed. I couldn't find a job scheduler that allows for recurrent tasks, so I ended up writing my own Javascript library for Postgres: https://github.com/meyer9/postqueue

I'd love an external service that ensured that my recurring tasks run reliably, but it would make 0 sense for me to use your service at that price level. I have hundreds or thousands of scheduled tasks, but I can't pay thousands of dollars to ensure that they are run.

[Ayesh]

Pretty much every CI/CD system supports scheduled builds. GitLab CI, GitHub Actions, Travis, Circle CI, and even Jenkins do.

[jmeyer2k]

Tests in my case mean page checks I run for my customers. Not tests on my code.