Helm website, helm.sh, Kubernetes package manager, Helm charts, chart repositories, releases, Artifact Hub, Helm CLI, Kubernetes applications, CNCF project, and WHOIS domain data

Helm

Helm is the Kubernetes package manager website and tool ecosystem centered on charts, repositories, releases, and reusable application packaging for Kubernetes clusters.

Core purpose

Helm helps users define, install, upgrade, share, and roll back Kubernetes applications through versioned packages called charts.

Official domain

helm.sh is the official Helm website for documentation, downloads, release information, chart guidance, community links, and project resources.

Domain created

October 20, 2015

The Helm site logo used as the brand image for the website page.View official Helm logo

What Helm is

Helm official site describes Helm as the package manager for Kubernetes. The website explains Helm concepts, links to installation and usage docs, points users to Artifact Hub for chart discovery, and provides project information for the Helm community. In practice, Helm combines a command-line tool, a chart packaging format, and repository workflows. It lets teams turn sets of Kubernetes resources into reusable packages that can be installed, upgraded, shared, and rolled back more consistently than copying YAML files by hand.

Charts, repositories, and releases

Helm documentation centers on three big concepts. A chart is a Helm package containing Kubernetes resource definitions. A repository is where charts can be collected and shared. A release is an instance of a chart running in a Kubernetes cluster, with its own release name and history.

Installing and upgrading apps

Helm is often used to install applications into Kubernetes clusters, then upgrade them as configuration or chart versions change. Commands such as install, upgrade, rollback, list, and search give operators a package-manager style workflow while still deploying Kubernetes resources under the hood.

Chart structure and values

A chart is organized as a directory of files such as Chart.yaml, templates, default values, optional schemas, dependencies, and documentation. Values let users configure deployments without rewriting every Kubernetes manifest, while templates turn those values into resources that Kubernetes can apply.

Discovery through Artifact Hub

The Helm site points users to Artifact Hub for exploring charts from public repositories. That connection matters because Helm itself provides the package workflow, while Artifact Hub gives users a searchable catalog for chart discovery, publisher information, and package metadata.

Who uses Helm

Helm is used by Kubernetes operators, platform engineers, DevOps teams, software vendors, open-source maintainers, cloud architects, SRE teams, and developers who need repeatable application installs on Kubernetes. Some users install third-party charts, while others publish internal charts for their own platforms.

Why it matters

Helm matters because Kubernetes applications can involve many related resources, configuration options, dependencies, and release steps. Charts give teams a repeatable packaging model, while Helm commands make common operations such as install, upgrade, and rollback easier to manage across clusters.

WHOIS domain data

Data pulled: May 24, 2026View current WHOIS record

Domain: helm.sh
IP address: 18.208.88.157
Registrar: 1API GmbH
WHOIS server: whois.1api.net
Referral URL: http://www.1api.net
Created: October 20, 2015
Updated: November 26, 2025
Expires: October 20, 2026
Nameservers: dns1.p02.nsone.net (198.51.44.2); dns2.p02.nsone.net (198.51.45.2); dns3.p02.nsone.net (198.51.44.66); dns4.p02.nsone.net (198.51.45.66)
Domain status: clientTransferProhibited
Contact privacy: Registrant name and contact details are redacted; registrant organization is listed as The Linux Foundation, and admin and technical contact details are redacted.

Key concepts

ChartA Helm package that describes a related set of Kubernetes resources.
RepositoryA place where charts are collected and shared for installation or reuse.
ReleaseA running instance of a chart installed into a Kubernetes cluster.
ValuesConfiguration data used to customize a chart without editing every template directly.

Common workflows

Install Helm, add chart repositories, search for charts, and install a chart into a Kubernetes cluster.
Customize chart values for different environments such as development, staging, and production.
Package and publish charts so other teams or users can install them.
Use Helm release history to inspect, upgrade, or roll back application deployments.

Common misconceptions

Helm is not Kubernetes itself; it is a package manager and workflow layer that deploys Kubernetes resources.
A chart being public does not automatically mean it is secure, maintained, or appropriate for production.
Helm charts reduce repetitive YAML work, but teams still need to understand the resources being deployed.

Open questions

How should teams balance chart reuse with the need to understand and audit generated Kubernetes resources?
How will Helm workflows evolve alongside GitOps tools, OCI registries, and policy-controlled deployment systems?
What trust and provenance signals should users expect before installing charts from public repositories?