Alternatives

	cron	BeyondCron	Dkron Dkron JobScheduler Mistral Rundeck Temporal
Interface
Command line help_outline	remove	check	~ ~ check check check check	Using curl and json. Using a REST api or PowerShell module. Workflow are defined using yaml files.
Shell help_outline	remove	check	remove remove remove remove remove remove
Web help_outline	remove	check	check check remove ~ check ~	Does not include the ability to visualise job flows. Enhanced interface requires Rundeck Enterprise. Does not support the ability to create or visually display workflows.
Job types
Command	check	check	check check check check check ~	Jobs run as the root on the dkron agent host. To run as a different user and/or on a different host, su/sudo and/or ssh are required. Along with ACLs, BeyondCron manages this transparently. Jobs run under the JobScheduler process user id. To run as a different user, use of su/sudo is required within the job definition. Along with ACLs, BeyondCron manages this transparently. As supported by the workflow language.
Delay/Trigger	remove	check	remove remove remove remove remove ~	As supported by the workflow language.
Container	remove	check	~ remove remove check remove ~	Requires Dkron Pro. As supported by the workflow language.
Email help_outline	remove	check	~ check check remove remove ~	Requires Dkron Pro. As supported by the workflow language.
SQL help_outline	remove	check	remove check remove ~ remove ~	Requires Rundeck Enterprise. As supported by the workflow language.
Webhook help_outline	remove	check	check remove check check remove ~	As supported by the workflow language.
Job options
Calendars	remove	check	remove check remove check remove remove	Requires Rundeck enterprise
Date/times help_outline	remove	check	remove remove remove remove remove ~	As supported by the workflow language.
Job flows help_outline	remove	check	~ check check check check check	On success only for a single parent job.
Wildcards help_outline	remove	check	remove remove remove remove remove remove
Inherited properties help_outline	remove	check	remove remove remove remove question_mark ~	As supported by the workflow language.
Private properties	remove	check	remove remove remove remove remove ~	As supported by the workflow language.
Timezones help_outline	remove	check	remove check remove remove check remove
Schedules
Calendar help_outline	remove	check	remove remove remove remove remove remove
Cron help_outline	check	check	~ remove check check remove check	Does not support L (last day) W (weekdays) or # (nth day-of-week of the month) symbols.
Daily help_outline	remove	check	remove check remove check check remove
Date help_outline	remove	check	check check remove remove remove remove
Monthly help_outline	remove	check	remove check remove check check remove
Repeat help_outline	remove	check	check check remove remove check remove
Sunrise/Sunset help_outline	remove	check	remove remove remove remove remove remove
Combination help_outline	remove	remove	remove question_mark remove remove remove remove
Security
Users	check	check	~ check remove check remove check	Requires Dkron Pro and only supports a single user and password.
RBAC help_outline	remove	check	~ ~ question_mark check ~ ~	Available as a preview in Dkron Pro. Does not include user/host control. e.g. restrict the ability to define jobs that execute as root, and/or in a production environment. Full support requires commercial version. Does not include user/host control. e.g. restrict the ability to define jobs that execute as root, and/or in a production environment.
Audit logs help_outline	remove	check	remove check question_mark check ~ ~	Commercial version only. Audit Logging only captures operations in the Temporal Cloud control plane and not the data plane. This means events such as Workflow Start, Workflow Terminate, Schedule Create, etc. won't be logged.
Job history help_outline	remove	check	check check question_mark check check check
Job output help_outline	remove	check	check check remove check check check
Server
Agentless	remove	check	~ check check check remove remove	Jobs run as the root on the dkron agent host. To run as a different user and/or on a different host, su/sudo and/or ssh are required. Along with ACLs, BeyondCron manages this transparently. Temporal executes workflows on the Temporal servers
Clustering help_outline	remove	check	check ~ question_mark ~ ~ check	Master-follower cluster architecture. Requires a commercial license. Rundeck Enterprise only. Warm standby of server available with commercial verison.
Scaling help_outline	remove	check	~ check question_mark ~ remove check	Single scheduler, multiple agents Rundeck Enterprise only.
Datastore	remove	AWS, SQL database	question_mark SQL database MySQL, PostgreSQL or Sqlite H2 or MySQL Ingres, MySQL or PostgreSQL Cassandra, MySQL, PostgreSQL or SQLite
Dependencies		Java git ssh sudo	remove Java Python Horizon ssh Java ssh Java Python Go, Java, PHP, Python, TypeScript or .NET
Reference open_in_new open_in_new open_in_new open_in_new open_in_new open_in_new			A distributed Cron service with, API, no SPOF and an easy to use dashboard Open source workload automation system designed for performance, resilience and security
Comments			No ability to stop/kill a running job dkron pro supports HTTP basic auth for a single identity All command jobs run under the JobScheduler process user id. All jobs appear to execute under the Schedulix user id. The user interfaces looks powerful but a challenge to use. Unlike BeyondCron, Temporal workflows do not appear to be able interact with each other.