ip-technology-diligence-memo.docx

1001-00004 · Ardent Capital Partners · Diligence

ip-technology-diligence-memo.docx DOCUMENT M&A / Corporate

30 / 78 ← → ✕

PRIVILEGED & CONFIDENTIAL — ATTORNEY-CLIENT PRIVILEGE / ATTORNEY WORK PRODUCT This memorandum was prepared by Calderwood & Harkness LLP at the direction of Ardent Capital Partners III LP and its affiliates and is protected by the attorney-client privilege and the work product doctrine. This memorandum and the information contained herein are strictly confidential and may not be disclosed, distributed, or reproduced, in whole or in part, to any third party without the prior written consent of Calderwood & Harkness LLP.

CALDERWOOD & HARKNESS LLP 7 Times Square New York, NY 10036

MEMORANDUM

To: James Prentice, Partner; Sandra Tung, Partner

From: Ryan Kowalski, Lead Associate; Megan Chu, Working Associate

Date: April 14, 2025

Re: IP & Technology Due Diligence Summary — Acquisition of Luminex Systems Holdings Inc. by Ardent Capital Partners III LP

Matter No.: 1001-00004

Classification: Privileged and Confidential

Right-click to update Table of Contents

I. Executive Summary

This memorandum summarizes the principal findings of the intellectual property and technology due diligence review conducted by Calderwood & Harkness LLP ("Calderwood & Harkness" or "C&H") in connection with the proposed acquisition (the "Transaction") of Luminex Systems Holdings Inc. ("Luminex Holdings" or the "Target") by Ardent Capital Partners III LP ("Ardent Capital" or the "Client"). The Transaction is structured as a reverse triangular merger under the Delaware General Corporation Law, with Ardent Apex Merger Sub Inc. ("Merger Sub"), a wholly owned subsidiary of Ardent Apex Holdings Inc., merging with and into Luminex Holdings, with Luminex Holdings surviving as a wholly owned indirect subsidiary of Ardent Capital, for an aggregate equity consideration of Two Billion Eight Hundred Million Dollars ($2,800,000,000) (the "Purchase Price").

The scope of this memorandum encompasses a comprehensive review of the Target's intellectual property assets, technology stack, software architecture, open-source software compliance, patent portfolio, trademark portfolio, trade secrets and proprietary know-how, domain name portfolio, intercompany IP licensing arrangements, third-party inbound and outbound technology licenses, employee and contractor IP assignment matters, and data privacy considerations to the extent they bear upon technology-related intellectual property. The review encompasses Luminex Holdings and each of its direct and indirect subsidiaries, including Luminex Systems AG (Switzerland), Luminex Systems Inc. (Delaware), Luminex Systems UK Ltd. (United Kingdom), Luminex Systems GmbH (Germany), and Luminex Systems Pte. Ltd. (Singapore) (each, a "Luminex Entity" and collectively, the "Luminex Group").

The documents and information reviewed in connection with this memorandum were obtained from the virtual data room maintained by Caldwell, Raines & Sheppard LLP ("CRS"), seller's counsel (principal contact: Patricia Okonkwo, Partner), as coordinated through Pinehurst Rothwell & Co., seller's financial advisor (principal contact: Samantha Delacroix, Managing Director). Supplemental information was obtained through management presentations, written due diligence questionnaire responses, and targeted interview sessions with Luminex management and in-house legal personnel.

Key Findings. Our principal findings are summarized as follows:

(i) Core IP Concentration. Luminex's core intellectual property is concentrated in the "Luminex One" cloud-based enterprise resource planning (ERP), procurement automation, and supply-chain analytics software-as-a-service (SaaS) platform. The foundational IP — including patents, trademarks, copyrights in source code, and trade secrets — is owned predominantly by Luminex Systems AG (Switzerland), with a limited number of U.S. utility patents held by Luminex Systems Inc. (Delaware). No intellectual property is held directly by Luminex Holdings, the merger target entity.

(ii) Patent Portfolio. The patent portfolio is modest in size (approximately 47 issued patents and 12 pending applications across U.S., European, Swiss, and Singaporean jurisdictions) but provides strategically meaningful defensive coverage for Luminex One's core technology. One assignment gap has been identified with respect to a 2013 U.S. patent application originally filed by a former consultant.

(iii) Trademark Portfolio. The trademark portfolio is well-maintained and provides comprehensive global coverage for Luminex's principal brands. No material disputes are pending.

(iv) Open-Source Software Usage. Open-source software usage is material. The Luminex One platform incorporates approximately 1,200 distinct open-source components. While the vast majority are under permissive licenses presenting low compliance risk, three components licensed under the GNU Affero General Public License, Version 3 ("AGPL v3") present elevated risk requiring verification of their isolation from customer-facing production code. No independent third-party open-source audit has been conducted, and we recommend one be commissioned prior to or promptly after closing.

(v) Intercompany IP Licensing. The intercompany IP licensing arrangement between Luminex AG (as licensor) and Luminex US (as licensee) provides for a royalty rate of 4.5% of U.S. net revenues. This rate falls below the arm's-length range identified in a preliminary transfer-pricing benchmark study conducted by Pendleton & Associates LLP, which indicates a median rate of approximately 6.0%. Post-closing restructuring of the royalty rate is contemplated. The intercompany IP license agreements do not contain change of control termination provisions.

(vi) Third-Party License Change of Control Provisions. Eight of approximately 45 material third-party technology licenses contain change of control provisions (consent or notice requirements). Outreach to the relevant counterparties has been initiated and is being tracked in the internal Change of Control / Consent Tracker.

(vii) IP Litigation. No material IP litigation is currently pending or, to the knowledge of Luminex management, threatened. Two patent assertion entity demand letters received in 2023 were resolved without payment or license.

Overall Risk Assessment. Based on our review, we assess the overall IP and technology risk profile of the Transaction as moderate — the identified issues are manageable with the pre-closing and post-closing remediation actions recommended in Section XV of this memorandum. No findings were identified that, in our assessment, constitute a material adverse condition warranting reconsideration of the Transaction or a material adjustment to the Purchase Price, though the open-source compliance matters and legacy contractor assignment gaps warrant focused attention in the Merger Agreement disclosure schedules and post-closing integration planning.

II. Scope of Review and Methodology

A. Documents Reviewed

In connection with this due diligence review, we reviewed the following categories of documents and materials made available through the virtual data room and supplemental production:

1. IP assignment and license agreements, including all executed intercompany IP license agreements among the Luminex Entities, as well as agreements reflecting the assignment of intellectual property from founders, employees, and third parties to the relevant Luminex Entities.

2. Patent filings, prosecution files, and maintenance records for all issued patents and pending patent applications held by Luminex Systems AG and Luminex Systems Inc., including original application filings, office action responses, notices of allowance, grant certificates, maintenance fee payment receipts, and assignment recordation confirmations filed with the U.S. Patent and Trademark Office ("USPTO"), the European Patent Office ("EPO"), the Swiss Federal Institute of intellectual Property ("IPI"), the intellectual Property Office of Singapore ("IPOS"), and relevant national patent offices.

3. Trademark registrations and applications across all jurisdictions in which the Luminex Group maintains trademark protection, including registration certificates, specimens of use, declaration filings (including Sections 8, 15, and 71 declarations for U.S. registrations), renewal receipts, and prosecution correspondence.

4. Domain name portfolio records, including registrar account documentation, WHOIS records, and DNS configuration summaries for all domain names maintained by the Luminex Group.

5. Open-source software audit reports and the software bill of materials ("SBOM") generated by Luminex's internal engineering team in Q4 2024, including component-level detail on license type, version, and deployment context within the Luminex One platform architecture.

6. Third-party software license agreements for all material inbound software licenses utilized by the Luminex Group in its operations, including cloud infrastructure service agreements, database platform licenses, analytics libraries, security tools, payment processing integrations, and monitoring platforms.

7. Intercompany IP license agreements between Luminex Systems AG and each of Luminex Systems Inc. (U.S.), Luminex Systems GmbH (Germany), Luminex Systems UK Ltd. (U.K.), and Luminex Systems Pte. Ltd. (Singapore), together with the underlying transfer-pricing documentation and the 2021 transfer-pricing study prepared in connection with the corporate reorganization.

8. Employee invention assignment agreements and proprietary information and inventions assignment agreements ("PIIAAs") for employees of each Luminex Entity, including jurisdiction-specific forms for the United States (including the California-compliant variant), Switzerland, Germany, the United Kingdom, and Singapore.

9. Consultant and independent contractor IP assignment agreements, including both current-form template agreements and legacy agreements dating to Luminex AG's founding period (2009–2014).

10. Technology partnership and co-development agreements to which any Luminex Entity is a party, including joint development arrangements, technology integration partnerships, and strategic alliance agreements.

11. Source code escrow agreements entered into with major enterprise customers, including the escrow deposit instructions, release conditions, and verification procedures established with the applicable third-party escrow agent.

12. Data processing agreements and data privacy agreements to the extent such agreements contain provisions relevant to IP ownership, derived data rights, or restrictions on the use of customer data for product improvement and AI/ML model training.

13. Insurance policies covering intellectual property-related risks, including errors and omissions (E&O) policies and cyber liability insurance policies maintained by the Luminex Group.

14. Correspondence with patent and trademark prosecution counsel, including docketing reports, prosecution status summaries, and renewal calendars.

15. Internal technology architecture documentation and technical memoranda, including system design documents, architectural diagrams, technology stack descriptions, and security posture assessments, including SOC 2 Type II audit reports and ISO 27001 certification documentation.

B. Interviews and Discussions

In addition to the documentary review described above, we conducted targeted interviews and participated in working sessions with the following individuals and advisors:

• Dr. Markus Vogt, Chief Technology Officer of Luminex Systems AG, who provided detailed information regarding the Luminex One platform architecture, the technology stack, the patent portfolio's relationship to core platform functionality, AI/ML model development and training data practices, and open-source software usage and governance practices.

• Luminex VP of Engineering (participated in technical working sessions), who provided supplemental detail on software development lifecycle processes, the CI/CD pipeline, source code repository management and access controls, and the current state of OSS governance tooling.

• Luminex General Counsel (In-House), who provided information regarding the history of the Luminex IP portfolio, the intercompany licensing structure, employee and contractor IP assignment practices, and the status of any IP-related disputes or claims.

