Helm Review 2026: The free, open-source package manager for Kubernetes
Affiliate disclosure: this review contains affiliate links — we may earn a commission if you sign up, at no cost to you. Ratings are our own editorial scores.
Helm
Pros
- Completely free and open source (Apache 2.0) — no license, seat, or subscription cost
- De facto standard with charts for thousands of apps and a massive ecosystem
- Full release lifecycle: versioned installs, one-command upgrades and rollbacks
- CNCF graduated with vendor-neutral governance, backed by Google, Microsoft, Red Hat, IBM
Cons
- Go templating over YAML gets complex and hard to debug on large charts
- No first-party commercial support — you rely on community or third-party vendors
- Bitnami's popular free charts moved to paid on 29 Sept 2025, forcing some migrations
- Steeper learning curve than template-free tools like Kustomize
Best for: Packaging and distributing Kubernetes applications, Managing complex multi-service deployments across environments, DevOps/platform engineers standardizing releases and rollbacks.
What is Helm?
Helm is the package manager for Kubernetes, and the project positions it as the best way to find, share, and use software built for Kubernetes. It is a graduated CNCF project, community maintained, and free. Instead of hand-editing dozens of YAML manifests per environment, you package an application as a chart: a directory holding Chart.yaml metadata, a values.yaml file of defaults, and a templates folder that renders real Kubernetes resources.
Once installed, a chart becomes a release, and every upgrade or rollback increments a revision so the cluster carries its own deployment history. Install paths cover Homebrew, Chocolatey, Scoop, and Snap, with the 4.x line current alongside legacy builds.
Charts, releases, and daily commands
The command surface stays small enough to memorize. helm search hub queries Artifact Hub, while helm search repo looks only at repositories added through helm repo add. From there, helm install creates a release, helm upgrade applies changes, helm uninstall removes it, and helm rollback returns a release to any earlier revision. Configuration rides on flags the Using Helm guide documents: --values (or -f) specifies a YAML file of overrides, --set specifies overrides on the command line and takes higher precedence when both are used, --wait waits until all Pods are in a ready state for as long as the --timeout value, and --generate-name lets Helm generate the release name when you leave it off.
Templating that scales past one chart
The Chart Template Guide is among the largest sections of the Helm documentation. Charts declare dependencies in Chart.yaml, then shape them with alias for reusing a subchart under several names, conditions and tags for toggling optional components, and import-values for lifting child values into a parent. Two features matter most for platform teams: values.schema.json validates overrides before they reach the cluster, and library charts hold shared helpers that other charts import rather than copy. Chart hooks handle lifecycle work; the crds directory lands custom resource definitions first.
Publishing charts to OCI registries
Helm reads classic HTTP repositories and OCI registries alike. Behind an oci:// reference, helm push uploads a chart, helm pull fetches one, helm registry login authenticates, and helm install, helm upgrade, helm template, and helm show all accept that reference directly. The registries documentation names Amazon ECR, Azure Container Registry, Docker Hub, Google Artifact Registry, Harbor, JFrog Artifactory, Cloudsmith, IBM Cloud Container Registry, and RepoFlow, then points at zot or a plain Docker Registry for rehearsing the whole loop locally.
What changed in Helm 4
The project reports that Helm 4 arrived roughly six years after v3, led by a redesigned plugin system that accepts WebAssembly based plugins and folds post-renderers in as plugins. Server side apply, resource waiting built on kstatus, local content-based caching, and reproducible chart archive builds fill out the operational side. For teams embedding Helm in their own tooling, logging moved to slog so SDK logging integrates with modern loggers, and the SDK's updated APIs support multiple chart versions, with a new experimental v3 chart API version described as coming soon. Dated bug-fix and security windows were published for the v3 line.
Cost and how support works
No pricing page exists on helm.sh because nothing is for sale. Support arrives through the community: the #helm-users and #helm-dev Slack channels, the kubernetes-helm tag on Stack Overflow, a weekly meeting, and a GitHub tracker whose easy-to-fix bugs carry a good first issue tag. Docs are translated into a dozen languages, and the site credits hundreds of contributors plus supporters including Bitnami, Google, IBM, Microsoft, and Red Hat. What Helm does not offer is a vendor desk with an SLA.
Who should choose Helm
Choose Helm if the same application ships to more than one cluster or environment and parallel manifest folders have become a chore. It fits platform teams packaging internal services, vendors distributing software to customers who run their own clusters, and anyone who wants an install or a rollback to be one command rather than a runbook. The public chart ecosystem is already sizable: helm search hub queries Artifact Hub, which the docs describe as listing charts from dozens of different repositories, and helm.sh links a search across 800+ charts. Helm is a weaker fit for a single small cluster of static manifests, where Kustomize overlays or plain YAML stay simpler to reason about.
Key features
| Feature | What it does |
|---|---|
| Charts | Package Kubernetes apps as reusable, versioned, shareable charts |
| Templating engine | Go-based templating with values.yaml for environment-specific config |
| Release lifecycle | Install, upgrade, roll back, and view history for every release |
| Dependency management | Bundle sub-charts and manage application dependencies automatically |
| Repositories & OCI | Host and pull charts from HTTP repos or OCI-compliant registries |
Helm pricing
| Plan | Price | Included |
|---|---|---|
| Helm (Open Source)POPULAR | $0 | Every feature, Apache 2.0 license, cross-platform CLI |
| Community Support | Free | Slack, GitHub discussions, Stack Overflow, weekly dev standups |
| Third-Party Enterprise Support | Varies | Optional contracts via Red Hat, SUSE, etc. — not sold by Helm |
How Helm compares
| Alternative | How it differs |
|---|---|
| Kustomize | Free, template-free YAML overlays built into kubectl; simpler but no packaging or release lifecycle |
| Helmfile | Free OSS wrapper to declaratively manage multiple Helm releases across environments |
| Timoni | Free CUE-based package manager; modern alternative but far smaller ecosystem |
Helm ratings on other platforms
Independent user ratings from third-party review sites, linked here for transparency. These are not our editorial score, are captured on the date shown, and may have changed since.
Frequently asked questions
Is Helm free?
Yes. Helm is 100% free and open source under the Apache 2.0 license, with no paid tiers, seats, or license fees. It's a CNCF graduated project maintained by 400+ community developers and backed by Google, Microsoft, Red Hat, and IBM. You download the binary and use every feature at zero cost.
How much does Helm cost?
Helm costs $0. There is no commercial edition, subscription, or per-node pricing from the project itself. The only related costs are optional third-party managed Kubernetes platforms or enterprise support contracts from vendors like Red Hat or SUSE. The Helm CLI, charts, and templating engine are entirely free to use in production.
Helm vs Kustomize — which should I use?
Both are free and open source. Helm uses templated, versioned, packageable charts with a release lifecycle (install, upgrade, rollback), ideal for distributing complex apps. Kustomize (built into kubectl since 1.14) patches plain YAML with no templating, favored for simpler GitOps overlays. Many teams use both: Kustomize for env overlays, Helm for app packaging.
Is Helm affected by the Bitnami deprecation?
No. Broadcom's Bitnami moved its free container images and Helm charts to a paid subscription on September 29, 2025, but the CNCF confirmed this does not impact the Helm project itself. Helm stays fully open source and Apache 2.0 licensed. Only teams depending on Bitnami's specific charts need to migrate to alternative sources.
What is Helm used for?
Helm is the package manager for Kubernetes. It bundles manifests into reusable, versioned 'charts' so you can install, upgrade, roll back, and share applications with a single command. It handles templating, dependency management, and release tracking, replacing dozens of raw YAML files. It's the de facto standard, with charts for thousands of popular applications.
Verdict
Helm is the default choice for anyone packaging or deploying non-trivial applications on Kubernetes — it's free, mature, CNCF-graduated, and universally supported. Use it if you distribute apps, manage multiple environments, or need reliable versioned rollbacks. Skip it (or pair it with Kustomize) if your needs are simple, single-environment YAML where Go templating only adds complexity. Since it costs nothing, the real decision is workflow fit, not budget.
Facts verified against: helm.sh, www.cncf.io, www.cncf.io, github.com, helm.sh, helm.sh, helm.sh, helm.sh, helm.sh, helm.sh, helm.sh, helm.sh (as of August 2026).
More in Cloud, Hosting & Dev
See all →
AI code-review tool that automates pull-request analysis
AI-first code editor with agentic coding and tab completions
Frontend cloud for deploying and hosting web apps