⭐ Community vs Pro
kwatch ships in two editions from the same binary. Community is free forever, with no account and no key. Pro needs a license key, one per cluster.
Pro is free during early access. Each license is free for 3 months and we may renew it. One license runs one cluster, with up to 2 per account or company. No payment details. If that ever changes, you will hear well in advance.
At a glance
| Community | Pro | |
|---|---|---|
| Cost | Free, no account, no key | Free during early access |
| Detection | Pod crashes, CrashLoop, OOM, image pull and config errors; Pending, Unschedulable, Evicted, Failed and stuck Terminating pods; liveness and startup probe failures; node NotReady | Adds readiness probe failures, node pressure and draining, rollouts, Jobs and CronJobs, PDBs, HPAs, storage, network, admission, certificates, quota, custom resources, control plane, probes and unusual events |
| Analysis | One-line cause | Full proof, shared-factor suspects, who changed what, impact and redacted log excerpts |
| Incidents | Basic dedup and noise control, state in memory | Flapping detection, startup summary, state kept on disk across restarts, changes made while kwatch was down, gap report |
| Delivery | 1 provider, namespace filters and silences | All providers, routing by scope, threads, text templates, audit log |
| Operations | RBAC audit, secret redaction, health, short text /status | Prometheus /metrics, severity overrides, maintenance holds, runbook links, heartbeat, /status JSON, flight recorder and replay-export |
| Support | GitHub issues and Discussions | Dedicated support: installation help, feature requests and fixes first |
The per-capability list is on the Pro page and in the generated feature reference. Every capability there carries its tier.
Community
Community is free forever and works without contacting any server.
- Detection of pod crashes, CrashLoop, OOM kills, image pull and config errors, Pending, Unschedulable, Evicted, Failed and stuck Terminating pods, liveness and startup probe failures, and NotReady nodes.
- One-line cause on every incident.
- Noise control: deduplication, namespace filters, ignore lists and silences.
- A short
/status. - One alert provider. If you configure several, Community keeps the one in
app.communityProvider, or the first by name when that is empty. - State in memory. After a restart kwatch takes a fresh baseline: existing failures are not re-sent, and only new or worsening ones alert.
Pro-only checks still run in Community and only count. Alerts can end with
one Pro line (a short note, or a note that Pro found a likely cause), and the
startup message, /status (a Pro checks: line) and the installer show how many issues the Pro
checks found, by category only: readiness probes, shared causes, preemption
and admission, and scheduling gates. The counts are computed in your cluster
and never leave it. Set app.hideProHints: true to remove the alert line, the
cause note and the startup count; /status and the installer keep their
count.
These moved to Pro: readiness probe failures, shared-factor causes, the
Prometheus /metrics endpoint, preemption, admission rejection, grace-period
kills and scheduling gates. In Community /metrics answers 404 and
kwatch logs one line saying it is part of Pro.
Pro
Pro adds everything marked Pro across these
docs: the extra detectors, the full root-cause and change history, routing,
threads, templates, severity overrides, maintenance holds, runbooks, audit
log, heartbeat and probes, persistence, the flight recorder, /status JSON
and more. Configuration for Pro features is accepted in
Community and ignored; kwatch lint prints an info: line for each one, and
the file stays valid when you upgrade.
Pro also includes dedicated support. See Getting help.
How Pro licensing works
- One license, one cluster. The first successful check binds the key to that cluster.
- Early access limits. Up to 2 clusters per account. With a work email the limit is 2 per company domain, shared by everyone using it. With a free mailbox provider such as Gmail the limit is per account.
- 3 months, renewable. Each license runs for 3 months from the day you start it, and we may renew it.
- Offline for up to 7 days. kwatch renews daily. A renewal is valid for 3 days, followed by a 4-day grace period, then kwatch falls back to Community features. Monitoring and alerts continue; reconnecting restores Pro automatically.
- 3 moves per 30 days to another cluster, with the installer (License / Pro, then Move license to this cluster) or Transfer on your account page.
- When a license ends, kwatch falls back to Community. Detection and alerting never stop.
- What is sent: a hashed cluster id, the kwatch version, the node count and the instance public key. A Community install without a key makes no license calls.
🔑 Get Pro
- Sign up and open the sign-in link.
- Choose Get 3 months of Pro free on your account page.
- Run the installer, open License / Pro and choose Add or replace key.
Details, moving a license and troubleshooting are on the License page, and the commands are in the CLI reference.
📄 Source available
kwatch is source available under the Elastic License 2.0 (ELv2). You may run
it for free in your own clusters, read and change the code, and share it. You
may not offer it as a hosted service or remove its license-key checks.
Releases up to and including v1.0.0-rc.10 stay under the MIT License. See
licensing.