Kuvasz

Kuvasz is distributed as a Docker image, so it runs on any system that supports Docker, and there is an official Helm chart for Kubernetes. It requires a PostgreSQL database (version 14 or newer); the provided Docker Compose file sets one up alongside Kuvasz if you don't already have one. An interactive install script is also available for Linux and macOS.

By default you log in to the web UI with an admin username and password set via environment variables, and the password must be at least 12 characters. Kuvasz also supports OIDC single sign-on, optional API-key authentication for the REST API, and a separate dedicated key for the MCP endpoint. Authentication can be disabled entirely if you prefer to handle access control at the reverse proxy.

Yes. Monitors, notification integrations, and app-level settings can all be defined in a YAML configuration file, which makes it straightforward to keep your monitoring setup in version control. Alternatively, you can manage everything through the web UI or the REST API, and YAML configuration also serves as a way to back up and migrate your setup.

Kuvasz ships a full REST API (documented at api-docs.kuvasz-uptime.dev) that covers monitor management, status, and settings, plus an unauthenticated health endpoint for readiness probes. An MCP server lets AI assistants query monitor status and incidents and create or toggle monitors through natural language. Metrics can be exported to Prometheus and OpenTelemetry, and there is an official Home Assistant integration.

Built-in channels include email, Slack (via webhook or bot), Discord, Telegram, Microsoft Teams, Apprise, Pushover, PagerDuty, and custom webhooks. Integrations can be configured globally for all monitors or assigned per monitor. Services without a dedicated integration, such as Google Chat, Mattermost, or Signal, can be reached through custom webhooks or Apprise.