Overview
Anaconda maintains two package repositories that serve different audiences. Understanding the distinction helps you configure your organization's channels correctly and ensures your users are pulling from the right source.
Premium versus Public
| Premium Repository | Public Repository | |
|---|---|---|
| URL | repo.anaconda.cloud | repo.anaconda.com |
| Access | Requires an active Anaconda subscription and organization token | Publicly accessible without authentication |
| Packages | The same core packages (main, r, msys2) as the Public repository, plus additional authenticated channels. Delivered with added CVE metadata, cryptographic package signatures, and SBOMs. | The same standard Anaconda Distribution packages, without the added security metadata, signatures, or SBOMs. |
| Security data | Full CVE scoring, status tracking, and policy filtering available | No CVE or policy filtering |
| Uptime SLA | Contractual uptime SLA (99.7%, or 99.9% for managed hosting) with service credits for paid subscribers | No uptime SLA |
| Use case | Production and enterprise environments where security and governance matter | Personal use, evaluation, and open exploration |
Note: Neither repository offers a package-build-time SLA; the SLA above covers service/repository uptime only.
Using the Premium Repository in your organization
When you create a Virtual or External channel in Anaconda Platform Cloud, the platform connects to the Premium Repository by default. Your organization's users access packages through the channel URLs provided in the platform, authenticated via their organization credentials.
To find your organization's repository endpoint:
1. Navigate to Organization Settings.
2. Select the Repository tab.
3. Copy the Repository URL and token for use in conda configuration.
Configuring conda to use the Premium Repository
To point conda to your organization's private channels, add the channel URL to your .condarc file or provide it directly in the conda install command.
Note: Your administrator can distribute a pre-configured .condarc file to all users via your organization's onboarding process, eliminating the need for manual configuration on each machine.