Manage Model Entities for Customization
Before running a customization job, you need to set up a Model Entity that points to your base model checkpoint. This section covers creating the required FileSet and Model Entity.
Task Guides
Create a FileSet containing your base model checkpoint from HuggingFace, NGC, or local storage.
Create a Model Entity that references your FileSet and enables customization.
Key Concepts
What is a FileSet?
A FileSet is a collection of files managed by the platform. For customization, you create a FileSet containing:
- Model weights (
.safetensors,.bin, or.nemofiles) - Model configuration (
config.json) - Tokenizer files (
tokenizer.json,tokenizer_config.json, and so on)
FileSets can be populated from:
- HuggingFace Hub - Download directly from HF repositories
- NGC - Download from NVIDIA NGC catalogs
- Local upload - Upload files from your local machine
What is a Model Entity?
A Model Entity is the platform’s representation of a model. It contains:
- FileSet reference - Points to where the model files are stored
- Model Spec - Auto-populated metadata about the model architecture
- Adapters - LoRA or other adapters attached to this model (populated after training)
- Base model link - For fine-tuned models, links back to the parent
Quick Start Example
Complete example of setting up a model for customization:
HuggingFace Token: If downloading from a gated HuggingFace repository (like Llama models), you will need to create a secret containing your HuggingFace API token first. Refer to Manage Secrets for instructions.
After the Model Entity is ready (has a spec), you can use it in customization jobs with model: "default/qwen3-1.7b".