WatchLog CloudFree for up to 5 nodes or servers →

Monitoring for Kubernetes, Docker and Linux servers, 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 and pod, every systemd service and process (PHP, Node, Go, Java, Python, anything), every container, 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 or server

  1. Sign up with GitHub, Google or email

    About a minute. No card, no company form.

  2. Run one command

    Helm on a cluster, or one line on each Linux server. A deb, an rpm and docker run work too.

    Kuberneteshelm install watchlog-agent … --set watchlog.clusterToken=wl_ct_••••
    Linux servercurl -fsSL https://ingest.watchlog.io/install.sh | sudo sh -s -- --token wl_ct_••••
  3. 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 withKubernetesDockerLinux servers

and readsRedisPostgreSQLMySQL and MariaDBMongoDBNginxTraefikRabbitMQKafkaPHP-FPM

WatchLog overview: cluster health, KPIs with sparklines, resources chart and the problems that need attention
What you get

The answers you need, without assembling a stack.

New in v0.4

Why is this broken? WatchLog tells you.

Every alert, failing connection and crashing pod, container, service or process gets its probable cause: one sentence, the evidence behind it, and what was checked. On a server too: a pm2 app that crash-loops after a release, a service OOM-killed at its MemoryMax, PHP-FPM at pm.max_children. Fixed rules over the data WatchLog already collects; no AI, no scores.

  • Kubernetesfrontend fails because api was scaled to 0: nothing answers its calls.
  • Dockershop-worker-1 is OOM-killed when it reaches its 256 MiB memory limit: 12 times in the last hour.
  • Linux servers, a pm2 appapi exits with code 1 since its executable changed at 14:01: a new release, 1 min before the first crash.
  • Linux servers, a systemd serviceorders.service is OOM-killed at its 512 MiB memory limit: 3 times in the last hour.
  • PHP-FPMEvery worker was busy 14 times in the last 10 minutes (pm.max_children reached); 6 requests are waiting.
How probable cause works →
Platform
WatchLog's Likely cause panel on a Kubernetes alert: the cause in one sentence, the evidence chain from the failing calls to the scale-down where it starts, and what was checkedWatchLog's Likely cause panel on a Docker alert: a container OOM-killed at its memory limit, the evidence behind it, and what was checked
MCP · Ask your cluster

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, Docker and Linux servers: a pod, a container, a systemd service or a pm2 app.

Works with
+ any MCP client

Read only: tokens can't change anything and never see secrets, and every call is logged. No AI runs inside WatchLog.

Cluster kind
answered

What's wrong with my clusters?

  1. get_problems182 ms2 critical problems in shop
  2. explain_alert95 msimage-resizer · OOMKilled, exit 137
  3. explain_alert88 mspayments-api · exit 1, CrashLoopBackOff
  4. get_events61 msWarning events of the last 2 h
  5. get_service_map112 msno failing connections
Claude Code

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?

  1. get_problems140 ms2 critical, 4 warnings
  2. list_alerts61 ms3 alerts firing
  3. explain_alert83 msstorefront-api · exit 2, restarting
  4. get_pod77 msbilling-worker · OOMKilled, exit 137
  5. get_node52 msdocker-02 · silent for 7 days
Claude Code

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.

What's wrong with my servers?

  1. get_problems1 critical, 1 warning on web-2
  2. get_serverweb-2 · services, process groups, containers
  3. get_eventsapi · CrashLoop, Release, FailedExit
Your assistant

web-fleet has two workloads in trouble, both on web-2.

1.api a pm2 app, exits with code 1 since its executable changed at 14:01: a new release, 1 min before the first crash.

2.orders.service is OOM-killed at its 512 MiB memory limit: 3 times in the last hour. systemd restarts it each time.

The other two servers are healthy.

An example on a Server fleet, written from the tools’ docs. Every MCP client gets the same tools.

Applications

Your databases, caches and queues, too.

Found automatically in what the agents already see: in a Kubernetes cluster, in Docker, or installed on the host of a Linux server. Connect with the command WatchLog writes for you, and each gets a full page, alerts and plain-language reasons.

All applications →
Pricing

Simple pricing: three dollars per node or server.

Billed on the 95th percentile of hourly node counts, so autoscaling spikes don’t inflate the bill. A Linux server counts as one node.

Compare plans →
  • Cloud Free

    $0forever

    • 1 cluster or Server fleet
    • Up to 5 nodes or servers
    • 3 days of data
    • 1 user
    • Alerts, service map, probable cause, MCP
    Start free
  • Cloud Pro

    $3/ node or server / month

    $15 minimum, the first 5 · annual: 2 months free

    • What changed and anomaly alertsNEW
    • Unlimited clusters, nodes and servers
    • 30 days of data
    • Up to 10 users
    • Email support, within 2 business days

    Coming to Pro: the multi-cluster view and SLO reports

    Start with Pro
  • Community

    Freeself-hosted

    • Unlimited clusters, fleets, nodes and servers
    • History you choose (15 days by default)
    • Unlimited users: Owner, Admin, Viewer
    • AGPL-3.0, one Helm chart or Compose file
    Install it yourself

Nothing is charged without a card you add on Stripe’s own page. Cloud Free and the self-hosted Community edition stay free: nothing in them will become paid. Organizations that started Pro during the beta keep it free until the date in their notice, sent 14 days ahead.

Your first cluster or server on screen in minutes.