gocron
Schedules YAML-defined cron jobs for self-hosters, with a web UI and run history
Alternative to: Alternatives to Zapier
GoCron runs recurring command jobs on standard five-field cron schedules defined in a YAML file. It passes per-job environment variables, expands ${VAR} in commands, and lets job-specific values override defaults. Jobs can inherit default schedules, timeouts, retries, environment variables, and pre- and post-commands. Configuration changes are loaded without a restart.
A web interface lets users view jobs, start runs manually, read logs, and use a sandboxed terminal. Run history and logs are stored in SQLite, with configurable retention, while live updates arrive through Server-Sent Events. It also supports HTTP health-check callbacks, optional OIDC sign-on, rate limiting, CORS controls, and configured reverse proxies.
It is for self-hosting users who need recurring command scheduling with a browser interface, logs, and single sign-on. Docker Compose, Docker run, Linux binaries, and NixOS are documented installation paths.
The supplied materials do not name a paid product that GoCron replaces, so a sourced product comparison is not possible. They also do not document support for non-Linux platforms or the full range of configuration options.
Key features
- YAML-defined jobs, schedules, and environment variables
- Standard five-field cron scheduling
- Inherited defaults for retries, timeouts, variables, and commands
- Web UI with manual runs, logs, themes, and sandboxed terminal
- SQLite run history with configurable retention
- HTTP callbacks for job starts, completions, and failures
- Optional OIDC single sign-on