Filament Jet Laravel Package

Product Decisions This Supports

• Feature triage for user-facing account management — this package bridges Laravel Jetstream (teams, profile, two-factor auth, API tokens, browser sessions) into Filament panel pages. It directly informs whether to build those screens in-house or adopt an existing integration.
• Build vs. buy for admin/portal scaffolding — if the product already standardizes on Filament for internal or customer-facing panels, adopting this avoids re-implementing Jetstream profile/team/token UI as custom Filament resources.
• Roadmap gating on framework currency — the 0.0.2 release adds support "up to Laravel 10," which means Laravel 11/12 projects are not covered. This is a decision input for whether the package fits the current or next platform upgrade cycle.
• Team/seat-management use cases — relevant for B2B products that need in-panel team membership, invitations, and API token self-service without building a second UI surface.
• Vendor/supply-chain risk scoring — 0.0.x versioning, a single primary maintainer, and a contributor base of one signal that this should be treated as an internal accelerant, not a load-bearing dependency.

When to Consider This Package

Consider it when:

• The application runs Laravel 10 (or earlier) and Filament v2/v3 alongside Jetstream, and you need Jetstream's profile/team/token features surfaced inside the Filament panel.
• You need to ship account-management UI fast for a prototype, internal tool, or an MVP where a 0.0.x dependency is acceptable.
• Your team is already fluent in Filament and wants to avoid duplicating Jetstream's backend logic in custom panel pages.
• You can vendor or fork the package if upstream stalls — the surface area is small enough to patch.

Look elsewhere when:

• You are on Laravel 11 or 12. The 0.0.2 bump stops at Laravel 10; there is no published compatibility path beyond it, and Laravel's yearly major cadence means this gap will widen.
• You need production-grade support, SLAs, or a maintained changelog with semantic versioning. A 0.0.x package makes no stability guarantees and may introduce breaking changes in any patch release.
• You do not use Jetstream. The package is additive to Jetstream, not a replacement — adopting it means adopting that stack.
• Filament's own first-party auth/profile features or a simpler custom resource set already cover the requirement.
• Security-sensitive surfaces (API tokens, 2FA, session revocation) require an audited, actively reviewed implementation.

How to Pitch It (Stakeholders)

To executives: This is a small integration package that plugs Laravel Jetstream's account features — profiles, teams, API tokens, active sessions — into the Filament admin panel we already use. It saves engineering time on screens users expect but rarely differentiate on. The catch is maturity: the project is at version 0.0.2 with essentially one maintainer, and the latest release only certifies compatibility through Laravel 10. Treat it as a time-saver on Laravel 10 work, not as a strategic dependency, and expect to own a fork or replace it if we move to Laravel 11+.

To engineering: 0.0.2 is a compatibility-only release — it raises the Laravel ceiling to 10 and adds a first-time contributor. No new features, no deprecations, no API changes. The practical read: the package is maintained but thinly, and its framework support lags current Laravel. Before adopting, confirm our Filament and Jetstream versions align, pin the dependency exactly, and have a plan for the Laravel 11 upgrade — either an upstream PR or an in-house replacement of the affected panel pages. Given the small surface area, forking is a realistic fallback rather than a crisis.