Editions
VoodBuilder ships as Community so you can evaluate and run the full visual site workflow. Developer and Agency are Anystack meta-packages that unlock paid companions. Same Filament panel — editions change entitlement, not the editor.
flowchart LR C[Community] --> D[Developer] D --> A[Agency]
| Edition | Package | Unlocks |
|---|---|---|
| Community | voodflow/voodbuilder |
Core + Vmedia + Vcookiebar |
| Developer | voodflow/voodbuilder-developer |
Elements · Dynamic Data · Templates |
| Agency | voodflow/voodbuilder-agency |
Developer set + Components · Dynamic API · Popups |
Capability matrix
| Capability | Community | Developer | Agency |
|---|---|---|---|
| Core editor & Theme Studio | ✓ | ✓ | ✓ |
| Vmedia + Vcookiebar | ✓ | ✓ | ✓ |
| Elements library | ✓ | ✓ | |
| Dynamic Data | ✓ | ✓ | |
| Templates | ✓ | ✓ | |
| Components | ✓ | ||
| Dynamic API | ✓ | ||
| Popups | ✓ |
How commercial editions install
- Purchase Developer or Agency (Anystack).
composer require voodflow/voodbuilder(if not already) and the meta-package (voodbuilder-developerorvoodbuilder-agency).- Run
php artisan voodbuilder:install. - Register the Filament plugins that ship with your bundle on the panel.
- Active licences are resolved by VoodFlow / Anystack APIs — you do not flip feature flags in
.envto “turn on” companions.
Companions are nested inside the meta-package. Do not composer require each companion separately when you already installed Developer or Agency.
No path from Developer to Agency
Anystack’s distribution model does not support upgrading a Developer licence into Agency. If you hold Developer and need Agency-only companions, purchase Agency as a new licence (full Agency price). Use that as a planning signal: pick Agency when you know you need Components, Dynamic API, or Popups.
Commercial questions: sales@voodflow.com.