head to head · open source

DoKit vs kubeshark

DoKit has 20,415 GitHub stars, 3,183 forks, 275 open issues and last shipped 11 days ago. kubeshark has 12,082 stars, 549 forks, 149 open issues and last shipped 9 days ago. DoKit leads on adoption by 69% (20,415 vs 12,082 stars). DoKit is written in Java under Apache-2.0; kubeshark is written in Go under Apache-2.0. DoKit has attracted 16% as many forks as stars, kubeshark 5%. kubeshark was the more recently maintained of the two, and both are self-hostable with no licence fee.

Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.

DoKit ★ 20K kubeshark ★ 12K category Infrastructure & Operations

← all 8884 open source comparisons

Side by side

DoKit kubeshark
GitHub stars ★ 20K ★ 12K
License Apache-2.0 Apache-2.0
Written in Java Go
Last push 2026-09-07 2026-09-09
Forks ⑂ 3.2K ⑂ 549
Self-hosting Yes Yes
Data ownership Your server Your server

pick DoKit if

  • You weight community size — 20K stars and counting
  • You want the Apache-2.0 license terms
  • Your stack matches Java
  • You value the larger contributor base for long-term maintenance

full DoKit profile →

pick kubeshark if

  • You want the kubeshark 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 kubeshark fits your workflow better

full kubeshark profile →

About DoKit

DoKit is an Apache 2.0 efficiency platform for the full research and development lifecycle of pan frontend products — Android, iOS, mini programs, Flutter and Web — built for mobile developers, test engineers and UI designers who want debugging, performance monitoring and visual inspection tooling inside a debug build instead of hand rolled into each application.

read the full DoKit overview →

About kubeshark

Kubeshark is an Apache 2.0, eBPF powered network observability tool for Kubernetes that indexes cluster wide L4/L7 traffic with full Kubernetes context and makes that traffic queryable by AI agents through the Model Context Protocol and by humans through a real time dashboard.

read the full kubeshark overview →

More in Infrastructure & Operations

Immich ★ 114K Uptime Kuma ★ 91K worldmonitor ★ 87K mall ★ 85K NetData ★ 81K Elasticsearch ★ 78K

Related comparisons

uptime-kuma vs worldmonitor uptime-kuma vs netdata uptime-kuma vs grafana worldmonitor vs netdata worldmonitor vs grafana netdata vs grafana uptime-kuma vs huginn worldmonitor vs huginn immich vs paperless-ngx immich vs ceph immich vs filestash immich vs garage immich vs storj immich vs alarik immich vs spinifex paperless-ngx vs ceph mall vs prometheus mall vs nocodb mall vs etcd mall vs dbeaver mall vs orm prometheus vs nocodb mall vs milvus mall vs tidb

More Monitoring & Observability projects

Compare either of these against the rest of the Monitoring & Observability field.

DoKit vs Uptime Kuma DoKit vs worldmonitor DoKit vs NetData DoKit vs Grafana DoKit vs huginn DoKit vs Sentry DoKit vs SigNoz DoKit vs Grafana Loki DoKit vs beszel DoKit vs cilium DoKit vs Apache SkyWalking DoKit vs jaeger

Frequently asked questions

Is DoKit or kubeshark more popular?

DoKit has 20,415 GitHub stars and kubeshark has 12,082. DoKit has the larger community by that measure.

Are DoKit and kubeshark free?

Both are open source. DoKit is licensed under Apache-2.0 and kubeshark under Apache-2.0. Neither carries a licence fee.

What is the difference between DoKit and kubeshark?

DoKit is written in Java and kubeshark 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, DoKit or kubeshark?

Choose DoKit if you want the larger community (20,415 stars) or its Apache-2.0 licence terms. Choose kubeshark if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.