<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Cronaut</title><description>Cronaut handles uptime monitoring, cron and heartbeat checks, and a public status page that updates itself. When a check fails, it opens the incident automatically. Built at an indie price.</description><link>https://cronaut.dev/</link><item><title>I stitched three tools together to know if my side project was down. So I built one.</title><link>https://cronaut.dev/blog/stop-stitching-monitoring-tools/</link><guid isPermaLink="true">https://cronaut.dev/blog/stop-stitching-monitoring-tools/</guid><description>UptimeRobot plus Healthchecks plus a status page is three logins, three bills, and a status page that goes stale. Here is why I built Cronaut to do all three on one engine.</description><pubDate>Sun, 07 Jun 2026 00:00:00 GMT</pubDate><category>product</category><category>launch</category></item><item><title>How to know if a cron job actually ran</title><link>https://cronaut.dev/blog/how-to-know-if-a-cron-job-ran/</link><guid isPermaLink="true">https://cronaut.dev/blog/how-to-know-if-a-cron-job-ran/</guid><description>Your cron job is configured, but did it run? Here is how to check cron logs on Linux, why logs are not enough, and how to get a real answer every time.</description><pubDate>Wed, 03 Jun 2026 00:00:00 GMT</pubDate><category>cron</category><category>tutorial</category><category>linux</category></item><item><title>Status pages without the busywork</title><link>https://cronaut.dev/blog/status-pages-without-the-busywork/</link><guid isPermaLink="true">https://cronaut.dev/blog/status-pages-without-the-busywork/</guid><description>A status page only earns trust if it is accurate during an incident, which is exactly when you have no time to update it. So let the monitoring do it.</description><pubDate>Wed, 03 Jun 2026 00:00:00 GMT</pubDate><category>status-pages</category><category>incidents</category></item><item><title>A Healthchecks.io alternative that also does uptime and status pages</title><link>https://cronaut.dev/blog/healthchecks-io-alternative/</link><guid isPermaLink="true">https://cronaut.dev/blog/healthchecks-io-alternative/</guid><description>Healthchecks.io is a clean cron monitor. If you also need uptime checks and a public status page, here is how Cronaut compares and when it is the better fit.</description><pubDate>Sat, 30 May 2026 00:00:00 GMT</pubDate><category>cron</category><category>comparison</category><category>alternatives</category></item><item><title>Cron monitoring that catches the job that never ran</title><link>https://cronaut.dev/blog/cron-monitoring-that-catches-silent-failures/</link><guid isPermaLink="true">https://cronaut.dev/blog/cron-monitoring-that-catches-silent-failures/</guid><description>A cron job that errors is easy to spot. The dangerous one is the job that quietly stopped running. Here is how heartbeat and deadline monitoring catch both.</description><pubDate>Wed, 27 May 2026 00:00:00 GMT</pubDate><category>cron</category><category>reliability</category></item><item><title>Introducing Cronaut: one tool for uptime, cron and status pages</title><link>https://cronaut.dev/blog/introducing-cronaut/</link><guid isPermaLink="true">https://cronaut.dev/blog/introducing-cronaut/</guid><description>Why we built Cronaut, and how running three monitoring jobs on one check engine lets your status page keep itself up to date.</description><pubDate>Wed, 20 May 2026 00:00:00 GMT</pubDate><category>product</category><category>monitoring</category></item><item><title>How to monitor cron jobs and get alerted when one fails</title><link>https://cronaut.dev/blog/how-to-monitor-cron-jobs/</link><guid isPermaLink="true">https://cronaut.dev/blog/how-to-monitor-cron-jobs/</guid><description>Cron runs your job and forgets about it. Here is a practical way to monitor cron jobs, catch silent failures, and get an alert the moment one stops running.</description><pubDate>Wed, 13 May 2026 00:00:00 GMT</pubDate><category>cron</category><category>monitoring</category><category>tutorial</category></item></channel></rss>