Filament Profile Laravel Package

Product Decisions This Supports

• Build vs. buy for account self-service: The plugin ships a Breeze-style profile page (profile form, password update, browser session management, account deletion) plus a configurable profile menu inside Filament. That removes a recurring "table stakes" build item from the roadmap for every Filament-based product we ship.
• Time-to-market on new admin panels: For internal tools and early-stage SaaS backends, this converts a multi-day build (forms, validation, session revocation, account deletion with confirmation flows) into an installation and a composer require.
• Standardization across products: Because views are publishable, we can adopt the plugin as the default account surface and layer our own branding/fields, rather than each team re-implementing a slightly different profile page.
• Scope negotiation: Gives a credible "already handled" answer when stakeholders request profile editing, password change, or "log out my other devices" — we can redirect that budget toward differentiating features.
• Roadmap signal: v1.0.0 is an initial release with a single contributor and a small feature surface. Treat it as a candidate for non-critical panels first; do not make it a dependency of security-sensitive, customer-facing account flows without a review.

When to Consider This Package

Consider adopting when:

• The app is built on Filament and users need a conventional profile/account page (name, email, password, sessions, delete account) without custom design requirements.
• We want Breeze-equivalent account UX in an admin or app panel and consider that UX non-differentiating.
• A small team needs to ship fast and is comfortable owning a published view layer (the form is publishable, so customization is expected).
• We are comfortable pinning a 1.x dependency and accepting single-maintainer risk, with the fallback of forking — the package is small enough that a fork is a realistic contingency.
• The panel is internal or low-risk; account deletion and session revocation behaviors need a quick security sanity check before customer-facing use.

Look elsewhere or build in-house when:

• We need 2FA, passkeys, SSO/SAML, audit logging, or step-up auth — none of that is in this release.
• The application is not Filament-based, or uses a Filament major version outside the plugin's supported range (verify compatibility before committing).
• Profile pages are a branded, differentiated surface where a stock Breeze-style layout would create rework.
• We require vendor SLAs, security review artifacts, or long-term maintenance guarantees — this is a first release from a first-time contributor.
• Multi-tenant or multi-guard account semantics are required beyond what a single profile page provides.

How to Pitch It (Stakeholders)

To executives: This is a small, free open-source add-on that gives our Filament admin panels a complete, familiar account page — edit profile, change password, see and revoke active sessions, delete account — in hours instead of days. It removes a repeated build item from every panel we launch and lets the team spend that time on features customers actually choose us for. The trade-off is maturity: it is a brand-new 1.0 release maintained by a single developer, so I recommend using it on internal and early-stage panels first, pinned to a specific version, while we keep the option to fork it — the code footprint is small enough that this is cheap insurance.

To engineering: Install, publish the profile form views, wire the menu entry, done. It follows Breeze conventions, so the account UX will be immediately legible to anyone who has used a Laravel starter kit, and the publishable views mean we customize rather than fight it. Scope we own: confirm Filament version compatibility, review the account-deletion and session-revocation paths before enabling them on customer-facing panels, and pin the version. Do not extend it for 2FA or SSO — that is separate work.