Progress OpenEdge licensing covers the OpenEdge relational database, Progress Application Server for OpenEdge, the OpenEdge add-on products and related tools. All of them are governed by the Progress OpenEdge 13.0 End User License Agreement, which applies to “all Progress OpenEdge products (excluding Progress OpenEdge Developer Kit and Progress OpenEdge Command Center)”.[1] The default licence type is perpetual.[1] Progress publishes separate agreements for the Developers Kit, the Classroom Edition, the DevOps Framework and Command Center.[3]
The EULA grants “a non-exclusive, non-transferable, limited, personal license (without the right to sublicense) to use the Product identified in the Order”. The licence model is named in the Order and described in the EULA.[1] The family section lists nine licence models plus several restricted-use licences, and notes that “not all license models are available for all Products”.[1] The same models appear in the older DataDirect agreement, which once covered OpenEdge, DataDirect and Corticon together.[2]
Editions
The EULA does not list editions or prices. It names products in its add-on and product-specific terms: the OpenEdge Enterprise RDBMS and Workgroup RDBMS, Progress Application Server for OpenEdge and its Development version, the OpenEdge Authentication Gateway, Pro2 products, and add-ons such as Transparent Data Encryption, Multi-Tenant Tables, Replication and Replication Plus (Enterprise and Workgroup), OpenEdge Management, Table Partitioning, Change Data Capture and Advanced Security.[1]
Several of these carry their own limits:
- Progress Application Server for OpenEdge - Development may be used only for internal development and testing, never in production.[1]
- The Authentication Gateway may be used only to authenticate users, and not, for example, as a general-purpose web server or application server.[1]
- Additional Products delivered with a Pro2 product may only be used with that Pro2 product. A Site-licensed Pro2 product follows the Site rules, and its Additional Products may carry a separate unit limit.[1]
Metrics
Server-based models
- Core License. “A Core License grants you the right to run the Product on a single Core, on a single Server. The total number of Cores on the Server may not exceed the total number licensed to you.”[1]
- CPU License. One CPU on one Server and one Platform, where the CPU has only one Core. For a multi-core CPU the customer must buy Core licences, or, if no Core model exists for the product, count each Core as one CPU.[1]
- Server/Machine License. One Server and one Platform.[1]
- Instance License. One Instance, meaning “an image of the Product that is created by executing the Product installation or by duplicating an existing Instance”. Not limited by Core, CPU or Server count, but every additional running Instance needs its own licence.[1]
- Site License. Any Server at one Site, a building or campus “sharing the same postal address”, for devices operated by users whose principal place of business is the Site.[1]
User- and device-based models
- Named User. A Named User is “a single individual, Non-Human Operated Device or Process”.[1] Non-Human Operated Devices include temperature devices, bar code scanners and tracking devices. A Process is any automated process not started by a Client Device or such a device, including background jobs.[1]
- Registered Device (also called Registered Client). A designated device, which may be a Client Device, a Non-Human Operated Device or a Process.[1]
- Concurrent Device (also called Concurrent User). A maximum number of devices or Processes accessing the product at any one time, on one Server and one Platform.[1]
- Access Agent. A user or Non-Human Operated Device that “cannot be uniquely identified” or can access the product “for less than two (2) hours a week”.[1]
Named User and Registered Device licences are “multi-server” licences: they are not limited by Core, CPU or Server count, but the product must run on a single Platform, which is “a specific combination of the hardware and the operating system”.[1]
Counting / floors
Every server counts. Core, CPU and Server/Machine licences are required for each Server that runs the product, “including, without limitation, Servers configured for disaster recovery, load balancing, clustering, development, testing and reporting”.[1] The same list applies to Instances and to Concurrent Device licences.[1]
Concurrent Devices are dedicated per server. The EULA gives an example: if a licence permits 100 Concurrent Devices and the customer directs 50 to Server A and 50 to Server B, “you would have to purchase an additional 50 Concurrent Device License for Server B”.[1] A Concurrent Device licence may not be moved between Servers or Platforms.
Named Users and Registered Devices. Each must be identifiable and countable. “A Named User does not have to be logged on to the Product to be counted as a Named User”, and the same is true for Registered Devices. Neither may be shared or used concurrently on several devices.[1] A designation may be moved to a new user or device only when the original no longer needs, or is no longer permitted, access.[1] The Registered Device model “cannot be used to account for, and the Product may not be used by, unknown users”.[1]
Access Agents should “always be purchased in combination with a Named User and/or Registered Device License”. The exception is an environment where none of the users or devices can be identified, or where none uses the application for two or more hours a week.[1]
Indirect use counts. The customer may not let another party access or use the product. “Use” includes “direct or indirect use via thin-client or web-based remote access software which but for the use thereof would have required a copy of the Product to be installed or used locally by that user”.[1] Users reaching an OpenEdge application through a web front end are therefore in scope of the user-based models. Because Named Users include devices and Processes, interfaces and batch jobs need to be counted as well.
Add-ons follow the database. An add-on such as Transparent Data Encryption, Replication or Table Partitioning requires a valid production licence for an OpenEdge database. Its “license model … and license unit quantity … must be the same as the license model and license unit quantity applicable for said database product”.[1] Enterprise replication add-ons require the Enterprise RDBMS, Workgroup replication add-ons require the Workgroup RDBMS, and Table Partitioning requires database version 11.4 or later.[1]
Legacy models. “Machine License, CPU License and Access Agent License models are available only to certain products … for versions 11.7 and lower”, or for later releases delivered as updates to customers who held those rights on or before 2019-02-15.[1] The older Server or Machine Unlimited User licence “is no longer a valid license”. A change to its machine or server, operating system vendor or site requires relicensing under a current model.[1]
Virtualization & partitioning
A Core is “a core processor of a CPU as allocated by you … in both a virtualized and/or non-virtualized environment, and regardless of whether used in a production or non-production (e.g., test, development) environment”.[1] The words “as allocated by you” tie the count to the cores the customer allocates. On that wording, a virtual machine with four allocated cores needs four Core licences, whatever the size of the host. A Server is “a logical computer (can be a physical hardware or a virtual machine)”, and “If the Product is installed on a Container, such Container is treated as a separate Server”.[1] Each container running OpenEdge needs its own server-based licences, or its own Concurrent Device allocation.
Products offered as container images may include third-party components. The customer must license the container technology at its own expense.[1]
Cloud / BYOL
The general terms allow customers to upload on-premises products to a third-party cloud instance, as long as the deployment “complies with all license model restrictions and usage limitations”. The cloud provider may operate the product only for the customer’s benefit, as a Permitted Third Party.[1] The Core and Container rules apply unchanged in the cloud. OpenEdge itself may not be used to provide outsourced, hosting or service bureau services to others.[1]
Programs
- Disaster Recovery License. Used only to recover an application after a failure, crash or data corruption, for a D/R Deployment Period of at most 90 days. Progress must be notified in writing within five business days of the start of the period.[1] The licence carries the same quantity limits and model as the production licence. No Disaster Recovery License is needed to switch to a secondary Server when the primary Server is permanently disabled, but any other temporary move to another Server needs one.[1]
- Testing and Staging License. For “internal quality assurance testing purposes only”; never production; not transferable.[1]
- Developer License. Limited to internal application development and support; not transferable.[1]
- Application Specific License. Where the Order names an application, or OpenEdge was obtained with a third-party application, it may be used only with that application.[1] This is how OpenEdge reaches many customers through independent software vendors.
- Evaluation License. Evaluation and proof of concept only. It “contains a disabling device that will automatically disable the Product thirty (30) days from installation”, unless another period is agreed.[1]
- Maintenance. Perpetual and term licences require first-year maintenance from delivery. Later years are optional, and lapsed maintenance may be reinstated for the current fee plus a reinstatement fee.[1]
- Subscriptions. Notwithstanding the general terms, OpenEdge subscriptions do not renew automatically, and each agreed renewal is priced at the then-current price.[1]
Audits and compliance
The audit clause in section 1.15 applies. Progress may audit records and systems, and underpaid fees are billed at the list price in effect when the audit is completed. If the shortfall exceeds 5% of fees paid, the customer also pays the audit costs.[1] The records the customer must keep include “the number of licenses purchased and being used”. For OpenEdge this means one count per licence model, per Server and per Platform.
Three OpenEdge clauses often matter in reviews. Use is internal to the licensee, and “may not be used by your Affiliates unless specifically authorized in the Order”.[1] Optional components on the installation media may be used only if “a valid license key or control code” was ordered and received.[1] Where the Order states a Use Case or user group, use is limited to it.[1]
Unencrypted ABL source code shipped with the product may be used “for any purpose”, without support.[1] Files marked as Redistributable Code may be distributed unmodified, and only bundled with the customer’s own application.[1]
Out of scope
- Prices and part numbers, which Progress does not publish for OpenEdge.
- The OpenEdge Developers Kit, Classroom Edition, DevOps Framework and Command Center agreements.[3]
- Licence agreements from independent software vendors that embed OpenEdge in their applications.