Introducing Cronguard: Backup, snapshot, restore your crontabs - and monitor them for signs of alteration or intrusion.
Only from Cronly... π
https://t.co/azP5Gp6M6A
So after a few months of leaving @CronlyApp on glide mode, we're ready to amp it up and excited to do so.
We're still in touch with @robinmartijn and through him met another great dev @CoenSchutte who's been involved in the next stage of @CronlyApp
...stay tuned for that.
Belatedly picking up on this thread after *finally* logging into the Twitter account π€£
We're the new owners (@easyDNS being the mother ship) - Cronly also slightly outside of our wheelhouse, but not by much.
Let's expand on Robin's thread from the acquirer side a bit... π
In December last year, I came across Cronly on MicroAcquire. A small tool for developers to monitor cron jobs. It was already finished and had paying customers, so it was mostly a marketing job.
I couldn't do that yet, but how hard could it be, right?
Yet, in a weird similar fashion to @robinmartijn - we don't know much about marketing either!
Our main driver on @easyDNS over the years was always word-of-mouth, but that's changing.
After exactly 150 days, Cronly version 2 launched!
π I lost all of my (paying) customers
π Existing API endpoints have broken
π There are still a lot of bugs
And despite all that, I'm still stoked! π₯
Here's why π
On June 1st, Cronly version 2 will be launched.
Because this is an entirely new, rewritten version, current customers will lose their accounts. All monitors will stop working from that day.
Of course, this sucks. A letter to my current customers:
https://t.co/klqJm6h3NJ
I MAY FINALLY TELL YOU! π₯
I purchased @CronlyApp on @microacquire!
Not only that, but I'll be building it completely in public.
To prove that to you, here are the most important metrics π
After spending the last few months on stabilising our monitors. We've now added a new feature: SSL certificates monitoring. #monitoring#developer#tools