Free during early access
Pro shows you
the whole story.
Community tells you that a pod or node broke. Pro tells you everything else: the full chain of cause, the change and who made it, what else is hit, and the logs that prove it.
Community and Pro, side by side
| Feature | Community | Pro |
|---|---|---|
| DETECTION | ||
| Crash loops, OOM kills, Pending pods | Yes | Yes |
| Node NotReady | Yes | Yes, plus pressure and draining |
| Readiness, stuck rollouts, failed Jobs and CronJobs | — | Yes |
| Storage, network, certificates, quota, admission | — | Yes |
| Control plane, custom resources, unusual events | — | Yes |
| ANALYSIS | ||
| Root cause | One-line headline | Full proof and confidence |
| Recent changes and who made them | — | Yes |
| Affected services and log excerpts | — | Yes |
| ALERTS | ||
| Channels | 1 | Unlimited |
| Routing by namespace and severity, threads, templates | — | Yes |
| Noise control and silences | Yes | Yes, plus flapping and maintenance windows |
| OPERATIONS | ||
| Incident history across restarts | — | Yes |
| Audit log, runbooks, heartbeat monitor | — | Yes |
| Account needed | No | Yes, email only |
How the license works
- Getting one
- Sign in with your email and press “Get a free Pro license”. Your key appears right away.
- Adding it
- Run the kwatch installer and choose License / Pro, then Add or replace key.
- One cluster
- A key runs one cluster. Move it to another up to 3 times in 30 days, from the installer or your account.
- Offline
- kwatch checks in once a day and keeps Pro for up to 7 days without a connection.
- When it ends
- kwatch falls back to Community. Alerts never stop.
- What's sent
- A hashed cluster ID, the kwatch version and the node count. Nothing from your workloads.