Ravenstash
Helm charts over OCI

Private Helm Chart Repository

Ravenstash hosts private Helm charts through standard OCI workflows, so teams can publish and deploy with Helm without operating a separate chart repository.

Package and push a chartbash
rvs art select platform/deployment-charts
rvs helm package ./charts/api
rvs helm push api-1.2.3.tgz charts
Pull a chartbash
rvs art select platform/deployment-charts
rvs helm pull charts/api --version 1.2.3
Workflows

A private Helm chart repository that stays close to your tools

Ravenstash is built to make private package publishing feel familiar for developers and manageable for teams.

Standard Helm OCI workflow

Use Helm to push, pull, show, template, install, upgrade, and resolve chart dependencies through OCI references.

Charts and images stay organized

Manage Helm charts and container images in separate private repositories while using one familiar Ravenstash workflow.

OCI charts only

Ravenstash supports Helm charts distributed as OCI artifacts, without classic index.yaml or ChartMuseum-compatible endpoints.

FAQ

Helm OCI questions

Does Ravenstash support classic Helm repositories?

No. Ravenstash supports standard Helm OCI charts only, not index.yaml, ChartMuseum APIs, or a generic chart archive upload endpoint.

Are Helm charts private by default?

Yes. Only authenticated Ravenstash users and automation can publish or install your organization’s charts.

Can chart signatures and provenance stay with the chart?

Yes. Ravenstash can keep chart signatures, provenance, and related evidence alongside the chart.