Nova Databoards Laravel Package

Product Decisions This Supports

• Feature decision: in-admin analytics. Whether to ship KPI dashboards inside the Laravel Nova admin panel instead of standing up a separate BI tool (Metabase, Redash, Looker Studio) and the integration/auth work that implies.
• Build vs. buy vs. borrow. The package is a shortcut for dashboard CRUD + chart widgets that would otherwise be a multi-week build. Because it is archived, the honest framing is borrow and fork: you are acquiring code, not a vendor relationship.
• Roadmap placement of self-serve reporting. Informs whether to invest in dashboards for non-technical internal users (support, sales ops, CS) or keep analytics with analysts in a dedicated tool.
• Nova version strategy. Adopting this effectively pins you to the Nova generation it was built for (released July 2020, so Nova 2/3-era, Laravel 6/7-era). That is a platform decision, not just a package decision.
• Scope triage for internal reporting use cases. Model-backed metric boards, ops/health views, and lightweight multi-board layouts for internal stakeholders — versus exploration, exports, scheduling, and alerting, which this does not credibly cover.
• Risk budgeting. 21 stars, last release 2020, archived: any adoption decision should be paired with an explicit owner and maintenance estimate, not treated as a zero-cost dependency.

When to Consider This Package

Consider it when all of the following hold:

• You already run Laravel Nova and want databoards embedded in the existing admin surface with minimal new infrastructure.
• The audience is internal and low-stakes — read-only KPI views, no regulated data, no formal security review gate.
• You are willing to fork and own the code: pin it, audit it, add tests, and carry it through PHP/Laravel upgrades.
• Scope is genuinely small: a handful of boards and widgets, not a reporting platform.

Look elsewhere when:

• You are on Nova 4/5, Laravel 9+, or PHP 8.1+. Expect incompatibility; budget a real migration, not a composer require.
• You need maintained dependencies, security patching, SSO, row-level/tenant permissions, or audit trails.
• Analysts need exploration, CSV/warehouse exports, scheduled delivery, or alerting — that is Metabase / Power BI / Looker Studio territory.
• You are on modern Laravel and want app-health or product metrics: Laravel Pulse, Nova's native metrics/cards, or Filament widgets if you are on Filament are lower-risk defaults.
• Multi-tenant data isolation is a hard requirement and unproven here.

Net: treat it as a reference implementation or a timeboxed fork candidate, not a dependency to adopt as-is.

How to Pitch It (Stakeholders)

To executives: This is a free, small Laravel Nova add-on that puts analytics dashboards directly in our existing admin panel — no new BI license, no separate login, no data pipeline. The catch is that it was archived in 2020 and has a tiny maintainer base (21 stars, no release in years), so it is a code acquisition, not a supported product. Recommendation: do not adopt it as a dependency. If we already run a legacy Nova admin and want internal dashboards fast, run a one-to-two-week spike/fork with a named owner; otherwise, use Nova's built-in metrics, Laravel Pulse for app health, or a maintained BI tool for analyst-facing reporting.

To engineering: Treat this as a fork candidate. Estimate: Nova API compatibility on our current version, PHP 8 / Laravel upgrade path, missing test coverage, and ongoing ownership. If the estimate exceeds roughly the cost of Nova native metric cards, skip it.

Decision asked for: approve a timeboxed evaluation (or decline and standardize on Nova native metrics / Pulse / Metabase).