Beta · Free tier, no card

Nobody reads your container logs. Dozzle Cloud does.

The average connected stack logs 75 distinct errors a day that nobody is watching. Every morning Dozzle Cloud reads them and tells you the two or three worth fixing — with no alert rules to configure.

How it works

It goes looking. You don't have to set anything up.

  1. 1

    It reads your error logs

    Every morning, without being asked. No alert rules to write, nothing to configure.

  2. 2

    Groups them into real problems

    Three hundred lines of the same error are one problem, not three hundred. The typical stack has 75 of them.

  3. 3

    Investigates what looks serious

    Pulls logs, inspects the container, checks what changed — and weighs what it already told you yesterday.

  4. 4

    It decides what to do

    With all of that context, every event lands in one of three places.

    Ignore
    Seventy-two of the seventy-five. Normal for your stack, and it stays that way.
    Track
    Still happening on day four, three times worse than yesterday. You see that it changed, not that it exists.
    Tell you
    Two or three things worth your morning, with what broke and where.

Two ways to hear about it.

The daily review is not real time, and it is not trying to be. It is the one that catches what nobody thought to watch for.

Every morning

It goes looking

Reads the error logs you are already sending, groups them, and reports what changed. Works the moment you connect — nothing to configure.

The moment it breaks

You set the rule

Write alert rules in your own Dozzle for the containers you care about. Dozzle Cloud triages what fires, groups the repeats, and sends one alert instead of forty.

One alert. The whole story.

Cause first. Counts grouped. Sent wherever you already are.

nginx-proxy
14:23:01ERROR: connect ECONNREFUSED 10.0.2.4:3000
14:23:01ERROR: upstream timed out (110: Connection timed out)
14:23:02WARN: retry attempt 1/3 for service payment-api
14:23:03ERROR: connect ECONNREFUSED 10.0.2.4:3000
14:23:04ERROR: upstream timed out (110: Connection timed out)
14:23:05ERROR: connect ECONNREFUSED 10.0.2.4:3000
14:23:05WARN: circuit breaker opened for payment-api
SlackEmailDiscordTelegramntfyWeb push

Ask the agent

When you want the why, just ask.

Every alert is one tap from a conversation. Walk through the failure, pull related logs, see what changed. In Telegram, Discord, or the web app.

9:41
Dozzle Cloud Assistant
Online
Message

Or bring your own AI

Preview

MCP for Claude, Cursor, anything.

Wire Dozzle Cloud into the assistant you already use. Read-only access to events, logs, and container state. Free on every plan.

How it works
$ claude mcp add dozzle-cloud \
--url https://mcp.dozzle.dev/mcp
--header "Authorization: Bearer dz_mcp_…"
I want to know when my containers crash overnight. But I don't want to get spammed about every incident over and over. One notification is enough.
Anders, self-hosted Dozzle user

Pay for the quiet, not the volume.

Free

$0

One homelab, read every morning.

500 triaged events / month

Most popular

Pro

$5/mo

Every host you run, two weeks of history.

10,000 triaged events / month

Team

$15/mo

Headroom for a real production stack.

50,000 triaged events / month

Connect your DozzleCompare plans

Free tier, no credit card.