Monitoring for Kubernetes and Docker, without running it yourself.
Install one agent. WatchLog Cloud runs the backend, keeps your data and tells you in plain words why something broke: every node, pod, container, service and the traffic between them.
Prefer your own servers? Self-host the same product for free (AGPL-3.0, no limits).
From signup to your cluster
- Sign up with GitHub, Google or email
About a minute. No card, no company form.
- Run one command
helm install watchlog-agent … --set watchlog.clusterToken=wl_ct_•••• - Watch it connect, live
A checklist ticks as the agents, the metrics and the service map arrive. First data in under a minute in our tests.
Works with
Kubernetes
Docker
and reads
Redis
PostgreSQL
MySQL and MariaDB
MongoDB
Nginx
Traefik
RabbitMQ
Kafka
Your cluster data, kept like it matters.
The agent is read-only and never reads Secrets, ConfigMap data or environment values. In the Cloud, every organization is isolated, and that isolation is tested on every change.
Isolated per organization
Row-Level Security in the database and an organization check on every query, API call and MCP tool, tested on every change.
How Cloud keeps data apart →A DPA and our subprocessors
Read the data processing agreement and the full list of services that process data for Cloud. Backups are encrypted before they leave the server.
Subprocessors →2FA and audited access
Two-factor sign-in for any account, required for Owners of paid organizations. Staff see your data only in a read-only support session you can review.
Support sessions →Leave any time
Export your configuration and metrics, or delete the organization, with 7 days to undo. Or move to the free self-hosted edition: same product.
Export and deletion →
The answers you need, without assembling a stack.
Why is this broken? WatchLog tells you.
Every alert, failing connection and crashing pod or container gets its probable cause: one sentence, the evidence behind it, and what was checked. Fixed rules over the data WatchLog already collects; no AI, no scores.
frontend fails because api was scaled to 0: nothing answers its calls.
shop-worker-1 is OOM-killed when it reaches its 256 MiB memory limit: 12 times in the last hour.
Service map from real traffic
eBPF sees every connection: who talks to whom, failures and latency, between pods or containers. No sidecars, no code changes.
What eBPF reads →Restart reasons, not just counts
OOMKilled, exit codes and crash loops explained in plain words, for pods and containers, with the change that came before.
See it in the live demo →Alerts that work on day one
Sensible rules switched on at install, to Slack, Telegram, email or a webhook, with the likely cause in the message.
The default rules →The services next to your apps
Redis, PostgreSQL, MySQL and MariaDB, MongoDB, Nginx, Traefik, RabbitMQ and Kafka found automatically, each with its own page.
Applications →Logs on demand
The last lines of a pod's or container's log, where you already look: redacted, streamed and never stored.
How logs work →Right-sizing hints
Requests and limits against seven days of real use, in plain sentences: what was set, what was used, what would cover it. No scores.
What each hint means →Press ⌘K, go anywhere
Pages, clusters, workloads, pods, nodes, hosts, containers and applications, found by name with ⌘K or Ctrl+K. Keyboard first.
How to find anything →Docker hosts, first class
The same views for hosts, Compose projects and containers, from one docker run per host.
Install on Docker →
Ask your AI what broke. It answers from WatchLog.
Connect Claude or ChatGPT with a read-only token. It reads real exit codes, OOM kills, slow queries and rollouts, on Kubernetes and Docker.
Try it on the live demo →How it works
Read only: tokens can't change anything and never see secrets, and every call is logged. No AI runs inside WatchLog.
What's wrong with my clusters?
Asking WatchLog…
- get_problems182 ms2 critical problems in shop
- explain_alert95 msimage-resizer · OOMKilled, exit 137
- explain_alert88 mspayments-api · exit 1, CrashLoopBackOff
- get_events61 msWarning events of the last 2 h
- get_service_map112 msno failing connections
kind-demo is red because two pods in shop keep crashing.
1.shop/image-resizer goes over its 32Mi memory limit and gets killed (OOMKilled, exit 137). Nothing was deployed before it.
2.shop/payments-api exits with code 1 and is in CrashLoopBackOff. It isn't memory: read its last run with kubectl logs --previous.
No nodes are down, and no connections are failing.
Recorded with Claude Code against WatchLog, shortened. Every MCP client gets the same tools.
What's wrong with my clusters?
Asking WatchLog…
- get_problems140 ms2 critical, 4 warnings
- list_alerts61 ms3 alerts firing
- explain_alert83 msstorefront-api · exit 2, restarting
- get_pod77 msbilling-worker · OOMKilled, exit 137
- get_node52 msdocker-02 · silent for 7 days
prod-fleet has a silent host and two containers in trouble.
1.docker-02 stopped reporting 7 days ago. Check that the host and its WatchLog agent are up, or remove it.
2.billing-worker was killed at its memory limit (OOMKilled, exit 137), three times so far.
3.storefront-api exits with code 2 every few seconds and Docker starts it again: 35 restarts. Read docker logs storefront-api.
Recorded with Claude Code against WatchLog, shortened. Every MCP client gets the same tools.
Your databases, caches and queues, too.
Found automatically in what the agents already see, on Kubernetes and Docker. Connect with the command WatchLog writes for you, and each gets a full page, alerts and plain-language reasons.
Simple pricing: one dollar per node.
Billed on the 95th percentile of hourly node counts, so autoscaling spikes don’t inflate the bill.
Cloud Free
$0forever
Start free- 1 cluster or Docker fleet
- Up to 5 nodes
- 3 days of data
- 1 user
- Alerts, service map, probable cause, MCP
Cloud Pro
Free during beta$1/ node / month
$10 minimum · annual: 2 months free
Try Pro free- Unlimited clusters and nodes
- 30 days of data
- Up to 10 users
- Email support, within 2 business days
Coming to Pro: the multi-cluster view, SLO reports and anomaly detection
Community
Freeself-hosted
Install it yourself- Unlimited clusters, fleets and nodes
- History you choose (15 days by default)
- Unlimited users: Owner, Admin, Viewer
- AGPL-3.0, one Helm chart or Compose file
Beta users get 14 days’ notice by email before any billing starts, and nothing is charged without a card you add. Nothing that is free today will ever become paid.