- What is Larament and how do I create a new Laravel project with it?
- Larament is a starter kit that scaffolds a Laravel 13.x application with FilamentPHP 5.x already installed and configured, including an admin panel, authentication, and role and permission management. You create a project with laravel new --using=codewithdennis/larament, which generates a fresh application with the panel, pages, and tooling in place. It is a bootstrap-and-fork scaffold rather than a runtime package, so the generated files belong to your repository once created.
- Which Laravel and Filament versions does Larament support?
- Larament targets Laravel 13.x and ships with FilamentPHP 5.x preinstalled and configured. Note that the package's own major version line (currently v7.x) is decoupled from Laravel's major version, so check the composer.json constraints after install rather than assuming alignment. If you are starting on a different Laravel major, verify compatibility before committing to the scaffold.
- Does Larament include authentication and roles and permissions?
- Yes. Larament wires up authentication and role and permission management as part of the generated baseline, along with seeded user, profile, and settings pages. This means you get login flows and role-gated access to Filament resources without building that plumbing yourself. You should still review the generated policies and seeding against your own security requirements before going to production.
- How do I install Larament into an existing Laravel application?
- Existing applications can pull the package and run php artisan larament:install to scaffold the Filament panel and related files. Be aware that retrofitting is effectively a diff-and-merge exercise against your existing conventions, and it carries ongoing drift risk. Greenfield projects are the intended and recommended path; if you must retrofit, commit to a clean branch and review every generated file.
- What testing and code quality tools come with Larament?
- Larament includes opinionated quality tooling: Pest for testing, Larastan for static analysis, Pint for code style, Rector for automated refactoring, and strict typing defaults. It also generates CI workflows so checks run on every push. Confirm whether the generated CI exercises the panel end to end, such as rendering pages and auth flows, or only runs lint and static analysis, since that affects how much confidence the pipeline gives you.
- Is Larament a runtime dependency, and what is the lock-in risk?
- Larament is a scaffold generator, not a runtime dependency. It writes files into your repository at project creation and does not expose services you must keep calling, so you own the generated code outright. The practical exit cost is refactoring code you already possess rather than migrating off a vendor platform, which is a significantly lower risk than adopting a hosted admin system.
- Can I use Larament for an API-first or headless Laravel project?
- It is not a good fit. Larament is panel-first: its defaults bias early architecture toward server-rendered admin patterns, which are expensive to unwind once domain code is layered on top. It suits admin-heavy back-office, internal operations, and CRUD-dominant tooling where tables, forms, and role-gated access are most of the build. For customer-facing products with bespoke UX, headless services, or mobile backends, a lighter starting point is a better choice.
- Is Larament actively maintained, and what are the maintenance risks?
- Recent releases such as v7.0.8 have been maintenance-only, consisting of Composer, npm, and GitHub Actions dependency bumps with no functional or migration changes. The project has a modest star count and effectively no Composer dependents, which is expected for a scaffold since consumers copy rather than require it, but it does mean maintainer concentration is a real risk. Plan for transitive dependency churn in Composer and npm builds even when the package code itself is unchanged.
- How does Larament compare to Laravel Breeze, Jetstream, or other Filament starter kits?
- Breeze and Jetstream are first-party Laravel kits focused on authentication and application scaffolding, while Larament's differentiator is a preconfigured Filament admin panel with roles, permissions, and seeded settings pages plus strict typing and static analysis tooling. Against established Filament starters, Larament is well regarded but not strongly differentiated. Choose it when you want a Filament-first baseline with quality tooling baked in; choose a first-party kit when you do not need a panel.
- What is the upgrade path between Larament major versions, and how do I handle v6 to v7 or v8?
- Because Larament generates code you own, upgrades are a re-scaffold and diff exercise rather than a Composer update you can trust blindly. Patch releases such as v7.0.8 are maintenance-only and low risk, but major boundaries, especially when Laravel or Filament alignment shifts, require planning and a fresh comparison against your fork. Check whether the previous major is still maintained and set a re-evaluation trigger for the next Laravel or Filament major release.