Nova Websockets Laravel Package

Product Decisions This Supports

• Internal observability inside the admin panel. It surfaces the laravel-websockets dashboard (connection counts, throughput, connected clients, per-app metrics) inside Laravel Nova, so support and ops staff can check real-time infrastructure health without a separate dashboard, SSH session, or engineer.
• Build vs. buy for internal tooling. This is effectively a "buy" at zero license cost, but the real cost is integration and maintenance. It's a useful data point when deciding whether to hand-roll an admin metrics page versus wrapping an existing dashboard — and a reminder that "free" internal tools still carry a maintenance liability that must be owned.
• Real-time roadmap gating. If your roadmap includes live notifications, presence, or broadcast events, you need a WebSocket layer. This package only makes sense if you have already committed to beyondcode/laravel-websockets; it should not be the reason to adopt that stack. Use it as a checkpoint: "do we already have this stack, or are we about to bet on a deprecated one?"
• Vendor/ecosystem risk tracking. Its 2019 last release and 14 stars are a concrete signal that the laravel-websockets ecosystem is winding down in favor of Laravel Reverb / Soketi / Pusher. That supports a roadmap item for migration rather than new adoption.
• Non-customer-facing productivity spend. Frame it as an ops-efficiency line item, not a product differentiator — it generates no revenue and no user-visible capability on its own.
• Reference implementation. If you're deciding how to expose operational metrics to non-engineers in Nova, this is a small, readable example of the pattern, even if you don't ship it.

When to Consider This Package

Consider it only when all of the following hold:

• You already run Laravel Nova (paid license) and beyondcode/laravel-websockets in the same application — the package adds no capability on its own.
• Your Nova version is from the 2019 era (Nova 2.x). It predates Nova 4/5 and should be expected to fail installation or break on modern Nova; verify before estimating any work.
• You need lightweight, ad-hoc inspection only — no alerting, no retention, no historical metrics, no SLA reporting.
• Access is restricted to trusted admins; you're comfortable pinning a dormant dependency in composer.json.
• You have the appetite to fork and maintain it yourself, since upstream support is effectively nonexistent.

Look elsewhere when:

• Starting fresh. Use Laravel Reverb (first-party) or Soketi; laravel-websockets itself is superseded, so wrapping its dashboard is a dead end.
• You need production observability. Reach for Laravel Pulse/Telescope, Horizon-style dashboards, or an APM (Datadog, Sentry, New Relic) — this gives you a status view, not monitoring, alerting, or tracing.
• Nova is modern (4/5) or absent. Don't buy a Nova license for this; don't assume compatibility.
• You require vendor support or security patching. 14 stars and no release since 2019 means no community safety net and no CVE response.
• You are mid-migration to Reverb. Adding this accelerates tech debt rather than reducing it.

How to Pitch It (Stakeholders)

For executives: This is a small, free, internal-only convenience that lets ops and support check WebSocket health from the admin panel they already use, saving context-switching for the team. It carries no direct revenue impact and no customer-facing change. The important message is the risk signal: the package hasn't been updated since 2019 and sits on top of a technology the Laravel ecosystem has since replaced, so I recommend we decline it for new work and treat it as a candidate for removal during our real-time migration. Cost of adoption is near zero; cost of owning it long-term is not.

For engineering: Integration is a single Composer dependency that mounts the laravel-websockets dashboard as a Nova tool — low code footprint, MIT licensed, easy to read. But it targets Nova 2.x, has had no release since October 2019, and depends on laravel-websockets, which is superseded by Laravel Reverb. Recommendation: do not add it to new applications; if it's already installed, plan removal alongside the Reverb/Soketi migration and replace the visibility it provides with first-party tooling (Pulse/Telescope) or APM. If a team wants it strictly for a legacy Nova 2 admin, that's an acceptable tactical exception with a named owner.

Bottom line: low cost, low value, high staleness — a tactical convenience at best, a liability at worst. Decision: no new adoption; deprecate existing usage.