Kubius · CronJobs

Run and watch Kubernetes CronJobs

Stop decoding cron strings and hunting for the last run. Kubius shows each CronJob's schedule in plain terms, its recent Jobs and their outcome, and lets you trigger a run on demand - then read its logs.

Works with Google GKE, Amazon EKS, Azure AKS, DigitalOcean, self-managed & more · macOS Sonoma (14) or later

CronJobs without the guesswork

Schedules made readable

See the cron schedule alongside the last and next run, so you know what runs when without parsing the expression.

Run now

Trigger a CronJob on demand - Kubius creates a Job from its template so you can test a change without waiting for the schedule.

Logs from any run

Jump from a CronJob to the Jobs and pods it spawned and read their logs, including from a run that failed.

Success and failure at a glance

Recent runs show completion and failure counts, so a job that's been quietly failing stands out.

Edit resources

Adjust the CronJob's container requests and limits and apply the change - useful when a run gets OOM-killed.

Live and native

Runs update live as they start and finish, in a native macOS app - no kubectl, no agents.

Simple, one-time pricing

Pay once. No subscription.

One-time licence from €49 - no subscription. 14-day free trial, no card required.

Free 14-day trial · macOS Sonoma (14) or later · No agents, nothing to install in-cluster

Questions, answered

Can I trigger a CronJob without waiting for its schedule?

Yes - the Run now action creates a Job from the CronJob's template immediately, so you can test a change or re-run a failed job on demand.

Can I see whether recent runs succeeded?

Yes. Each CronJob shows its recent Jobs with completion and failure counts, and you can open any run's pods to read the logs.

Can I fix a CronJob that keeps getting OOM-killed?

You can edit the CronJob's container resource requests and limits and apply the change; if it's memory, Kubius also surfaces OOM kills on the run's pods.

Do I need kubectl or anything in-cluster?

No - Kubius reads and triggers CronJobs directly through the Kubernetes API with your kubeconfig.

Take control of your CronJobs