Background
Actian sells Actian Zen, a database-management system formerly known as Pervasive PSQL. Itron makes technology used by energy and water utilities, and its products allegedly depend on Actian’s software. Different versions of the software are governed by different end-user license agreements. Some licenses permit only narrow single-user or single-server uses, while more expensive licenses allow broader deployment and access by many users.
Actian alleged that communications about additional licenses revealed that Itron had used, copied, and distributed the software beyond what it purchased. According to the amended complaint, Itron included Actian’s software in products installed on customers’ systems, made unauthorized copies during upgrades, exceeded limits on commercial deployment and concurrent users, and refused a requested license audit.
An earlier complaint was dismissed with leave to amend because it did not identify the relevant agreements and alleged distribution clearly enough. Actian returned with all 21 asserted agreements and more detailed allegations. Itron again moved to dismiss the contract claim and the direct, contributory, and vicarious copyright claims.
The Court’s Holding
Judge Beth Labson Freeman denied the motion in full. The amended complaint adequately identified the contracts and the provisions allegedly breached. At the pleading stage, Actian did not need to map every wrongful act to every version of the agreement with precision. It was enough to attach the asserted agreements, identify material terms, and plausibly allege at least one breach of each. Actian’s commercial-deployment and audit theories cleared that threshold even though its concurrent-user theory may ultimately depend on which license applied.
The direct copyright claim also survived. Actian alleged more than the distribution of license keys: it alleged that Itron distributed products containing the software for installation on customer-owned systems. It separately alleged unauthorized reproduction when Itron upgraded customer systems. Disputes over whether certain agreements permitted a reasonable number of copies, or whether “Client Software” differed from the protected software, required factual development and could not be resolved on a motion to dismiss.
The court likewise allowed the secondary-liability claims to proceed. Actian plausibly treated Itron’s users and licensees as third parties whose conduct could support contributory infringement. Whether Actian acquiesced by not validating Itron’s use was a factual question. For vicarious infringement, the complaint alleged that Actian’s software provided secure, reliable utility data and operational efficiency, supporting a reasonable inference that the software helped draw customers to Itron’s products.
The ruling decides only whether the allegations are sufficient, not whether infringement occurred. The parties also agreed that only Version 15 was federally registered, limiting potential statutory damages and attorneys’ fees to that version.
Key Takeaways
- A software licensor can plead across multiple license versions by identifying the agreements, the material restrictions, and at least one plausible breach for each.
- Embedding licensed software in a product delivered to customers can support a distribution theory distinct from merely supplying license keys.
- Contract permission and copyright liability may turn on fact-sensitive questions about the applicable license, the kind of software copied, and whether limits are conditions of the copyright license.
- Software that supplies important functionality to a defendant’s product may satisfy the customer-draw element of vicarious infringement at the pleading stage.
Why It Matters
The decision illustrates how an ordinary software-audit dispute can become a copyright case. Vendors should draft license scopes and audit rights clearly, preserve version-specific agreements, and plead exactly how deployment exceeded permission. Customers that integrate third-party code into products should track not only the number of licenses purchased but also copying, installation, distribution, server, and concurrent-user restrictions.
The case also shows the practical importance of amendment. Actian cured an initially deficient complaint by supplying the agreements and concrete deployment allegations. That was enough to move the dispute from pleading rules into discovery, where the parties will have to determine what software was installed, under which agreement, and on what systems.
Your browser cannot display this PDF inline.