kogutdocs

    Type to search page titles, headings and text.

    kogut documentation

    Server, container and uptime monitoring in one binary, with one alert that says what broke.

    Quick startWhat is kogut
    curl -fsSL https://kogut.dev/install | sh

    Browse the docs

    Getting startedInstall kogut, add your site and get your first alert in five minutes.InstallationLinux, Docker, Caddy, Tailscale, Coolify, Dokploy, Railway, NixOS and more.AgentServer and container metrics from a small agent that finds what runs on the host.MonitoringHTTP, TCP, DNS and ping checks, heartbeats, certificates, domains and internal services.Web appsPage views, Web Vitals and JavaScript errors from one script, without cookies.DeploysMark deploys from CI or GitHub, and see what changed.AlertsSensible defaults, sent to ntfy, Slack, Discord, Telegram, email or a webhook.IncidentsRelated alerts grouped into one incident, with likely causes and Copy for AI.Status pageA public page on your own domain with 90 days of history.When kogut itself is downRun kogut so alerts still arrive when a server fails, and back it up.Sign-inPasswords, OpenID Connect and forward auth from your proxy, with admins and viewers.Referencekogut.toml, environment variables, the CLI, the HTTP API and MCP tools.

    One alert that explains itself

    Checks, servers, containers, visitors and deploys share one timeline. When something breaks, kogut looks at what happened around it and sends one alert with what is affected and what probably caused it. The incident behind the link shows the evidence, such as memory rising after the deploy.

    How kogut finds the likely cause 
    api is down since 14:07 (2 signals failing)

API health failing since 14:07: status 503, expected 2xx.
Checkout API failing since 14:08: no answer within 10000 ms.
Likely cause: deploy of api 3f9c2e1 at 14:02.
Also affected: website.

https://kogut.acme.com/incidents/42