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.
Declarative cron scheduling via Kubernetes CRDs. Define schedules as code, version them in Git, and let the operator handle the rest.
Automatically discover repositories across your organization. Filter by group and topic to control exactly which projects get updated.
Run multiple Renovate jobs simultaneously with configurable concurrency control. Process hundreds of repos without bottlenecks.
Monitor discovered projects, job status, and execution history through a built-in web interface. No external dashboard required.
Native Prometheus metrics endpoint and health checks. Plug into your existing monitoring stack with zero configuration.
TTL-based cleanup, active deadlines, and automatic retries. Failed jobs get retried, completed jobs get cleaned up — all configurable.
At the defined time of your schedule, a Renovate discovery job is started automatically.
After discovery finishes, all discovered projects appear in the built-in UI with group and topic filtering.
All projects are set to be scheduled. CRD-based cron schedules control when each project runs.
Every 10 seconds the operator checks for scheduled projects and starts a new Renovate job.
Only as many jobs as defined in spec.parallelism execute at the same time.
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) | — | — | ✓ |
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 →Teams keep dependencies automatically up to date, reducing technical debt and security risks. The mogenius Renovate Operator is an open-source Kubernetes operator that scales Renovate executions with declarative cron scheduling via CRDs, parallel job execution, a built-in web dashboard, and Prometheus metrics. Instead of per-repo scripts, dependency maintenance runs cluster-native and scales from one to hundreds of repositories.
Organizations use the same operator regardless of their preferred Git platform. Supported platforms are GitHub, GitLab, Bitbucket, Azure DevOps, Gitea, and Forgejo, with native webhook integrations for GitHub and GitLab. This makes the operator usable in heterogeneous organizations running multiple Git systems in parallel, without needing separate tools per platform.
Teams keep credentials and dependency data within their own infrastructure and meet regulatory requirements. The self-hosted operator runs in public cloud, on-premises, hybrid, and air-gapped environments, without limits on job volume or repository count and without external data flows. Regulated industries and organizations with strict compliance requirements can use dependency automation that would otherwise not be approved.
Teams get started quickly and do not have to build deployment infrastructure themselves. Installation is done via Helm chart from the GitHub Container Registry or the mogenius Helm repository, after which RenovateJob CRDs are configured with cron schedule, repository filter, and platform credentials. Teams are productive within minutes and can version-control the configuration like any other Kubernetes resource via GitOps.
Teams gain full transparency over the state of dependency automation without additional tools. The operator provides a native Prometheus metrics endpoint, health checks, a built-in web UI with job status and execution history, TTL-based cleanup, active deadlines, and automatic retries. Dependency maintenance plugs directly into existing monitoring stacks without the need to maintain a separate dashboard.
Organizations get full transparency and control without license costs. The Renovate operator is fully open source and available at github.com/mogenius/renovate-operator, including source code, CRD definitions, and documentation. Companies can audit the code themselves, contribute customizations, and stay independent of commercial licensing models.
Install the operator, configure your platform credentials, and let Renovate handle the rest.