Automation V3: Execution License Usage in Provar
Overview
Provar supports different license types to meet varied usage needs. An Execution license is intended exclusively for command-line execution and automation scenarios. To ensure correct usage and maintain licensing integrity, Provar enforces safeguards that prevent Execution licenses from being used to launch or operate the Provar UI.
This help document explains how Execution licenses work, how to activate them correctly, and what to expect if they are applied incorrectly.
License Types at a Glance
- Execution License: Intended only for CLI-based execution (Ant / ProvarDx).
- Development (Floating) License: Supports both Provar UI usage and CLI execution.
Legacy license behavior remains unchanged.
Execution License Behavior
When an Execution license is used:
- Provar UI cannot be launched or used.
- CLI-based execution continues to work normally.
- License checks remain enforced even if license validation calls are blocked.
If an Execution license is applied through the UI, Provar displays an error and prevents activation. The error message is “License key provided is for execution only.”
What Happens if an Execution License Is Used in the UI
- Provar blocks UI access immediately.
- License activation or validation fails.
- A clear error message is shown to guide correct usage.
These safeguards apply to both new and existing Execution licenses.
Logging and Monitoring
To support auditing, troubleshooting, and analytics:
- Open Settings in Provar
- Navigate to Preferences.
- Locate the AI Features toggle.
This information helps administrators and support teams track license behavior and usage patterns.
Backward Compatibility
- Existing license validation and activation flows continue to function as designed.
- Legacy Development and Execution licenses retain their defined behavior.
- No regression is introduced for existing projects or automation workflows.
The changes take effect immediately after the setting is updated.
Conclusion
Execution licenses are strictly enforced for CLI-only usage in Provar. This ensures reliable automation execution, clearer licensing boundaries, and improved visibility into license usage while maintaining full compatibility with existing license models.