This page covers the current release. Notes for earlier releases are kept as versions of this page.

VAM 1.0.1

Released 2026-10-21. This patch release tightens the licensing model and introduces the service registry. VAM and the Configuration Service now authenticate to the entitlement orchestrator with a bearer token.

Component Versions

Component

Version

VAM core service

1.0.1

Configuration Service (API + GUI)

1.0.1

Deployment Console (vamctl)

1.0.1

Configuration Service API contract

1.14.0

Entitlement Orchestrator

1.0.8

Viz AI Knowledge Base

0.9.36

Viz AI Designer

0.1.23

The Viz AI Design Knowledge Base remains a preview package and is not included in this release. Every other package keeps the version of VAM 1.0.0.

Changes in This Release

  • Licensing. VAM is now licensed on or off with no seat count. Each replica waits at startup for an entitlement snapshot and does not accept traffic until VAM and the write feature are licensed.
  • Entitlement orchestrator authentication. VAM and the Configuration Service now send a bearer token when calling the entitlement orchestrator. Replication requires both the VAM license and the REPLICATION feature to be active in the orchestrator.
  • Service registry. Secondary services can register their bindings against VAM instead of being wired by hand.
  • Deployment Console. Bootstrap and machine-configuration fixes, with improved TLS handling for in-cluster registries.

Fixes

  • Binding presets with Microsoft Entra ID. The Configuration Service requests its forwarding token with the <audience>/.default scope, so binding presets load instead of failing with AADSTS90014.
  • Viz Pilot Edge with authentication. When OIDC is configured for PCS, PCS and the Pilot Change Broadcast Service connect to RabbitMQ over TLS on port 5671. Before, they dialed the plaintext port and the broker dropped them.
  • Platform FQDN in the Deployment Console. The FQDN entered for one cluster no longer carries over to the next deployment in the same session. The FQDN step proposes the selected cluster's own name.

Platform Capabilities

The capabilities below are the standing feature set of the platform as of this release.

Storage, Versioning & APIs

  • Durable core. VAM stores assets in an S3-compatible object store, with a SurrealDB document store and a RabbitMQ event bus behind it.
  • Everything is versioned. Every document and blob carries a version identifier, and conditional writes return 412 on a stale ETag so concurrent edits never clobber one another.
  • Optional full-text and semantic search through OpenSearch enriches asset discovery when enabled.
  • Integrator surfaces. A Schema API lets integrators define and evolve task schemas, and an MCP server exposes the platform to AI agents over the Model Context Protocol.

Editorial Integrations

  • Pilot Core Service bridges Viz Pilot to VAM, and the Pilot Change Broadcast Service keeps rundown changes in sync.

Installation & Cluster Topologies

  • Install workflows: Installation for an online installation. An air-gapped installation with Prepare Offline Bundle and Offline Installation needs assistance from Vizrt support.
  • Supported targets: Hyper-V, VMware vSphere or an existing Kubernetes cluster.

Configuration Service

  • Replication. Clusters can be paired for active-active replication using a single-use connection code.
  • Identity provider. Microsoft Entra ID is the supported identity provider.
  • Certificates. Issuer options include Microsoft AD Certificate Services (AD CS), and Trust Roots distributes uploaded root CAs across the cluster.
  • Backups & recovery. Schedule, verify and restore backups, up to full disaster recovery onto a new cluster.
  • Safe upgrades. Package upgrades are managed in-cluster, and a failed upgrade can be rolled back.
  • Auditability. An Audit Log records configuration changes.