DevOps Platform Engineers
Open Source · MIT License

Self-hosted Renovate.
Kubernetes-native.

Run Renovate on your own infrastructure with CRD-based scheduling, parallel execution, auto-discovery, and a built-in UI. If you self-host Renovate and already run Kubernetes, this operator gives you the control and observability that plain self-hosted setups lack.

Renovate Operator Web UI showing discovered projects and job status
Supports
GitHub GitLab Bitbucket Azure DevOps Gitea

Everything you need to
run Renovate at scale.

📅

CRD-based Scheduling

Declarative cron scheduling via Kubernetes CRDs. Define schedules as code, version them in Git, and let the operator handle the rest.

🔍

Auto-Discovery with Filtering

Automatically discover repositories across your organization. Filter by group and topic to control exactly which projects get updated.

Parallel Execution

Run multiple Renovate jobs simultaneously with configurable concurrency control. Process hundreds of repos without bottlenecks.

💻

Built-in Web UI

Monitor discovered projects, job status, and execution history through a built-in web interface. No external dashboard required.

📈

Prometheus Metrics & Health Checks

Native Prometheus metrics endpoint and health checks. Plug into your existing monitoring stack with zero configuration.

🔄

Job Lifecycle Management

TTL-based cleanup, active deadlines, and automatic retries. Failed jobs get retried, completed jobs get cleaned up — all configurable.

From schedule to PR in five steps

01

Discovery Trigger

At the defined time of your schedule, a Renovate discovery job is started automatically.

02

Project Discovery

After discovery finishes, all discovered projects appear in the built-in UI with group and topic filtering.

03

Scheduling

All projects are set to be scheduled. CRD-based cron schedules control when each project runs.

04

Job Processing

Every 10 seconds the operator checks for scheduled projects and starts a new Renovate job.

05

Concurrency Control

Only as many jobs as defined in spec.parallelism execute at the same time.

Renovate at scale
needs an operator.

The CLI and Community Edition are great starting points. When you’re managing hundreds of repositories on Kubernetes, the operator adds the scheduling, concurrency, observability, and lifecycle management to keep everything running smoothly.

Feature CLI Community Edition Operator
Fully open source, no signup
Automated dependency updates
Runs on your own infrastructure
Auto-discovery
Webhook API for on-demand runs
Web UI
Declarative cron scheduling via CRD
Auto-discovery with group/topic filtering
Per-project status tracking in-cluster
Parallel execution with concurrency control
Prometheus metrics & health checks
Kubernetes-native pod scheduling
Leader election for high availability
Job lifecycle management (TTL, deadlines, retries)

Up and running
in one command.

OCI Registry
$ helm -n renovate-operator \
  upgrade --install renovate-operator \
  oci://ghcr.io/mogenius/helm-charts/renovate-operator \
  --create-namespace --wait
Helm Repository
$ helm repo add mogenius \
  https://helm.mogenius.com/public \
  --force-update

$ helm -n renovate-operator \
  upgrade --install renovate-operator \
  mogenius/renovate-operator \
  --create-namespace --wait
319+
GitHub Stars
159
Releases
MIT
License
6
Platforms

Need more than dependency updates?

The mogenius platform gives you multi-cluster Kubernetes management, developer self-service, AI governance, and toolchain orchestration — all from one control plane.

Explore the Platform →

Get started
in minutes.

Install the operator, configure your platform credentials, and let Renovate handle the rest.

View on GitHub Read the Docs →