CronMaster
CronMaster is a web interface for viewing, creating, editing, and managing the cron jobs on your host system.
Platform availability
Available on 2 of 10 platforms
- Unraid
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
73/100 Good
- Maintained
- 82last commit 27 days ago
- Popular
- 631,402 GitHub stars
- Easy to install
- 452 install platforms, install notes, Docker image
- Light to run
- No data
- Security check
- 94no serious findings, 1 minor, CI, tests
Based on 4 of 5 factors.
Availability: platform listings confirmed today, links checked 23 days ago
- GitHub stars
- 1,402
- Open issues
- 8
- Last commit
- 2026-10-25
- Latest release
- 2.4.1
- License
- AGPL-3.0
- Activity
- declining
Checked 7 days ago - source: GitHub (fccview/cronmaster)
Resources & Compatibility
Requirements not published yet.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Set password and target user first In CronMaster's settings file, set AUTH_PASSWORD to a strong password and HOST_CRONTAB_USER to the user whose host crontab (scheduled-task list) it should manage. If you skip these, you may expose the admin page or have it edit the wrong user's scheduled jobs. source
- Leave host permissions in place If you want CronMaster to manage jobs on your actual machine, keep the docker.sock volume (the pipe that lets the app container talk to Docker) and the extra system access settings from the example. Removing them can stop it from seeing or running your host cron jobs. source
- Keep data, scripts, and snippets saved Point the ./scripts, ./snippets, and ./data folders (Docker calls these volumes) to real folders on your machine so your job files, custom snippets, and logs stay outside the container. If you don't, rebuilding or deleting the container can wipe out your CronMaster work. source
- Run container as privileged CronMaster must run in privileged mode to reach the host crontab; without it, it cannot view or modify the host's scheduled jobs. source
Fetched 47 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Does CronMaster require privileged access to manage host cronjobs?
Yes. The app needs to run privileged in order to work as intended.
Can I run a cron job directly from the CronMaster UI?
Yes, you can run jobs from the UI.
Answers sourced from github.com
Community
- Reddit (reddit)
- Central monitor and management for remote cronjobs? : r/selfhosted - Reddit (reddit)
- Recent Discussions - Welcome To The Cronometer Community (forum)
- Rolex Forums - Rolex Forum (forum)
Collected 48 days ago - public community threads