Updated just now

Share this article

Related News

Oracle outlines four layers of controls in its Deep Trust AI architecture

Oct 26, 2026

Oracle outlines four layers of controls in its Deep Trust AI architecture

Oracle’s October 26 blueprint puts platform maintenance, database rules, object APIs and APEX application execution in one architecture. The announcement leaves component availability and independent security outcomes unestablished.

OracleAI agentsEnterprise AI

Ollama adds Phonon speech on Macs, with different licences for model variants

Oct 26, 2026

Ollama adds Phonon speech on Macs, with different licences for model variants

Ollama’s October 24 speech release brings Phonon to Apple Silicon Macs. The default 31M English model and 40M language variants differ in licence and voice scope; Windows and Linux support remain forthcoming.

OllamaPhononText-to-speech

Docker’s BAND kit brings local agents into shared collaboration rooms

Oct 26, 2026

Docker’s BAND kit brings local agents into shared collaboration rooms

Docker’s October 21 walkthrough connects a repository agent in a sandbox to people and remote agents through BAND rooms. Model choice, credentials, workspace tools and network access remain distinct setup decisions.

DockerBAND AIAI agents

Baseten Sealed Volumes pin model data by digest, with a warning about mutable tags — Source: OpenTools Team · AI-generated conceptual illustrationSource image

Baseten Sealed Volumes pin model data by digest, with a warning about mutable tags

By OpenTools Team

Baseten’s October 26 release versions read‑only model artifacts for deployment. Digest pins and mutable tags behave differently during scaling, and the feature requires current CLI/Truss versions with T4 and L4 excluded.

A versioned home for files a model reads

Baseten released BDN Sealed Volumes on October 26, giving teams a way to publish read‑only model data once and reference a specific version from deployments. The feature covers more than weights: the announcement names adapters, tokenizers, embedding indexes, lookup tables, compiled engines and reference data as possible contents.

A volume is a named collection of files with a series of versions. Baseten says a completed push or synchronization seals a new version and gives it a content digest. A deployment can then name that digest and mount the files at a chosen path. This separates the identity of the model’s data from a copy stored on a developer’s laptop or an independently maintained path in each environment.

A mutable tag can put different replicas on different versions

The release’s important deployment warning concerns tags. A label such as prod can be moved to another sealed version; the digest identifying a version does not change. Deployments pinned to the old digest stay there until their source is changed and they are redeployed.

A deployment that references the mutable tag has a different boundary: existing replicas keep serving their current version, while new or scaled‑up replicas mount the tag’s new target. Baseten explicitly warns that this can leave one deployment serving two versions at once. Moving a label therefore should not be described as an atomic update of every running replica.

For rollback, the documented flow is to select an earlier digest, set it as the source and redeploy. The announcement also describes a seven‑day restoration window for a deleted version.

Publish locally or synchronize an existing source

Baseten documents two entry points: baseten volume push for a local directory, and baseten volume sync start for an external source. The synchronization job runs on Baseten and reports a sealed reference when it reaches READY; that reference goes under bdn.mounts in the deployment configuration.

Supported source types named in the release include Hugging Face, S3, GCS, Azure Blob, Cloudflare R2 and CoreWeave buckets. Private sources use a Baseten secret, with OIDC access described as an alternative for S3 and GCS. These are the service’s documented access options, not evidence that a particular account or bucket is already authorized.

Read‑only mounts and hardware exclusions still apply

The announced requirements are Baseten CLI 1.1.0 or newer, and Truss 0.18.30 or newer for Truss deployments. Volume mounts are not available on T4 or L4 instances as of the article’s last update. Mounts are read‑only; Baseten directs runtime writes to its separate b10cache facility.

Existing deployments using a weights block do not need an immediate configuration change, according to the release. Baseten describes an automatic migration as it rolls out, while encouraging direct volume use for new weights. That remains a migration statement, rather than proof that every existing deployment has already changed. The announcement does not specify complete plan, regional or pricing terms.

AI‑generated conceptual illustration by OpenTools Team: a sealed cartridge and movable tags represent fixed model‑data versions and mutable labels. This is illustrative artwork, not an actual product interface, company location, hardware device or tested result.

Sources

1.released BDN Sealed Volumes on October 26 (baseten.co)
2.imagedelivery.net (imagedelivery.net)

Tags

BasetenAI infrastructureModel deploymentDeveloper tools