Cron, but centralized.

A central control plane for cron jobs across clients, projects, and servers.

CronCommander gives you a live inventory of cron jobs and executions across your infrastructure — organized by workspace, visible from one dashboard, with a full audit trail.

Agents view screenshot

Agents: know what machines exist — and which ones are alive

CronCommander starts with a live inventory of servers running cron jobs.

  • See every registered agent in a workspace
  • Organize servers by client or project with workspaces
  • OS, environment tags, and last-seen status
  • Quickly spot offline or unhealthy machines

This answers questions that are often hard to answer:
"Where is cron actually running?" and "Which client's server needs attention?"

Cron Jobs view screenshot

Cron Jobs: one list, across all servers

Instead of SSH'ing into machines or grepping /etc/cron*, CronCommander shows all cron jobs in a workspace, across all agents.

  • Job name, schedule, command, and next run
  • Jobs scoped to one agent or many
  • No guessing, no duplicated configs
Cron Job detail panel screenshot

Job details: status, history, and configuration

Each job has a dedicated detail view.

  • Active / disabled status
  • Success rate and average execution time
  • Assigned agent and exact command
  • Recent executions at a glance
Executions list screenshot

Executions: what actually ran, ordered by reality

CronCommander records every execution across the fleet.

  • Most recent runs first, regardless of host
  • Status, duration, and start time
  • Filter by job, agent, or time range
  • Full audit trail for compliance
Execution detail panel screenshot

Execution details: no SSH, no log hunting

Click any execution to inspect what happened.

  • Exact command
  • Captured stdout and stderr
  • Exit code and execution time
  • Which agent ran it

CronCommander does not replace cron.
It adds a control plane around it — with the auditability cron never had.

Roadmap (January 2026)

CronCommander is already usable today.
The focus for the first public release is reliability, security, and operational basics.

Planned before public launch (mid–late January):

  • Email, Slack, and Telegram notifications
  • Multi-user support
    • Create additional users
    • Assign users to workspaces
  • Workspace administration
    • Admin users create and manage workspaces
  • Security hardening
    • Authentication and authorization reviews
    • Transport and credential handling improvements

Security is a first-class concern.
We prefer delaying features over shipping something unsafe.

Requirements

The CronCommander agent runs on Linux, FreeBSD, and macOS (amd64, arm64). Any system with cron and outbound network access is supported.

See full requirements →