Skip to content

Dozzle vs Drydock

Dozzle is a best-in-class real-time log viewer. Drydock focuses on container update monitoring and safe auto-updates. They solve different problems and work well together — Dozzle for log analysis, Drydock for keeping containers up-to-date.

Dozzle — ActiveDrydock — Active

Feature Comparison

Here's how we compare on the features that matter most.

FeatureDozzleDrydock
Project statusActively maintainedActively maintained
LanguageGoTypeScript
Web UIYesYes
Primary focusReal-time log viewingContainer update monitoring
Image update detectionNoYes, across 23 registries
Auto-update containersNoYes (optional, monitor-first)
Security scanningNoTrivy + SBOM + cosign verification
Automatic rollbackNoYes, on health check failure
Image backupNoPre-update backup with retention
NotificationsSlack, Discord, Ntfy, webhooks20 native trigger integrations
MQTT / Home AssistantNoYes
Prometheus metricsNoFull /metrics endpoint + Grafana template
Audit logNoYes, with REST API
Log viewerAdvanced (SQL, split-screen, regex)Basic (level filtering, auto-fetch)
Log analytics / SQLYesNo
Resource monitoringYes (CPU, memory, network — live)Planned
Multi-host agentsYesYes (SSE-based)
Container start/stop/restartYesYes
OIDC authenticationVia forward proxy (Authelia, Authentik, Cloudflare)Yes (Authelia, Auth0, Authentik)
RBACYesPlanned
Docker SwarmYesPlanned
KubernetesYes (since v8.11)Planned (v2.0.0)
LicenseMITAGPL-3.0

Key Differentiators

What we built that Dozzle doesn't cover.

Image Update Detection

Dozzle is a log viewer — it doesn't monitor for image updates. Drydock continuously checks 23 registries and notifies you when new versions are available.

Security Scanning

Trivy vulnerability scanning, SBOM generation, and cosign signature verification before updates are applied. Dozzle has no image security capabilities — no vulnerability scanning, SBOM generation, or signature verification.

Safe Update Pipeline

Dry-run preview, pre-update backup, automatic rollback on health check failure, and maintenance windows. Dozzle doesn't manage container updates at all.

20 Trigger Integrations

Drydock notifies across 17 native channels — Slack, Discord, Telegram, Teams, Matrix, SMTP, MQTT, and more — plus Docker, Docker Compose, and Command actions. Dozzle sends runtime alerts (log patterns, CPU/memory spikes, container crashes) via webhooks to Slack, Discord, or ntfy.

23 Registry Integrations

Dedicated integrations for Docker Hub, GHCR, ECR, GCR, GAR, GitLab, Quay, Harbor, Artifactory, Nexus, and more.

Works Great Together

Dozzle for deep log analysis and Drydock for update monitoring — they solve different problems and can run side-by-side in your Docker stack.

Using Dozzle?

Drydock and Dozzle are complementary tools. Use Dozzle for real-time log viewing and Drydock for monitoring container updates, applying them safely, and getting notified across 20 services. One Docker command to add Drydock.

Quick start
$ docker run -d \
  --name drydock \
  -v /var/run/docker.sock:/var/run/docker.sock \
  -p 3000:3000 \
  -e DD_ANONYMOUS_AUTH_CONFIRM=true \
  codeswhat/drydock  # open dashboard — add real auth before exposing this

Ready to try Drydock?

No SaaS subscription, no data sent off your host, and we ship updates fast.