ToolJet
ToolJet bundles its MCP server into the EE image as AI builder features land in the LTS track
Comparison · Infra & APIs
Kubeshark vs werf
A side-by-side editorial comparison of Kubeshark and werf — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:kubernetes
Kubeshark vs werf: at a glance
What is Kubeshark?
Kubeshark rebuilt its backend for V2 and is redrawing the free tier around it.
Kubeshark is mid-transition from V1 to V2, announced for January 2026. The v52.11.0 release rewrote the backend entirely — V2 runs on the new implementation while V1 stays on the legacy one — and added cluster-wide L4 PCAP export plus L7-to-L4 mapping that ties API calls back to the TCP and UDP connections carrying them. Since then the releases have been smaller: connectivity map performance, per-flow PCAP files in snapshot archives, and a migration of every service domain from kubehq.com to kubeshark.com.
What is werf?
werf ships weekly across two tracks — v3 dev gets JSON Schemas and Harbor v2 fixes, v2 alpha gets the backports.
werf operates two active release channels in parallel: v3.x ("dev") for new capabilities and v2.x ("alpha") for stabilized backports. The September 2026 sprint covers v3.3–v3.5 and v2.78–v2.79, with several meaningful improvements — JSON Schema publication for werf config files, a netavark networking requirement replacing CNI/slirp4netns, and a Harbor registry fix that clears a real registry-compatibility issue. The dual-track cadence lets teams stay on the stable alpha channel while the dev track absorbs the larger changes.
Kubeshark vs werf: editorial side-by-side
Kubeshark
0.0INFRA · APIS
Kubeshark rebuilt its backend for V2 and is redrawing the free tier around it.
◆ Current state
Kubeshark is mid-transition from V1 to V2, announced for January 2026. The v52.11.0 release rewrote the backend entirely — V2 runs on the new implementation while V1 stays on the legacy one — and added cluster-wide L4 PCAP export plus L7-to-L4 mapping that ties API calls back to the TCP and UDP connections carrying them. Since then the releases have been smaller: connectivity map performance, per-flow PCAP files in snapshot archives, and a migration of every service domain from kubehq.com to kubeshark.com.
◆ Where it's heading
The product is moving down the stack. It started as an API-level traffic viewer and the recent work is all about L4 — connectivity maps, raw PCAP export, mapping L7 calls onto the connections beneath them — which puts it closer to a cluster-wide packet capture tool than a service-mesh observability dashboard. The licensing is moving in the opposite direction of the feature set: an almost-unlimited complimentary licence through the end of 2025 was replaced by one capped at 100 nodes, so the free tier is being defined rather than left open. Two releases also mention agentic infrastructure being staged but not yet usable.
◆ Prediction
Expect V2 to consolidate onto the new backend and the legacy V1 path to be dropped once the transition completes, since the release notes already describe V1 as being sunset. The staged agentic infrastructure is the most likely candidate for the next substantive feature, given it has been shipped inert twice.
werf
5.0INFRA · APIS
werf ships weekly across two tracks — v3 dev gets JSON Schemas and Harbor v2 fixes, v2 alpha gets the backports.
◆ Current state
werf operates two active release channels in parallel: v3.x ("dev") for new capabilities and v2.x ("alpha") for stabilized backports. The September 2026 sprint covers v3.3–v3.5 and v2.78–v2.79, with several meaningful improvements — JSON Schema publication for werf config files, a netavark networking requirement replacing CNI/slirp4netns, and a Harbor registry fix that clears a real registry-compatibility issue. The dual-track cadence lets teams stay on the stable alpha channel while the dev track absorbs the larger changes.
◆ Where it's heading
werf's dev track is progressively expanding its deploy primitives: renderPatches support, returning rendered resources from ReleaseInstall, and authenticated secret write capability (v3.3.0) all suggest a push toward more programmable, auditable deploy pipelines. The embedded Deno binary in v3.2.0 — bundled behind a feature gate — hints at scripted deployment hooks as a coming capability. JSON Schemas for werf config files make editor tooling a first-class citizen.
◆ Prediction
The Deno embedding will likely surface as a supported scripting API for pre/post-deploy hooks in the next major dev release. A corresponding migration of Helm-centric users toward werf's native deploy primitives appears to be the longer arc.
Alternatives to Kubeshark and werf
Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Kubeshark or werf.
GitHub
GitHub adds Claude Opus 5.5 and GPT-6 models while shipping sandboxed agent execution
Parse Server
Parse Server patches three security CVEs: GraphQL disclosure and protectedFields bypass
Buildkite
Buildkite ships Agent v4, an MCP server for AI-native CI, and a VS Code extension in a dense September push.
Jackett
Jackett's daily tracker churn adds 11 new APIs and formalizes its security policy in a week
Chromatic
Chromatic ships Vitest Browser Mode and React Native visual testing, moving beyond Storybook
See all Kubeshark alternatives → · See all werf alternatives →
Recent activity from Kubeshark and werf
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 13h agowerfwerf v3.5.0: JSON Schema for config files, Harbor v2 fix, build report versioning
- 1d agowerfwerf v2.79.0 alpha: backport build reporting and deploy fixes from v3.5.0
- 13d agowerfwerf v2.78.2 alpha: fix buildah layer re-compression on stage push
- 14d agowerfwerf v3.4.0: netavark replaces CNI/slirp4netns for buildah networking
- 14d agowerfwerf v2.78.1 alpha: fix stapel stage builds tied to image catalog
- 15d agowerfwerf v3.3.1: fix host-cleanup freed space measurement
- 7mo agoKubesharkv52.12.0 moves every service domain to kubeshark.com
- 8mo agoKubesharkComplimentary licence is redefined as free up to 100 nodes
- 8mo agoKubesharkBackend fully rewritten for V2, with L7-to-L4 traffic mapping ⚡
- 9mo agoKubesharkNear-unlimited complimentary licence bundled into the Helm chart
Frequently asked questions
What is the difference between Kubeshark and werf?
Both compete on the same themes — kubernetes — within Infra & APIs. werf is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is Kubeshark better than werf?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. werf is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
What are the best alternatives to Kubeshark?
Top Kubeshark alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Kubeshark alternatives" section above for the current picks, or visit /alternatives/kubeshark for the full list with editorial commentary on each.
What are the best alternatives to werf?
Top werf alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "werf alternatives" section above for the current picks, or visit /alternatives/werf for the full list with editorial commentary on each.