Who it is for
Multimodal product teams without frontier compute, retrieval and index vendors, and builders of speech or vision features who currently rent a whole stack to get one capability.
Why now
Each of these dependencies used to require the full stack: paired-data scale for image generation, a VLM tax for visual retrieval, and multimodal co-training for speech-visual understanding. All four removals landed between 2026-09-04 and 09-10, three of them with code, weights, recipes or a frozen-model path attached, so the assembly route is testable now rather than aspirational.
What would kill it
Reproduction attempts showing the from-scratch encoder or the frozen-VLM transcript routing only work at the specific evaluated scales and benchmarks, or that the released recipes still require paired-data-scale or compute small teams do not have — in which case openness is nominal and the monolithic stack keeps its advantage.