Product Decisions This Supports
- Real-time feature delivery without building a WebSocket layer. This package wires Laravel's broadcasting system to Centrifugo, letting the team ship live notifications, chat, presence, dashboards, and collaborative editing backed by a proven pub/sub server rather than a custom socket service. It is an infrastructure-enabling dependency: it gates roadmap items that depend on real-time UX.
- Build vs. buy on the realtime transport. Adopting Centrifugo + this driver is a "buy/assemble" decision versus running Laravel Reverb, Pusher, Soketi, or Ably. This package makes Centrifugo a low-friction option — worth pricing against managed Pusher/Ably tiers at expected concurrent-connection volume, since Centrifugo is self-hosted and the driver is free.
- Upgrade and platform-roadmap planning. The v3.0.2 release extends verified support to Laravel 8.75 – 13.x on PHP 8.0 – 8.4, so the real-time layer is no longer a blocker on a Laravel 12→13 upgrade path. This is a direct input to "can we take the framework upgrade this quarter?" decisions.
- Risk/continuity assessment for a single-maintainer dependency. Small Opekunov-maintained package in the critical path of real-time features — the PM decision is whether to accept that concentration risk, vendor/fork it, or wrap it behind an internal abstraction so the transport can be swapped.
- Scope decisions on what the product can promise. Because the driver is a thin broadcast bridge, features needing message history, presence semantics, or server-side channel authorization must be assessed against Centrifugo's own capabilities — informing which real-time features are cheap vs. expensive.
When to Consider This Package
Consider it when:
- The product needs server-push updates (notifications, live feeds, chat, presence, live counters) and the team has chosen Centrifugo as the realtime server — typically for self-hosting, horizontal scale, and multi-protocol support (WebSocket, SSE, HTTP streaming).
- The stack is on Laravel 8.75 through 13.x / PHP 8.0–8.4, including teams currently planning a Laravel 13 upgrade — support is now CI-verified across that range, not merely declared.
- You want Laravel's familiar
broadcast() / event / channel abstractions to remain the developer interface, keeping realtime code idiomatic and cheap to onboard.
- You need a small, single-purpose dependency rather than a full realtime platform SDK.
Look elsewhere when:
- You are not running Centrifugo — this driver is Centrifugo-specific; Laravel Reverb, Pusher, Ably, or Soketi each have their own first-party or community paths.
- You need managed hosting with an SLA and vendor support contract; this is a community package with no commercial backing.
- The product requires guaranteed long-term maintenance, security response commitments, or an audited supply chain — a single-maintainer package in the critical path should be forked internally or replaced with a first-party option.
- Real-time needs are trivial and intermittent (a single notification badge) — polling or Laravel's built-in options may be cheaper than operating Centrifugo.
- You require deep Centrifugo features (history, delta compression, presence APIs beyond basic channel auth) exposed as first-class Laravel APIs — you may end up calling Centrifugo's HTTP/GRPC API directly anyway.
How to Pitch It (Stakeholders)
To executives: This is a small, free, open-source connector that lets our Laravel application push live updates — notifications, chat, dashboards — through Centrifugo, a self-hosted realtime server. The new v3.0.2 release matters for two business reasons: it removes a blocker on our Laravel 13 upgrade by officially supporting Laravel 8.75–13.x on PHP 8.0–8.4 with CI-verified testing, and the maintainer has added a full test suite and code-quality pipeline, which materially lowers the risk of adopting a single-maintainer dependency. Cost profile is favorable versus managed services like Pusher or Ably at scale, since Centrifugo is self-hosted and the driver is free; the trade-off is that we, not a vendor, operate it.
To engineering: v3.0.2 is a compatibility and hygiene release, not a feature release. It adds laravel/framework ^13.0, orchestra/testbench ^11.0, and phpunit ^12, with the CI matrix now actually running against Laravel 13 on PHP 8.3/8.4 — compatibility is verified, not just declared. Flaky timeout/retry tests were made deterministic by dropping the external httpstat.us dependency, and 100% coverage plus Pint/PHPStan pipelines were added. No breaking API changes are indicated; the practical action is to confirm our Centrifugo server version and channel-auth setup still align, then treat the Laravel 13 bump as unblocked. Recommendation: adopt behind a thin internal broadcast abstraction so the transport stays swappable, and budget a small maintenance allowance given single-maintainer risk.