The practical licensing question for most organizations using Python data tooling is not about conda the program but about what it downloads. Anaconda, Inc. distinguishes between its own installers and repositories, which fall under its Terms of Service, and open-source tools and community channels it does not charge for. The distinctions below are those Anaconda states in its legal FAQ, the Miniconda licence and its documentation.[1]
Editions: the installers
Anaconda publishes two installers. Anaconda Distribution installs conda, Python, Anaconda Navigator and hundreds of packages into a pre-built base environment; the documentation lists more than 600 packages and an install size of about 9.7 GB. Miniconda installs only conda, Python and their dependencies, with more than 130 packages and about 900 MB. Both are created and published by Anaconda and give access to the same package repositories.[7]
| Installer | Licence document | Commercial licence position stated by Anaconda |
|---|---|---|
| Anaconda Distribution | Terms of Service | The Distribution installer is separate software from conda and requires a commercial licence for organizations over 200 employees or contractors[1] |
| Miniconda | Miniconda End User License Agreement | No commercial licence for the installation itself; one is required once Miniconda is used to gain access to package updates from Anaconda repositories[1][2] |
| Miniforge, Mambaforge | Not provided by Anaconda | No commercial licence; configured by default to use conda-forge[1] |
| conda (the package manager) | Open source | The program itself needs no licence[1] |
Catalog rules: Miniconda is free to install but not to use for Anaconda repository access above the threshold, Miniforge and Mambaforge are not provided by Anaconda and The conda tool needs no licence but the Anaconda Distribution installer does.
The Miniconda licence
The Miniconda End User License Agreement is a short redistribution licence with four conditions: source redistributions keep the copyright notice and disclaimer, binary redistributions reproduce them, the Anaconda or Miniconda name may not be used to endorse products without permission, and Miniconda may not be used to access or allow third parties to access Anaconda package repositories if that would circumvent paid licensing requirements or is otherwise restricted by the Terms of Service.[2] The Terms of Service say the same in their own words: use of Miniconda is under its separate terms, but to the extent it is used to access the Platform or Offerings the Terms apply, including the payment requirements.[3] Anaconda notes that Miniconda points to its repository by default and that, from July 15, 2025, users of the newest release are prompted to accept the Terms of Service on the command line before accessing Anaconda repositories.[1]
Channels: what the payment requirement attaches to
The licence gate is the channel. A conda client reads its channel list from configuration. The special name defaults stands for the channels Anaconda ships in Anaconda Distribution and Miniconda: main, msys2 and r at repo.anaconda.com, unless default_channels is set. The documentation marks the r channel as past end of support from November 2025 and msys2 from September 2026, and says use of these channels is subject to the Terms of Service.[6] The command-line plugin documentation says that to use Anaconda’s default channels to install and update packages, the Terms of Service must be accepted.[5] Catalog rules: The defaults channel points to the main, r and msys2 channels on repo.anaconda.com and Using the default channels requires accepting the Terms of Service through the conda plugin.
Channels hosted on anaconda.org are split. The Anaconda.org Offering Description says the licensing restrictions and payment requirements apply only to Anaconda-maintained channels and packages, such as the main channel, and not to community-provided or third-party channels.[4] The legal FAQ answers directly that payment requirements do not apply to the user-uploaded packages and channels at anaconda.org, which includes conda-forge, because Anaconda does not build those packages and hosts them as a free service; the Terms of Service still apply to hosted third-party content, so users must not upload prohibited content.[1] Catalog rule: conda-forge and other community channels on anaconda.org carry no payment requirement.
| Channel or source | Anaconda’s position |
|---|---|
| repo.anaconda.com main, r, msys2 (defaults) | Subject to the Terms of Service; paid above the threshold[6][1] |
| Anaconda-maintained channels on anaconda.org (for example main) | Licensing and payment requirements apply[4] |
| conda-forge and user-uploaded channels on anaconda.org | No payment requirement[1] |
| Anaconda.org public packages | Free for downloading and uploading public packages; accounts are personal and free by default[8] |
Dates that matter for older installs
Anaconda’s FAQ states that its terms changed to a commercial model on April 30, 2020. Packages downloaded from the repository before that date need no commercial licence for continued use, but updates to them do for organizations not eligible for free use. All versions of the Distribution installer downloaded before March 31, 2024 need no commercial licence, although continued package updates and pulls from the current repository into the installer do.[1] Catalog rule: Installers downloaded before 31 March 2024 are free, but package updates are not. The consequence for an inventory is that the age of an installer does not decide the position; the question is which repository the client updates from and who is using it.
Counting for a conda estate
The Terms count Users, not installs. An identified User, one with a registered Anaconda account or user identification, is counted once regardless of devices. An unidentified User is counted for each instance of download or use.[1][3] Non-human clients such as CI/CD jobs and service accounts are Users.[3] The plugin gives CI environments three ways to accept the Terms automatically: a .condarc setting, a conda configuration command, or an environment variable. The documentation shows the variable being passed to Docker containers because the CI variable is not inherited by manually invoked Docker commands.[5] The documentation also states that an enterprise licence agreement supersedes terms shown to licensed users through the plugin.[5]
For organization-wide visibility, Anaconda describes bulk registration, in which an organization token is distributed in an org_token file in the system conda directory so that conda clients identify themselves as belonging to the organization, and says registration helps align use with licence agreements.[9] Its recommended companion condarc setting keeps telemetry enabled so that the token continues to be sent.[9] The plugin was added to Anaconda Distribution 2025.06-0 and Miniconda 25.1-1-0.[5]
Virtualization and cloud
No rule ties the Anaconda licence to virtual machines, containers or cloud instances as such. Containers, CI runners and serverless jobs matter because they are Users or because of the scaled enterprise deployment restriction in the Terms of Service.[3]
Out of scope
This article does not state the licences of the packages inside the channels (BSD, MIT, GPL and others), which remain with their authors. It does not cover conda-forge’s own terms, the Anaconda Platform plans and tokens, the academic and non-profit programs, or the Anaconda v. Intel dispute, in which Anaconda alleged unlicensed use of its conda packages. See Anaconda v. Intel.