---
title: "Hugging Face Registry for Models and Datasets | Cloudsmith"
description: "Store, proxy, and govern Hugging Face models and datasets in Cloudsmith. Use the Hugging Face SDK and CLI with policy control alongside 30+ formats."
canonical_url: "https://cloudsmith.com/product/formats/hugging-face"
last_updated: "2026-11-15T12:01:49Z"
---
# Hugging Face Registry for Models and Datasets | Cloudsmith

## Govern **Hugging Face** models and datasets with confidence

Teams pull models and datasets straight from Hugging Face Hub, and your AI supply chain grows with every download. Cloudsmith gives you a private, fully compatible registry that proxies, caches, and governs those artifacts next to your packages and containers.

## Why teams choose Cloudsmith for **Hugging Face**

AI adoption moves fast, and your teams drive it. Cloudsmith gives security a control point and gives developers the models they need without the wait.

[Book a demo with one of our experts](/book-a-demo)

| Without Cloudsmith | With Cloudsmith |

| --- | --- |

| Developers pull models straight from the public Hub, which skips scanning, policy checks, and audit trails. | Cloudsmith proxies and caches Hugging Face Hub, so pulls flow through your registry. Policies apply before a model reaches any workflow. |

| Nobody can say which model version runs in production, where it came from, or what depends on it. | Every commit becomes an immutable, versioned package. You can show which model is deployed, where it came from, and reproduce any build. |

| Models live in a separate system from the rest of your supply chain, which leaves policy gaps and audit blind spots. | Models and datasets sit with your containers and language packages, under the same access controls, policies, and audit logging. |

| Pickle and PyTorch checkpoints carry known serialization risks, and nothing stops unsafe model file formats entering your pipeline. | Write OPA Rego policies to quarantine or block risky file formats before they reach developers. |

| Open-weight models carry custom license terms, and those terms go unchecked when models are pulled directly. | Cloudsmith exposes license metadata to policy rules, so only approved licenses get through. |

Universal format support

## **One registry for models, datasets, and packages.** Cloudsmith is the governed store for every AI artifact and software package you use.

- Use Hugging Face + 30 other formats
- Push, pull, and version models and datasets with the Hugging Face SDK and CLI
- Proxy and cache models from Hugging Face Hub with your policies applied

## How we support **Hugging Face**

Cloudsmith is fully compatible with Hugging Face tooling, so your teams keep their workflow while you gain control over what they pull.

[Read our Hugging Face documentation](https://docs.cloudsmith.com/formats/hugging-face-repository)

### Compatible with Hugging Face tooling

Use the huggingface_hub library and the Hugging Face CLI against Cloudsmith. Set HF_ENDPOINT to your repository and your existing commands keep working.

### Upstream proxy and caching

Configure a Cloudsmith repository as an upstream for Hugging Face Hub. Pulls flow through your registry, which caches artifacts and applies your policies first.

### Versioning by commit

Each Hugging Face repository becomes a package and each commit an immutable version. Tags resolve to the right commit, so every build is reproducible.

### Policy on model metadata

Write OPA Rego policies against model card metadata such as license, file formats, and training data provenance. Block risky models before they reach developers.

### Storage deduplication

Identical files are stored once, even across repositories in the same workspace. Large model weights and datasets cost less to keep.

## Get started with **Hugging Face** on Cloudsmith

[Book a demo](/book-a-demo)

[View pricing](/pricing)

## Frequently asked questions

### Is Cloudsmith compatible with the Hugging Face SDK and CLI?

Yes. Cloudsmith works with the huggingface_hub Python library and the Hugging Face CLI. Set HF_ENDPOINT to your Cloudsmith repository URL and HF_TOKEN to your Cloudsmith API token, and your push, pull, and download commands work as they do against the Hub.

[Read the Hugging Face docs](https://docs.cloudsmith.com/formats/hugging-face-repository)

### What Hugging Face artifacts does Cloudsmith support?

Cloudsmith supports Hugging Face model repositories and dataset repositories, including weights, configs, tokenizer files, and model cards. Hugging Face Spaces are not currently supported.

[See supported formats](https://docs.cloudsmith.com/formats)

### Is Cloudsmith limited to Hugging Face?

No. Cloudsmith's ML Model Registry integrates with the Hugging Face SDK and CLI and stores other model files, including PyTorch, TensorFlow, and ONNX, in the same repositories as your packages and containers.

### Can Cloudsmith proxy and cache models from Hugging Face Hub?

Yes. Configure a Cloudsmith repository as an upstream for the public Hub. Pull requests flow through your registry, which caches artifacts and lets you apply policies before a model reaches a developer or production.

[Read the upstream proxying docs](https://docs.cloudsmith.com/repositories/upstreams)

### How does Cloudsmith handle model versioning?

A Hugging Face repository becomes a Cloudsmith package, and each commit becomes a distinct, immutable version identified by its commit hash. Tags such as main or v1.0 resolve to the correct commit.

[Read the Hugging Face docs](https://docs.cloudsmith.com/formats/hugging-face-repository)

### How can I enforce policies on Hugging Face models?

Write OPA Rego policies in Cloudsmith's Enterprise Policy Manager. Cloudsmith parses model card metadata and exposes license type, training data provenance, and file formats to your rules, so you can block risky formats like Pickle.

### Does Cloudsmith deduplicate model and dataset storage?

Yes. Hugging Face repositories use native file storage deduplication. If the same files are uploaded more than once, even across repositories in a workspace, Cloudsmith stores a single copy.

### How do I authenticate to the Hugging Face registry?

Set HF_TOKEN to your Cloudsmith API token before running huggingface_hub or hf commands. Cloudsmith also supports entitlement tokens for distributing models downstream, and OIDC for CI/CD such as GitHub Actions and Jenkins.

### Can I store Hugging Face models alongside other formats?

Yes. Cloudsmith supports 30+ formats in one platform, so models and datasets sit beside Docker images, Python packages, npm packages, Helm charts, and Maven artifacts under the same access controls and audit logging.

[Read the upstream proxying docs](https://docs.cloudsmith.com/repositories/upstreams)

### Can I migrate existing models into Cloudsmith?

Yes. Upload with the huggingface_hub upload_folder function or the hf upload command, with HF_ENDPOINT pointed at Cloudsmith. If you source models from the public Hub, an upstream proxy caches them as they are pulled, so no bulk migration is needed.

### Does Cloudsmith work with CI/CD pipelines that use Hugging Face models?

Yes. Set HF_ENDPOINT and HF_TOKEN in your pipeline environment and existing model download steps resolve through Cloudsmith, with caching, policy enforcement, and audit logging and no pipeline code changes.
