Run Renovate as a Kubernetes resource: repos and schedules are CRDs, jobs are isolated per repo, webhooks trigger immediate runs, and a built-in UI replaces digging through pod logs. For teams running Renovate self-hosted at scale, beyond what a cron job or SaaS runner can handle. No external database, no license key, no SaaS lock-in. Configurable parallelism, non-root execution by default.MIT License, fully open source
No reviews yetBe the first to leave a review for mogenius Renovate Operator
Maker
π
Hey Product Hunt π
Quick context on why we built this: we run a lot of Kubernetes workloads ourselves and kept hitting the same wall with self-hosted Renovate. The official Helm chart is essentially a CronJob, hosted runners mean SaaS lock-in, and Mend's CE/EE requires a license key. None of that fit how we wanted to operate Renovate at scale.
So we built a Kubernetes operator:
- CRDs as the single source of truth. Your Renovate config lives next to the rest of your manifests, manageable via kubectl, Argo CD, or Flux. No external database.
- Job isolation. Each repo runs as its own Kubernetes Job with configurable parallelism. One stuck repo doesn't block the queue.
- Webhook support out of the box for GitHub and GitLab, so updates trigger on push instead of waiting for the next cron tick.
- Built-in UI for discovered repos, job status, and run history. No more grepping pod logs to find out what happened.
- Non-root execution, minimal privileges, secrets stay in the cluster.
MIT License and fully open source. No paid tier, no upsell.
If you're already running Renovate self-hosted, curious what your setup looks like and what's missing.
Repo + install via Helm: https://github.com/mogenius/reno...
Thanks for checking it out.
Mailwarm
It's amazing. I actually love this. Nice tool!!
mogenius
@daniel_nwankwoΒ Thank you, we really appreciate your feedback :)