The End User Agreement (EUA) is the master document behind TIBCO Software licences. It is a Cloud Software Group agreement, not a TIBCO-specific one: it says it is a legal agreement between the customer and the Cloud Software Group Holdings business unit that enters the Order, and it defines the “Business Unit” as the affiliate responsible for developing, supporting and licensing a specific Product.[1] TIBCO-specific terms sit in the Business Unit Terms and product pages.[4] This article walks through the parts that matter for compliance, audit and renewal. Citrix has its own page on the same agreement family, Citrix End User Agreement.
Versions
The retrieved EUA shows “Version 2.5” and a 2026 copyright and no effective date.[1] The Enterprise Message Service 10.4.0 licence package contains “Version 2.0 - Page 1 of 97” with a 2025 copyright, which appended third-party notices to the EUA text.[2] A customer might therefore hold paper or downloaded copies of different versions, and the relevant one is the version incorporated in the Order or accepted on delivery. The Terms provide that the Business Unit Terms, Maintenance terms and some other documents may be updated by the vendor from time to time without notice, and that continued access and use constitutes acceptance of the then-current terms.[1] Archiving a dated copy of each incorporated document at each order is the only way to know what applied at a given time.
The oldest wording still online is the 2004-era EULA (version 5.0, 8/04), republished with Cloud Software Group branding, which defines Permitted Instances, Server Instances, Enterprise, Site and Fab licences and has a one-sentence audit right.[5]
Grant and restrictions
Under section 2.1 the vendor grants a limited, non-transferable, non-sublicensable, non-exclusive, worldwide licence to install, run, access and use the Number of Units during the Term solely for internal business purposes, in accordance with the Business Unit Terms, the Order and the Documentation.[1] Section 2.7 bars the customer from:[1]
- making more copies than needed or using unlicensed versions;
- using Products not listed in an Order;
- letting anyone other than Authorized Users install or use them;
- sublicensing, distributing or pledging the Software;
- modifying, reverse engineering or decompiling;
- using embedded or bundled components stand-alone;
- using third-party software with a Product except as provided in Documentation, or in a way that subjects the Product to a third-party licence;
- marketing, offering to sell or reselling Products; and
- using Products for competitive benchmarking or analysis unless the law permits it.
An Authorized User is an employee, agent, contractor, consultant or other permitted third party who has agreed in writing to be bound by terms at least as protective of the vendor as the EUA.[1] The version 2.0 text adds that Authorized User specifically excludes a third party that deploys, operates and manages the Software in an environment owned or controlled by that third party on the customer’s behalf, which has implications for outsourcing and hosting.[2] The 2025 licence-information page for TIBCO Platform, on the other hand, allows deployment in a third-party Cloud Computing Environment so long as the provider grants access to no one else and the customer remains responsible for the provider’s compliance.[7] The cloud policy has a parallel clause.[8]
Order of precedence and changes
The EUA says any conflict between its terms and supplementary terms is resolved in this order: an Order, the Business Unit Terms, then the EUA. Terms in a customer purchase order do not modify the Agreement.[1] Where the Order includes a customised enterprise agreement, that document therefore beats the generic text on this page, which is why the end-of-term notices in signed agreements are often more specific than the general 60-day rule.
Assignment and corporate change
The customer may not assign rights or delegate duties without prior written consent, and an attempted assignment is void.[1] Section 2.10 adds that users, divisions or entities added or divested through an Extraordinary Corporate Event are not authorised to use the Products until a signed written amendment adds them (or, for a divested entity, the divested entity signs its own).[1] The older EULA treats a change in control as an assignment.[5] On the vendor side, if a Business Unit is divested from the Cloud Software Group organisation, the Agreement is deemed duplicated for the customer’s use of the divested product.[1]
Audit
Version 2.5
Section 15.2 provides that during the term of any Order and for one year after its termination, the vendor or its independent auditors, at the vendor’s expense, may, on 10 days notice and at reasonable times, audit the customer’s compliance and report results to the vendor and its licensors. The customer must, at no cost to the vendor, provide reasonably requested assistance and make requested systems, personnel, records and information available. Failing to comply is a material breach. The customer must promptly cure any noncompliance, and if the audit reveals material noncompliance, the customer reimburses the reasonable costs and expenses of the audit, including reasonable attorneys’ fees. The clause does not waive the vendor’s termination rights and does not affect its right to payment for usage in excess of the Number of Units.[1]
Version 2.0
The text in the Enterprise Message Service 10.4.0 package is similar, with these differences: the customer’s assistance includes installing and operating audit software, and the cost shift applies where the audit reveals noncompliance exceeding 5 percent of entitlement.[2] The 2.5 text replaces the numeric threshold with “material noncompliance”, which the document does not define.
Legacy wording
The 2004-era EULA gives the vendor and its independent auditors the right to audit compliance in a single sentence, without notice period, cost-allocation or look-back terms.[5]
Practical points
- The clause allows independent auditors, and the litigation in TIBCO v. GAIN Capital concerned an audit performed by an independent accounting firm, including discovery of the auditor’s methodology. Nothing in the clause lists the data sources; “requested systems, personnel, records, and information” is wide.
- The audit window continues for a year after an Order ends, so ceasing use does not close the exposure.
- Vendor audit is separate from the deployment report and usage report duties, which are self-certifications (see TIBCO enterprise licences and deployment reporting).
Termination and consequences of breach
Either party may terminate the Agreement or an Order for an uncured material breach 30 days after notice. The vendor may terminate immediately if the customer materially breaches Sections 2 (licence grant and limitations), 5 (intellectual property) or 13 (export and compliance with laws).[1] On termination, the customer discontinues use and, on written request, certifies that all deployed Units were de-installed and destroyed.[1] A multi-year Subscription is bought for its full value and cannot be cancelled during the Term, and all purchases are final with no right of refund or set-off except as expressly provided.[1] Unpaid fees carry a charge of 1.5 percent per month or the lower legal maximum.[1]
The liability section waives indirect and consequential damages and caps liability at the amounts paid for the Product in the preceding twelve months, but it excepts a breach by the customer of Section 2 and infringement or misappropriation of the other party’s intellectual property.[1] In practical terms, a use-scope overrun is a Section 2 matter and does not benefit from the cap. Statements of exposure in negotiations should be read with that in mind.
Governing law
Customers entering the Agreement from a European Union member country, the United Kingdom, Norway, Switzerland, Japan, India or Australia are under Irish law with exclusive jurisdiction of Irish courts. Otherwise Florida law applies and suits must be brought in the state or federal courts in Broward County, Florida.[1] The 2004-era EULA instead names California law and the courts in San Francisco, which is why older contracts appear in Northern District of California litigation.[5]
Maintenance
The Maintenance Terms are incorporated into the EUA.[3] Their main points are these.
| Topic | Term |
|---|---|
| Access | Defects are reported through the support portal; the customer must supply a problem description, a method to reproduce it and continuous access to a contact |
| Severity | Handled under the Service Levels Guide on commercially reasonable efforts |
| Updates | May replace existing copies; the right to use Updates expires with the Maintenance term |
| Release support | At least 12 months after a new release version is generally available; up to 12 months written notice before retirement |
| Fixes | Made to the most current version, with minor releases or the latest service pack at the vendor’s discretion |
| Exclusions | Non-vendor software, custom configuration, product modification, new products charged separately, on-site services, Materials |
| Perpetual licences | Initial Maintenance Term is one year from the Order Form effective date |
| Subscriptions | Maintenance ends when the Subscription Term expires |
| Same level | One service level for all quantities of Software licensed |
| Suspension | On 10 days written notice for breach |
| Reinstatement | Pay fees for the lapsed period and for the 12 months from reinstatement |
All rows are from the Maintenance Terms.[3] The reinstatement rule makes allowing support to lapse expensive for perpetual licences: the customer pays the lapsed period and a further twelve months.
Third-party terms
Some products carry additional terms. TIBCO Foresight HIPAA products license code sets from the American Dental Association and the American Medical Association, with U.S.-only or territory-limited use, and Spotfire products have market restrictions.[6] Some software contains redistributable IBM Java runtimes, and the terms note that use of Commercial Features requires a separate licence from Oracle.[6]
Review checklist
- Collect the Order, any signed master agreement, the EUA version and the Business Unit Terms in force at each order date.
- Identify the audit clause that applies and calendar the one-year tail.
- Confirm who the Authorized Users are, particularly outsourcers and hosting providers.
- Check merger and divestiture plans against section 2.10 and the assignment clause.
- Make sure Maintenance covers all licensed quantities and that renewal dates are tracked.