OpenText licensing

OpenText licensing covers two document families under one contract. All OpenText software is licensed under the OpenText End User License Agreement (EULA, dated 1 July 2026). The EULA grants a non-transferable, internal-business-use licence “subject to the License Models”, and that licence is perpetual unless the Transaction Document (TD) says otherwise.^[2] The EULA defines the License Model Schedule as either the “License Model Schedule” or the “Additional License Authorization (ALA)” posted by OpenText.^[2] The OpenText License Model Schedule (v3.0, effective 29 April 2024) defines the OpenText License Models without naming products, so the TD states which model applies to a product such as Content Server or Documentum.^[3] Former Micro Focus products are governed by the EULA together with product-family Additional License Authorizations and the Non-Production Licensing Guide.^[1]

Editions

OpenText does not publish one edition list for its portfolio. Each ALA opens with a table of the products it covers and each product’s non-production class.

• Application Quality Management (ALM / Quality Center). Application Lifecycle Management (ALM) Edition, Quality Center Enterprise Edition and Quality Center Express Edition. ALM Edition includes a High Availability Server. Quality Center Enterprise needs a separate licence for one.^[4]
• Software Delivery Management (ALM Octane). Pro, Enterprise and Enterprise with MBT Editions, plus the Developer Add-On and the Aviator Add-On.^[4]
• Project and Portfolio Management. Sold as modules and as Enterprise, Portfolio Manager, Project Manager and Team Member Suites. Each suite is a fixed bundle of Named, Casual Named or Power Named User module licences.^[4]
• Functional Testing (UFT). UFT One, UFT Developer, UFT Ultimate Edition, Business Process Testing, Service Test, and Functional Testing Lab for Mobile and Web (Express, Professional, Premium and Ultimate).^[5]
• Performance Engineering (LoadRunner). LoadRunner Professional, LoadRunner Enterprise, Diagnostics, Network Virtualization and Service Virtualization.^[6]
• Content Server, Documentum and other OpenText content products. The License Model Schedule does not list these products by name. Its models (Named User, Concurrent User, Server, CPU and others) apply as the TD specifies. Some software needs more than one License Model at the same time.^[3]

Metrics

OpenText names its metrics in two vocabularies. The License Model Schedule uses “License Models” and the ALAs use “License Options”. The catalog keeps the vendor names apart, even where two of them sound alike (Standard Named User and Named User).

For background on the metric families, see named-user licensing, concurrent and device licensing and processor and core licensing.

Counting / floors

License Model Schedule (effective 2024-04-29)

• Standard Named User. One licence for each individual authorized to access the Software, whether or not they use it. Each additional login or password, and each additional implementation that connects to a unique logical database, needs another licence. A licence can be re-allocated only after the person leaves or permanently changes role, and only once their account has been deleted.^[3] Rules: Standard Named User: license every authorized individual; re-allocate only after leaving or role change and account deletion, Named User: extra licence per additional login and per additional implementation on a unique logical database.
• Occasional Named User. Use on no more than 52 calendar days per calendar year. From the 53rd day the user needs a Standard Named User licence. Occasional status must be assigned when the user is first authorized.^[3] Rule: Occasional Named User: no more than 52 calendar days per calendar year; Standard Named User from the 53rd day.
• Standard Concurrent User. Add up the maximum concurrent capacity of every Program Instance. That capacity is the higher of peak simultaneous users and the keys installed. Keys are permanent to their server. A user on two Program Instances at once needs a licence on each.^[3] Rule: Standard Concurrent User: sum the maximum concurrent capacity of every Program Instance; keys are permanent to a server.
• Multiplexing does not reduce Named or Concurrent User counts.^[3] Rule: Multiplexing does not reduce Named or Concurrent User counts.
• Version. Licences follow the License Model Schedule version in force when they were bought. Earlier versions are 2.0 (21 July 2016) and 1.0 to 1.2 (2011).^[3] Rule: The License Model Schedule version in force at purchase governs those licences.

Additional License Authorizations

