Unreported / Non-Citable
Background
Actian Corporation licenses Actian Zen, formerly Pervasive PSQL, database software through end-user license agreements covering versions 8 through 15. It alleged that utility-technology company Itron used, copied, and distributed the software beyond its licenses, refused an audit, and would not obtain additional licenses or compensate Actian.
The court previously dismissed Actian’s original complaint. It gave leave to amend the contract claim because one agreement used as an example did not give fair notice of alleged breaches across the many agreements. It also gave leave to amend the direct and secondary copyright claims because the alleged distribution lacked supporting facts. A negligence claim was dismissed with prejudice under the economic-loss rule. Actian’s first amended complaint attached the relevant agreements and asserted breach of contract, direct copyright infringement, contributory infringement, and vicarious infringement. Itron again moved to dismiss under Rule 12(b)(6).
The Court’s Holding
Judge Beth Labson Freeman denied the motion in full. The amended complaint adequately alleged the contracts by attaching all 21 end-user agreements and identifying the provisions supposedly breached. Actian did not need at the pleading stage to describe every agreement’s terms with precision or tie every alleged act separately to every agreement. Although the agreements differed, Actian needed to plausibly allege only one breach of each, not all three theories it advanced.
The court found adequate allegations for two contract theories. Actian alleged commercial, revenue-generating use beyond internal business purposes because Itron products relied on the software and more than 500 companies used one identified system. It also alleged a breach of audit provisions by asserting that Actian performed through providing the software and Itron refused an audit. The concurrent-user allegations were sparse, but that did not defeat the claim because other breach theories were sufficiently pleaded.
The copyright counts also survived. The amended complaint alleged that Itron distributed meter-reading software incorporating Actian’s software to customer-owned servers and reproduced it during upgrades. It plausibly treated restrictions on a single server and distribution as conditions of the licenses, so exceeding them could support infringement rather than only contract liability.
For contributory infringement, references to users and licensees reasonably identified third parties, and disputes about Itron’s knowledge or Actian’s acquiescence were factual matters unsuitable for dismissal. For vicarious infringement, allegations that Actian’s software was essential to Itron’s products, delivered operational value, and supported secure and reliable data permitted an inference that customers sought Itron’s products because of the embedded software. Itron was ordered to answer by October 29, 2026.
Key Takeaways
- Attaching the relevant licenses and identifying the allegedly breached provisions cured the earlier fair-notice problem.
- A contract count can proceed when at least one breach theory is plausible for each agreement, even if another theory is thin.
- Embedding licensed software in products installed on customer servers plausibly alleged distribution and reproduction.
- Knowledge, acquiescence, and license scope remained factual questions; the court did not decide that infringement or breach actually occurred.
- The order denied dismissal of all four amended claims and set a specific answer deadline of October 29, 2026.
Why It Matters
Software licensors drafting or enforcing enterprise agreements can use the order as a practical pleading guide: identify each operative license, the provisions at issue, how deployment exceeded permission, and the role of downstream users. Detailed product-architecture allegations may support direct and secondary copyright theories at the same time.
Defendants should read the posture carefully. The ruling accepts well-pleaded allegations as true and draws reasonable inferences for Actian; it does not establish ownership, breach, copying, knowledge, or financial benefit. Those issues remain for discovery and later adjudication.