PowerShell Universal Dashboard is the most popular web framework for PowerShell. Check out this short video to find out more.
The entire Universal Dashboard platform has been moved underneath the PowerShell Universal umbrella. This was done in order to simplify the maintenance of our products and provide a consistent experience for our users. UD Community is no longer being developed.
That said, you can still accomplish everything you could before with PowerShell Universal. You can still create dashboards for free and host them in PSU. You’re existing dashboards should also work if you select the v2 framework. Additionally, many controls that used to be closed source are now available for free and on GitHub.
A premium license of Universal Dashboard provides additional dashboard features within PowerShell Universal. You will be able to enforce authentication and authorization, track dashboard diagnostics, utilize the UD Admin Console. The license is per dashboard.
PowerShell Universal Dashboard site licensing is provided for users that require large scale deployments of Universal Dashboard. If you are running more than a hand full of dashboards, you should consider contacting us about pricing for a site license that will allow you to run as many dashboards as you require.
PowerShell Pro Tools provides a Visual Studio, Visual Studio Code and PowerShell solution. The same license key applies to all three. If you choose to build forms in Visual Studio but package scripts in Visual Studio Code, you can use the same license for each. The license is good for one year of upgrades.
Universal Dashboard is a web framework for PowerShell. You can create interactive websites, simple end-user tools or dashboards to display data. You aren’t limited to charts and graphs. Build tools to make your help desk colleagues more productive.
No. PSScriptPad is just an alternative to VS Code. It currently only supports Windows PowerShell and doesn’t have all the features and extensibility you will find in VS Code. That said, it’s much smaller and faster to launch. It’s great for quickly editing and debugging scripts but might not be suitable for working on large projects. That said, it has features that VS Code does not including a Windows Form Designer and script packaging.
Universal Dashboard is built to service a couple thousand requests a second on good hardware. Don’t expect to use UD to run the next Stack Overflow or Reddit. It works perfectly well for internal tools that tens or hundreds of users are using but isn’t designed to service thousands or tens of thousands of users.
Universal Dashboard is a web framework for PowerShell. It uses technologies that allow you to develop GUIs using PowerShell in the browser. It has a lot of the same functionality as WinForm development in PowerShell. You can create controls such as buttons, text boxes and charts. You can react to user input and interaction as well as invoke PowerShell scripts and cmdlets from your GUIs. Universal Dashboard also runs on any platform, unlike WinForms.
You can use Universal Dashboard Forge to build desktop applications with Universal Dashboard.
Universal Dashboard and Grafana are completely different solutions. While Universal Dashboard can provide the same functionality as Grafana, it requires a working knowledge of PowerShell. Unlike it’s name may suggest, Universal Dashboard is much more than just dashboards. You can build entire tools using UD and PowerShell that accept user input, interact with React components and update dynamically. Grafana is all about reporting. UD is much more about providing a web framework for PowerShell.
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.
Azure Automation requires an Azure Subscription and is billed based on usage of runbooks and usage of other components. Universal Automation is billed via a once a year license fee.
Azure Automation 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.
Azure Automation collects output from the stdout stream. Universal Automation processes and handles native PowerShell object output that can then be stored or passed directly into child processes.
Universal Automation only supports the direct execution of PowerShell Scripts. (Not Python or Graphical)
Universal Automation allows specification of PowerShell version to use on a schedule / per execution basis.
Both Azure Automation and Universal Automation allow the definition of variables that can be used in Scripts.
Both Azure Automation and Universal Automation allow the definition of credentials that can be used in Scripts as well as function as a “run as” account for the script.
Both Azure Automation and Universal Automation allow for users to provide parameters to scripts when running them that are automatically retrieved from the param block of your scripts.
Azure Automation has features for Configuration Management and Update Management. Universal Automation does not have these components.
PowerShell Pro Tools is licensed per user. Each user will need their own license. That user can use that license on as many machines as they are using but only if they are the sole user.
PowerShell Pro Tools augments PowerShell Tools for Visual Studio and the Visual Studio Code PowerShell extension. Rather than a dedicated PowerShell scripting environment, PowerShell Pro Tools integrates into existing development environments. PowerShell Pro Tools supports GUI creation via Windows Forms, packaging as executables and services and even creating installers, just like Sapien PowerShell Studio. Because PowerShell Pro Tools is built into Visual Studio and Visual Studio Code, you also benefit from all the features of those environments such as Git integration. PowerShell Pro Tools even offers features, such as code conversion, that PowerShell Studio does not.