Anaconda, Inc. v. Intel Corporation is a copyright action filed on August 8, 2024 in the United States District Court for the District of Delaware. Anaconda alleges that Intel continued to use and distribute the Anaconda Distribution and associated conda packages after Intel’s paid licences lapsed.[1] Intel denies infringement.[2] The claims are pleaded in copyright, not in breach of contract.
Background
Anaconda describes conda as a free, open-source package and environment manager, and conda-compatible packages as versions of open-source software prepared to work with it. It says anyone can build conda packages and channels, but that it wrote and maintains more than 8,000 such packages. It alleges that the Anaconda Distribution, which bundles hundreds of the most popular ones, is protected by a registered copyright, “Anaconda Distribution and Associated Packages Release 2024.02-01”, No. TX 9-407-381.[1]
The complaint states that the Distribution is a free download subject to the Anaconda Terms of Service, and quotes the terms and pricing page as then worded: use on behalf of an organization of 200 or more employees or contractors requires a paid licence, and the pricing page said use at an organization of more than 200 employees requires a Business or Enterprise licence.[1] The current Terms of Service, dated July 15, 2025, say a Business Plan is required above 200 total employees or contractors, counting Affiliates.[3] The two wordings differ at exactly 200 people, a point that illustrates why the version in force at the time of use matters.
The dispute
Anaconda’s allegations
Anaconda alleges that Intel previously held licence agreements and paid for them, integrating Anaconda’s technology into its internal software and development platforms and into its AI Analytics Toolkit, distributed to customers. It alleges the licences expired, Intel did not renew, and Intel continued to use and distribute Anaconda’s conda packages without permission or payment.[1] It makes three factual claims. First, Intel allowed employees and internal tools to keep using the Distribution and packages after the licence ended. Second, Intel distributed the AI Analytics Toolkit with copied Anaconda packages and hosted a public repository of packages, some with the same digital signatures as Anaconda’s. Third, after being told of the alleged infringement, Intel copied the content from the Anaconda-hosted repository to an Intel-hosted one.[1] Anaconda says it sent Intel a letter on June 6, 2024 identifying evidence.[1]
The complaint pleads two counts: direct copyright infringement and secondary liability, contributory and vicarious, for the acts of users of the toolkit. It asks for a finding of willful infringement, a permanent injunction, actual or statutory damages, an accounting, impoundment, fees and a jury trial.[1] The pleading is a copyright claim, not a breach-of-contract claim, and relies on registered rights in the selection and arrangement of packages and in what Anaconda calls proprietary components.[1]
Intel’s response
Intel’s answer admits that Anaconda asserts the registration and that the registration certificate carries the stated title, but denies infringement. It says Anaconda built its business on open-source and freely available software, that users relied on Anaconda’s representation that certain offerings were “always free”, and that Anaconda sought a thirty-fold increase in Intel’s annual licence fee. It says Intel had bought licences for distribution and for repository access for employees who needed it, and that Anaconda disabled Intel’s channel on Anaconda.org.[2] Intel admits hosting a public repository on anaconda.org until access was disabled, and that afterwards it provided copies of permitted versions of its toolkit and download instructions, including for dependencies from conda-forge, on an Intel-hosted repository, while denying those contained protected Anaconda components used without permission.[2]
Intel’s eight defenses include that the claims are not ripe because Anaconda did not first use the dispute resolution process under the Intel Services Agreement, that Anaconda does not own valid protectable rights, that its use was under a valid licence including a licence to distribute permitted versions of the toolkit, and that equitable estoppel, acquiescence, waiver and abandonment bar claims over resources promoted as “always free”.[2] Intel also denies that the term “Anaconda Distribution” is clearly defined in the complaint.[2]
Decision or outcome
No judgment, order on the merits, settlement or dismissal appears in the court records retrieved. The complaint is Docket 1 and the answer is Docket 14, both obtained from the public RECAP archive.[1][2] The outcome is therefore recorded as pending, with the caveat that the case may have progressed since.
Significance for software licensing and SAM practice
The pleadings frame three questions that recur in Anaconda licensing. The first is where the paid boundary lies. Anaconda’s current FAQ says payment requirements do not apply to user-uploaded channels at anaconda.org such as conda-forge, but do apply to Anaconda-provided channels, and that Miniconda needs no licence until it is used to reach package updates from Anaconda repositories.[4] The second is the difference between internal use and redistribution: the current Terms require an Embedding licence for incorporating Anaconda content into a product offered to third parties.[3] The third is what happens when a licence ends: the Terms require the customer to stop using the Platform, destroy copies of the Offerings and, if asked, provide evidence such as a system scan report.[3]
Lessons learned
- Plan the end of a licence. Anaconda alleges that use continued after the licences lapsed.[1] Decide in writing which downloads, mirrors and copies must stop and what, if anything, remains licensed.
- Do not generalize “free”. Intel relies on statements that some resources were always free.[2] Anaconda’s own FAQ ties the free position to specific channels, so the channel and the document that governs it decide, not the product family name.[4]
- Separate distribution rights from internal-use rights. The complaint centres on the toolkit that Intel distributes to its customers; the Terms treat embedding in third-party products as needing its own licence.[1][3]
- Read the dispute clause. Intel argues the claims are not ripe because the services agreement’s dispute process was not followed.[2]