Add the behavior you need to the form you already have. FLEX controls can sit
alongside native Filament fields in your existing Resource. Start with one
specialized input, then reuse its configuration and connected workflows wherever
your application needs them.
Reuse more than the appearance
FLEX connects configurable controls with a shared instance lifecycle and media
workflows. Repeated fields share resources, optional features follow each
instance, and changing tabs or nested dialogs retain the resources still in use.
This builds on Filament’s existing form and extension capabilities, including
on-demand assets and optional Spatie integration. The benefit is a connected
implementation you can configure and reuse across your application’s workflows.
Use the component’s PHP examples directly, or give your assistant the
optional FLEX skill and installed API discovery tools.
They help it configure existing controls and integrations using the installed
package. Check generated configuration by saving, reopening and validating real
values, just as you would with manually written application code.
Connect only the workflows you need
- Existing models: ordinary fields bind to their intended attributes. Managed
JSON field groups are a separate, optional workflow.
- Browser resources: FLEX uses a shared runtime and base styles, then loads
component dependencies according to active use. Built-in controls declare
those requirements; you configure their features.
- Media: choose your storage and access rules. Enable image encoders, workers
or Spatie packages for the processing and integration options you select.
- Large catalogs: combine virtualized rows with scoped, paginated providers
to control both rendering and fetched results.
- Updates: follow the deployment guide and verify the
workflows your application uses when upgrading.
Start with one field and a real saved value. For optional
services and commercial use, see Requirements & integrations
and Licensing. Last modified on October 17, 2026
