Standard Helm OCI workflow
Use Helm to push, pull, show, template, install, upgrade, and resolve chart dependencies through OCI references.
Ravenstash hosts private Helm charts through standard OCI workflows, so teams can publish and deploy with Helm without operating a separate chart repository.
rvs art select platform/deployment-charts
rvs helm package ./charts/api
rvs helm push api-1.2.3.tgz chartsrvs art select platform/deployment-charts
rvs helm pull charts/api --version 1.2.3Ravenstash is built to make private package publishing feel familiar for developers and manageable for teams.
Use Helm to push, pull, show, template, install, upgrade, and resolve chart dependencies through OCI references.
Manage Helm charts and container images in separate private repositories while using one familiar Ravenstash workflow.
Ravenstash supports Helm charts distributed as OCI artifacts, without classic index.yaml or ChartMuseum-compatible endpoints.
Keep private charts in your preferred storage region, then give developers, CI, and deployments fast authenticated access worldwide.
Only authenticated users and automation can access your organization’s charts.
Learn more →Keep private charts in Ravenstash-managed storage or supported storage owned by your organization.
Learn more →Give developers, CI, and deployments fast authenticated chart downloads worldwide.
Learn more →No. Ravenstash supports standard Helm OCI charts only, not index.yaml, ChartMuseum APIs, or a generic chart archive upload endpoint.
Yes. Only authenticated Ravenstash users and automation can publish or install your organization’s charts.
Yes. Ravenstash can keep chart signatures, provenance, and related evidence alongside the chart.