Covetrus, Inc. v. Actian Corp. was a lawsuit in the United States District Court for the District of Maine between Actian Corporation, publisher of the Data Integrator software, and its licensee Veterinary Data Services, Inc. (VDS), together with VDS’s parent company Covetrus, Inc. After an Actian audit and a demand for USD 13.5 million, VDS and Covetrus sued for a declaration that they had not breached the end user licence agreement (EULA) or infringed Actian’s copyright. Actian counterclaimed for breach of contract and copyright infringement.[2] The court’s rulings touch most of the issues that arise in a modern audit: parent and subsidiary liability, CPU versus core counting, cloud servers as “internal” networks, service-bureau restrictions and mandatory support. The parties reported a settlement in March 2026, shortly before a scheduled jury trial.[3]
Background
VDS, a Kentucky company, licensed Data Integrator in 2006 to map and migrate historical veterinary data into practice management systems for third-party veterinary clinics. It bought a perpetual licence for version 8 in 2006 and upgraded to version 9 in 2011. The version 9 EULA governed; Covetrus, a Maine corporation formed in 2019, was not a signatory. Actian’s predecessor Pervasive, named in the EULA, merged with Actian in 2013.[2]
A 2017 Actian audit request indicated that VDS had installed version 9 on five production engines, and Actian made no allegation of breach at that time. In December 2019 VDS bought another year of maintenance and post-obsolescence support for USD 5,199. A 2021 audit then showed version 9 installed on 21 computers with 12 users, against three licences purchased. Actian alleged that VDS should have bought commercial rather than non-commercial licences and demanded USD 13.5 million. VDS rejected the demand and, with Covetrus, filed suit on 2021-04-06.[2]
The dispute
Actian alleged three main breaches:[2]
- Service-bureau use. Section 6 of the EULA said the licensee “may not use, access, or allow access to the Software in any manner to provide service bureau, ASP, time-sharing, or other computer services to third parties without prior written approval”. Actian said VDS acted as an unauthorised “middleman” by migrating data for veterinary clinics. VDS said its own staff alone ran the software and customers never accessed it.
- Over-deployment. Section 1 allowed installation in a single location, or on a network server used to run the software over an internal network, with a licence “for each individual who will use the Software”. Actian counted 21 host computers against three licences, nine more users than licensed, installation on twelve Azure virtual machines outside VDS’s internal network, and 42 unlicensed cores, arguing that each CPU core needed a licence. The version 9 EULA referred to CPUs, not cores; later EULAs referred to both.
- Pricing. Actian argued damages should reflect commercial licences.
VDS also argued that the EULA terminated automatically on its first breach in 2006 or 2011, so Actian’s claims were limited to copyright and were time-barred, and that Actian had known of its use since training sessions in 2006 and support in 2009. Covetrus argued it was not a party to the EULA.[2]
Decision or outcome
Motion to dismiss (2022-01-20)
Judge Lance E. Walker denied the motion to dismiss Actian’s counterclaims. The EULA’s automatic termination on breach did not stop Actian from claiming contract damages measured by unpaid licence fees: the court found it “a doubtful proposition” that Texas law, which governed the EULA, would leave a software developer with no contract remedy for breach of a EULA. Actian was also given leave to amend its allegations against Covetrus. Those allegations included that Covetrus paid for the software, that Covetrus employees handled negotiations and VDS’s December 2020 self-audit response, and that Covetrus had described itself as VDS’s “successor-in-interest”. If Covetrus was “running the show” at VDS, the court held, it was plausible that Actian could recover from Covetrus as well as VDS.[1]
Summary judgment (2026-02-06)
Judge Stacey D. Neumann decided two contract questions as a matter of law and denied both sides’ motions for summary judgment on the rest.[2]
- Support policy not incorporated. The 2020 sales order referred to the “Actian corporation support policy” with a URL. That policy said perpetual licences require active, ongoing support. Applying Texas law, the court held that merely referencing a document does not incorporate it, and the EULA said it was the sole contract regardless of any purchase order. VDS’s decision to stop buying support after 2021 was therefore “not an actionable breach of contract”.
- Survival clause. The EULA terminated automatically on breach, but listed sections that “will survive any termination”, including the copyright restrictions and the third-party use clause. Those sections continued to apply, so Actian could seek damages under them.
- Service-bureau clause ambiguous. Reading “use” as only direct third-party access would make the words “access” and “allow access” redundant, so the court rejected VDS’s reading. But “other computer services” was undefined, both readings were reasonable, and the jury would have to decide whether VDS’s data migration services were covered.
- Facts for trial. Whether “CPUs” and “cores” were treated as synonymous when the contract was made, which decided whether installation on 112 cores breached a three-CPU licence; whether Azure and Covetrus.net servers were part of an “internal” network; when Actian had enough information to investigate; whether VDS concealed its deployment in the 2017 audit; whether version 9 had enough original content for a valid copyright registration; and whether Covetrus was VDS’s alter ego.
Settlement
The court set jury selection for 2026-06-01 and trial for 2026-06-22. After a settlement conference on 2026-03-12, the docket records a “Notice of Settlement and Procedural Order Re: Settlement” on 2026-03-27.[3] No terms are public.
Significance for software licensing and SAM practice
The case ran from April 2021 to March 2026, and set a USD 13.5 million demand against a 2020 support order of USD 5,199.[2][3] The rulings are trial-court decisions on one EULA, but several themes recur in audits:
- Group structure. An audit of one subsidiary can widen to the parent when the parent pays, negotiates and answers audit requests.[1]
- Legacy metrics. A per-CPU licence written before multi-core processors and public cloud invites a dispute over cores and virtual machines.[2] See processor and core licensing.
- Internal use and service restrictions. Using licensed software to deliver services to clients can fall within service-bureau wording even where clients never see the software.[2]
- Support terms. Whether support is mandatory for a perpetual licence depends on what the signed documents incorporate, not on a policy published on the vendor’s website.[2] See software maintenance and support.
Lessons learned
- A parent company that runs a subsidiary’s licensing and audit responses can be drawn into the subsidiary’s licence dispute. The court allowed Actian’s claims against Covetrus to proceed on allegations that Covetrus paid for, negotiated and handled the audit of the software.[1]
- Old EULAs that count “CPUs” create disputes once multi-core and cloud machines are in use; map each metric to today’s hardware. Whether 112 cores breached a three-CPU licence depended on what the terms meant when the contract was made.[2]
- Service-bureau and third-party-use clauses can reach services delivered with the software, even if customers never touch it. The court rejected the argument that “use” required direct third-party access and left the scope of “other computer services” to a jury.[2]
- A support policy only linked from a sales order may not bind the customer; check what each order actually incorporates. The court held the linked policy was not part of the contract.[2]
- An earlier audit that found excess installs without complaint does not settle the question; it becomes evidence for both sides. VDS relied on the 2017 audit as notice to Actian, while Actian alleged VDS had concealed its deployment in that audit.[2]