App-owned, Versioned Helm Charts
AdoptFactorial rates App-owned Helm charts as Adopt (2026). Subtool and the Rust engine of FlowDrop both work this way: the app repository owns the chart and publishes it to our registry as an OCI artifact on every release, and a deploy repository names the chart version that production runs, together with its values and 1Password secret paths.
In this pattern the chart lives in the same repository as the application. It describes what only the application knows: services, ports, probes, required environment variables and secrets. Every release publishes the chart as an immutable OCI artifact whose version matches the release, and the chart's default image tag is the same version, so a chart always deploys the images it was built for.
What differs per installation (host names, cluster issuer, storage class, resources, secret paths) lives in a separate deploy repository or values file, which pins a chart version the same way it pins an image tag. A change to the application's runtime contract then ships in one merge request together with the code that needs it.
Updates
Subtool and the Rust engine of FlowDrop both work this way: the app repository owns the chart and publishes it to our registry as an OCI artifact on every release, and a deploy repository names the chart version that production runs, together with its values and 1Password secret paths. We moved FlowDrop's chart into the app repository after keeping it separate: every change to the environment contract spanned two repositories, and code could land without the chart change it needed. Deriving the chart version from the release tag, instead of bumping it by hand, removed a whole class of failed publishes.