- What is FilaKit and what does it include out of the box?
- FilaKit is a Laravel starter kit built on Filament 3 that scaffolds authentication, user and admin management, role handling, and profile settings. It ships a multi-panel structure and a multi-auth guard setup, so you inherit a pre-wired admin panel instead of assembling those conventions yourself. It is an opinionated foundation aimed at greenfield Filament projects, and its value comes from the conventions it pre-wires rather than from code you would write anyway.
- How do I install jeffersongoncalves/filakit?
- Install it with Composer into a Laravel 13 application that targets Filament 3, then follow the repository README for migrations, seeding, and asset build steps. Because recent releases move models, resources, and login handling onto separate user and admin packages, check the exact release you pin rather than trusting the version number. The GitHub repository is the authoritative source for bootstrap commands and current constraints.
- Does FilaKit support Laravel 13 and Filament 3?
- Yes. FilaKit is built on Laravel 13.x and Filament 3.x, and its release tags track Filament versions rather than the package's own change surface. That means a tag like 3.3.56 reflects upstream Filament alignment, not necessarily a small internal change. Confirm the declared composer.json constraints before you commit to a runtime.
- How does FilaKit's multi-panel and multi-auth guard setup work?
- FilaKit provides multiple Filament panels backed by separate authentication guards, with user and admin side by side. Since the 3.3.56 change, that wiring comes from external user and admin packages rather than from self-contained scaffolding inside the starter kit. If you published or overrode the original models or login page, reconcile them with the new locations so your overrides do not silently drift from upstream.
- Can I customize the User and Admin models or the login page without forking FilaKit?
- The package was originally designed to be overridden, but PR #197 relocated models, resources, and login handling into separate user and admin packages. There is no documented migration note, deprecation path, or upgrade guide for that change, so verify each override point against the current release. Where possible, extend the shipped classes rather than publishing and editing copies.
- What PHP version does FilaKit require?
- Static analysis for the package now runs on PHP 8.4, and the CI workflows were standardized around that runtime. The release notes do not publish a supported PHP matrix or a minimum Filament constraint. Confirm the platform requirement in composer.json before you standardize your own runtime.
- Does FilaKit include role and permission management?
- FilaKit scaffolds user and role management alongside profile settings in the admin panel. The exact permission backend now depends on the user and admin packages it composes, so review those dependencies to see which authorization layer you actually inherit. Teams with specific RBAC requirements should audit that layer before building on it.
- Is FilaKit production ready, and what are the maintenance risks?
- It is a reasonable head start for a greenfield Filament 3 admin panel, but it carries a single-maintainer bus factor, with nearly all commits and CI changes coming from one author. Roughly 20 of 24 recent PRs are automated dependency bumps or CI and funding churn, so release notes are a weak changelog. Diff releases and read PR titles instead of relying on semver signals.
- How do I safely upgrade FilaKit when its versions track Filament?
- Because tags follow Filament's numbering, a patch-level bump can carry a structural change such as moving models, resources, and login into external packages. Pin an exact version, read the PR titles between your current and target release, and review diffs for relocated classes. Test the upgrade on a branch and keep any overrides under version control so drift is visible.
- What are alternatives to FilaKit for a Filament admin panel?
- If you do not want FilaKit's opinions, you can pair plain Filament 3 with Laravel's native auth scaffolding and build your own panel provider and guard setup. FilaKit's value is precisely the pre-wired conventions, so teams planning to hand-roll auth and panels will discard most of what it provides. Treat it as an opinionated foundation rather than a drop-in library.