Roadmap

What is coming, and when.

Past milestones are dated by what actually happened; the dates ahead are the ones we stand behind today. They are revised at each milestone rather than smoothed over: a roadmap that is never corrected is not being kept, it is being forgotten.

01

Milestones

From the first trials to version 1.0.

  1. May 2026 — Delivered

    First vibecoding experiments around MXL

    Exploratory prototypes on the MXL bus, to find out what could be built on it.

  2. June 2026 — Delivered

    Bobi.Studio project started

    The orchestrator and the first container plugins were built.

  3. July 2026 — Delivered

    Trials in real conditions

    A server deployed at a customer site, running two multiviewers. Tests, but in a real gallery.

  4. August 2026 — Delivered

    Operational fixes

    A month of corrections coming out of real use, ahead of the beta.

  5. Late August 2026 — Delivered

    NMOS With MXL (BCP-007-03)

    The internal graph is published as IS-04 resources under the MXL transport. With it: an embedded IS-04 registry, DNS-SD discovery, IS-07 for tally and IS-09 for the PTP domain.

  6. 1 September 2026 — In progress

    Beta — available

    The complete, installable distribution: orchestrator, node agent and the shipped plugins. It installs exactly like the final release, and is aimed at evaluation and supported pilot installations.

  7. September 2026 — Next

    IBC 2026

    We will be there. If you would like to talk it through in person, let us arrange to meet.

  8. November 2026 — Later

    Version 1.0

    The first release intended for production operation, with the installation and infrastructure documentation up to date.

  9. By the end of 2026 — Later

    Media plugins

    Player, recorder, stills and transcoder — the family announced as in preparation on the Capabilities page.

  10. During 2027 — Later

    What follows

    New container types and new integrations, at the pace of the needs met in production.

Updated 30 August 2026.

02

What each stage commits to

A version name says nothing until you say what can be done with it.

  1. Beta

    Installable and complete, but still liable to change. The right use is to evaluate, build a mock-up and prepare an infrastructure — not to go on air unsupported.

  2. Version 1.0

    The release you install to operate. The infrastructure and installation documentation is authoritative, and later updates do not break saved projects.

The beta is available.

It installs exactly like the final release, and we support the first pilot installations. Tell us what you want to build.