OnlineOrNot's features
Monitoring for the things customers notice first.
Start with uptime checks. Add API assertions, Playwright browser checks, cron job monitoring, heartbeats, alert routing, and status pages when your team needs the next layer of confidence.
Production checks
All systems normal
Website
API
Cron
Alert route
- Website monitoring.
- Check production websites every 30 seconds from multiple regions. Verify more than reachability: status codes, SSL, redirects, expected content, and the pages customers actually depend on.
- Confirm failures before alerting, so one regional network blip does not wake the team.
- Monitor homepages, signup, checkout, docs, billing, and any endpoint that should always work.
- Send the alert to Slack, PagerDuty, SMS, email, Microsoft Teams, or a webhook.
- API monitoring.
- Test APIs the way your app relies on them. Send custom methods, headers, and bodies, then assert on status codes, response text, headers, and JSON values.
- Catch deploys that return the wrong payload while health checks stay green.
- Monitor authenticated endpoints with API keys, bearer tokens, basic auth, and custom headers.
- Use API checks for REST, GraphQL, webhooks, third-party integrations, and internal contracts.
- Browser checks.
- Run checks in real Chrome browsers for login pages, checkout flows, dashboards, and JavaScript-heavy apps. Use Playwright when a page needs interaction before it proves it works.
- Catch blank React, Vue, Angular, and single-page app screens after a deploy.
- Verify rendered text, critical paths, and customer-facing flows instead of just raw HTTP responses.
- Debug scripted failures with browser-check output alongside the rest of your monitoring.
- Cron job monitoring.
- Backups, queues, billing jobs, scripts, and scheduled tasks should not fail quietly. Give each job a check-in URL and OnlineOrNot alerts when the expected run never arrives.
- Know when backups stop running, billing jobs fail, or queues stop draining.
- Use curl, fetch, cron, GitHub Actions, workers, servers, or any language that can make HTTP requests.
- Route missed runs through the same alerts your team already uses for outages.
The first check most teams need.
Because 200 OK can still be wrong.
Real Chrome for the parts HTTP checks cannot see.
Stop trusting silent background work.
Alerts for how incidents actually get handled.
Not every failure deserves the same response. Page humans for urgent production outages, send lower-priority events to chat, notify customers from a status page, or route events into your own incident workflow with webhooks.
Are you a nerd? So are we.
Use the dashboard when you want speed. Use the API, CLI, assertions, regions, and webhooks when monitoring should fit the way your team provisions services, ships releases, and investigates incidents.
- API.
- Create checks during provisioning, sync status into internal dashboards, manage webhooks, and pull monitoring data into your own systems with an OpenAPI-backed HTTP API. Learn more
- CLI.
- Log in from your terminal, list checks, inspect status, and use OnlineOrNot in scripts or CI without opening the dashboard. Learn more
- Integrations.
- Connect chat, on-call, incident management, third-party status components, and custom webhook workflows so monitoring fits the way your team already responds. Learn more
There's more.
OnlineOrNot is built around the boring, high-consequence work of operating real software: detecting failures, routing alerts, and keeping customers informed while you fix the problem.
- Heartbeat monitoring.
- Let internal systems, servers, workers, devices, and long-running processes tell OnlineOrNot they are still alive. If the signal stops, the alert starts. Learn more
- Status pages.
- Publish incidents, maintenance windows, component status, uptime history, subscribers, private pages, and custom-domain status pages from one place. Learn more
- Flexible alerts.
- Send urgent failures to on-call, routine events to chat, customer communication to status pages, and everything else through webhooks. Learn more
The last monitoring setup you'll want to rebuild.
Start with one website check. Add the pieces you need as production gets more serious, without stitching together a separate tool for every kind of failure.
Get started for free