Laravel Dashboard Chart Tile Laravel Package

Product Decisions This Supports

• Dashboard/analytics feature delivery: This tile lets a Laravel Dashboard render a chart (bar/line/pie/etc.) as a first-class dashboard card, so a PM can scope "metrics on the ops dashboard" as a configuration task rather than a front-end build.
• Build vs. buy for internal dashboards: Rather than commissioning custom charting UI work, this package (built on the Spatie Laravel Dashboard ecosystem plus a charting backend) covers the common case: periodic refresh, polling interval, and a self-contained tile class.
• Roadmap/framework upgrade planning: Version 6.3.0 adds Laravel 13.x support, which removes a framework-version blocker from the platform upgrade roadmap. Teams planning a Laravel 13 migration can keep their dashboard tiles rather than freezing or rewriting them.
• Use cases well served: internal KPI tiles, sales/revenue trend cards, support-ticket volume, uptime/error-rate panels, and any "one chart, auto-refreshing" widget for authenticated staff.
• Use cases not served: customer-facing analytics, ad-hoc exploration/drill-down, or dashboards requiring complex interactivity — those need a dedicated BI tool.

When to Consider This Package

Adopt when all of the following hold:

• You already use (or plan to use) spatie/laravel-dashboard — this package is a tile for that system, not a standalone dashboard.
• Requirements are single-series or simple multi-series chart cards refreshed on an interval, not interactive exploration.
• Your Laravel version is supported — 6.3.0 explicitly covers Laravel 13.x, so teams mid-upgrade are unblocked.
• You are comfortable owning the data query and transformation yourself; the tile renders what you feed it, so data correctness and performance remain your responsibility.
• Audience is internal and the dashboard is behind authentication.

Look elsewhere when:

• You need a general-purpose BI/embedded analytics product (Metabase, Looker, Metabase-style tooling).
• You need real-time streaming rather than polled refresh.
• You are not on Spatie Laravel Dashboard and don't intend to be — adopting this pulls in that ecosystem.
• You need guaranteed long-term maintenance; this is a single-maintainer community package, and the charting layer beneath it carries its own upgrade churn.

How to Pitch It (Stakeholders)

For executives: This is a small, focused open-source add-on that puts charts on our existing internal Laravel dashboard without custom front-end development. The latest release adds support for Laravel 13, so it does not block our framework upgrade — that was the main risk with the component.

For engineering: fidum/laravel-dashboard-chart-tile provides a Spatie Dashboard tile that renders a chart from data you supply via a tile class. 6.3.0 is a compatibility release only — Laravel 13.x support, no API changes, no breaking changes, no deprecations — so it is a drop-in upgrade from 6.2.0. Cost of adoption is low if we are already on Spatie Dashboard; the main ongoing risk is dependency churn in the underlying charting library and the fact that this is a single-maintainer package. Recommend pinning the version and treating it as an internal-tooling dependency, not a platform-critical one.