Licensing

How VeloPhex subscriptions work on the Orchestrator, which components are open source, and where to find license terms and third-party notices.

VeloPhex is licensed as a subscription on the Orchestrator, per tenant or for the whole installation. There is no counting of users, seats or Robots. This page explains how a subscription is applied, which components are open source, and where to find the terms that apply.

Open source: the extensibility surface#

These packages are licensed under the MIT License. You can use them to build your own activities, tools and integrations:

Package What it is for
Velophex.Workflow.Sdk Writing runtime activities
Velophex.Studio.Sdk Design-time presentation of activities in Studio
VeloPhex.Platform.Contracts, VeloPhex.Platform.Executor.Protocol, VeloPhex.Platform.Contracts.Testing The shared contracts: project.json, package manifest, signatures, protocols, error catalog and test vectors
velophex (Python SDK) Writing, running, packing and publishing Python automations
VeloPhex.ActivityPackage.Build, VeloPhex.ActivityPackage.Templates Building activity packages: the packaging targets, the manifest generator and the dotnet new template

Each MIT package carries the license expression and the full MIT text with its copyright notice.

Proprietary components#

Everything else is proprietary to VeloPhex:

  • Studio, the Robot (including the Assistant and the User Host), the Orchestrator and the Browser Host.
  • The workflow engine's compiler, runtime and executor (Velophex.Workflow.Compiler, Velophex.Workflow, Velophex.Workflow.Executor).
  • All activity packages, including VeloPhex.UIAutomation.Core.

Proprietary packages include a LICENSE.txt notice. Use of the products is governed by the VeloPhex End User License Agreement and by your agreement with VeloPhex.

The EULA#

Every installer shows the EULA and asks you to accept it: the Robot and Studio Setup bundles (a license link and an accept checkbox on the first page) and the MSIs (a license dialog). A silent install accepts the terms by being silent, as with any Windows installer, so make sure whoever deploys silently has accepted the terms for your organization.

The Browser Host MSI has no user interface; it installs the EULA next to its license and notices in %ProgramFiles%\VeloPhex\BrowserHost.

Third-party components#

VeloPhex products include open-source components such as the .NET runtime, Roslyn, FlaUI, PuppeteerSharp, ClosedXML, AvalonEdit, uv and CPython. Their licenses and notices travel with the product:

  • THIRD-PARTY-NOTICES.txt is installed next to each product.
  • Every release includes a CycloneDX SBOM (*.cdx.json) listing the components and versions.

Studio includes libgit2 for Git support, under GPL-2.0 with a linking exception that permits shipping it unmodified in a proprietary product.

Subscriptions#

A tenant's subscription comes from, in order:

  1. The tenant's own subscription, assigned by a platform administrator (PUT /api/v1/tenants/{tenantId}/subscription).
  2. Otherwise the instance licence: a signed licence file a platform administrator uploads under Platform admin, Licence. The file is verified offline against a signer built into the Orchestrator, and it can be limited to one installation and to named tenants.

A tenant that neither covers runs without restrictions unless the deployment sets Licensing:RequireSubscription=true, in which case it is in limited mode.

A subscription is trial or active until its term ends, then in grace for the number of grace days it carries, then lapsed. In limited mode (lapsed or cancelled) new job starts, replays, attended starts and package publishes are refused with 402 subscription_lapsed, and time and queue triggers skip without being disabled. Reads, administration and jobs already running are never blocked, and platform administrators are never locked out. Administrators get notices 30, 7 and 1 days before the term ends.

Any tenant member with tenant.view can read the tenant's subscription: GET /api/v1/tenants/{tenantId}/subscription.

No call home

The Orchestrator does not contact VeloPhex to validate a licence. An optional online refresh exists for renewals, but it is off unless a platform administrator configures Licensing:RefreshUrl.

Product services per tenant#

A tenant's services decide which parts of the product its members see. A platform administrator manages them under Platform admin, Tenants, Services. Home and the Orchestrator are always included; optional products such as QA Hub or Launchpad are available only when the subscription names them. You can check what a tenant has with:

HTTPCopy
GET /api/v1/tenants/{tenantId}/services

Commercial questions#

For subscriptions, terms or anything about your agreement, contact your VeloPhex account team or the sales contact on velophex.com. For product questions, see Getting help.

Next steps#

Open source: the extensibility surface

Proprietary components

The EULA

Third-party components

Subscriptions

Product services per tenant

Commercial questions

Next steps