Licensing
Licensing options for PowerShell Universal
PowerShell Universal is licensed per server. We provide licenses for individuals and organizations.
A server is a single running instance of PowerShell Universal.
The license applies to each container instance and not the container host. For example, if you have 10 container instances running, you will need 10 licenses.
Each website running PowerShell Universal will need a license and not a single license for the entire IIS server.
To install a license, click Settings \ License. Click the Add License button to upload your license file. You can also install licenses using the
Set-PSULicense cmdlet. Offline licenses do not require an internet connection but will need to be reinstalled when the subscription expires, in you wish to update the version of PowerShell Universal. Online licenses require an internet connection and access to https://ironmansoftware.com in order to verify subscription status. Proxy configuration can be done by clicking Settings \ General and configuring the proxy URI and, optionally, credentials. You can also configure proxy settings with the
Set-PSUSetting cmdlet. When a server license is purchased, you will be able to generate developer licenses for users building solutions for your team. Developer licenses do not allow remote access and are intended to be used locally. Do not use developer licenses when hosting a server for remote access for testing or production.
You can generate a developer license on the Settings \ License page by clicking the Generate Developer License button.
Generate Developer License
The following features of PowerShell Universal require a license.
- Debugging Tools
- Enterprise Authentication
- OpenID Connect
- SAML2
- WS-Federation
- Windows Authentication
- Custom Authentication Scripts
- Enterprise Authorization
- Access Controls
- Custom Authorization Scripts
- Git Support
- Module Management
- Non-Database Credential Vaults
- SQL Support
- Triggers
- Terminals
- Custom Login Page
Last modified 2mo ago