You shipped it. Now something has to watch it while you're not looking.
Uptime OS checks your sites, APIs and scheduled jobs from the outside, alerts you where you already work, and stays out of your way otherwise.
Heartbeat monitoring for cron & background jobs
Your job pings a unique URL on schedule; we alert the moment it goes quiet, not when someone notices data stopped updating.
Alerts where you already are
Outbound webhooks to Slack, Discord, or your own endpoint, alongside email, WhatsApp and SMS.
Confirmed before it pages you
A failure has to repeat before it's treated as real, so a flaky network blip doesn't wake anyone up.
One honest note on what this isn't
There's no public REST API yet for provisioning monitors programmatically — sites are added through the dashboard today. What you do get is outbound webhooks: point any alert at Slack, Discord, or your own endpoint, and wire it into whatever you already use for on-call.
- TCP checks confirm 80/443 are accepting connections, plus SSH/SMTP as an informational signal
- Heartbeat monitoring for any scheduled job via a unique ping URL
- Ask us if scripted provisioning matters for your setup — worth a conversation
What's watched, specifically
- HTTP & HTTPS monitoring with automatic retries
- TCP port checks (80/443, plus SSH/SMTP as informational)
- Heartbeat / cron monitoring via a unique ping URL
- Outbound webhooks — Slack, Discord, or a generic endpoint
- SSL certificate & domain expiry, flagged 30 days out
- Malware & defacement scanning
Questions developers ask
Not yet as a public API — today, sites are added through the dashboard. If scripted provisioning matters for how you'd use this, tell us — it's worth a conversation.
Yes, via outbound webhooks — set one up once and route alerts wherever your team already looks.
Add a heartbeat monitor — you get a unique URL your job pings on completion. Miss enough pings, and we alert you.
Yes — TCP checks confirm your server is accepting connections on 80/443, alongside an informational check on SSH (22) and SMTP (25/587).
Bring a URL and a cron job to the call.
We'll show you exactly what gets watched, and where the honest gaps are for your setup.