Nova Dashboard Manager Laravel Package

Product Decisions This Supports

• Build vs. buy for internal analytics surfaces. If the team already runs Laravel Nova, this package supplies dashboard CRUD, card arrangement, and per-user saved views for free — roughly 1–3 dev weeks of work you don't have to scope. That's a legitimate "buy" (adopt) decision for a non-differentiating internal feature.
• Feature validation before platform investment. A cheap way to test whether internal ops/CS/finance teams actually use self-serve dashboards before committing budget to a hosted BI tool (Metabase, Superset, PostHog). Ship it, watch usage for a quarter, then decide.
• Roadmap scoping for "self-serve reporting" epics. Helps separate the 20% of the request that's real (saveable views, reordering, per-team layouts) from the 80% that's actually a BI product (drill-down, ad-hoc query, alerting) and belongs in a different tool.
• Lock-in assessment on Nova itself. Adding this package deepens dependence on a paid, commercial admin panel. If dashboards are a core product surface rather than an internal convenience, this is a signal to reconsider the host framework — a decision worth surfacing now, not after two more packages land on top of it.
• Concrete use cases to evaluate against: internal KPI walls, ops/on-call monitoring pages, per-team saved metric layouts, exec snapshot boards — all internal, low-stakes, low-compliance.

When to Consider This Package

Adopt if all of these hold:

• You are already licensed and running Laravel Nova (the sunk cost is the whole value proposition — this package is worthless without it).
• The audience is internal only: employees behind SSO, no external tenants, no contractual uptime or audit obligations.
• The need is genuinely narrow — create/rename/reorder dashboards, attach Nova metric cards, per-user visibility.
• You are willing to vendor/fork the code into your repo and assign a named maintainer, treating it as a starting point rather than a dependency.
• You need something in a sprint and "good enough" beats "nothing."

Look elsewhere if any of these hold:

• Maintenance risk is disqualifying. Last release September 2023, ~21 stars, apparent single-maintainer bus factor. There is no credible security-response path and Nova majors move — compatibility breakage is a matter of when.
• The surface is customer-facing or embedded in your product. Different bar entirely.
• You need multi-tenant row-level security, PII scoping, or audit trails. Not in scope here.
• You need real analytics: charting, exploration, drill-down, alerting, scheduled delivery. This is dashboard management, not a BI engine — be precise about that distinction before anyone promises "analytics" to a stakeholder.
• You are not on Nova, or are evaluating whether to stay.
• Dashboards are a differentiator rather than table stakes — then build deliberately or buy a real BI layer.

How to Pitch It (Stakeholders)

To executives (one paragraph): This is a small, free, MIT-licensed add-on that gives our Laravel Nova admin panel user-configurable dashboards — roughly one to three weeks of engineering we would otherwise spend building it ourselves. The trade-off is maintenance: the project has been quiet since September 2023, has very low adoption, and appears to be one person's side project. My recommendation is to treat it as an internal-only prototype or a code we vendor into our own repository with a named owner — not as a dependency we rely on for anything customer-facing or contractual.

To engineering (framing): Low-risk spike, not a platform bet. Fork it, pin it, own it. Budget half a sprint to evaluate Nova-version compatibility and card-type extensibility; if the internals are clean, the cost of ownership is a few hours a quarter. If they're not, we've learned that cheaply.

Decision requested: Approve a one-sprint evaluation with a hard go/no-go, or skip it and go straight to a hosted BI tool if dashboards are strategic rather than a convenience. The failure mode to avoid is drifting into a half-owned, unmaintained dependency on a surface someone eventually promises to a customer.