Use Cases

Self-Service Scheduling

Self-Service Scheduling

The Problem

Every enterprise has operational workloads that need to be scheduled to run unattended. Sometimes these are maintenance tasks. Other times these are business batch processing or analytics jobs. When it comes to tools, you previously had to choose between a sprawl of individual schedulers (Cron, Task Scheduler, etc.) or the expense of a complicated monolithic enterprise scheduler (Tidal, Control-M, Autosys, etc.).



With the individual scheduling tools, you have to contend with the management overhead of multiple low-level local configurations. With the centralized enterprise schedulers, you get an overly complicated tool requiring specialized knowledge to write and manage — and lets not forget the budget-busting per job license model.




To further complicate matters, neither type of tool was designed for self-service. Without self-service capabilities it is difficult to avoid the bottlenecks and the delays that come from only a few people being able to manage creating and maintaining scheduled jobs. 


The Rundeck Solution

Rundeck makes it simple and easy to setup self-service job scheduling. Rundeck provides a centralized solution that is easy to manage, doesn’t involve new skills or language, and is highly cost-effective (open source or enterprise licenses with no per-job costs).




  • Quickly create workflow jobs that span your existing tools, scripts, system commands, and API calls
  • Leverage the existing automation tools and languages that your teams already know
  • Define the schedule for each job (workflow)
  • Make your scheduled jobs safer to run unattended by leverage built-in features like error-handling, fork and merge style workflow features, conditionals, data passing between steps, notifications, and more
  • Use Rundeck’s built-in access control features to define the fine-grained permissions (use you existing AD/LDAP or SSO for authentication) determining who can create, modify, or view what jobs.
  • Rundeck’s simplicity and low barrier to entry means that you can easily allow any number of your colleagues to define and manage operations tasks, analytics jobs, or any other scheduled activity
  • Use read-only access combined with logging and notification features to give broad visibility into provisioning activity across your organization. 
  • Rundeck’s resource model learns details about your environment from multiple sources (Rundeck plugin points) so you automation can be parameterized and kept up to date


ROI Tips

  • If you are consolidating multiple local schedulers, baseline the overhead costs of managing individual schedulers. Be sure to consider both the maintenance cost (labor to setup infrastructure  and maintain) and cost of issues that arise from schedule collisions, missing configurations, or other errors. 
  • If you are avoiding enterprise schedulers, baseline the overhead costs of having a complicated and expensive siloed solution. Be sure to consider the cost of having to train and maintain knowledge of a complicated specialized tool and also consider the expensive per job based licensing costs.
More about Rundeck’s ROI