Formats/Conda

Secure, managed Conda repositories for data science and engineering teams

Cloudsmith gives you a fully managed Conda repository that works with native tooling, proxies public channels, enforces governance policies, and delivers packages globally at low latency.

Universal format support

Conda is one of 30+ formats Cloudsmith manages in a single, secure platform.

  • Use Conda + 30 other formats in one place
  • Store scientific Python, R, and compiled packages alongside containers and raw assets
  • Centralise Conda channels and OSS upstreams under a single managed platform

How we support Conda

Cloudsmith gives you a fully managed Conda repository that works with native tooling, scales with your team, and gives you control over what packages reach your pipelines.
    Full Conda repository support
    Push, pull, and manage Conda packages using native conda tooling. Cloudsmith exposes a fully compliant channel endpoint, so your existing workflows need no changes.
    Upstream proxying and caching
    Proxy and cache from any remote Conda channel, including conda-forge and Bioconda. Teams get fast, reliable package resolution without direct dependence on public registries.
    Governance policies
    Create and enforce rules governing which Conda packages are permitted in your repositories. Block specific versions, require specific metadata fields, or quarantine packages that do not meet your criteria before any team member installs them.
    Flexible authentication
    Secure every channel with entitlement token auth or HTTP Basic Auth. Manage access per repository, per team, and per service account without changing how developers interact with conda.
    Global CDN delivery
    Packages are served from 600+ edge points of presence worldwide. Data science and ML teams across distributed offices resolve and install Conda packages at low latency regardless of location.

Why teams choose Cloudsmith for Conda

Self-hosted registries and public channels leave data science and engineering teams exposed to slow resolution, broken environments, and no control over what packages reach production. Cloudsmith changes that.
Without CloudsmithTeams pull directly from public channels like conda-forge with no caching, causing slow solves and brittle CI pipelines when upstream registries are slow or unavailable.
With CloudsmithCloudsmith proxies and caches upstream Conda channels, so package resolution is fast and builds stay reliable even when public registries have outages.
Without CloudsmithThere is no way to control which Conda packages or versions are permitted across the organisation. Any engineer can install any package from any public channel.
With CloudsmithGovernance policies let you block prohibited package versions, require specific metadata, and quarantine non-compliant packages before they reach any developer environment.
Without CloudsmithPrivate internal Conda packages are shared ad-hoc via file shares or custom scripts, with no audit trail and no consistent access control for geographically distributed teams.
With CloudsmithCloudsmith gives every team a private, authenticated Conda channel with full audit logs, entitlement-based access control, and global CDN delivery so all locations get the same experience.

Signs you're ready to switch to Cloudsmith for Conda

If Conda environment management is creating friction for your teams, it is often the underlying infrastructure that is the problem. Cloudsmith removes the operational burden so you can focus on building.
    Slow environment solves blocking CI
    Direct pulls from conda-forge or Anaconda default channels are slow and unpredictable. Cloudsmith's caching layer gives you consistent, fast resolution every time.
    No control over approved packages
    Without a private channel with policy controls, anyone on the team can pull any version of any package. Cloudsmith lets you define and enforce exactly what is permitted.
    Fragile self-hosted infrastructure
    Running your own Conda mirror means managing servers, availability, and patching. Cloudsmith is fully managed so your team gets a reliable registry without the operational overhead.
    Conda packages siloed from the rest of your stack
    Data science teams use Conda while engineering teams use Docker, Python, and more. Cloudsmith hosts all formats in one place, giving every team a single source of truth.
    No visibility into package consumption
    Without audit logs and download analytics, you have no way to know what packages your teams are consuming or where issues are coming from. Cloudsmith gives you full observability across every Conda pull.

Get started with Conda on Cloudsmith

Frequently asked questions

  1. Yes. Cloudsmith exposes a fully compliant Conda channel endpoint, so you use the standard conda CLI to install, upload, and manage packages with no changes to your existing workflows.

  2. Cloudsmith supports entitlement token authentication and HTTP Basic Authentication for Conda channels. You can configure credentials in your .condarc file or directly in your environment.yml.

  3. Yes. Cloudsmith supports upstream proxying and caching for Conda channels, including conda-forge, Bioconda, and the Anaconda default channel. Packages are cached on first pull, so subsequent installs are fast and resilient to upstream outages.

  4. Yes. You can create public repositories for open-source packages and private repositories for internal packages. Access control, entitlement tokens, and team-level permissions are applied per repository.

  5. You can create and enforce rules that govern which Conda packages and versions are permitted in your repositories. Policies can block specific versions, require metadata fields to be present, or automatically quarantine packages that do not meet your criteria before any team member can install them.

  6. Yes. Cloudsmith supports 30+ formats in a single platform, so your Conda packages, Docker images, Python packages, and raw assets all live in the same place with unified access control and audit logging.

  7. Cloudsmith supports Conda repodata patching, allowing you to update package metadata when dependencies change and backwards compatibility is broken. This helps keep environment solves accurate without requiring you to republish packages.

  8. Yes. Cloudsmith is a fully managed, cloud-native platform backed by a global CDN with 600+ edge points of presence. Your Conda channels are available to teams worldwide with low-latency package resolution and no infrastructure to manage.

  9. Yes. You can upload existing Conda packages via the Cloudsmith CLI, API, or web app, then reconfigure your .condarc or environment.yml files to point to your new Cloudsmith channel. The transition is straightforward and does not require changes to how developers use conda.

  10. Yes. Cloudsmith provides full client and audit logs for every upload and download event, along with package analytics. You can see exactly which Conda packages teams are consuming, when, and from where.

Formats

There’s more than just Conda on Cloudsmith