• ALM / Quality Center (ALA of 2026-05-28). Licensed only as Site, Area or Global Concurrent User. Moving a Site or Area licence costs a geographic relocation fee.^[4] Rule: Site, Area and Global licences: relocation fee; Remote Access outside the Area needs Global.
• Named User License Option (2026-05-28). Installed on a single Device, for the number of Named Users in the order. A Named User can be changed permanently, or temporarily to cover an absent worker.^[4] Rule: ALA Named User License: single Device install; change a Named User permanently or temporarily for an absent user.
• LoadRunner Professional (ALA of 2025-01-20). Load tests need Controller and Virtual User licences. VU+C products include unlimited Controllers. Concurrently used Virtual Users cannot exceed the number licensed. A multiprotocol script uses one licence from each protocol bundle it contains. Virtual User Flex Days last 24 hours from first execution and expire one year after purchase.^[6] Rules: LoadRunner Professional: Controller + Virtual User licences; VU key on a Controller at a Site in the licensing country; one Controller user at a time, Multiprotocol Virtual User scripts consume one licence per protocol bundle, Virtual User Flex Days: unlimited runs for 24 hours from first execution; expire one year after purchase.
• UFT One / UFT Developer (ALA of 2026-06-19). Licensed by Seat User or Concurrent User, for functional testing only. Under Seat User, Remote Access is limited to users regularly employed at the Site, and the application under test must reside at the same Site. UFT Ultimate is Concurrent User only.^[5] Rule: UFT One / UFT Developer: Seat User or Concurrent User; functional testing only; Seat User Remote Access limited to Site users.

Non-production

• License Model Schedule (2024-04-29). Non-production licences cover testing, development, backup, failover and hot or cold standby. They do not cover load balancing.^[3] Rule: License Model Schedule non-production licences: test, development, backup, failover or standby only; no load balancing.
• Micro Focus products (Guide dated January 2025). For Class 1 products, up to six no-charge non-production licences per production licence: one hot standby, one cold standby, one development system and up to three test systems. Class 3 products get none. Term and subscription UFT and LoadRunner are Class 3 in their ALAs. Non-production licences for term products expire with the term.^[7][5][6] Rule: Micro Focus products, Class 1: up to six no-charge non-production licences per production licence.

Virtualization & partitioning

• Server (License Model Schedule, 2024-04-29). Each operating-system instance on a physical server counts as a separate Server. A virtual server with its own operating system in an isolated partition is also a Server. No single Server may have more than 32 CPUs, and a CPU is one processing core.^[3] Rule: Server = each OS instance or virtual server; no Server may exceed 32 CPUs.
• Production Logical CPU (2024-04-29). On an IBM AIX LPAR or a similar partition, each unit of CPU processing power, or fraction of one, needs one licence.^[3] Rule: Production Logical CPU: one licence per unit of virtual CPU capacity (e.g. each LPAR unit or fraction).
• Operating System Instance (Performance Engineering ALA, 2025-01-20). Each virtual machine, container, guest or zone is its own OS Instance. Diagnostics needs one licence per OS Instance that contains an Application Server.^[6]
• Concurrent User License Option (ALAs). The software may be installed on any number of Devices, physical or virtual, as long as actual simultaneous use stays within the licences bought.^[4]

The retrieved documents publish no host-based, cluster-wide or unlimited-virtualization licence option. See virtualization and partitioning.

Cloud / BYOL

OpenText publishes no public-cloud BYOL policy in the documents retrieved. The EULA (2026-07-01) licenses internal business use only. It prohibits using the Software for “outsourcing, hosting, service bureau or like use” and allowing access by, or use for the benefit of, any third party.^[2] Rule: EULA: internal business use only; no hosting, outsourcing or service bureau use; no transfer. Because the License Model Schedule treats a virtual server as a Server, a customer-managed cloud VM is counted like any other Server.^[3] Third Party Use of ALM / Quality Center at the third party’s location needs an Area or Global Concurrent User licence.^[4] Rule: Third Party Use of ALM / Quality Center at the third party's location requires an Area or Global licence. OpenText-hosted SaaS falls under the separate Cloud Services General Terms and Service Descriptions.^[1]

Programs

• Support (OpenText Support and Maintenance Program). Governed by the current maintenance programme handbook. Support runs in 12-month periods from delivery. OpenText may suspend Support for an uncured breach, including non-payment, or if the customer does not cooperate with verification.^[2] See software maintenance and support.
• Term LTU and Term Support (Term License to Use (Term LTU) and Term Support). A Term LTU is valid for a stated period (1M, 1Y and so on) and is not perpetual. Term Support is valid only for the period of the Term LTU.^[4] Rule: EULA: licences perpetual unless the Transaction Document specifies otherwise. See subscription and consumption licensing.
• Non-Production Licensing (Non-Production Licensing (Classes 1-4)). Classes 1 to 4. Available only for products on active support with fees paid.^[7]
• Compliance (EULA 2026-07-01). Customers keep records during the term and for 24 months after it. They return self-audit questionnaires within 30 days. OpenText may audit once a year. A shortfall is billed at the then-current list price plus Support fees for the period of non-compliance.^[2] Rule: EULA Compliance: records for 24 months after term, self-audit within 30 days, annual audit, shortfall at list price plus Support. See software license audit.
• Evaluations. The EULA sets a 30-day Trial (60 days for pre-release software). The 2024 License Model Schedule describes a 60-day evaluation on one Server for up to five individuals. The two documents differ.^[2][3] Rule: Evaluations: EULA Trial 30 days (60 days pre-release); License Model Schedule evaluation 60 days, single Server, up to five individuals.

