Filament Kanban Laravel Package

Product Decisions This Supports

• Build vs. buy for internal workflow tooling: mokhosh/filament-kanban is a Filament plugin that adds drag-and-drop Kanban boards to Laravel admin panels. It directly informs the "buy" side of a build-vs-buy decision for status/pipeline boards — CRM deal stages, support ticket triage, editorial calendars, sprint or task tracking, onboarding checklists — where the alternative is weeks of custom Vue/Livewire work.
• Roadmap acceleration for admin-facing features: if the roadmap already includes a Filament admin panel, this package makes a board view a configuration task rather than a frontend project, shortening time-to-demo for internal tools and reducing the need for dedicated frontend capacity.
• Platform standardization: adopting it signals a commitment to the Filament ecosystem as the admin-layer standard, which compounds — every additional Filament plugin lowers marginal cost of the next internal tool.
• Use-case scoping: it supports simple, record-status boards well. It does not support swimlanes, WIP limits, cycle-time analytics, or real-time multi-user collaboration. Product should scope ambitions accordingly rather than promising a Jira replacement.
• Risk posture for v2.11.0 specifically: this release is maintenance-only — CI dependency bumps (Dependabot), a method-signature fix, and a community bug fix (issue #81). No new features, no deprecations, no breaking changes. It is evidence of active upkeep, not a reason to re-plan. No roadmap impact.

When to Consider This Package

Adopt when:

• The stack is already Laravel + Filament; the integration cost is near-zero and the plugin inherits Filament's auth, policies, and resource conventions.
• The need is an internal, moderate-scale board where users move records between statuses — not a customer-facing product surface.
• The team is small and would rather configure than build; a board view is a secondary feature, not the product.
• You want a permissively scoped dependency that can be forked or vendored if maintenance lapses.

Look elsewhere when:

• You are not on Filament (or not on Laravel) — the package offers little standalone value.
• Requirements include swimlanes, WIP limits, cumulative-flow or cycle-time analytics, dependency links, or real-time co-editing. These are not in scope and v2.11.0 does not move toward them.
• The board is customer-facing or revenue-critical, where a single-maintainer community plugin is an unacceptable availability risk without a fork-and-own plan.
• You need guaranteed SLAs, security review artifacts, or vendor support contracts.
• Scale or data volume exceeds what a Filament resource-backed board comfortably handles — validate against your record counts before committing.

Note on this release: v2.11.0 introduces two first-time contributors and fixes an API-signature bug. That is a modest positive signal for community health, but it also reinforces that the project depends on volunteer throughput — plan for pinning versions and reviewing releases rather than tracking main.

How to Pitch It (Stakeholders)

For executives: This is a small, free, community-maintained add-on that gives our Laravel admin panel drag-and-drop workflow boards — the kind of view we would otherwise pay to build or buy a seat-based SaaS for. The latest release (v2.11.0) is routine maintenance: dependency updates and two bug fixes, no breaking changes, no new commitments. Cost of adoption is low; cost of exit is low, since it is a scoped plugin we can remove or fork. The main caveat is that it is maintained by volunteers, so we should treat it as suitable for internal tooling rather than customer-facing or revenue-critical surfaces.

For engineering: Filament-native plugin, integrates as a page/widget against existing Eloquent resources; no separate frontend build, no new auth model. v2.11.0 is a patch-level release — CI action bumps, a method-signature correction, and a fix for issue #81. No migration work, no deprecated APIs. Recommend pinning to a minor version, adding it to the dependency-review and upgrade cadence, and confirming it against our Filament major version before rollout. Because it is a single-maintainer project with growing but thin contributor depth, treat a fork as a contingency rather than a plan.

Recommendation: proceed with a timeboxed pilot on one internal board; do not commit to it for customer-facing surfaces until we have exercised it at our data volumes.