Overview

Neouptime watches your websites, servers, and certificates from the outside and tells you the moment something breaks. You point it at a URL or host, it checks on a schedule, and it alerts the people you choose when a check fails.

The core loop

1. Create a monitor for each thing you want to watch (a website, an API, a port, a TLS certificate).
2. Add one or more alert channels (email, Slack, or webhook) so you hear about problems.
3. When a monitor fails its threshold, Neouptime opens an incident and notifies your channels.
4. When the check recovers, the incident resolves and the recovery is sent out too.

Putting it in front of others

• Groups organize monitors into sections like "Production" or "APIs".
• Clients attach monitors to the customer they belong to — useful for agencies.
• Status pages publish a public, login-free uptime page at /status/<slug>.
• Maintenance windows suppress alerts and exclude planned downtime from your SLA.
• Reports turn raw checks into client-ready uptime summaries.