Why Rundeck Enterprise?
Rundeck Enterprise is the only way to get professional support from the creators and maintainers of Rundeck. From advice about your Rundeck usage to help with troubleshooting, our support team has you covered. Standard and 24x7 options are available.
Time is your most valuable asset. From onboarding to implementation services, our expert professional services team is ready to help your team quickly maximize the value of your Rundeck investment. Professional services are available exclusively for Rundeck Enterprise customers.
The following features are only available in Rundeck Enterprise. Features may appear in more than one section of this page.
Your Rundeck is a critical service, treat it like one. Whether you are using Rundeck for responding to incidents, provisioning, scheduling batch tasks, or more — your Rundeck has to be there for you. Rundeck Enterprise has the critical capabilities that deliver the resiliency that your business demands.
Rundeck Enterprise's cluster capabilities ensure that your Rundeck service is highly available, easily expandable, and easy to manage.
If a Cluster Member goes down all scheduled jobs on that member are moved to a healthy instance.
This plugin allows Jobs to Resume execution at a failed workflow step.
Within a clustered or active/passive model, the Job replication plugin automatically replicates Job definitions to a secondary Rundeck instance whenever a Job is modified within a project.
Keep the data between instances current. This plugin shares execution data between Rundeck servers to keep them in sync.
Rundeck Enterprise readily handles two types of scale: increasing workload and onboarding more users. Rundeck Enterprise provides the capabilities necessary to handle expanding usage, all while keeping your Rundeck infrastructure simple and easy to manage. Rundeck's customer success team is always available to help Rundeck Enterprise customers design their optimum solution.
Rundeck Enterprise's cluster capabilities ensure that your Rundeck service is highly available, easily expandable, and easy to manage.
Horizontally scale your Rundeck cluster by designating specific cluster members to handle certain types of traffic (user interface vs job execution) or designating specific cluster members to handle certain types of jobs (e.g., Windows vs Linux or PCI vs non-PCI). For end-users, the perception is they are simply accessing a centralized, highly-performant Rundeck.
To simplify the onboarding experience, Rundeck Enterprise can be configured to work with the SSO solutions (e.g. Okta or Ping Identity)
Rundeck features powerful fine-grained access control capabilities. Rundeck Enterprise includes a GUI-based interface that simplifies the building of access control rules and another GUI-based interface for evaluating and testing those rules. This makes it easy to both create rules and see what effect those rules have on a specific person's or group's access — a must for enterprise usage.
As your Rundeck usage grows, so will the infrastructure across which Rundeck jobs will execute. That infrastructure is represented as Nodes. Health Checks allow you to check the health status of Nodes periodically and on-demand. Common uses include showing the status of a Node visually in the Rundeck GUI, and using status to filter out unhealthy nodes when running Jobs.
Securing your Rundeck is an essential part of using Rundeck within your company. Rundeck Enterprise has additional security-minded features that are often considered mandatory for enterprise usage. Also, as a Rundeck Enterprise customer, Rundeck's support and services teams will help you review and implement your company's security requirements.
Rundeck's key storage facility is very useful for controlling access to secrets like SSH keys or passwords. Using this feature, you can expand the number of people who can execute actions that previously required access to passwords or access to privileged environments. Rundeck's key storage facility is encrypted by default in Rundeck Enterprise
Rundeck project configurations often contain sensitive information. In Rundeck Enterprise, project configurations are encrypted.
In addition to using Active Directory or LDAP for authentication, Rundeck Enterprise can be configured to work with the SSO solutions (e.g. Okta or Ping Identity)
Rundeck features powerful fine-grained access control capabilities. Rundeck Enterprise includes a GUI-based interface that simplifies the building of access control rules and another GUI-based interface for evaluating and testing those rules. This makes it easy to both create rules and see what effect those rules have on a specific person's or group's access — a must for enterprise usage.
For most users, Rundeck is their interface to operations. Rundeck Enterprise provides an enhanced user experience for all involved — job writers, job runners, observers, and Rundeck administrators.
The Ruleset Workflow Strategy Plugin gives the Job writer a lot more control over a Job's workflow. You can define a set of rules to describe when and if steps in the workflow should run. Now you can easily do things like forking/merging workflow and conditional execution of specific steps.
Rundeck Enterprise includes the ability to visualize workflows. During execution, the workflow visualization indicates the progress of a job as it executes. This visualization feature is useful for a Job writer or Job runner to understand a Job at a glance. Additionally, the visualization is an indispensable part of helping a broader audience follow the execution of a job.
Webhooks are an essential integration tool. Webhook support in Rundeck Enterprise includes a powerful capability to parse the load of a Webhook and take action based on rules you define. For example, enable selective execution of one or more Jobs based on event data passed to Rundeck via Webhook.
Rundeck Enterprise includes a schedule visualization tool that will show you all of the upcoming Job executions. This feature provides an administrative view that is essential to anyone using Rundeck to execute scheduled batch or maintenance tasks.
Not everyone who runs or views a Job will understand the log output. The Progress Badge feature enables you to easily create graphic badges that will display if the log output for a Job step matches the conditions you define. This feature is helpful to indicate if a step has succeeded, failed, or a warning is needed. Colors, custom text, and even emojis ("😄💯") are supported.
Rundeck features powerful fine-grained access control capabilities. Rundeck Enterprise includes a GUI-based interface that simplifies the building of access control rules and another GUI-based interface for evaluating and testing those rules. This makes it easy to both create rules and see what effect those rules have on a specific person's or group's access — a must for enterprise usage.
Rundeck features a highly pluggable architecture. In addition to supporting a select set of plugins from the Rundeck community, Rundeck Enterprise includes plugins maintained exclusively for Rundeck Enterprise customers. Below is a partial list:
Webhook support in Rundeck Enterprise includes a powerful capabilty to parse the payload of a Webhook and execute Jobs based on the rules you define. For example, enable selective execution of one or more Jobs based on event data passed to Rundeck via Webhook.
Includes Rundeck workflow steps that changes an incident state, checks assigned incidents, checks an incident state, comments an incident, creates an incident, and provides server information from Service Now CMDB.
Execute jobs directly from PagerDuty with this enhanced Webhook Plugin.
Use Rundeck jobs to execute commands and copy files on Windows Servers.
A collection of Workflow Steps that allow creating and managing VMWare Virtual Machines.
Allows users to Power-Off/Power-On/Restart/Suspend/Stand-By a VM.
The Github script plugin is a Workflow Step plugin included with Rundeck Enterprise that runs a command located on a GitHub repo.
The SQLRunner plugin is a node step plugin included with Rundeck Enterprise that executes a .sql script against a JDBC compliant database system.
