Kubeshark Pricing: Choose Your Spend Level, Pay per Targeted Pod
Running Kubeshark on a single dev cluster is simple. Running it on a large production cluster, or across many clusters, raises a fair question: what will it cost, and will that number keep climbing as the clusters grow? Our answer is to put the spend level in your hands. Enterprise is priced per targeted pod, regardless of cluster size, and you can change your level whenever you need.
How it works
You decide how many pods Kubeshark targets, for example 10, 100 or 1,000. That number sets the price. The number of nodes, the size of each cluster and how many clusters you run do not. When your needs change, you change the level, up or down.
Why per targeted pod, and not cluster size?
A cluster with hundreds of nodes may run thousands of pods, but the traffic you need while chasing a failing API call or a latency spike usually belongs to a much smaller set of workloads. Paying for every node to see a handful of services means paying for visibility you don't use. With Enterprise, you target the workloads that matter and pay for those. The same holds when you run many clusters: what drives the cost is the pods you target, not how many nodes sit underneath them or how your infrastructure is split up.
Growth without surprises
Clusters grow. Autoscalers add nodes, teams add services, new clusters appear. None of that changes your Kubeshark bill on its own. The price moves only when you decide to target more pods. You know the cost before you commit, and the scope is a decision you make, not a side effect of autoscaling. That is what we mean by a predictable budget, with spend you control.
Enterprise
On top of per-targeted-pod pricing, Enterprise adds four things:
- Support for clusters of any size
- Air-gapped support, so no internet connectivity is required
- SSO/authorization and sensitive data redaction
- Dedicated support
Community
Community stays free for development and testing. It covers clusters of up to 3 nodes or 60 pods and requires internet connectivity. If you're evaluating Kubeshark, debugging locally, or running it in a test environment, Community is the place to start. Production use requires a license other than Community.
What happens at the Community limits
When a cluster goes beyond the Community limits, the Kubeshark dashboard points you to https://kubeshark.com/pricing, where you can compare the offerings and request a quote. Nothing about how you install or run Kubeshark changes. The license is what changes.
Getting started
If you haven't tried Kubeshark yet, install it from https://docs.kubeshark.com or explore the live demo from https://kubeshark.com. For Enterprise, tell us how many pods you want to target at https://kubeshark.com/get-started and we'll reply with pricing. You can change that number later.