From the source
Baseten released BDN Sealed Volumes, which let teams publish read-only model data once and mount it in any deployment, available today with the Baseten CLI 1.1.0 or newer.
- The feature addresses data drift, where checkpoints, LoRA adapters and indexes get copied between laptops, buckets and deployments until nobody can tell which revision is serving.
- A volume is a named, versioned set of files in a namespace such as weights; when a push or sync finishes, BDN commits the files as a new version and seals it, identifying it by a content digest like bdn:weights/qwen3-8b@b3:9f3c.
- Deployments pin that digest in config.yaml, so every replica streams identical bytes read-only, later pushes cannot change what a deployment mounts, and rollback means pointing the config at an earlier digest.
- BDN splits files into chunks stored once by content hash, so an updated checkpoint uploads only changed chunks, and because the volume is mounted at a chosen path, files are available as soon as the container starts rather than after a download.
- Sync works the same way for Hugging Face, S3, GCS, Azure Blob, R2 and CoreWeave buckets, with private sources taking a Baseten secret or OIDC for S3 and GCS, and a deleted version stays restorable for 7 days.
