# Baseten — BDN Sealed Volumes: publish once, mount anywhere

- Company: Baseten (baseten.co)
- Announced: 2026-10-26T21:23:55+00:00
- Category: developer-tool-release
- Coverage: not counted
- Announcement: yes
- Group: announcements
- Source: https://www.baseten.co/blog/bdn-sealed-volumes-publish-once-mount-anywhere
- Record: https://forck.live/items/28001-bdn-sealed-volumes-publish-once-mount-anywhere
- Subject: Baseten
- Models affected: Qwen3-8B

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, Cloudflare 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.

## Evidence

Verbatim from https://www.baseten.co/blog/bdn-sealed-volumes-publish-once-mount-anywhere:

> BDN Sealed Volumes do for model data what container images do for code: publish once, get a digest, mount it anywhere. Mounts take seconds.
> 
> Authors
> 
> Published
> 
> October 26, 2026
> 
> Share
> 
> Published
> 
> October 26, 2026
> 
> BDN is built to distribute any content (weights, container images, training checkpoints) across model serving infrastructure. Now, BDN Sealed Volumes let you publish any read-only data once and mount it in any deployment. Sealed Volumes are available today with the Baseten CLI 1.1.0 or newer.
> 
> When there’s no single source of truth for model files, data drifts from its source.
> 
> Say you fine-tune a model, then save the checkpoint to cloud storage. Then someone downloads a copy to their laptop to test it, uploads it somewhere else so it can be served, and each deployment—e.g., staging, production, and testing—has its own config file pointing to the checkpoint. When one person pins another revision, nobody notices until the outputs differ.
> 
> The same problem applies to LoRA adapters, vector indexes, tokenizers, embedding indexes, lookup tables, and any model or deployment artifact.

---

Record: https://forck.live/items/28001-bdn-sealed-volumes-publish-once-mount-anywhere
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md