I kept hitting the same pattern in Laravel / Filament projects:
the first version of the admin panel is usually fine, but later the data side keeps changing.
New content type.
More custom fields.
Better filtering.
Dashboards.
API requirements.
Tenant-specific behavior.
More exceptions.
At that point, every "small" change becomes another migration, another model, another Filament resource, and another layer of maintenance.
So I built a plugin called **Filament Studio** for Filament v5.
The idea is to let you create collections and fields at runtime, manage records through generated Filament UI, build dashboards, add advanced filtering, and expose APIs without rebuilding a brand-new schema layer every time requirements shift.
It also includes things I thought were important if this is going to be useful beyond a demo:
- authorization
- multi-tenancy
- versioning
- soft deletes
- custom field and panel extensibility
I know some people will immediately look at the EAV angle and prefer hand-built resources anyway, which is fair.
I am mostly curious about where other Laravel developers draw that line.
If you are building something with a stable schema, I still think hand-built resources make sense.
But if the admin/data model changes constantly, would you rather keep building each resource manually, or use something like this?
Repo if you want to look at it:
GitHub: https://github.com/flexpik/filament-studio
I am not looking for empty promotion here. I would rather hear the real objections or the kinds of projects where this would actually help.