Monitor websites and APIs from your computer with notifications via Slack, email, and other channels when downtime or slow response occurs.
StatusOK is a self-hosted monitoring tool that checks websites and APIs for uptime and performance from your computer. It sends notifications via Slack, email, or other channels when servers are down or response times exceed configured thresholds, helping developers maintain service reliability.
Developers, DevOps engineers, and small teams who need a simple, self-hosted solution to monitor website and API uptime without relying on third-party SaaS services.
It offers a lightweight, configurable alternative to commercial monitoring services with support for multiple notification channels, InfluxDB integration for metrics storage, and easy Docker deployment for full control over monitoring infrastructure.
Monitor your Website and APIs from your Computer. Get Notified through Slack, E-mail when your server is down or response time is more than expected.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Monitoring rules and notifications are defined in a single config.json file, making setup straightforward without complex scripting, as shown in the README examples.
Supports running as a Docker container or with Docker Compose, including pre-configured examples for InfluxDB and Grafana integration, easing deployment.
Offers alerts via Slack, SMTP email, Mailgun, HTTP endpoints, and Dingding, with extensibility for custom clients, providing multiple ways to stay informed.
Can monitor REST APIs with configurable request types (GET, POST, DELETE), headers, and parameters, allowing detailed checks beyond simple uptime.
Only compatible with InfluxDB 0.9.3+, as stated in the README, and integrating other databases requires writing custom code, limiting flexibility.
Relies entirely on external tools like Grafana for dashboards, adding setup complexity and dependencies for data analysis.
Running as a background process requires manual job control (e.g., using 'jobs' and 'kill' commands), which is less robust than service managers like systemd.