Cronitor

San Francisco, CA, USA
2014
  |  By Shane Harter
It might surprise you that the version of cron that runs on your server today is largely compatible with the crontab spec written in the 1970s. One downside of this careful backwards compatibility is that jobs, even on the same server, can be created and scheduled differently.
  |  By Shane Harter
Cron job failures create chaos for your users and your team. After analyzing over a million failure reports these 4 problems emerged as the most likely causes of preventable job failures.
  |  By Shane Harter
In the first 30 days after moving Cronitor to AWS in January, 2015 we collected $535 in MRR and paid $64.47 for hosting, data transfer and a domain name. In the time since we’ve continued to increase our footprint, level-up instances and add more managed services. Despite the AWS reputation as an expensive foot-gun we’ve improved availability while keeping our bill consistently close to 12.5% of revenue. Here’s a look.
  |  By Shane Harter
Ten years ago, still young in my career building software things, I got my first taste of DevOps. We didn’t call it that back then but for the first time I had to worry about how my software would be delivered to the world.
  |  By Shane Harter
In June, 2014 we shipped an MVP for Cronitor that was so basic I cringe a little when I think about it. It didn’t do very much, most features were cut, but it shipped with paid subscriptions on day one. We sold one to a friend. My earliest work on subscription integration was primitive: The first month’s charge was captured during the upgrade but we created each subscription by hand in the Stripe dashboard.

Cron monitoring and uptime healthchecks for your websites, services and APIs.

Monitor cron jobs, micro services and almost anything else. Realtime alerts when your tasks and services don't run on schedule, run too long or fail unexpectedly. Easier cron troubleshooting and no more silent failures.

Solve cron job, scheduled task, and data pipeline observability for your team: When cron jobs, scheduled tasks and data pipelines fail, the uptime and integrity of your system is at risk. With easy no-code integration and alerts when things go wrong, find out fast when jobs fail (or never start) and detect pipeline problems early.

Monitor the websites, APIs and services your team relies on in production with healthchecks: Downtime happens to everybody and every minute can impact your customers, injure your brand and cost you the trust of your stakeholders. Create simple network availability checks or build complex tests with multiple assertions. Healthchecks ensure that when problems happen in production, you know fast.

Respond quickly when bad things happen with alerts where you need them: Email, Slack, PagerDuty and more: Response and recovery can only begin when the right person or team is notified. Ensure you reach the right people for every kind of failure with Email and SMS alerts and easy integrations like Slack and PagerDuty. Combine different alert channels into notification lists for easy reuse.