• Daniel Feinberg, Associate at Caldwell, Raines & Sheppard LLP (seller's counsel), who coordinated the production of responsive documents in the virtual data room and facilitated management access for due diligence interview sessions.

• Dr. Lukas Breitfeld, Partner at Breitfeld Hess & Partner AG (Swiss local counsel to Calderwood & Harkness), who provided input on Swiss IP law considerations, including the Swiss Code of Obligations provisions governing employee inventions (Art. 332 CO), the enforceability of non-compete covenants under Swiss law, and the ownership and assignment of intellectual property created by Swiss-based employees and contractors.

• Dr. Katarina Wendt, Partner at Wendt Schäfer Rechtsanwälte PartG mbB (German local counsel to Calderwood & Harkness), who provided input on German IP law considerations, including the German Employee Inventions Act (Arbeitnehmererfindungsgesetz, "ArbNEG"), the proper claiming and compensation of employee inventions under German law, and German data privacy law considerations relevant to the IP and technology review.

• Kelvin Tan, Partner at Tan Liang & Associates LLP (Singapore local counsel to Calderwood & Harkness), who provided input on Singapore IP law considerations, including the Singapore Patents Act and Copyright Act provisions governing ownership of IP created by employees and contractors.

C. Limitations. The following limitations apply to this memorandum and the findings set forth herein:

• Source Code Review. A detailed technical source code review has not been completed as of the date of this memorandum. Access to certain source code repositories has been requested but remains pending clearance from Luminex's security team. Ardent Capital's independent technology consultants are expected to conduct a supplemental technical source code review upon access being granted. Findings from that review, if material, will be addressed in a supplemental memorandum.

• Freedom-to-Operate Analysis. A comprehensive third-party IP infringement freedom-to-operate ("FTO") analysis was not conducted as part of this review. Our review has confirmed that no pending patent infringement claims exist against the Luminex Group, and Luminex's in-house counsel is not aware of any threatened claims. However, if Ardent Capital desires a comprehensive FTO clearance opinion with respect to the Luminex One platform's core technology — particularly with respect to the predictive analytics and AI/ML modules — we recommend engaging a specialized patent clearance firm to conduct a separate FTO study.

• Reliance on Management Representations. Certain factual findings in this memorandum are based, in part, on representations made by Luminex management and in-house counsel during interview sessions and through due diligence questionnaire responses. To the extent that material facts differ from management representations, our findings and risk assessments may need to be revised.

• No Tax or Accounting Advice. While this memorandum references transfer-pricing considerations relating to the intercompany IP licensing structure, it does not constitute tax or accounting advice. Transfer-pricing and tax structuring matters are being addressed separately by Pendleton & Associates LLP (Richard Chow) and by Sylvia Hartwell of Calderwood & Harkness's tax practice group.

III. Overview of Luminex's Business and Technology

A. Business Overview

Luminex Systems Holdings Inc. is a Delaware corporation incorporated on June 14, 2021, in connection with a corporate reorganization (the "2021 Reorganization") designed to establish a U.S. intermediate holding company structure. Luminex Holdings serves as the direct parent of Luminex Systems Inc. (Delaware), which in turn conducts the Luminex Group's U.S.-based operations. Luminex Holdings also serves as the direct or indirect parent of the Luminex Group's international operating subsidiaries through the original Swiss parent entity, Luminex Systems AG.

Luminex Systems AG was founded in 2009 in Zürich, Switzerland (Commercial Register No. CHE-284.391.057) by Dr. Stefan Kessler (Chief Executive Officer) and Dr. Markus Vogt (Chief Technology Officer). The company's global headquarters remain at Bahnhofstrasse 71, 8001 Zürich, Switzerland, while the U.S. operational headquarters are located at 2100 Reston Gateway Drive, Suite 800, Reston, Virginia 20191.

As of the date hereof, the Luminex Group employs approximately 4,200 individuals globally, of whom approximately 1,650 are based in the United States. The remaining workforce is distributed across Switzerland (approximately 900), Germany (approximately 700), the United Kingdom (approximately 450), Singapore (approximately 350), and other locations (approximately 150).

For the fiscal year ended December 31, 2024, the Luminex Group reported total revenue of approximately $487 million, consisting of $441 million in annual recurring revenue ("ARR") derived from SaaS subscription fees and $46 million in professional services revenue. The Luminex Group reported adjusted EBITDA of approximately $121.8 million for the same period, representing an adjusted EBITDA margin of approximately 25.0%. Revenue is concentrated across four principal geographic regions: the DACH region (Germany, Austria, Switzerland), representing approximately 35% of total revenue; North America, representing approximately 40%; the United Kingdom and Nordics, representing approximately 15%; and the Asia-Pacific ("APAC") region, representing approximately 10%.

B. Core Product — Luminex One Platform

The Luminex Group's core product offering is the Luminex One platform, a cloud-based enterprise resource planning (ERP), procurement automation, and supply-chain analytics SaaS platform. Luminex One is designed to serve mid-market and enterprise customers across a range of industries, providing an integrated suite of tools for managing procurement workflows, supply-chain operations, vendor relationships, invoice processing, and contract lifecycle management.

Architecture. Luminex One is built on a multi-tenant SaaS architecture deployed on major cloud infrastructure. The platform utilizes a microservices-based architectural pattern with containerized deployment, enabling independent scaling and deployment of individual service components. This architecture supports high availability, horizontal scalability, and continuous deployment capabilities.

Core Modules. The Luminex One platform consists of the following principal functional modules:

• ERP Module: Core enterprise resource planning functionality, including financial management, general ledger, accounts payable and receivable, and budgeting and forecasting tools.

• Procurement Automation Module: Automated procurement workflows, including requisition-to-purchase order processing, approval routing, and supplier bidding and evaluation tools. This module incorporates proprietary AI/ML algorithms for spend optimization and automated vendor selection.

• Supply-Chain Analytics Module: Predictive supply-chain analytics engine that leverages proprietary algorithms and machine learning models to provide demand forecasting, inventory optimization, risk assessment, and supply-chain visibility dashboards. This module represents a core competitive differentiator for Luminex.

• Vendor Management Module: Comprehensive vendor lifecycle management, including onboarding, performance monitoring, compliance tracking, and risk scoring.

• Invoice Processing Module: intelligent invoice processing and data extraction capabilities, leveraging optical character recognition (OCR) and natural language processing (NLP) technologies for automated invoice capture, validation, and matching.

• Contract Lifecycle Management (CLM) Module: NLP-based contract analytics, authoring, negotiation, and management tools, including automated clause extraction, obligation tracking, and renewal management.

Proprietary Technology. The Luminex One platform incorporates significant proprietary technology, including proprietary algorithms for predictive supply-chain analytics and spend optimization, as well as AI/ML modules developed using Luminex's internally generated training data sets. These proprietary elements represent key competitive differentiators and form the core of Luminex's trade secret portfolio.

Customer Base. As of the date hereof, Luminex maintains approximately 340 commercial customer contracts and 26 enterprise license agreements ("ELAs") with large customers. A number of these agreements contain change of control provisions that are relevant to the Transaction; these provisions are being tracked in the Change of Control / Consent Tracker maintained as an internal working document. For a comprehensive analysis of Luminex's material customer contracts, including change of control provisions, reference is made to the separate Material Contracts Review Memorandum and the Change of Control / Consent Tracker prepared in connection with the Transaction.

Government Customers. Luminex maintains a significant U.S. federal government customer base, including contracts with the U.S. Department of Defense ("DOD") for a logistics software module, the U.S. Department of Energy ("DOE") for a procurement platform, and the U.S. General Services Administration ("GSA") under an enterprise license arrangement. These government contracts are subject to the Federal Acquisition Regulation ("FAR") and, in the case of the DOD contract, the Defense Federal Acquisition Regulation Supplement ("DFARS"), and carry assignment/novation requirements that must be coordinated with the broader Transaction closing process. Additionally, the Luminex Group's government customer relationships and the associated technology are relevant to the ongoing review by the Committee on Foreign Investment in the United States ("CFIUS") under CFIUS Tracking No. CFIUS-2025-0087.

C. Subsidiary Technology Operations

The Luminex Group's technology development, sales, and service delivery operations are conducted through the following operating subsidiaries:

• Luminex Systems Inc. ("Luminex US"), a Delaware corporation, serves as the U.S. operating entity responsible for U.S.-based product development, sales, customer success, and professional services. Luminex US reported 2024 U.S. revenue of approximately $194.8 million. Luminex US holds 9 U.S. utility patents assigned from employee inventors and is the licensee under the intercompany IP License Agreement with Luminex AG.

• Luminex Systems AG ("Luminex AG"), a Swiss Aktiengesellschaft (Commercial Register No. CHE-284.391.057), headquartered in Zürich, Switzerland, serves as the core research and development center and the primary holder of the Luminex Group's intellectual property. Luminex AG owns the majority of the Luminex Group's issued patents (approximately 38 of 47), all registered trademarks, and the foundational copyrights in the Luminex One platform source code and associated trade secrets.

• Luminex Systems GmbH ("Veltronix GmbH"), a German Gesellschaft mit beschränkter Haftung (Commercial Register No. HRB 247891, registered with the Munich Commercial Register), serves as the European development and sales hub, with a particular focus on the DACH region. Veltronix GmbH reported 2024 German revenue of approximately €67 million.

• Luminex Systems UK Ltd. ("Luminex UK"), a company incorporated in England and Wales (Company No. 12847362), headquartered in London, serves as the sales and professional services entity for the United Kingdom and Nordics markets.

• Luminex Systems Pte. Ltd. ("Luminex Singapore"), a company incorporated in Singapore (Unique Entity Number 201924781K), serves as the APAC regional development hub and sales entity.

IV. Patent Portfolio

A. Overview and Statistics

The Luminex Group's patent portfolio consists of approximately 47 issued patents and 12 pending patent applications across the United States, Europe (via the European Patent Office and national phase validations), Switzerland, and Singapore. The portfolio is concentrated in the technological domains most closely associated with the Luminex One platform's core functionality.

The primary patent holder within the Luminex Group is Luminex Systems AG, which holds approximately 38 of the 47 issued patents. These patents were either filed directly by Luminex AG or assigned to Luminex AG from employee inventors and, in certain cases, from the company's co-founders. Luminex Systems Inc. (Luminex US) holds 9 U.S. utility patents that were assigned from U.S.-based employee inventors in accordance with the terms of their respective PIIAAs.

It is important to note that no patents are held directly by Luminex Holdings, the entity that will survive the reverse triangular merger. All patents are held at the operating subsidiary level — principally by Luminex AG and, to a lesser extent, by Luminex US. This ownership structure means that the patent assets will be acquired indirectly through the acquisition of Luminex Holdings' equity interest in its subsidiaries, rather than through a direct transfer of patent ownership. This structure preserves continuity of patent ownership at the subsidiary level and avoids the need to record new patent assignments in connection with the Transaction itself, provided the surviving corporation structure is maintained as contemplated.

A complete listing of all issued patents and pending applications, including patent/application numbers, titles, jurisdictions, filing dates, issue dates, expiration dates, owner entities, and current statuses, is set forth in Appendix A to this memorandum.

B. Subject Matter Coverage

The patent portfolio provides coverage across the principal technology areas that underlie the Luminex One platform. The patents cluster into the following subject matter groups:

• Predictive Supply-Chain Analytics Algorithms (approximately 14 patents): This cluster represents the core defensive group within the portfolio and covers Luminex's proprietary algorithms for demand forecasting, supply-chain risk assessment, inventory optimization, and predictive logistics modeling. These patents protect Luminex One's primary competitive differentiator in the marketplace.

• Automated Procurement Workflow Optimization (approximately 10 patents): This cluster covers methods and systems for automating procurement processes, including intelligent requisition routing, automated vendor selection, bid evaluation algorithms, and dynamic approval workflows.

• Multi-Tenant SaaS Data Isolation and Security Architecture (approximately 8 patents): This cluster covers aspects of Luminex One's multi-tenant architecture, including methods for tenant data isolation, secure multi-tenancy in shared infrastructure environments, and role-based access control mechanisms within a SaaS deployment model.

• Invoice Processing and intelligent Data Extraction (approximately 7 patents): This cluster covers Luminex's technologies for automated invoice capture, intelligent data extraction using OCR and pattern recognition, invoice-to-purchase-order matching algorithms, and exception handling workflows.

• Contract Analytics and NLP-Based Contract Management (approximately 8 patents): This cluster covers Luminex's natural language processing technologies for contract clause extraction, obligation identification, risk scoring, and automated contract analytics.

The 12 pending patent applications are focused on next-generation AI/ML procurement modules, including advanced machine learning techniques for spend classification, anomaly detection in procurement patterns, and reinforcement learning approaches to supply-chain optimization. These pending applications, if granted, would extend the portfolio's defensive perimeter into Luminex's emerging AI/ML capabilities.

C. Geographic Coverage

The patent portfolio provides geographic coverage across Luminex's principal markets:

• United States (USPTO): 23 issued patents and 7 pending applications. The U.S. portfolio is the most extensive, reflecting North America's position as Luminex's largest revenue market.

• European Patent Office (EPO) / National Validations: 18 issued patents and 4 pending applications. EPO-granted patents have been validated in Germany, France, the United Kingdom, and Switzerland, providing protection across Luminex's key European markets. Post-Brexit U.K. validations of pre-Brexit EPO grants remain effective under the U.K.'s transitional provisions.

• Singapore (IPOS): 6 issued patents and 1 pending application. The Singapore portfolio provides protection in Luminex's APAC hub jurisdiction.

We note that the portfolio does not include patent filings in certain markets where Luminex has commercial activity, including Australia, Japan, and the broader Nordic countries. While this is not unusual for a company of Luminex's size and stage, Ardent Capital may wish to evaluate whether supplemental patent filings in additional jurisdictions would be strategically beneficial post-closing.

D. Maintenance and Prosecution Status

Based on our review of the maintenance records and prosecution files made available in the data room, all 47 issued patents are current on maintenance fee and annuity payments. No lapses were identified in any jurisdiction. Pending patent applications are being prosecuted in the ordinary course, and no missed deadlines or abandoned applications were identified during our review period.

Patent prosecution for the Luminex Group is handled by outside patent prosecution counsel engaged directly by Luminex AG and Luminex US. Calderwood & Harkness does not serve as Luminex's patent prosecution counsel. We have reviewed the prosecution correspondence and docketing reports provided by Luminex's in-house legal team and have not identified any material issues with respect to the conduct of patent prosecution or the timing of prosecution actions.

E. Assignments and Chain of Title

We have reviewed the chain of title documentation for the patent portfolio, including employee invention assignment agreements, founder assignment records, and assignment instruments recorded with the relevant patent offices.

Employee Invention Assignments. We reviewed the invention assignment agreements executed by key engineering personnel and the company's co-founders. Dr. Markus Vogt (CTO), as co-founder, executed a comprehensive invention assignment agreement at the time of Luminex AG's founding in 2009, covering all intellectual property developed in the course of his employment with Luminex AG. Similar agreements were executed by other members of the founding engineering team. Current PIIAAs for U.S. employees include standard present-tense assignment language assigning to Luminex US all inventions conceived or reduced to practice during the course of employment that relate to Luminex's business. Swiss and German employees are subject to the applicable statutory frameworks (Swiss Code of Obligations Art. 332 and German ArbNEG, respectively), and supplemental invention assignment agreements have been executed by R&D staff in those jurisdictions.

Founder Assignments. Several early-stage patents were originally filed under the personal name of Dr. Stefan Kessler (CEO, co-founder) during the period prior to the formalization of Luminex AG's IP assignment procedures. These patents were subsequently assigned to Luminex AG through executed assignment instruments that have been recorded with the USPTO and the EPO, as applicable. The recorded assignment instruments were reviewed and appear to be in proper form.

Assignment Gap Identified. We identified one assignment gap that warrants attention. A 2013 U.S. patent application (relating to an early procurement workflow module) was filed under the name of a former independent consultant engaged by Luminex AG during the company's early development phase. An assignment instrument was subsequently executed and recorded with the USPTO, transferring the application from the consultant to Luminex AG. However, the underlying consultant agreement — which would typically contain the contractual IP assignment obligation — has not been located in the data room. In the absence of the underlying agreement, there is a theoretical risk that the assignment could be challenged as lacking adequate consideration or contractual basis, although the executed and recorded assignment instrument itself provides significant evidence of the parties' intent. We recommend that Luminex obtain a confirmatory assignment from the former consultant, or that the matter be addressed through appropriate representations, warranties, and indemnification provisions in the Merger Agreement's disclosure schedules. This item is discussed further in our recommendations in Section XV.

Liens and Encumbrances. Based on our review of the data room documents and representations from Luminex's in-house counsel, no liens, security interests, or encumbrances have been granted with respect to any patents in the portfolio. We recommend that UCC lien searches (with respect to Luminex US and Luminex Holdings) and WIPO lien searches (with respect to Luminex AG and other non-U.S. entities) be completed to confirm the absence of recorded encumbrances. These searches are being coordinated separately.

F. Freedom-to-Operate and Infringement Considerations

Based on our review, there are no pending patent infringement claims asserted against any Luminex Entity, and no Luminex Entity has asserted patent infringement claims against any third party.

Luminex's in-house counsel confirmed receipt of two demand letters from patent assertion entities ("PAEs") in 2023. Both demand letters related to broadly drafted patents covering generic cloud computing and SaaS architectures. In each case, Luminex's outside patent counsel responded with a detailed non-infringement analysis, and both matters were resolved without any payment, license, or settlement. There are no active disputes arising from these demand letters, and no follow-up correspondence has been received.

As noted in Section II.C above, a comprehensive freedom-to-operate analysis was not conducted as part of this review. While the absence of pending claims and the resolution of the PAE demand letters are encouraging indicators, they do not constitute a comprehensive clearance of the Luminex One platform's technology against all potentially relevant third-party patents. If Ardent Capital desires a higher level of confidence regarding FTO, we recommend engaging a specialized patent clearance firm to conduct a targeted FTO study focused on Luminex One's core proprietary algorithms, particularly in the areas of predictive analytics and AI/ML-based procurement automation, where the patent landscape is evolving rapidly.

V. Trademark Portfolio

A. Overview. The Luminex Group maintains a trademark portfolio consisting of approximately 34 registered trademarks and 6 pending trademark applications across multiple jurisdictions worldwide. The portfolio provides comprehensive brand protection for Luminex's principal marks, including "LUMINEX," "LUMINEX ONE," "LUMINEX SYSTEMS," and associated design marks and logos. Trademark registrations cover goods and services in International Classes 9 (computer software), 35 (business management and administration services), 38 (telecommunications services), and 42 (technology services, including SaaS and cloud computing).

A complete listing of all registered trademarks and pending applications, including registration/application numbers, marks, jurisdictions, international classes, registration dates, renewal dates, owner entities, and current statuses, is set forth in Appendix B to this memorandum.

B. Key Registrations by Jurisdiction

The trademark portfolio provides coverage in the following principal jurisdictions:

• United States (USPTO): 12 registered trademarks and 2 pending applications. U.S. registrations include the primary word marks "LUMINEX," "LUMINEX ONE," and "LUMINEX SYSTEMS," as well as the associated logo design marks, across the relevant international classes.

• European Union (EUIPO): 8 registered trademarks and 1 pending application. EU trademark registrations provide unitary protection across all EU member states.

• Switzerland (IPI): 5 registered trademarks and 1 pending application. Swiss registrations provide protection in Luminex AG's home jurisdiction.

• United Kingdom (UKIPO): 4 registered trademarks and 1 pending application. Following the United Kingdom's withdrawal from the European Union, Luminex proactively re-filed certain marks with the UKIPO to ensure continued U.K. protection. Comparable rights from pre-Brexit EU registrations were also automatically cloned in accordance with U.K. transitional provisions.

• Singapore (IPOS): 3 registered trademarks and 1 pending application. Singapore registrations protect the brand in Luminex's APAC hub jurisdiction.

• Additional National Registrations: Luminex maintains additional national trademark registrations in Germany (supplemental to EU-wide EUIPO registrations), Australia, and Japan, reflecting Luminex's commercial activities in those markets.

C. Ownership. All trademark registrations in the Luminex Group's portfolio are held by Luminex Systems AG as the primary brand owner. This centralized ownership structure is consistent with Luminex AG's role as the core IP holding entity within the Luminex Group. Luminex AG licenses the use of its trademarks to the operating subsidiaries (Luminex US, Luminex UK, Veltronix GmbH, and Luminex Singapore) under the terms of the intercompany IP license agreement described in Section VIII of this memorandum. The license structure ensures that each subsidiary's use of the Luminex marks inures to the benefit of Luminex AG as the registered owner, which is important for maintaining the validity and enforceability of the trademark registrations.

D. Maintenance and Renewal Status

Based on our review, all trademark registrations in the portfolio are current, and no missed renewal deadlines were identified. For U.S. registrations, Section 8 Declarations of Continued Use and Section 15 Declarations of Incontestability have been filed on a timely basis. Luminex's in-house legal department maintains a renewal calendar for the trademark portfolio and has confirmed that all upcoming renewal deadlines through the end of 2025 have been docketed and are being tracked. We recommend that Ardent Capital's post-closing IP management team conduct a comprehensive audit of the trademark renewal calendar during the integration process to ensure continuity of all registrations.

E. Third-Party Disputes

One opposition proceeding was identified in the trademark portfolio's history. In 2022, a third party filed an opposition before the EUIPO, alleging likelihood of confusion between one of Luminex's EU trademark registrations and the opposing party's mark registered in a different international class. The EUIPO Opposition Division rejected the opposition, finding no likelihood of confusion between the marks given the dissimilarity of the goods and services at issue. The decision has become final, and no appeal was filed by the opposing party. No other pending trademark disputes, oppositions, or cancellation proceedings were identified in any jurisdiction.

F. Coexistence and Consent Agreements

Two trademark coexistence agreements were identified in the data room:

(i) Medical Device Company Coexistence Agreement. A coexistence agreement between Luminex AG and a medical device company using a phonetically similar mark in International Class 10 (medical devices). Under the terms of the agreement, Luminex's use of its marks is limited to International Classes 9, 35, and 42 (software, business management, and technology services), while the medical device company's use is limited to Class 10. The agreement was entered into in 2017 and contains mutual commitments not to expand into each other's designated classes.

(ii) Lighting Products Company Coexistence Agreement. A coexistence agreement between Luminex AG and a lighting products company using a similar mark in International Class 11 (lighting and heating apparatus). There is no overlap between the parties' respective goods and services, and the agreement reflects a mutual acknowledgment of peaceful coexistence.

Neither coexistence agreement contains change of control restrictions, termination-upon-assignment provisions, or consent requirements that would be triggered by the Transaction. Accordingly, these agreements do not present obstacles to closing.

VI. Trade Secrets and Proprietary Know-How

A. Identification of Key Trade Secrets

Luminex's trade secret portfolio is a critical component of the company's overall intellectual property position. While the patent and trademark portfolios provide formal registered IP protection, a substantial portion of Luminex's competitive advantage derives from proprietary, unregistered know-how and trade secrets that are not (and, in many cases, cannot be effectively) protected through formal registration. The principal categories of trade secrets and proprietary know-how identified through our review include:

• Proprietary Algorithms: The algorithms underlying the Luminex One platform's predictive supply-chain analytics engine represent a core competitive differentiator. These algorithms incorporate proprietary mathematical models, statistical techniques, and optimization methods that have been developed and refined over more than a decade of R&D investment. While certain aspects of the algorithmic functionality are protected by the patent portfolio's predictive analytics cluster, the underlying implementation details, parameter tuning methodologies, and proprietary enhancements go beyond the scope of the published patent claims and are maintained as trade secrets.

• Training Data Sets and AI/ML Models: Luminex's AI/ML modules for procurement automation and supply-chain analytics have been trained on extensive data sets derived from anonymized and aggregated customer usage data ("Platform Data"). The trained models themselves, including their architectures, hyperparameters, and learned weights, constitute significant proprietary IP. The training data sets, data curation methodologies, and feature engineering techniques are similarly proprietary.

• Customer Pricing Models and discounting Frameworks: Luminex's internal pricing models, discounting frameworks, competitive pricing intelligence, and deal-structuring methodologies represent commercially sensitive trade secrets.

• Internal Product Roadmap Documentation: Luminex's multi-year product development roadmap, including planned features, technology investment priorities, and strategic product direction, constitutes confidential business information and trade secrets.

• Source Code: The source code for the Luminex One platform is maintained in private repositories and has not been published or made publicly available. The source code embodies Luminex's proprietary implementation of the platform's core functionality and represents a significant trade secret asset.

B. Protection Measures

We reviewed the measures that Luminex has implemented to protect the secrecy of its trade secrets and proprietary know-how. The existence and adequacy of reasonable protection measures is a legal prerequisite for trade secret protection under the Defend Trade Secrets Act (18 U.S.C. § 1836), the Uniform Trade Secrets Act (as adopted in applicable U.S. states), the Swiss Unfair Competition Act (UWG), and comparable laws in other jurisdictions where Luminex operates.

Contractual Protections. All employees of the Luminex Group are required to execute proprietary information and inventions assignment agreements ("PIIAAs") at the time of hire. These agreements include confidentiality obligations covering trade secrets and proprietary information, as well as invention assignment provisions (discussed in Section XI below). Consultant and contractor agreements similarly include confidentiality and IP assignment provisions, subject to the gap noted in Section IV.E above with respect to certain legacy contractor agreements from the 2009–2014 period.

Technical Access Controls. Luminex maintains physical and logical access controls designed to limit access to trade secret information on a need-to-know basis. Source code repositories are subject to role-based access controls, with access limited to authorized engineering personnel. Multi-factor authentication ("MFA") is enforced for all access to source code repositories and other sensitive technical systems. Audit logging is maintained for access to source code and other sensitive IP assets, enabling retrospective review of access patterns if a suspected misappropriation or unauthorized disclosure occurs.

Source Code Escrow. Luminex's source code is not published or deposited in any publicly accessible repository. Two source code escrow agreements are in place with major enterprise customers, under which copies of the Luminex One source code are deposited with a third-party escrow agent. Release of the escrowed source code is triggered only upon the occurrence of specified events, including material breach of the applicable SaaS agreement by Luminex that remains uncured for 90 days, or the bankruptcy or insolvency of Luminex. These escrow arrangements are limited in scope and do not represent a general exposure of the source code to third parties. The escrow agreements are discussed in greater detail in Section IX.D below.

Trade Secret Register. We note that Luminex does not currently maintain a formal trade secret register or inventory — i.e., a systematic, documented catalog identifying specific trade secrets, their custodians, applicable protection measures, and access permissions. While the absence of such a register does not, by itself, undermine Luminex's trade secret protections (given the other measures in place), a formal trade secret identification and cataloging program is considered best practice and would strengthen Luminex's ability to assert trade secret claims in the event of misappropriation. We recommend that Ardent Capital implement such a program post-closing as part of the broader IP governance enhancement initiative.

C. Non-Compete and Non-Solicitation Agreements

Key engineering and R&D personnel within the Luminex Group are subject to post-termination non-compete and non-solicitation restrictions. The enforceability and scope of these restrictions vary by jurisdiction:

• Switzerland: Post-termination non-compete covenants are enforceable under Swiss law (Art. 340–340c CO), subject to requirements of reasonableness with respect to geographic scope, duration, and subject matter, as well as the requirement that the restriction protect a legitimate business interest (e.g., access to trade secrets or customer relationships). Dr. Markus Vogt (CTO) is subject to a 12-month post-termination non-compete covenant governed by Swiss law. Annelise Gruber (CFO) is subject to an 18-month post-termination non-compete covenant, also governed by Swiss law.

• Germany: Post-termination non-compete covenants are enforceable under German law, subject to the statutory requirements of Section 74 et seq. of the German Commercial Code (Handelsgesetzbuch, "HGB"), including the obligation to pay compensation during the non-compete period of at least 50% of the employee's last-received compensation. Based on our review, Veltronix GmbH's non-compete arrangements with key German employees appear to comply with the statutory requirements.

• United States: The enforceability of post-termination non-compete covenants varies significantly by state. Non-compete covenants are generally enforceable in Virginia (where Luminex US's headquarters are located), subject to reasonableness limitations. However, non-compete covenants are generally unenforceable in California under California Business and Professions Code Section 16600, and Luminex US employs a number of remote employees in California. For California-based employees, reliance must be placed on confidentiality agreements, trade secret protections, and non-solicitation provisions (to the extent enforceable) rather than non-compete covenants.

• Singapore: Post-termination non-compete covenants are enforceable in Singapore, subject to reasonableness analysis under Singapore common law (following the approach established in Man Financial (S) Pte Ltd v. Wong Bark Chuan David [2008] 1 SLR(R) 663). Luminex Singapore's employment agreements include non-compete provisions for key R&D personnel.

Post-closing employment agreements for Dr. Stefan Kessler (CEO) and Annelise Gruber (CFO) will contain updated restrictive covenants, including non-compete, non-solicitation, and confidentiality provisions, as negotiated in connection with the Transaction. The terms of these updated agreements are being addressed in the Employment & Benefits Due Diligence Summary Memorandum.

VII. Open-Source Software Usage

A. Overview. The Luminex One platform incorporates a significant volume of open-source software ("OSS") components, as is typical for modern enterprise SaaS platforms. In Q4 2024, Luminex's internal engineering team conducted an OSS audit that identified approximately 1,200 distinct OSS components incorporated into the Luminex One platform's codebase and build environment. The results of this audit, including the associated software bill of materials ("SBOM"), were made available in the data room and were reviewed by our team.

It is important to note that the Q4 2024 OSS audit was performed by Luminex's internal engineering team using internal tooling and was not conducted by an independent third-party OSS audit firm. While the internal audit provides a useful baseline, it may not capture all OSS components present in the codebase — particularly components that may have been introduced through transitive dependencies, bundled libraries, or legacy code modules. Accordingly, we recommend that an independent third-party OSS audit firm be engaged to conduct a comprehensive binary-level scan of the Luminex One production build, as discussed further in our recommendations.

A summary of material OSS components organized by license type, component name, version, module in which incorporated, and risk rating is set forth in Appendix C to this memorandum.

B. License Categories Identified

The approximately 1,200 OSS components identified in the Q4 2024 audit fall into three broad license categories, each carrying a different level of compliance risk:

Permissive Licenses (approximately 78% of components — Low Risk). The majority of OSS components incorporated into the Luminex One platform are licensed under permissive open-source licenses, including the MIT License, the Apache License, Version 2.0, and the BSD License family (2-Clause and 3-Clause). Permissive licenses impose minimal obligations on licensees — typically limited to the retention of copyright notices and license text in redistributed copies. Permissive licenses do not impose "copyleft" obligations requiring the disclosure of source code for derivative works or combined works. These components present low compliance risk.

Weak Copyleft Licenses (approximately 15% of components — Moderate Risk). Approximately 15% of the identified OSS components are licensed under weak copyleft licenses, primarily the GNU Lesser General Public License, Version 2.1 ("LGPL 2.1") and the Mozilla Public License, Version 2.0 ("MPL 2.0"). Weak copyleft licenses require compliance with notice and source-availability obligations for modifications made to the licensed component itself, but do not generally propagate copyleft obligations to the larger proprietary work with which the component is combined, provided that the component is linked in a manner that preserves the modularity of the licensed component (e.g., dynamic linking rather than static linking). Based on our review of the Q4 2024 audit report and discussions with Luminex's VP of Engineering, LGPL-licensed components are dynamically linked in the current architecture. Dynamic linking is the generally accepted approach to avoid copyleft propagation to Luminex's proprietary code. However, it is important to confirm, through the recommended independent third-party audit, that no LGPL components have been statically linked, which could expand the scope of the copyleft obligations.

Strong Copyleft Licenses (approximately 7% of components — Higher Risk). Approximately 7% of the identified OSS components are licensed under strong copyleft licenses, including the GNU General Public License, Version 2 ("GPL v2"), the GNU General Public License, Version 3 ("GPL v3"), and the GNU Affero General Public License, Version 3 ("AGPL v3"). Strong copyleft licenses impose more extensive obligations that, depending on the nature and manner of use, may require the disclosure of source code for the larger work in which the copyleft-licensed component is incorporated. The analysis of these components is as follows:

• GPL v2/v3 Components. GPL-licensed components identified in the audit are used in internal build tools and development environments (e.g., build system utilities, compiler toolchains, and development-time testing frameworks). These components are not distributed to Luminex's customers in a manner that would trigger the GPL's distribution-triggered copyleft obligations. Moreover, under Luminex's SaaS delivery model, the Luminex One platform is provided to customers as a hosted service rather than distributed as a software copy, and the GPL's copyleft obligations are triggered by "distribution" or "conveying" of copies, not by provision of a hosted service. Accordingly, the use of GPL v2/v3 components in the manner described does not appear to implicate the GPL's source code disclosure obligations. However, the interaction between GPL-licensed components and AGPL-licensed components in the build and deployment environment warrants careful review to ensure there is no unintended copyleft propagation.

• AGPL v3 Components. Three components licensed under the AGPL v3 were identified in the audit. The AGPL differs from the standard GPL in a critical respect: Section 13 of the AGPL extends copyleft obligations to software that interacts with users over a computer network, even absent traditional "distribution." This provision was specifically designed to close the so-called "ASP loophole" and ensure that copyleft obligations apply to software provided as a service. If AGPL-licensed components are incorporated into or interact with the Luminex One platform code that is accessible to customers over the network, Luminex could face obligations to make the corresponding source code of the combined work available to those customers, which could implicate trade secret protections for Luminex's proprietary platform code.

Based on our review of the audit report and discussions with Luminex's engineering team, the three AGPL v3 components are used in non-customer-facing internal monitoring and observability tools that are separate from the Luminex One production codebase. If this characterization is accurate, and if the AGPL components are properly isolated from the customer-facing production codebase (i.e., there is no code sharing, dynamic linking, API integration, or process-level interaction between the AGPL components and the Luminex One platform), the AGPL copyleft obligations should not propagate to the proprietary Luminex One code.

However, verification of this isolation is critical. This verification should be conducted through a comprehensive binary-level scan by an independent third-party OSS audit firm, which can confirm at a technical level whether the AGPL components are present in or interact with the Luminex One production build artifacts that are served to customers.

C. Compliance Status and Risk Assessment

Luminex maintains an OSS policy document that establishes guidelines for the evaluation, approval, and use of open-source components within the Luminex One platform. The policy document was reviewed in the data room and covers topics including license categorization, approval workflows, and attribution requirements. Luminex also maintains an internal SBOM generated through automated tooling integrated into the development workflow.

Attribution Compliance. Attribution notices required by permissive licenses (including copyright notices and license text) are included in Luminex One's product documentation and in a dedicated open-source attribution file accessible through the platform's administrative interface. Based on our review, the attribution practices appear to be generally compliant with the requirements of the applicable permissive licenses.

LGPL Compliance. For LGPL-licensed components, Luminex uses dynamic linking, which is the generally accepted approach to maintaining separation between the LGPL-licensed component and the proprietary code and to avoiding copyleft propagation. As noted above, we recommend that the independent third-party OSS audit confirm that no LGPL components have been statically linked.

AGPL Risk Assessment. The three AGPL v3 components represent the highest-priority OSS compliance risk identified in this review. If these components are not properly isolated from the Luminex One production codebase, the AGPL's network interaction copyleft provision could require Luminex to make the corresponding source code of the combined work available to customers accessing the platform over the network. Such an obligation, if triggered, could directly conflict with Luminex's trade secret protections for its proprietary platform code and could materially impair the value of the proprietary IP. For this reason, verification of the isolation of AGPL components is critical and should be a priority item in the recommended independent third-party OSS audit.

Recommendations. We recommend the following actions with respect to OSS compliance:

1. Independent Third-Party OSS Audit. Engage an independent third-party OSS audit firm to conduct a comprehensive binary-level scan of the Luminex One production build prior to or promptly after closing. The scope of the audit should include confirmation of (a) the completeness of the SBOM, (b) the absence of undisclosed strong copyleft components in the production codebase, (c) the isolation of the AGPL v3 components from the production codebase, and (d) the absence of static linking of LGPL components.

2. Enhanced OSS Governance. Post-closing, implement an enhanced OSS governance framework, including (a) an OSS review committee with authority to approve or reject the introduction of new OSS components, (b) automated OSS scanning integrated into the CI/CD pipeline to detect and flag the introduction of components under restricted licenses, and (c) regular (at least quarterly) SBOM refresh and review processes.

D. Inbound OSS Contributions

Luminex contributes to several open-source projects, primarily in the Kubernetes ecosystem and Apache Software Foundation projects. Based on our review, these outbound contributions are limited to non-proprietary tooling, infrastructure utilities, and bug fixes, and do not expose any proprietary Luminex One platform code or proprietary algorithms. Contributor license agreements ("CLAs") are in place for all outbound contributions made by Luminex employees, ensuring that Luminex has the necessary rights to contribute code and that contributors have not inadvertently assigned proprietary rights to the open-source

PRIVILEGED & CONFIDENTIAL — ATTORNEY-CLIENT PRIVILEGE / ATTORNEY WORK PRODUCT This memorandum was prepared by Calderwood & Harkness LLP at the direction of Ardent Capital Partners III LP and its affiliates and is protected by the attorney-client privilege and the work product doctrine. This memorandum and the information contained herein are strictly confidential and may not be disclosed, distributed, or reproduced, in whole or in part, to any third party without the prior written consent of Calderwood & Harkness LLP.
CALDERWOOD & HARKNESS LLP 7 Times Square New York, NY 10036
MEMORANDUM
To: James Prentice, Partner; Sandra Tung, Partner
From: Ryan Kowalski, Lead Associate; Megan Chu, Working Associate
Date: April 14, 2025
Re: IP & Technology Due Diligence Summary — Acquisition of Luminex Systems Holdings Inc. by Ardent Capital Partners III LP
Matter No.: 1001-00004
Classification: Privileged and Confidential
Right-click to update Table of Contents
I. Executive Summary
This memorandum summarizes the principal findings of the intellectual property and technology due diligence review conducted by Calderwood & Harkness LLP ("Calderwood & Harkness" or "C&H") in connection with the proposed acquisition (the "Transaction") of Luminex Systems Holdings Inc. ("Luminex Holdings" or the "Target") by Ardent Capital Partners III LP ("Ardent Capital" or the "Client"). The Transaction is structured as a reverse triangular merger under the Delaware General Corporation Law, with Ardent Apex Merger Sub Inc. ("Merger Sub"), a wholly owned subsidiary of Ardent Apex Holdings Inc., merging with and into Luminex Holdings, with Luminex Holdings surviving as a wholly owned indirect subsidiary of Ardent Capital, for an aggregate equity consideration of Two Billion Eight Hundred Million Dollars ($2,800,000,000) (the "Purchase Price").
The scope of this memorandum encompasses a comprehensive review of the Target's intellectual property assets, technology stack, software architecture, open-source software compliance, patent portfolio, trademark portfolio, trade secrets and proprietary know-how, domain name portfolio, intercompany IP licensing arrangements, third-party inbound and outbound technology licenses, employee and contractor IP assignment matters, and data privacy considerations to the extent they bear upon technology-related intellectual property. The review encompasses Luminex Holdings and each of its direct and indirect subsidiaries, including Luminex Systems AG (Switzerland), Luminex Systems Inc. (Delaware), Luminex Systems UK Ltd. (United Kingdom), Luminex Systems GmbH (Germany), and Luminex Systems Pte. Ltd. (Singapore) (each, a "Luminex Entity" and collectively, the "Luminex Group").
The documents and information reviewed in connection with this memorandum were obtained from the virtual data room maintained by Caldwell, Raines & Sheppard LLP ("CRS"), seller's counsel (principal contact: Patricia Okonkwo, Partner), as coordinated through Pinehurst Rothwell & Co., seller's financial advisor (principal contact: Samantha Delacroix, Managing Director). Supplemental information was obtained through management presentations, written due diligence questionnaire responses, and targeted interview sessions with Luminex management and in-house legal personnel.
Key Findings. Our principal findings are summarized as follows:
(i) Core IP Concentration. Luminex's core intellectual property is concentrated in the "Luminex One" cloud-based enterprise resource planning (ERP), procurement automation, and supply-chain analytics software-as-a-service (SaaS) platform. The foundational IP — including patents, trademarks, copyrights in source code, and trade secrets — is owned predominantly by Luminex Systems AG (Switzerland), with a limited number of U.S. utility patents held by Luminex Systems Inc. (Delaware). No intellectual property is held directly by Luminex Holdings, the merger target entity.
(ii) Patent Portfolio. The patent portfolio is modest in size (approximately 47 issued patents and 12 pending applications across U.S., European, Swiss, and Singaporean jurisdictions) but provides strategically meaningful defensive coverage for Luminex One's core technology. One assignment gap has been identified with respect to a 2013 U.S. patent application originally filed by a former consultant.
(iii) Trademark Portfolio. The trademark portfolio is well-maintained and provides comprehensive global coverage for Luminex's principal brands. No material disputes are pending.
(iv) Open-Source Software Usage. Open-source software usage is material. The Luminex One platform incorporates approximately 1,200 distinct open-source components. While the vast majority are under permissive licenses presenting low compliance risk, three components licensed under the GNU Affero General Public License, Version 3 ("AGPL v3") present elevated risk requiring verification of their isolation from customer-facing production code. No independent third-party open-source audit has been conducted, and we recommend one be commissioned prior to or promptly after closing.
(v) Intercompany IP Licensing. The intercompany IP licensing arrangement between Luminex AG (as licensor) and Luminex US (as licensee) provides for a royalty rate of 4.5% of U.S. net revenues. This rate falls below the arm's-length range identified in a preliminary transfer-pricing benchmark study conducted by Pendleton & Associates LLP, which indicates a median rate of approximately 6.0%. Post-closing restructuring of the royalty rate is contemplated. The intercompany IP license agreements do not contain change of control termination provisions.
(vi) Third-Party License Change of Control Provisions. Eight of approximately 45 material third-party technology licenses contain change of control provisions (consent or notice requirements). Outreach to the relevant counterparties has been initiated and is being tracked in the internal Change of Control / Consent Tracker.
(vii) IP Litigation. No material IP litigation is currently pending or, to the knowledge of Luminex management, threatened. Two patent assertion entity demand letters received in 2023 were resolved without payment or license.
Overall Risk Assessment. Based on our review, we assess the overall IP and technology risk profile of the Transaction as moderate — the identified issues are manageable with the pre-closing and post-closing remediation actions recommended in Section XV of this memorandum. No findings were identified that, in our assessment, constitute a material adverse condition warranting reconsideration of the Transaction or a material adjustment to the Purchase Price, though the open-source compliance matters and legacy contractor assignment gaps warrant focused attention in the Merger Agreement disclosure schedules and post-closing integration planning.
II. Scope of Review and Methodology
A. Documents Reviewed
In connection with this due diligence review, we reviewed the following categories of documents and materials made available through the virtual data room and supplemental production:
1.  IP assignment and license agreements, including all executed intercompany IP license agreements among the Luminex Entities, as well as agreements reflecting the assignment of intellectual property from founders, employees, and third parties to the relevant Luminex Entities.
2.  Patent filings, prosecution files, and maintenance records for all issued patents and pending patent applications held by Luminex Systems AG and Luminex Systems Inc., including original application filings, office action responses, notices of allowance, grant certificates, maintenance fee payment receipts, and assignment recordation confirmations filed with the U.S. Patent and Trademark Office ("USPTO"), the European Patent Office ("EPO"), the Swiss Federal Institute of intellectual Property ("IPI"), the intellectual Property Office of Singapore ("IPOS"), and relevant national patent offices.
3.  Trademark registrations and applications across all jurisdictions in which the Luminex Group maintains trademark protection, including registration certificates, specimens of use, declaration filings (including Sections 8, 15, and 71 declarations for U.S. registrations), renewal receipts, and prosecution correspondence.
4.  Domain name portfolio records, including registrar account documentation, WHOIS records, and DNS configuration summaries for all domain names maintained by the Luminex Group.
5.  Open-source software audit reports and the software bill of materials ("SBOM") generated by Luminex's internal engineering team in Q4 2024, including component-level detail on license type, version, and deployment context within the Luminex One platform architecture.
6.  Third-party software license agreements for all material inbound software licenses utilized by the Luminex Group in its operations, including cloud infrastructure service agreements, database platform licenses, analytics libraries, security tools, payment processing integrations, and monitoring platforms.
7.  Intercompany IP license agreements between Luminex Systems AG and each of Luminex Systems Inc. (U.S.), Luminex Systems GmbH (Germany), Luminex Systems UK Ltd. (U.K.), and Luminex Systems Pte. Ltd. (Singapore), together with the underlying transfer-pricing documentation and the 2021 transfer-pricing study prepared in connection with the corporate reorganization.
8.  Employee invention assignment agreements and proprietary information and inventions assignment agreements ("PIIAAs") for employees of each Luminex Entity, including jurisdiction-specific forms for the United States (including the California-compliant variant), Switzerland, Germany, the United Kingdom, and Singapore.
9.  Consultant and independent contractor IP assignment agreements, including both current-form template agreements and legacy agreements dating to Luminex AG's founding period (2009–2014).
10.  Technology partnership and co-development agreements to which any Luminex Entity is a party, including joint development arrangements, technology integration partnerships, and strategic alliance agreements.
11.  Source code escrow agreements entered into with major enterprise customers, including the escrow deposit instructions, release conditions, and verification procedures established with the applicable third-party escrow agent.
12.  Data processing agreements and data privacy agreements to the extent such agreements contain provisions relevant to IP ownership, derived data rights, or restrictions on the use of customer data for product improvement and AI/ML model training.
13.  Insurance policies covering intellectual property-related risks, including errors and omissions (E&O) policies and cyber liability insurance policies maintained by the Luminex Group.
14.  Correspondence with patent and trademark prosecution counsel, including docketing reports, prosecution status summaries, and renewal calendars.
15.  Internal technology architecture documentation and technical memoranda, including system design documents, architectural diagrams, technology stack descriptions, and security posture assessments, including SOC 2 Type II audit reports and ISO 27001 certification documentation.
B. Interviews and Discussions
In addition to the documentary review described above, we conducted targeted interviews and participated in working sessions with the following individuals and advisors:
•  Dr. Markus Vogt, Chief Technology Officer of Luminex Systems AG, who provided detailed information regarding the Luminex One platform architecture, the technology stack, the patent portfolio's relationship to core platform functionality, AI/ML model development and training data practices, and open-source software usage and governance practices.
•  Luminex VP of Engineering (participated in technical working sessions), who provided supplemental detail on software development lifecycle processes, the CI/CD pipeline, source code repository management and access controls, and the current state of OSS governance tooling.
•  Luminex General Counsel (In-House), who provided information regarding the history of the Luminex IP portfolio, the intercompany licensing structure, employee and contractor IP assignment practices, and the status of any IP-related disputes or claims.
•  Daniel Feinberg, Associate at Caldwell, Raines & Sheppard LLP (seller's counsel), who coordinated the production of responsive documents in the virtual data room and facilitated management access for due diligence interview sessions.
•  Dr. Lukas Breitfeld, Partner at Breitfeld Hess & Partner AG (Swiss local counsel to Calderwood & Harkness), who provided input on Swiss IP law considerations, including the Swiss Code of Obligations provisions governing employee inventions (Art. 332 CO), the enforceability of non-compete covenants under Swiss law, and the ownership and assignment of intellectual property created by Swiss-based employees and contractors.
•  Dr. Katarina Wendt, Partner at Wendt Schäfer Rechtsanwälte PartG mbB (German local counsel to Calderwood & Harkness), who provided input on German IP law considerations, including the German Employee Inventions Act (Arbeitnehmererfindungsgesetz, "ArbNEG"), the proper claiming and compensation of employee inventions under German law, and German data privacy law considerations relevant to the IP and technology review.
•  Kelvin Tan, Partner at Tan Liang & Associates LLP (Singapore local counsel to Calderwood & Harkness), who provided input on Singapore IP law considerations, including the Singapore Patents Act and Copyright Act provisions governing ownership of IP created by employees and contractors.
C. Limitations.  The following limitations apply to this memorandum and the findings set forth herein:
•  Source Code Review. A detailed technical source code review has not been completed as of the date of this memorandum. Access to certain source code repositories has been requested but remains pending clearance from Luminex's security team. Ardent Capital's independent technology consultants are expected to conduct a supplemental technical source code review upon access being granted. Findings from that review, if material, will be addressed in a supplemental memorandum.
•  Freedom-to-Operate Analysis. A comprehensive third-party IP infringement freedom-to-operate ("FTO") analysis was not conducted as part of this review. Our review has confirmed that no pending patent infringement claims exist against the Luminex Group, and Luminex's in-house counsel is not aware of any threatened claims. However, if Ardent Capital desires a comprehensive FTO clearance opinion with respect to the Luminex One platform's core technology — particularly with respect to the predictive analytics and AI/ML modules — we recommend engaging a specialized patent clearance firm to conduct a separate FTO study.
•  Reliance on Management Representations. Certain factual findings in this memorandum are based, in part, on representations made by Luminex management and in-house counsel during interview sessions and through due diligence questionnaire responses. To the extent that material facts differ from management representations, our findings and risk assessments may need to be revised.
•  No Tax or Accounting Advice. While this memorandum references transfer-pricing considerations relating to the intercompany IP licensing structure, it does not constitute tax or accounting advice. Transfer-pricing and tax structuring matters are being addressed separately by Pendleton & Associates LLP (Richard Chow) and by Sylvia Hartwell of Calderwood & Harkness's tax practice group.
III. Overview of Luminex's Business and Technology
A. Business Overview
Luminex Systems Holdings Inc. is a Delaware corporation incorporated on June 14, 2021, in connection with a corporate reorganization (the "2021 Reorganization") designed to establish a U.S. intermediate holding company structure. Luminex Holdings serves as the direct parent of Luminex Systems Inc. (Delaware), which in turn conducts the Luminex Group's U.S.-based operations. Luminex Holdings also serves as the direct or indirect parent of the Luminex Group's international operating subsidiaries through the original Swiss parent entity, Luminex Systems AG.
Luminex Systems AG was founded in 2009 in Zürich, Switzerland (Commercial Register No. CHE-284.391.057) by Dr. Stefan Kessler (Chief Executive Officer) and Dr. Markus Vogt (Chief Technology Officer). The company's global headquarters remain at Bahnhofstrasse 71, 8001 Zürich, Switzerland, while the U.S. operational headquarters are located at 2100 Reston Gateway Drive, Suite 800, Reston, Virginia 20191.
As of the date hereof, the Luminex Group employs approximately 4,200 individuals globally, of whom approximately 1,650 are based in the United States. The remaining workforce is distributed across Switzerland (approximately 900), Germany (approximately 700), the United Kingdom (approximately 450), Singapore (approximately 350), and other locations (approximately 150).
For the fiscal year ended December 31, 2024, the Luminex Group reported total revenue of approximately $487 million, consisting of $441 million in annual recurring revenue ("ARR") derived from SaaS subscription fees and $46 million in professional services revenue. The Luminex Group reported adjusted EBITDA of approximately $121.8 million for the same period, representing an adjusted EBITDA margin of approximately 25.0%. Revenue is concentrated across four principal geographic regions: the DACH region (Germany, Austria, Switzerland), representing approximately 35% of total revenue; North America, representing approximately 40%; the United Kingdom and Nordics, representing approximately 15%; and the Asia-Pacific ("APAC") region, representing approximately 10%.
B. Core Product — Luminex One Platform
The Luminex Group's core product offering is the Luminex One platform, a cloud-based enterprise resource planning (ERP), procurement automation, and supply-chain analytics SaaS platform. Luminex One is designed to serve mid-market and enterprise customers across a range of industries, providing an integrated suite of tools for managing procurement workflows, supply-chain operations, vendor relationships, invoice processing, and contract lifecycle management.
Architecture. Luminex One is built on a multi-tenant SaaS architecture deployed on major cloud infrastructure. The platform utilizes a microservices-based architectural pattern with containerized deployment, enabling independent scaling and deployment of individual service components. This architecture supports high availability, horizontal scalability, and continuous deployment capabilities.
Core Modules. The Luminex One platform consists of the following principal functional modules:
•  ERP Module: Core enterprise resource planning functionality, including financial management, general ledger, accounts payable and receivable, and budgeting and forecasting tools.
•  Procurement Automation Module: Automated procurement workflows, including requisition-to-purchase order processing, approval routing, and supplier bidding and evaluation tools. This module incorporates proprietary AI/ML algorithms for spend optimization and automated vendor selection.
•  Supply-Chain Analytics Module: Predictive supply-chain analytics engine that leverages proprietary algorithms and machine learning models to provide demand forecasting, inventory optimization, risk assessment, and supply-chain visibility dashboards. This module represents a core competitive differentiator for Luminex.
•  Vendor Management Module: Comprehensive vendor lifecycle management, including onboarding, performance monitoring, compliance tracking, and risk scoring.
•  Invoice Processing Module: intelligent invoice processing and data extraction capabilities, leveraging optical character recognition (OCR) and natural language processing (NLP) technologies for automated invoice capture, validation, and matching.
•  Contract Lifecycle Management (CLM) Module: NLP-based contract analytics, authoring, negotiation, and management tools, including automated clause extraction, obligation tracking, and renewal management.
Proprietary Technology. The Luminex One platform incorporates significant proprietary technology, including proprietary algorithms for predictive supply-chain analytics and spend optimization, as well as AI/ML modules developed using Luminex's internally generated training data sets. These proprietary elements represent key competitive differentiators and form the core of Luminex's trade secret portfolio.
Customer Base. As of the date hereof, Luminex maintains approximately 340 commercial customer contracts and 26 enterprise license agreements ("ELAs") with large customers. A number of these agreements contain change of control provisions that are relevant to the Transaction; these provisions are being tracked in the Change of Control / Consent Tracker maintained as an internal working document. For a comprehensive analysis of Luminex's material customer contracts, including change of control provisions, reference is made to the separate Material Contracts Review Memorandum and the Change of Control / Consent Tracker prepared in connection with the Transaction.
Government Customers. Luminex maintains a significant U.S. federal government customer base, including contracts with the U.S. Department of Defense ("DOD") for a logistics software module, the U.S. Department of Energy ("DOE") for a procurement platform, and the U.S. General Services Administration ("GSA") under an enterprise license arrangement. These government contracts are subject to the Federal Acquisition Regulation ("FAR") and, in the case of the DOD contract, the Defense Federal Acquisition Regulation Supplement ("DFARS"), and carry assignment/novation requirements that must be coordinated with the broader Transaction closing process. Additionally, the Luminex Group's government customer relationships and the associated technology are relevant to the ongoing review by the Committee on Foreign Investment in the United States ("CFIUS") under CFIUS Tracking No. CFIUS-2025-0087.
C. Subsidiary Technology Operations
The Luminex Group's technology development, sales, and service delivery operations are conducted through the following operating subsidiaries:
•  Luminex Systems Inc. ("Luminex US"), a Delaware corporation, serves as the U.S. operating entity responsible for U.S.-based product development, sales, customer success, and professional services. Luminex US reported 2024 U.S. revenue of approximately $194.8 million. Luminex US holds 9 U.S. utility patents assigned from employee inventors and is the licensee under the intercompany IP License Agreement with Luminex AG.
•  Luminex Systems AG ("Luminex AG"), a Swiss Aktiengesellschaft (Commercial Register No. CHE-284.391.057), headquartered in Zürich, Switzerland, serves as the core research and development center and the primary holder of the Luminex Group's intellectual property. Luminex AG owns the majority of the Luminex Group's issued patents (approximately 38 of 47), all registered trademarks, and the foundational copyrights in the Luminex One platform source code and associated trade secrets.
•  Luminex Systems GmbH ("Veltronix GmbH"), a German Gesellschaft mit beschränkter Haftung (Commercial Register No. HRB 247891, registered with the Munich Commercial Register), serves as the European development and sales hub, with a particular focus on the DACH region. Veltronix GmbH reported 2024 German revenue of approximately €67 million.
•  Luminex Systems UK Ltd. ("Luminex UK"), a company incorporated in England and Wales (Company No. 12847362), headquartered in London, serves as the sales and professional services entity for the United Kingdom and Nordics markets.
•  Luminex Systems Pte. Ltd. ("Luminex Singapore"), a company incorporated in Singapore (Unique Entity Number 201924781K), serves as the APAC regional development hub and sales entity.
IV. Patent Portfolio
A. Overview and Statistics
The Luminex Group's patent portfolio consists of approximately 47 issued patents and 12 pending patent applications across the United States, Europe (via the European Patent Office and national phase validations), Switzerland, and Singapore. The portfolio is concentrated in the technological domains most closely associated with the Luminex One platform's core functionality.
The primary patent holder within the Luminex Group is Luminex Systems AG, which holds approximately 38 of the 47 issued patents. These patents were either filed directly by Luminex AG or assigned to Luminex AG from employee inventors and, in certain cases, from the company's co-founders. Luminex Systems Inc. (Luminex US) holds 9 U.S. utility patents that were assigned from U.S.-based employee inventors in accordance with the terms of their respective PIIAAs.
It is important to note that no patents are held directly by Luminex Holdings, the entity that will survive the reverse triangular merger. All patents are held at the operating subsidiary level — principally by Luminex AG and, to a lesser extent, by Luminex US. This ownership structure means that the patent assets will be acquired indirectly through the acquisition of Luminex Holdings' equity interest in its subsidiaries, rather than through a direct transfer of patent ownership. This structure preserves continuity of patent ownership at the subsidiary level and avoids the need to record new patent assignments in connection with the Transaction itself, provided the surviving corporation structure is maintained as contemplated.
A complete listing of all issued patents and pending applications, including patent/application numbers, titles, jurisdictions, filing dates, issue dates, expiration dates, owner entities, and current statuses, is set forth in Appendix A to this memorandum.
B. Subject Matter Coverage
The patent portfolio provides coverage across the principal technology areas that underlie the Luminex One platform. The patents cluster into the following subject matter groups:
•  Predictive Supply-Chain Analytics Algorithms (approximately 14 patents): This cluster represents the core defensive group within the portfolio and covers Luminex's proprietary algorithms for demand forecasting, supply-chain risk assessment, inventory optimization, and predictive logistics modeling. These patents protect Luminex One's primary competitive differentiator in the marketplace.
•  Automated Procurement Workflow Optimization (approximately 10 patents): This cluster covers methods and systems for automating procurement processes, including intelligent requisition routing, automated vendor selection, bid evaluation algorithms, and dynamic approval workflows.
•  Multi-Tenant SaaS Data Isolation and Security Architecture (approximately 8 patents): This cluster covers aspects of Luminex One's multi-tenant architecture, including methods for tenant data isolation, secure multi-tenancy in shared infrastructure environments, and role-based access control mechanisms within a SaaS deployment model.
•  Invoice Processing and intelligent Data Extraction (approximately 7 patents): This cluster covers Luminex's technologies for automated invoice capture, intelligent data extraction using OCR and pattern recognition, invoice-to-purchase-order matching algorithms, and exception handling workflows.
•  Contract Analytics and NLP-Based Contract Management (approximately 8 patents): This cluster covers Luminex's natural language processing technologies for contract clause extraction, obligation identification, risk scoring, and automated contract analytics.
The 12 pending patent applications are focused on next-generation AI/ML procurement modules, including advanced machine learning techniques for spend classification, anomaly detection in procurement patterns, and reinforcement learning approaches to supply-chain optimization. These pending applications, if granted, would extend the portfolio's defensive perimeter into Luminex's emerging AI/ML capabilities.
C. Geographic Coverage
The patent portfolio provides geographic coverage across Luminex's principal markets:
•  United States (USPTO): 23 issued patents and 7 pending applications. The U.S. portfolio is the most extensive, reflecting North America's position as Luminex's largest revenue market.
•  European Patent Office (EPO) / National Validations: 18 issued patents and 4 pending applications. EPO-granted patents have been validated in Germany, France, the United Kingdom, and Switzerland, providing protection across Luminex's key European markets. Post-Brexit U.K. validations of pre-Brexit EPO grants remain effective under the U.K.'s transitional provisions.
•  Singapore (IPOS): 6 issued patents and 1 pending application. The Singapore portfolio provides protection in Luminex's APAC hub jurisdiction.
We note that the portfolio does not include patent filings in certain markets where Luminex has commercial activity, including Australia, Japan, and the broader Nordic countries. While this is not unusual for a company of Luminex's size and stage, Ardent Capital may wish to evaluate whether supplemental patent filings in additional jurisdictions would be strategically beneficial post-closing.
D. Maintenance and Prosecution Status
Based on our review of the maintenance records and prosecution files made available in the data room, all 47 issued patents are current on maintenance fee and annuity payments. No lapses were identified in any jurisdiction. Pending patent applications are being prosecuted in the ordinary course, and no missed deadlines or abandoned applications were identified during our review period.
Patent prosecution for the Luminex Group is handled by outside patent prosecution counsel engaged directly by Luminex AG and Luminex US. Calderwood & Harkness does not serve as Luminex's patent prosecution counsel. We have reviewed the prosecution correspondence and docketing reports provided by Luminex's in-house legal team and have not identified any material issues with respect to the conduct of patent prosecution or the timing of prosecution actions.
E. Assignments and Chain of Title
We have reviewed the chain of title documentation for the patent portfolio, including employee invention assignment agreements, founder assignment records, and assignment instruments recorded with the relevant patent offices.
Employee Invention Assignments. We reviewed the invention assignment agreements executed by key engineering personnel and the company's co-founders. Dr. Markus Vogt (CTO), as co-founder, executed a comprehensive invention assignment agreement at the time of Luminex AG's founding in 2009, covering all intellectual property developed in the course of his employment with Luminex AG. Similar agreements were executed by other members of the founding engineering team. Current PIIAAs for U.S. employees include standard present-tense assignment language assigning to Luminex US all inventions conceived or reduced to practice during the course of employment that relate to Luminex's business. Swiss and German employees are subject to the applicable statutory frameworks (Swiss Code of Obligations Art. 332 and German ArbNEG, respectively), and supplemental invention assignment agreements have been executed by R&D staff in those jurisdictions.
Founder Assignments. Several early-stage patents were originally filed under the personal name of Dr. Stefan Kessler (CEO, co-founder) during the period prior to the formalization of Luminex AG's IP assignment procedures. These patents were subsequently assigned to Luminex AG through executed assignment instruments that have been recorded with the USPTO and the EPO, as applicable. The recorded assignment instruments were reviewed and appear to be in proper form.
Assignment Gap Identified. We identified one assignment gap that warrants attention. A 2013 U.S. patent application (relating to an early procurement workflow module) was filed under the name of a former independent consultant engaged by Luminex AG during the company's early development phase. An assignment instrument was subsequently executed and recorded with the USPTO, transferring the application from the consultant to Luminex AG. However, the underlying consultant agreement — which would typically contain the contractual IP assignment obligation — has not been located in the data room. In the absence of the underlying agreement, there is a theoretical risk that the assignment could be challenged as lacking adequate consideration or contractual basis, although the executed and recorded assignment instrument itself provides significant evidence of the parties' intent. We recommend that Luminex obtain a confirmatory assignment from the former consultant, or that the matter be addressed through appropriate representations, warranties, and indemnification provisions in the Merger Agreement's disclosure schedules. This item is discussed further in our recommendations in Section XV.
Liens and Encumbrances. Based on our review of the data room documents and representations from Luminex's in-house counsel, no liens, security interests, or encumbrances have been granted with respect to any patents in the portfolio. We recommend that UCC lien searches (with respect to Luminex US and Luminex Holdings) and WIPO lien searches (with respect to Luminex AG and other non-U.S. entities) be completed to confirm the absence of recorded encumbrances. These searches are being coordinated separately.
F. Freedom-to-Operate and Infringement Considerations
Based on our review, there are no pending patent infringement claims asserted against any Luminex Entity, and no Luminex Entity has asserted patent infringement claims against any third party.
Luminex's in-house counsel confirmed receipt of two demand letters from patent assertion entities ("PAEs") in 2023. Both demand letters related to broadly drafted patents covering generic cloud computing and SaaS architectures. In each case, Luminex's outside patent counsel responded with a detailed non-infringement analysis, and both matters were resolved without any payment, license, or settlement. There are no active disputes arising from these demand letters, and no follow-up correspondence has been received.
As noted in Section II.C above, a comprehensive freedom-to-operate analysis was not conducted as part of this review. While the absence of pending claims and the resolution of the PAE demand letters are encouraging indicators, they do not constitute a comprehensive clearance of the Luminex One platform's technology against all potentially relevant third-party patents. If Ardent Capital desires a higher level of confidence regarding FTO, we recommend engaging a specialized patent clearance firm to conduct a targeted FTO study focused on Luminex One's core proprietary algorithms, particularly in the areas of predictive analytics and AI/ML-based procurement automation, where the patent landscape is evolving rapidly.
V. Trademark Portfolio
A. Overview.  The Luminex Group maintains a trademark portfolio consisting of approximately 34 registered trademarks and 6 pending trademark applications across multiple jurisdictions worldwide. The portfolio provides comprehensive brand protection for Luminex's principal marks, including "LUMINEX," "LUMINEX ONE," "LUMINEX SYSTEMS," and associated design marks and logos. Trademark registrations cover goods and services in International Classes 9 (computer software), 35 (business management and administration services), 38 (telecommunications services), and 42 (technology services, including SaaS and cloud computing).
A complete listing of all registered trademarks and pending applications, including registration/application numbers, marks, jurisdictions, international classes, registration dates, renewal dates, owner entities, and current statuses, is set forth in Appendix B to this memorandum.
B. Key Registrations by Jurisdiction
The trademark portfolio provides coverage in the following principal jurisdictions:
•  United States (USPTO): 12 registered trademarks and 2 pending applications. U.S. registrations include the primary word marks "LUMINEX," "LUMINEX ONE," and "LUMINEX SYSTEMS," as well as the associated logo design marks, across the relevant international classes.
•  European Union (EUIPO): 8 registered trademarks and 1 pending application. EU trademark registrations provide unitary protection across all EU member states.
•  Switzerland (IPI): 5 registered trademarks and 1 pending application. Swiss registrations provide protection in Luminex AG's home jurisdiction.
•  United Kingdom (UKIPO): 4 registered trademarks and 1 pending application. Following the United Kingdom's withdrawal from the European Union, Luminex proactively re-filed certain marks with the UKIPO to ensure continued U.K. protection. Comparable rights from pre-Brexit EU registrations were also automatically cloned in accordance with U.K. transitional provisions.
•  Singapore (IPOS): 3 registered trademarks and 1 pending application. Singapore registrations protect the brand in Luminex's APAC hub jurisdiction.
•  Additional National Registrations: Luminex maintains additional national trademark registrations in Germany (supplemental to EU-wide EUIPO registrations), Australia, and Japan, reflecting Luminex's commercial activities in those markets.
C. Ownership.  All trademark registrations in the Luminex Group's portfolio are held by Luminex Systems AG as the primary brand owner. This centralized ownership structure is consistent with Luminex AG's role as the core IP holding entity within the Luminex Group. Luminex AG licenses the use of its trademarks to the operating subsidiaries (Luminex US, Luminex UK, Veltronix GmbH, and Luminex Singapore) under the terms of the intercompany IP license agreement described in Section VIII of this memorandum. The license structure ensures that each subsidiary's use of the Luminex marks inures to the benefit of Luminex AG as the registered owner, which is important for maintaining the validity and enforceability of the trademark registrations.
D. Maintenance and Renewal Status
Based on our review, all trademark registrations in the portfolio are current, and no missed renewal deadlines were identified. For U.S. registrations, Section 8 Declarations of Continued Use and Section 15 Declarations of Incontestability have been filed on a timely basis. Luminex's in-house legal department maintains a renewal calendar for the trademark portfolio and has confirmed that all upcoming renewal deadlines through the end of 2025 have been docketed and are being tracked. We recommend that Ardent Capital's post-closing IP management team conduct a comprehensive audit of the trademark renewal calendar during the integration process to ensure continuity of all registrations.
E. Third-Party Disputes
One opposition proceeding was identified in the trademark portfolio's history. In 2022, a third party filed an opposition before the EUIPO, alleging likelihood of confusion between one of Luminex's EU trademark registrations and the opposing party's mark registered in a different international class. The EUIPO Opposition Division rejected the opposition, finding no likelihood of confusion between the marks given the dissimilarity of the goods and services at issue. The decision has become final, and no appeal was filed by the opposing party. No other pending trademark disputes, oppositions, or cancellation proceedings were identified in any jurisdiction.
F. Coexistence and Consent Agreements
Two trademark coexistence agreements were identified in the data room:
(i) Medical Device Company Coexistence Agreement. A coexistence agreement between Luminex AG and a medical device company using a phonetically similar mark in International Class 10 (medical devices). Under the terms of the agreement, Luminex's use of its marks is limited to International Classes 9, 35, and 42 (software, business management, and technology services), while the medical device company's use is limited to Class 10. The agreement was entered into in 2017 and contains mutual commitments not to expand into each other's designated classes.
(ii) Lighting Products Company Coexistence Agreement. A coexistence agreement between Luminex AG and a lighting products company using a similar mark in International Class 11 (lighting and heating apparatus). There is no overlap between the parties' respective goods and services, and the agreement reflects a mutual acknowledgment of peaceful coexistence.
Neither coexistence agreement contains change of control restrictions, termination-upon-assignment provisions, or consent requirements that would be triggered by the Transaction. Accordingly, these agreements do not present obstacles to closing.
VI. Trade Secrets and Proprietary Know-How
A. Identification of Key Trade Secrets
Luminex's trade secret portfolio is a critical component of the company's overall intellectual property position. While the patent and trademark portfolios provide formal registered IP protection, a substantial portion of Luminex's competitive advantage derives from proprietary, unregistered know-how and trade secrets that are not (and, in many cases, cannot be effectively) protected through formal registration. The principal categories of trade secrets and proprietary know-how identified through our review include:
•  Proprietary Algorithms: The algorithms underlying the Luminex One platform's predictive supply-chain analytics engine represent a core competitive differentiator. These algorithms incorporate proprietary mathematical models, statistical techniques, and optimization methods that have been developed and refined over more than a decade of R&D investment. While certain aspects of the algorithmic functionality are protected by the patent portfolio's predictive analytics cluster, the underlying implementation details, parameter tuning methodologies, and proprietary enhancements go beyond the scope of the published patent claims and are maintained as trade secrets.
•  Training Data Sets and AI/ML Models: Luminex's AI/ML modules for procurement automation and supply-chain analytics have been trained on extensive data sets derived from anonymized and aggregated customer usage data ("Platform Data"). The trained models themselves, including their architectures, hyperparameters, and learned weights, constitute significant proprietary IP. The training data sets, data curation methodologies, and feature engineering techniques are similarly proprietary.
•  Customer Pricing Models and discounting Frameworks: Luminex's internal pricing models, discounting frameworks, competitive pricing intelligence, and deal-structuring methodologies represent commercially sensitive trade secrets.
•  Internal Product Roadmap Documentation: Luminex's multi-year product development roadmap, including planned features, technology investment priorities, and strategic product direction, constitutes confidential business information and trade secrets.
•  Source Code: The source code for the Luminex One platform is maintained in private repositories and has not been published or made publicly available. The source code embodies Luminex's proprietary implementation of the platform's core functionality and represents a significant trade secret asset.
B. Protection Measures
We reviewed the measures that Luminex has implemented to protect the secrecy of its trade secrets and proprietary know-how. The existence and adequacy of reasonable protection measures is a legal prerequisite for trade secret protection under the Defend Trade Secrets Act (18 U.S.C. § 1836), the Uniform Trade Secrets Act (as adopted in applicable U.S. states), the Swiss Unfair Competition Act (UWG), and comparable laws in other jurisdictions where Luminex operates.
Contractual Protections. All employees of the Luminex Group are required to execute proprietary information and inventions assignment agreements ("PIIAAs") at the time of hire. These agreements include confidentiality obligations covering trade secrets and proprietary information, as well as invention assignment provisions (discussed in Section XI below). Consultant and contractor agreements similarly include confidentiality and IP assignment provisions, subject to the gap noted in Section IV.E above with respect to certain legacy contractor agreements from the 2009–2014 period.
Technical Access Controls. Luminex maintains physical and logical access controls designed to limit access to trade secret information on a need-to-know basis. Source code repositories are subject to role-based access controls, with access limited to authorized engineering personnel. Multi-factor authentication ("MFA") is enforced for all access to source code repositories and other sensitive technical systems. Audit logging is maintained for access to source code and other sensitive IP assets, enabling retrospective review of access patterns if a suspected misappropriation or unauthorized disclosure occurs.
Source Code Escrow. Luminex's source code is not published or deposited in any publicly accessible repository. Two source code escrow agreements are in place with major enterprise customers, under which copies of the Luminex One source code are deposited with a third-party escrow agent. Release of the escrowed source code is triggered only upon the occurrence of specified events, including material breach of the applicable SaaS agreement by Luminex that remains uncured for 90 days, or the bankruptcy or insolvency of Luminex. These escrow arrangements are limited in scope and do not represent a general exposure of the source code to third parties. The escrow agreements are discussed in greater detail in Section IX.D below.
Trade Secret Register. We note that Luminex does not currently maintain a formal trade secret register or inventory — i.e., a systematic, documented catalog identifying specific trade secrets, their custodians, applicable protection measures, and access permissions. While the absence of such a register does not, by itself, undermine Luminex's trade secret protections (given the other measures in place), a formal trade secret identification and cataloging program is considered best practice and would strengthen Luminex's ability to assert trade secret claims in the event of misappropriation. We recommend that Ardent Capital implement such a program post-closing as part of the broader IP governance enhancement initiative.
C. Non-Compete and Non-Solicitation Agreements
Key engineering and R&D personnel within the Luminex Group are subject to post-termination non-compete and non-solicitation restrictions. The enforceability and scope of these restrictions vary by jurisdiction:
•  Switzerland: Post-termination non-compete covenants are enforceable under Swiss law (Art. 340–340c CO), subject to requirements of reasonableness with respect to geographic scope, duration, and subject matter, as well as the requirement that the restriction protect a legitimate business interest (e.g., access to trade secrets or customer relationships). Dr. Markus Vogt (CTO) is subject to a 12-month post-termination non-compete covenant governed by Swiss law. Annelise Gruber (CFO) is subject to an 18-month post-termination non-compete covenant, also governed by Swiss law.
•  Germany: Post-termination non-compete covenants are enforceable under German law, subject to the statutory requirements of Section 74 et seq. of the German Commercial Code (Handelsgesetzbuch, "HGB"), including the obligation to pay compensation during the non-compete period of at least 50% of the employee's last-received compensation. Based on our review, Veltronix GmbH's non-compete arrangements with key German employees appear to comply with the statutory requirements.
•  United States: The enforceability of post-termination non-compete covenants varies significantly by state. Non-compete covenants are generally enforceable in Virginia (where Luminex US's headquarters are located), subject to reasonableness limitations. However, non-compete covenants are generally unenforceable in California under California Business and Professions Code Section 16600, and Luminex US employs a number of remote employees in California. For California-based employees, reliance must be placed on confidentiality agreements, trade secret protections, and non-solicitation provisions (to the extent enforceable) rather than non-compete covenants.
•  Singapore: Post-termination non-compete covenants are enforceable in Singapore, subject to reasonableness analysis under Singapore common law (following the approach established in Man Financial (S) Pte Ltd v. Wong Bark Chuan David [2008] 1 SLR(R) 663). Luminex Singapore's employment agreements include non-compete provisions for key R&D personnel.
Post-closing employment agreements for Dr. Stefan Kessler (CEO) and Annelise Gruber (CFO) will contain updated restrictive covenants, including non-compete, non-solicitation, and confidentiality provisions, as negotiated in connection with the Transaction. The terms of these updated agreements are being addressed in the Employment & Benefits Due Diligence Summary Memorandum.
VII. Open-Source Software Usage
A. Overview.  The Luminex One platform incorporates a significant volume of open-source software ("OSS") components, as is typical for modern enterprise SaaS platforms. In Q4 2024, Luminex's internal engineering team conducted an OSS audit that identified approximately 1,200 distinct OSS components incorporated into the Luminex One platform's codebase and build environment. The results of this audit, including the associated software bill of materials ("SBOM"), were made available in the data room and were reviewed by our team.
It is important to note that the Q4 2024 OSS audit was performed by Luminex's internal engineering team using internal tooling and was not conducted by an independent third-party OSS audit firm. While the internal audit provides a useful baseline, it may not capture all OSS components present in the codebase — particularly components that may have been introduced through transitive dependencies, bundled libraries, or legacy code modules. Accordingly, we recommend that an independent third-party OSS audit firm be engaged to conduct a comprehensive binary-level scan of the Luminex One production build, as discussed further in our recommendations.
A summary of material OSS components organized by license type, component name, version, module in which incorporated, and risk rating is set forth in Appendix C to this memorandum.
B. License Categories Identified
The approximately 1,200 OSS components identified in the Q4 2024 audit fall into three broad license categories, each carrying a different level of compliance risk:
Permissive Licenses (approximately 78% of components — Low Risk). The majority of OSS components incorporated into the Luminex One platform are licensed under permissive open-source licenses, including the MIT License, the Apache License, Version 2.0, and the BSD License family (2-Clause and 3-Clause). Permissive licenses impose minimal obligations on licensees — typically limited to the retention of copyright notices and license text in redistributed copies. Permissive licenses do not impose "copyleft" obligations requiring the disclosure of source code for derivative works or combined works. These components present low compliance risk.
Weak Copyleft Licenses (approximately 15% of components — Moderate Risk). Approximately 15% of the identified OSS components are licensed under weak copyleft licenses, primarily the GNU Lesser General Public License, Version 2.1 ("LGPL 2.1") and the Mozilla Public License, Version 2.0 ("MPL 2.0"). Weak copyleft licenses require compliance with notice and source-availability obligations for modifications made to the licensed component itself, but do not generally propagate copyleft obligations to the larger proprietary work with which the component is combined, provided that the component is linked in a manner that preserves the modularity of the licensed component (e.g., dynamic linking rather than static linking). Based on our review of the Q4 2024 audit report and discussions with Luminex's VP of Engineering, LGPL-licensed components are dynamically linked in the current architecture. Dynamic linking is the generally accepted approach to avoid copyleft propagation to Luminex's proprietary code. However, it is important to confirm, through the recommended independent third-party audit, that no LGPL components have been statically linked, which could expand the scope of the copyleft obligations.
Strong Copyleft Licenses (approximately 7% of components — Higher Risk). Approximately 7% of the identified OSS components are licensed under strong copyleft licenses, including the GNU General Public License, Version 2 ("GPL v2"), the GNU General Public License, Version 3 ("GPL v3"), and the GNU Affero General Public License, Version 3 ("AGPL v3"). Strong copyleft licenses impose more extensive obligations that, depending on the nature and manner of use, may require the disclosure of source code for the larger work in which the copyleft-licensed component is incorporated. The analysis of these components is as follows:
•  GPL v2/v3 Components. GPL-licensed components identified in the audit are used in internal build tools and development environments (e.g., build system utilities, compiler toolchains, and development-time testing frameworks). These components are not distributed to Luminex's customers in a manner that would trigger the GPL's distribution-triggered copyleft obligations. Moreover, under Luminex's SaaS delivery model, the Luminex One platform is provided to customers as a hosted service rather than distributed as a software copy, and the GPL's copyleft obligations are triggered by "distribution" or "conveying" of copies, not by provision of a hosted service. Accordingly, the use of GPL v2/v3 components in the manner described does not appear to implicate the GPL's source code disclosure obligations. However, the interaction between GPL-licensed components and AGPL-licensed components in the build and deployment environment warrants careful review to ensure there is no unintended copyleft propagation.
•  AGPL v3 Components. Three components licensed under the AGPL v3 were identified in the audit. The AGPL differs from the standard GPL in a critical respect: Section 13 of the AGPL extends copyleft obligations to software that interacts with users over a computer network, even absent traditional "distribution." This provision was specifically designed to close the so-called "ASP loophole" and ensure that copyleft obligations apply to software provided as a service. If AGPL-licensed components are incorporated into or interact with the Luminex One platform code that is accessible to customers over the network, Luminex could face obligations to make the corresponding source code of the combined work available to those customers, which could implicate trade secret protections for Luminex's proprietary platform code.
Based on our review of the audit report and discussions with Luminex's engineering team, the three AGPL v3 components are used in non-customer-facing internal monitoring and observability tools that are separate from the Luminex One production codebase. If this characterization is accurate, and if the AGPL components are properly isolated from the customer-facing production codebase (i.e., there is no code sharing, dynamic linking, API integration, or process-level interaction between the AGPL components and the Luminex One platform), the AGPL copyleft obligations should not propagate to the proprietary Luminex One code.
However, verification of this isolation is critical. This verification should be conducted through a comprehensive binary-level scan by an independent third-party OSS audit firm, which can confirm at a technical level whether the AGPL components are present in or interact with the Luminex One production build artifacts that are served to customers.
C. Compliance Status and Risk Assessment
Luminex maintains an OSS policy document that establishes guidelines for the evaluation, approval, and use of open-source components within the Luminex One platform. The policy document was reviewed in the data room and covers topics including license categorization, approval workflows, and attribution requirements. Luminex also maintains an internal SBOM generated through automated tooling integrated into the development workflow.
Attribution Compliance. Attribution notices required by permissive licenses (including copyright notices and license text) are included in Luminex One's product documentation and in a dedicated open-source attribution file accessible through the platform's administrative interface. Based on our review, the attribution practices appear to be generally compliant with the requirements of the applicable permissive licenses.
LGPL Compliance. For LGPL-licensed components, Luminex uses dynamic linking, which is the generally accepted approach to maintaining separation between the LGPL-licensed component and the proprietary code and to avoiding copyleft propagation. As noted above, we recommend that the independent third-party OSS audit confirm that no LGPL components have been statically linked.
AGPL Risk Assessment. The three AGPL v3 components represent the highest-priority OSS compliance risk identified in this review. If these components are not properly isolated from the Luminex One production codebase, the AGPL's network interaction copyleft provision could require Luminex to make the corresponding source code of the combined work available to customers accessing the platform over the network. Such an obligation, if triggered, could directly conflict with Luminex's trade secret protections for its proprietary platform code and could materially impair the value of the proprietary IP. For this reason, verification of the isolation of AGPL components is critical and should be a priority item in the recommended independent third-party OSS audit.
Recommendations. We recommend the following actions with respect to OSS compliance:
1.  Independent Third-Party OSS Audit. Engage an independent third-party OSS audit firm to conduct a comprehensive binary-level scan of the Luminex One production build prior to or promptly after closing. The scope of the audit should include confirmation of (a) the completeness of the SBOM, (b) the absence of undisclosed strong copyleft components in the production codebase, (c) the isolation of the AGPL v3 components from the production codebase, and (d) the absence of static linking of LGPL components.
2.  Enhanced OSS Governance. Post-closing, implement an enhanced OSS governance framework, including (a) an OSS review committee with authority to approve or reject the introduction of new OSS components, (b) automated OSS scanning integrated into the CI/CD pipeline to detect and flag the introduction of components under restricted licenses, and (c) regular (at least quarterly) SBOM refresh and review processes.
D. Inbound OSS Contributions
Luminex contributes to several open-source projects, primarily in the Kubernetes ecosystem and Apache Software Foundation projects. Based on our review, these outbound contributions are limited to non-proprietary tooling, infrastructure utilities, and bug fixes, and do not expose any proprietary Luminex One platform code or proprietary algorithms. Contributor license agreements ("CLAs") are in place for all outbound contributions made by Luminex employees, ensuring that Luminex has the necessary rights to contribute code and that contributors have not inadvertently assigned proprietary rights to the open-source

MEMORANDUM

Record

Parties

Dates

Amounts