Filament Accounts Auth Laravel Package

Product Decisions This Supports

• Roadmap alignment: Confirms the package is ready for the Filament 5 / Livewire 4 / Laravel 12–13 stack, making it a viable dependency for new Filament-based products or planned framework upgrades.
• Build vs. buy: Supports buying/adopting authentication UI instead of building custom auth pages, especially when the product needs setup flows, localized pages, two-factor challenge, and Filament-native account integration.
• Upgrade planning: v5.0.0 is a major-version jump with hard requirements (PHP 8.2+, Laravel 12/13, Livewire 4, Filament 5, tomatophp/filament-accounts 5). Teams on older stacks should treat this as a planned migration, not a routine patch.
• Security and access control: The /auth/setup/* pages are limited to local environments or the viewAuthSetup gate, which is useful for product decisions around exposing setup tooling safely.
• Localization and UX: Language-config-driven page text with per-locale overrides supports internationalization decisions; the register-page phone label fix is a small but user-facing quality improvement.
• Dependency risk management: The declared conflict with devdojo/auth due to the shared Devdojo\Auth namespace is a concrete constraint for products already using or evaluating that package.

When to Consider This Package

Consider adoption when:

• You are starting a new Filament 5 application on Laravel 12/13 and want ready-made authentication pages or setup flows.
• You are already using tomatophp/filament-accounts 5 and need an auth UI layer that integrates with the accounts guard and configured account model.
• You need configurable, locale-aware auth page text, two-factor challenge support, and controlled access to auth setup pages.
• You value having a maintained test/CI baseline (Pest, PHPStan, Laravel 12/13 matrix) as part of the dependency decision.

Look elsewhere or defer when:

• Your application is not yet on Laravel 12/13, Livewire 4, Filament 5, or PHP 8.2+.
• You already depend on devdojo/auth; the namespace conflict makes coexistence unsafe without a migration plan.
• You need a long-term support path on older Laravel/Filament versions; the release notes state the 1.x line stays on the v3 branch, so older lines will diverge.
• You require fully custom auth UX or cannot accommodate the published public/auth/build asset pipeline and system-font fallback behavior.

How to Pitch It (Stakeholders)

For executives: This release keeps the authentication package current with the latest Laravel, Livewire, and Filament ecosystem. It reduces the need to build and maintain custom auth screens, supports localized user-facing pages, and adds controlled setup-page access. The main caveat is that it is a major upgrade requiring the newest framework versions, so it is best treated as part of a planned platform upgrade rather than an immediate drop-in change.

For engineering: v5.0.0 aligns the package with Filament 5, Livewire 4, Laravel 12/13, PHP 8.2+, and tomatophp/filament-accounts 5. It introduces a hard conflict with devdojo/auth because both use the Devdojo\Auth namespace. Setup pages are gated to local environments or the viewAuthSetup gate, two-factor challenge uses the accounts guard, and the testing environment no longer overrides the host app’s Blade Icons factory. The release includes Pest tests, PHPStan, and a Laravel 12/13 CI matrix. The 1.x line remains on the v3 branch, so teams staying on older stacks should expect separate maintenance paths.