Skip to main content
When a Baseten Training job completes, Baseten automatically saves your checkpoints to Baseten storage. You can deploy any of them to an inference engine without downloading or re-uploading anything. Engine-Builder-LLM, BEI, and BIS-LLM all support this workflow.
For deploying weights from external cloud storage (GCS, S3, Azure), see Deploy from cloud storage.

Checkpoint reference

The repo and revision fields in checkpoint_repository specify which training project and checkpoint to deploy.
  • repo: Your Baseten Training project name.
  • revision: Which job and checkpoint to target. The following formats are supported:
To look up checkpoint names for a job, run:

LLM deployment

Use Engine-Builder-LLM or BIS-LLM to deploy a fine-tuned language model. Set base_model to decoder:
config.yaml
Once deployed, call the model using the OpenAI-compatible chat completions endpoint:
See Call your model for full inference options including streaming and the OpenAI SDK.

Embeddings deployment

Use BEI to deploy a fine-tuned embedding or reranker model. Use encoder_bert for BERT-based models (sentence-transformers, rerankers, classifiers) or encoder for causal embedding models:
config.yaml
Encoder models have specific requirements:
  • No tensor parallelism: Omit tensor_parallel_count or set it to 1.
  • Fast tokenizer required: Your checkpoint must include a tokenizer.json file. Models using only the legacy vocab.txt format aren’t supported.
  • Embedding model files: For sentence-transformer models, include modules.json and 1_Pooling/config.json in your checkpoint.
The webserver_default_route field sets the inference endpoint path:
  • /v1/embeddings: For embedding models.
  • /rerank: For rerankers.
  • /predict: For classifiers.
  • /predict_tokens: For token-level prediction.
Once deployed, call the model using the embeddings endpoint:
See Call your model for full inference options.