head to head · open source
worldmonitor vs kube-state-metrics
worldmonitor has 90,021 GitHub stars, 13,905 forks, 313 open issues and last shipped yesterday. kube-state-metrics has 6,234 stars, 2,201 forks, 109 open issues and last shipped yesterday. worldmonitor leads on adoption by 1,344% (90,021 vs 6,234 stars). worldmonitor is written in TypeScript under AGPL-3.0; kube-state-metrics is written in Go under Apache-2.0. worldmonitor has attracted 15% as many forks as stars, kube-state-metrics 35%. worldmonitor was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 1 topic tag (monitoring), so they are genuine substitutes rather than adjacent tools.
Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.
← all 20902 open source comparisons
Side by side
| worldmonitor | kube-state-metrics | |
|---|---|---|
| GitHub stars | ★ 90K | ★ 6.2K |
| License | AGPL-3.0 | Apache-2.0 |
| Written in | TypeScript | Go |
| Last push | 2026-11-02 | 2026-11-02 |
| Forks | ⑂ 14K | ⑂ 2.2K |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick worldmonitor if
- You weight community size — 90K stars and counting
- You want the AGPL-3.0 license terms
- Your stack matches TypeScript
- You value the larger contributor base for long-term maintenance
pick kube-state-metrics if
- You want the kube-state-metrics feature set and don't need the biggest community
- You prefer the Apache-2.0 license terms
- Your stack matches Go
- You evaluated both and kube-state-metrics fits your workflow better
About worldmonitor
World Monitor 简体中文 日本語 Real time global intelligence dashboard — AI powered news aggregation, geopolitical monitoring, and infrastructure tracking in a unified situational awareness interface. Documentation · Releases · Contributing What It Does Curated news feeds across global and regional categories, AI synthesized into briefs Dual map engine — 3D globe (globe.gl) and WebGL flat map (deck.gl) with a shared map layer catalog Panel inventory — concrete panel implementations across specialized variants Cross stream correlation — military, economic, disaster, and escalation signal convergence Country Instability…
read the full worldmonitor overview →
About kube-state-metrics
Overview kube state metrics (KSM) is a simple service that listens to the Kubernetes API server and generates metrics about the state of the objects. (See examples in the Metrics section below.) It is not focused on the health of the individual Kubernetes components, but rather on the health of the various objects inside, such as deployments, nodes and pods. kube state metrics is about generating metrics from Kubernetes API objects without modification. This ensures that features provided by kube state metrics have the same grade of stability as the Kubernetes API objects themselves. In turn, this means that…
read the full kube-state-metrics overview →
More in Infrastructure & Operations
Related comparisons
More Monitoring & Observability projects
Compare either of these against the rest of the Monitoring & Observability field.
Frequently asked questions
Is worldmonitor or kube-state-metrics more popular?
worldmonitor has 90,021 GitHub stars and kube-state-metrics has 6,234. worldmonitor has the larger community by that measure.
Are worldmonitor and kube-state-metrics free?
Both are open source. worldmonitor is licensed under AGPL-3.0 and kube-state-metrics under Apache-2.0. Neither carries a licence fee.
What is the difference between worldmonitor and kube-state-metrics?
worldmonitor is written in TypeScript and kube-state-metrics in Go. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, worldmonitor or kube-state-metrics?
Choose worldmonitor if you want the larger community (90,021 stars) or its AGPL-3.0 licence terms. Choose kube-state-metrics if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.