Companions

Companions extend VoodBuilder without forking the editor. Community companions ship with core. Paid companions arrive inside the Developer or Agency Anystack meta-package, then you register their Filament plugins.

flowchart TB
  subgraph community [Community]
    Vm[Vmedia]
    Vc[Vcookiebar]
  end
  subgraph developer [Developer meta-package]
    El[Elements]
    Dd[Dynamic Data]
    Tp[Templates]
  end
  subgraph agency [Agency meta-package]
    Co[Components]
    Da[Dynamic API]
    Po[Popups]
  end
  community --> developer --> agency

Community

Developer

Agency

Rules that apply to every paid companion

1. Install via voodflow/voodbuilder-developer or voodflow/voodbuilder-agency — not by requiring nested packages one by one.
2. Run php artisan voodbuilder:install after Composer changes that affect the host app.
3. Register the companion’s Filament plugin on the panel.
4. Let licence APIs decide entitlement — do not document or rely on per-feature enable flags in .env.

See Editions · Edition bundles.