Universal Automation is the ultra-fast, simple, and lightweight automation platform for PowerShell.
Universal Automation is part of PowerShell Universal.
Why Universal Automation?
I have had such a pleasurable time working with UA so far. This is such a freaking fantastic product for us. You are going to save us so much time. I love the simplicity and design of UA. I have been geeking out about it all day to my coworkers.
Honestly, I wish we had known about this before we cut over to full Jenkins for our job scheduling.
Simple Automation For PowerShell
Run scripts, schedule jobs, and view feedback all in a simple to use dashboard.
View script information such as content, commit history and historical runs of the job, right in the browser.
Easily view the status of jobs. With a click of a button you can see execution time, script output, pipeline output and even the child jobs called from a job.
User Input Controls
Universal Automation reads the parameters of your scripts and automatically creates a UI based on the type of parameter and even performs basic validation. Create simple help desk tools without having to build a UI yourself.
Automate the Automation
Interface with UA via the UA PowerShell module or REST API. Kick off jobs, create new scripts and view results from your console. Changes will automatically be sync’d to git.
Free Updates for a Year
Money Back Guarantee
Frequently Asked Questions
Universal Automation licensing is per PowerShell Universal server. You’ll need to license each instance of a server, even if you are running many on the same machine.
Universal Automation is a cross-platform PowerShell module that is installed from the PowerShell Gallery and works on Windows, Linux and Mac. Schedule jobs are built into PowerShell and integrate with the Windows Task Scheduler.
Universal Automation and Scheduled Jobs can both schedule execution of scripts, retrieve output from the scripts and access the result of scripts.
Universal Automation uses a git repo for configuration that can be stored locally or in a git remote. Schedule jobs uses the local computer system to store files and Task Scheduler tasks to configure jobs.
Universal Automation is PowerShell specific. Unlike Jenkins, it does not require the installation of a separate plugin to execute PowerShell scripts. Universal Automation also integrates with features of PowerShell such as Read-Host and Write-Progress to provide a more native PowerShell experience. Just as with Jenkins, it does collect script output.
Both Jenkins and Universal Automation can execute scripts and schedule scripts to run.
Both Jenkins and Universal Automation allow for users to provide parameters to scripts when running them. Universal Automation doesn’t require any configuration for these parameters as they will be interpreted from the param block of your scripts.
Jenkins has the concept of projects, pipelines, and steps. Universal Automation’s architecture is simpler and doesn’t have the same level of organization. Scripts within UA can trigger other scripts to achieve pipeline-like functionality.
UA and Jenkins both other role-based access. UA provides authentication through its Universal Dashboard website. This requires some configuration of UA.
Jenkins requires the installation of Java as well as the Jenkins server itself. UA is distributed as a PowerShell module and can be downloaded using PowerShellGet.
Universal Automation is PowerShell specific. Although Azure DevOps has tasks that integrate with PowerShell, they only collect output from the stdout stream and don’t integrate as tightly with PowerShell.
Azure DevOps requires a connection to the internet to control the execution of scripts on agents that run on-premises. Universal Automation is a stand-alone agent and does not require a connection to a master to drive the execution of scripts.
Both Azure DevOps and Universal Automation can execute scripts and schedule scripts to run.
Both Azure DevOps and Universal Automation allow for users to provide parameters to scripts when running them. Universal Automation doesn’t require any configuration for these parameters as they will be interpreted from the param block of your scripts.
Azure DevOps has the concept of projects, pipelines, tasks, and steps. Universal Automation’s architecture is simpler and doesn’t have the same level of organization. Scripts within UA can trigger other scripts to achieve pipeline-like functionality.
Azure DevOps offers extensive role-based access and access controls. UA provides role-based access controls. UA provides authentication through its Universal Dashboard website. This requires some configuration of UA.
Azure DevOps configuration is handled through the use of YAML scripts within the configured repository. UA uses PowerShell scripts for configure and jobs that are run as PowerShell scripts.