# Model serving infrastructure

Baseten now lets read-only model data be published once as a sealed volume: a directory or checkpoint is committed as an immutable version addressed by a content digest that any deployment can mount. Previously the same checkpoint was downloaded and re-uploaded to several places, each deployment holding its own config pointing at a copy, so a mismatched revision surfaced only when outputs diverged. Volumes are chunked and keyed by content hash, so a push transfers only changed chunks, and a mount makes files available as the container starts, removing the pull phase from startup. Sealed Volumes ship with Baseten CLI 1.1.0 and newer.

Baseten now lets read-only model data be published once as a sealed volume: a directory or checkpoint is committed as an immutable version addressed by a content digest that any deployment can mount. Previously the same checkpoint was downloaded and re-uploaded to several places, each deployment holding its own config pointing at a copy, so a mismatched revision surfaced only when outputs diverged. Volumes are chunked and keyed by content hash, so a push transfers only changed chunks, and a mount makes files available as the container starts, removing the pull phase from startup. Sealed Volumes ship with Baseten CLI 1.1.0 and newer.