Out of scope

• OpenText Cloud Services (SaaS) terms and Service Descriptions.^[1]
• Vertica / Analytics Database. Rocket Software acquired it on 11 May 2026.^[1]
• Other ALAs not catalogued here: Service Management, Operations Bridge, Application Security (Fortify), Identity and Access Management, COBOL and host connectivity, Secure Content Management, among others.^[1]
• Actuate / BIRT and Connectivity (Exceed) models in the License Model Schedule appendices.^[3]
• Price lists and part numbers: none were found among the retrieved OpenText documents.
• Product-specific Content Server and Documentum model assignments, which appear only in customer TDs.

Catalog rows

• Metrics
  • Standard Named User
  • Occasional Named User
  • Standard Concurrent User
  • Standard Anonymous User
  • Server
  • CPU
  • Program Instance
  • Transactions Per Year
  • Named User
  • Casual Named User
  • Power Named User
  • Concurrent User
  • Seat
  • Seat User
  • Instance
  • Virtual User
  • Virtual User Flex Days
  • Operating System Instance
• Rules
  • Standard Named User: license every authorized individual; re-allocate only after leaving or role change and account deletion
  • Named User: extra licence per additional login and per additional implementation on a unique logical database
  • Multiplexing does not reduce Named or Concurrent User counts
  • Occasional Named User: no more than 52 calendar days per calendar year; Standard Named User from the 53rd day
  • Standard Concurrent User: sum the maximum concurrent capacity of every Program Instance; keys are permanent to a server
  • Server = each OS instance or virtual server; no Server may exceed 32 CPUs
  • Production Logical CPU: one licence per unit of virtual CPU capacity (e.g. each LPAR unit or fraction)
  • License Model Schedule non-production licences: test, development, backup, failover or standby only; no load balancing
  • Micro Focus products, Class 1: up to six no-charge non-production licences per production licence
  • Site, Area and Global licences: relocation fee; Remote Access outside the Area needs Global
  • Third Party Use of ALM / Quality Center at the third party's location requires an Area or Global licence
  • ALA Named User License: single Device install; change a Named User permanently or temporarily for an absent user
  • LoadRunner Professional: Controller + Virtual User licences; VU key on a Controller at a Site in the licensing country; one Controller user at a time
  • Multiprotocol Virtual User scripts consume one licence per protocol bundle
  • Virtual User Flex Days: unlimited runs for 24 hours from first execution; expire one year after purchase
  • UFT One / UFT Developer: Seat User or Concurrent User; functional testing only; Seat User Remote Access limited to Site users
  • EULA: internal business use only; no hosting, outsourcing or service bureau use; no transfer
  • EULA Compliance: records for 24 months after term, self-audit within 30 days, annual audit, shortfall at list price plus Support
  • Evaluations: EULA Trial 30 days (60 days pre-release); License Model Schedule evaluation 60 days, single Server, up to five individuals
  • The License Model Schedule version in force at purchase governs those licences
  • EULA: licences perpetual unless the Transaction Document specifies otherwise
• Programs
  • OpenText Support and Maintenance Program
  • Term License to Use (Term LTU) and Term Support
  • Non-Production Licensing (Classes 1-4)
• Evidence
  • Standard Named User License Model (i)
  • Named User additional logins and implementations
  • Multiplexing does not reduce licences
  • Occasional Named User 52 calendar days
  • Standard Concurrent User maximum concurrent capacity
  • Server definition: 32 CPU cap
  • Production Logical CPU LPAR example
  • Non-Production Licenses exclude load balancing
  • Class 1: six no-charge Non-Production Licenses
  • Remote Access outside the Area requires Global
  • Third Party Use requires Area or Global
  • ALA Named User change rule
  • LoadRunner Professional Virtual User quantity
  • Multiprotocol Virtual User uses two licences
  • VUFD validity and expiry
  • UFT One Seat User Remote Access
  • EULA use restriction: outsourcing, hosting, service bureau
  • EULA non-compliance at list price
  • EULA Support 12-month period
  • EULA Software Term
  • License Model Schedule version at purchase
• Sources
  • OpenText End User License Agreement (01 July 2026)
  • OpenText License Model Schedule v3.0 (April 2024)
  • ALA: Software Delivery, Application Quality and Portfolio Management (May 2026)
  • ALA: Functional Testing (June 2026)
  • ALA: Performance Engineering (January 2025)
  • Non-Production Licensing Guide (January 2025)
  • Software License & Cloud Services Documents index