@tjholowaychuk first off, thanks for being such a great inspiration for all engineers looking to start their own thing - bootstraping anything ain't easy at all. i love the fact that you share your process along the way. re product feedback - have you considered making it even more API oriented by supporting things such as "chained" (or connected) checks. eg. login - get auth token then reuse the auth token to do fetch a resource etc.

@vesln thanks man! Should be fun :). I've thought about leveraging scripting for the assertion side of things, but using it for full control over the requests could be pretty interesting!

@tjholowaychuk just wanted to +1 on what @vesln - thanks for being an inspiration to a ton of engineers :)

@tjholowaychuk Great job! Given your price for 30 checks, the one thing that keeps me with Pingdom is the Public Status Page. If you can make this happen, you've got yourself a new customer :)

@benoit great to hear! I'll have it in the pipeline soon. Updates will be in-app / https://blog.apex.sh/ if you're interested in staying informed there

@vesln thank!

@konradcaban great list! Thanks :)

@hugocore public status pages are certainly on the list :)

@hugocore the first iteration is out! https://blog.apex.sh/apex-ping-p...

@itsnblackburn it's definitely on the list, I figured it was reasonable low priority compared to other features but I will make note :) thanks!

@jonathanmarvens haha thanks for the support! :D much appreciated