Builds in your own registry

Services that Ryvn builds from GitHub can now push their images and Helm charts to a registry you own — ECR, GHCR, Harbor, Docker Hub, or any OCI registry — instead of the Ryvn Registry. Bind the service to a connected registry and set image to the tag-less repository it should publish to, and every release lands in your registry under your retention, scanning, and access controls. If pull and push need different credentials, add a dedicated publish credential — an IAM role for ECR or a push-scoped token for generic registries — under Settings > Private Registries; GitHub Actions workflows using the Ryvn build action pick up the brokered publish login automatically.