Stop stitching together three monitoring tools
Cronaut watches your sites, your cron jobs and your SSL certificates. When a check fails, it opens an incident on your public status page automatically. One tool instead of UptimeRobot, Healthchecks and Instatus, at a price that works for indie hackers.
No credit card required · Free tier · Cancel anytime
HTTP · 142 ms · 99.98%
CRON · 0 2 * * * · last 3h ago
SSL · expires soon
One subscription instead of
What you get
Three monitoring jobs, one engine
Uptime, cron and SSL checks all run on the same check engine. That is why your incidents, status page and live updates come from one place instead of three.
Active uptime monitoring
HTTP, keyword and SSL checks run from a probe fleet you can scale out. Reads are capped, intervals are fast, and latency is tracked on every check.
Cron and heartbeat checks
Send a ping when a job starts, succeeds or fails. Cronaut knows when the next ping is due, so it catches the job that never ran, not only the one that errored.
A status page that updates itself
A public, SEO-friendly status page built from your incidents and state changes. It is cacheable behind a CDN and updates live over SSE.
Incidents without the typing
When a check fails, Cronaut opens an incident on your status page. When it recovers, Cronaut closes it. You never post an update by hand.
Alerts when it matters
Email, Slack, Discord and webhook alerts fire when a monitor actually changes state. Flap detection keeps a brief blip from waking you up.
Indie price
Made for indie hackers and small teams. It does three jobs well and skips the rest, so you get one plan instead of a Datadog-sized bill.
How it works
The status page that updates itself
Every change in Cronaut comes down to one event: a monitor changing state. That single event writes the log, opens the incident and pushes the live update, so you never touch a status page by hand.
Add a monitor
Give Cronaut a URL, a cron schedule or a TLS endpoint. Whatever you need to watch, it all goes in one place.
A check fails
The check engine handles deadlines, grace periods and flap detection, then records one state change from UP to DOWN.
The incident posts itself
That state change opens an incident on your public status page and fires your alerts. When the check recovers, the incident closes on its own.
Pricing
Indie price, no surprises
One plan replaces UptimeRobot + Healthchecks + Instatus.
Start on the free tier and move up when you grow.
Free
For your first side project.
- 10 monitors
- 3-minute checks
- 1 status page
- Email, Slack & Discord alerts
- 30-day history
Indie
Enough room to run real projects.
- 50 monitors
- 30-second checks
- Unlimited status pages
- Custom status-page domain
- 1-year history
Studio
For a portfolio of products.
- 200 monitors
- 15-second checks
- Team members
- Priority support
- 3-year history
From the blog
Notes on keeping things online
What does 99.9% uptime actually mean?
A plain-English guide to uptime percentages: how much downtime each of the nines really allows, why the math surprises people, and how to think about SLAs without fooling yourself.
How to monitor SSL certificate expiry before it takes your site down
An expired TLS certificate is a full outage that you can see coming weeks ahead. Here is how SSL certificates expire, why auto-renewal is not enough, how to check expiry yourself, and how to monitor it so a renewal never slips.
How to monitor website uptime, and the best practices that make it reliable
A practical guide to monitoring whether your website is actually up: why it matters, how external checks work, and the best practices that stop both real outages and false alarms.