Servicedeskkitv4 Laravel Package

Product Decisions This Supports

• Build vs. buy for internal support tooling. servicedeskkitv4 is a Filament v4-based service desk / helpdesk scaffold (models, resources, and admin login). For teams already standardized on Laravel + Filament v4, adopting it collapses weeks of CRUD, auth, and admin-UI plumbing into a starting point — a clear "buy/adopt" play for internal ticketing.
• Roadmap acceleration for admin-facing products. The package explicitly layers on Filament (now pinned to 4.14.0) and tracks upstream closely (Dependabot auto-merge, PHPStan on PHP 8.4, standardized CI). That means the maintenance tax lands mostly upstream, not on our team.
• Composability as a product bet. Release 4.14.0's headline change — "Use user/admin packages for models, resources and login" (PR #63) — signals a modular design where we swap in our own user/admin implementations instead of inheriting the package's. This de-risks "we adopted a scaffold and now we're locked in."
• Use cases to scope first: internal IT helpdesk, customer support ticket intake, and service-request workflows where an admin-facing Filament UI is acceptable. Not a fit for full ITSM (SLA engines, billing, complex routing) without significant build on top.
• Decision trade-off to frame for leadership: high value if we're on Filament v4, marginal if we're not — the "buy" only pays off when the surrounding stack is already aligned.

When to Consider This Package

Consider adoption when:

• You are on Laravel + Filament v4 and need a service desk / helpdesk admin UI quickly.
• You want a starting point, not a locked-in product — 4.14.0's user/admin package split is explicitly designed so you can plug in your own models, resources, and login.
• Your team values low maintenance overhead: this release is dominated by dependency bumps, standardized CI, Dependabot auto-merge for GitHub Actions minor/patch, and PHPStan on PHP 8.4 — strong signals of an actively maintained package with modern tooling.
• You need composable building blocks rather than an opinionated vertical suite.

Look elsewhere when:

• You require a multi-tenant SaaS helpdesk with SLA management, routing rules, billing, or reporting beyond CRUD — this is a Filament scaffold, not a full ITSM product.
• You are not on Filament v4; adopting it forces a stack pivot whose cost likely exceeds the build savings.
• You need a commercial vendor SLA / security posture; this is a community package with a fast release cadence (4.13.4 → 4.14.0, largely maintenance).
• Your roadmap already includes a bespoke admin UI, making the buy value marginal.

How to Pitch It (Stakeholders)

For executives: We're evaluating servicedeskkitv4, an actively maintained Laravel/Filament package that gives us an internal service desk / support ticketing admin panel out of the box — auth, admin resources, and data models included. The 4.14.0 release is a maintenance-and-modularity drop: it bumps Filament to 4.14.0, hardens CI (PHPStan on PHP 8.4, automated dependency updates), and — most importantly — decouples the user/admin models, resources, and login so we can substitute our own auth/admin layer. Net: lower build cost, low lock-in, active upstream tracking. Recommendation is to proceed to a scoped evaluation against our existing stack.

For engineering: No breaking API changes are signaled — this is primarily dependency bumps and CI standardization, plus the PR #63 refactor to source user/admin models, resources, and login from dedicated packages. That refactor is the one item to validate: run a spike or staging branch to confirm our customizations still compose, and note Filament is now resolved to ^4.14.0. Risk is low, but confirm the new user/admin wiring before committing. Strong candidate for adoption if we're already on Filament v4; otherwise weigh the stack pivot first.