With Pro 3.1, can I avoid Anaconda license fees by using conda-forge?

[KirkKuykendall3]

Hi Community -

Using Pro 3.1, I would like to be able to clone my python environment and install a package from conda-forge.

Google AI says:

The conda package manager itself is free and open-source, but some distribution channels, like the official "defaults" channel on Anaconda, have terms of service requiring payment for commercial use by larger organizations. Conda-forge is a way to get software without these costs.

Esri support says   : 
Esri customers current on maintenance or who have an active subscription will continue to be able to use Anaconda packages deployed through Esri Software at no additional cost ... Beginning with ArcGIS Pro 3.4, information is added to identify that requests to Anaconda repos are coming from ArcGIS Pro to help Esri customers comply with Anaconda’s licensing terms..

Can someone please confirm that those on 3.1 won't incur costs by installing packages from conda-forge?

Thanks,

Kirk

[Sean_Perks · Accepted solution]

Using conda-forge is free and you wont have any issues with incurring costs if you stick with installs like 'conda install -c conda-forge <package_name>'. I had the same question because I work for a larger organization that has to pay for Anaconda if we use the default channel. I found this blog from Anaconda's website helpful  https://www.anaconda.com/blog/is-conda-free

Here is a little snippet

The default Channel

Anaconda, where conda was first created, generates revenue by charging for access to specific channels containing packages that are curated, built, maintained, and served by Anaconda’s engineers on its secure cloud infrastructure. Anaconda’s default channel is one of these. The default channel emphasizes security and stability.

Most channels, including conda-forge and Bioconda, are run by volunteer communities and offer best effort security; they are not recommended for use in sensitive environments. This can work well for research projects, prototypes, and education. In these scenarios, you probably aren’t working with sensitive data such as personally identifiable or financial information, or in a regulated industry. Getting hacked is still a huge pain, but you are unlikely to go bankrupt, get sued for a data breach, or cause traffic lights to stop working. Anaconda’s default channel uses a secure open-source software supply chain, thus helping prevent security breaches that community processes can be vulnerable to.

F : Ah, so Anaconda generates revenue by selling access to default for those who need more security and stability than community channels can provide?

D : Yes, and part of that revenue is funneled back into the conda ecosystem to pay Anaconda engineers to maintain default, work on conda, support anaconda.org (where conda-forge, Bioconda, and many other community channels are hosted), and support many other open source communities as well.

[KirkKuykendall3]

Thanks for the fast response!

When I clone arcgispro-py3 environment, conda pulls packages down from the default channel.  If I'm using Pro 3.1 this would incur costs.

If I set up Anaconda for offline use following these steps in the documentation , will I be able to clone arcgispro-py3 the same way I was before, but without incuring costs? 

Would I then be able to add a conda-forge package to that cloned environment?

[JoshuaBixby]

Esri will fully retire ArcGIS Pro 3.1.x in 6 months (April, 2026).  If you upgrade to a recent version now, these questions/issues are moot.

[Sean_Perks]

It might be worth reaching out to an Anaconda rep to be 100% sure.

I might not see your specific issue with 3.1, but as I understand it, and what we've been told is that any package that you get from cloning pro or downloading it from the Python package manager within ArcGIS Pro is included in the ArcGIS Pro license and is not subject to any additional costs from Anaconda regardless of what channel they come from (because it is covered in the Pro license). If that was not the case you'd have to pay for both an ArcGIS Pro and Anaconda license separately. The issue would be cloning a pro environment then installing packages outside of the package manager within pro that come from the default Anaconda channel. 

You can also run 

conda list

in the Python Command Prompt to see what packages are installed and from where. When I run conda list on a freshly cloned environment I don't see any packages from the default channel. I'm running ArcGIS Pro 3.3.6 though so might be different for 3.1.