TIBCO Software is an enterprise integration, messaging, analytics and data-management software vendor that now operates as a business unit of Cloud Software Group. Its licensing is not defined in a single price list or contract. A customer’s rights come from an Order, the Cloud Software Group End User Agreement, a set of business-unit terms and definitions, a handful of counting policies, and product-specific “licence information” pages on the vendor’s documentation site.[1][2] This article maps those documents and the main constructs that a software asset manager meets. The deeper articles listed under See also cover individual areas.
Document stack
The End User Agreement (EUA) says it is a legal agreement between the customer and the Cloud Software Group business unit that enters the Order, and that product-specific terms live in the Business Unit Terms.[1] The footer of the version retrieved for this article reads “Version 2.5” with a 2026 copyright, and it prints no effective date.[1] Older package documents are still published with product releases. The Enterprise Message Service 10.4.0 package, for example, carries version 2.0 with a 2025 copyright, and the two versions differ on audit costs and on the deployment report (see TIBCO End User Agreement, audit and maintenance).[10]
The Business Unit Terms contain a section for the TIBCO, ibi, DataSynapse and ON EBX business units. It points to the maintenance terms, to the TIBCO licence-information page and to additional product-specific terms, and it repeats the licence definitions (Enterprise, Pack, Processor, Named User, Production, ProdPlus, DevTest, Bundle).[2] A separate “TIBCO Definitions” PDF carries a similar but not identical list, and it still refers to Master Terms and links on a former terms site, so it should be read as the older of the two.[3] Spotfire has its own business-unit section and its own licence-information page.[2][5]
Two policies govern the Processor Unit type: the TIBCO Processor Licensing Policy (effective 2011-12-01) and the TIBCO Cloud Computing Environment Licensing Policy (effective 2021-12-01).[6][7] The Maintenance Terms cover support, releases and reinstatement.[8]
The TIBCO website that hosted the former terms library returned an access-denied response to automated requests when this article was prepared, so documents that exist only there are not cited. Where the vendor’s documents point to that library, the corresponding PDFs published on the Cloud Software Group site were used instead.
Licence models
The Business Unit Terms and the EUA recognise Subscription, Perpetual and Term licences. A Subscription includes Maintenance for the Subscription Term. A Perpetual licence is an indefinite on-premise licence (or 99 years if applicable law renders a perpetual licence invalid) with Maintenance in addition. A Term licence is on premise with optional Maintenance in addition.[3][1] Much of TIBCO’s current portfolio, including TIBCO Platform and Spotfire, is described in subscription terms, and both licence-information pages ask the customer to certify deployed quantities every year.[4][5]
The grant itself is narrow: 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.[1] The limitations section bars use of Products not listed in an Order, reselling, and competitive benchmarking unless the law permits it.[1] Embedded or bundled components may be used only to enable the product that contains them.[3]
Unit types and metrics
A “Unit” is the licence restriction that describes how a copy may be deployed, such as Site, Processor, Pack, Named User, Connected Processor or Processor Source Locked.[3] The metrics that matter most in practice are these.
| Metric | What is counted | Where defined |
|---|---|---|
| Processor | Virtual or Physical Processors, with a 0.5 factor for multi-threading | Business Unit Terms; Processor Licensing Policy; CCEL Policy |
| Named User | An identifiable individual authorised to access the Product | Definitions; Spotfire information |
| Application Instance | An application instance, inside a container on container platforms | TIBCO License Information |
| Connection | A client link to a messaging server or broker | TIBCO License Information |
| Pack | A product-specific bundle of Instances, Processors or Containers | Business Unit Terms; product information |
| Instance | The smallest functionally-complete copy, or an OS process | Business Unit Terms |
| Core/vCPU | Cores or virtual CPUs of specified server components | TIBCO License Information |
| Transaction | A unit of work or standardised document | TIBCO License Information |
The TIBCO Platform page lists a “Usage Metric to be submitted” for each component, for example Application Instance for BusinessWorks, Connection for Enterprise Message Service, Node for ActiveSpaces, MSU for the mainframe products and Transactions for BusinessConnect.[4] It also states that these metrics can change with six months notice.[4] Product-line detail is in TIBCO Platform, integration and messaging licensing and TIBCO Spotfire licensing.
Environments and licence types
Orders state a “License Type”, meaning the environment in which the Software may be used. Production is an operational environment processing live data to which the intended users have access. Non-Production is a non-operational environment that is not processing live data and not running any operations of the customer, and it is defined to include development, hot standby, high-availability and test environments.[2] Two bundled licence types simplify ordering. ProdPlus includes 1 Unit of Production or Hot Standby, 4 Units of Test, 5 Developers and unlimited Warm or Cold Standby units, and DevTest includes 2 Units of Test and 5 Developers, in each case unless the Documentation says otherwise.[2] The TIBCO Platform page defines ProdPlus more loosely as a licence type allowing deployment in Production or Non-Production.[4] Product pages can override the generic definition, so the product-level text should be checked first.
Counting Processors
Several older products are licensed per Processor. In a Virtualized Environment the policy counts the maximum whole number of Virtual Processors that could ever be assigned to each Virtual Machine running the Product. On physical machines it counts every Physical Processor on the machine unless Fixed Partitioning confines the Product to a subset. Where multi-threading is enabled the total is multiplied by 0.5, and fractions round up.[6] In public clouds a separate policy applies, and moving on-premise licences to a cloud environment can trigger an administrative fee.[7] See TIBCO Processor and cloud licensing.
Enterprise and Project licences
An Enterprise licence gives unlimited deployment until the Enterprise Term Expiration Date. The deployed count by licence type then becomes fixed and no further units may be deployed, and the customer must give written notice of the deployed quantities within 60 days after the term ends.[2] A Project licence is the same construct limited to a defined project scope.[3] Neither extends to an Extraordinary Corporate Event such as a merger, acquisition or divestiture.[1] These constructs are the usual source of disputes and are covered in TIBCO enterprise licences and deployment reporting.
Reporting, audit and maintenance
The EUA lets the vendor ask in writing for a Deployment Report certifying the Number of Units deployed. The reported number becomes the basis for any renewal Subscription, and the vendor has no obligation to offer a renewal if the report is not provided.[1] Separately, the TIBCO Platform and Spotfire pages require annual Usage Reports due 60 days after each 12-month Reporting Period.[4][5] The audit clause allows the vendor or independent auditors to audit on 10 days notice during an Order and for one year afterwards.[1]
Maintenance requires the same service level for all licensed quantities and runs for at least 12 months after a new release becomes generally available. Maintenance bundled with a Subscription ends when the Subscription Term expires.[8]
Specific restrictions
The additional product-specific terms add restrictions that are easy to miss. Spotfire products cannot be used in the Global Research Market or the Clinical Research Market unless a mutually executed Order Form says otherwise, and the terms list companies to which Spotfire may not be resold or distributed. Products containing dental or medical code sets carry third-party terms and territory limits.[9]
Litigation
Two US federal cases brought by TIBCO concern deployment after an enterprise period. In TIBCO Software Inc. v. Bank of America Corporation the court compelled arbitration under the parties’ master agreement. In TIBCO Software Inc. v. GAIN Capital Group, LLC the case ended by stipulated dismissal after discovery disputes about a third-party audit. Their practical lessons are the same: the end-of-term deployment report fixes the licence position, and the evidence behind it should be kept.
Practical checklist
- Identify which agreement and EUA version govern each Order, including any signed agreement that overrides the standard terms.
- For every product, find the licence-information page and the metric to be reported, and keep a dated inventory by environment type.
- Treat Enterprise and Project end dates as hard deadlines for the deployed-count notice.
- Recount Processor-licensed products whenever virtualisation, hardware multi-threading or cloud placement changes.
- Diary the annual Usage Report (60 days after each Reporting Period) and any Deployment Report request.
- Check Maintenance coverage covers all licensed quantities before renewal.