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 for you. 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 where you work
Email, webhooks and Slack channels 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 subscription does the work of three. Start on the free tier and move up when you grow.
Free
For your first side project.
- 5 monitors
- 1-minute checks
- 1 status page
- Email alerts
- 30-day history
Indie
Enough room to run real projects.
- 50 monitors
- 30-second checks
- Unlimited status pages
- Webhook & Slack alerts
- 1-year history
- Custom status-page domain
Studio
For a portfolio of products.
- 250 monitors
- Team members
- Priority alerting
- SSO
- Priority support
From the blog
Notes on keeping things online
Status pages without the busywork
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.
Cron monitoring that catches the job that never ran
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.
Introducing Cronaut: one tool for uptime, cron and status pages
Why we built Cronaut, and how running three monitoring jobs on one check engine lets your status page keep itself up to date.
Monitor everything. Post nothing.
Set up uptime, cron and status pages in a few minutes, then let a failed check handle the incident reporting for you.