Pubcontrol Laravel Package

Product Decisions This Supports

• Real-time feature feasibility: Informs whether a Laravel product can publish events to a Fanout/EPCP-backed real-time delivery layer for notifications, live dashboards, chat, collaborative features, or event fan-out.
• Build vs. buy / vendor strategy: Supports evaluation of using a hosted pub/sub delivery service versus building or buying a modern Laravel-native real-time stack.
• Legacy maintenance vs. migration: If the product already depends on Fanout/EPCP, this package anchors a decision to keep, fork, wrap, or replace the integration.
• Roadmap risk assessment: Low adoption, archived status, and zero dependents make this a poor foundation for new roadmap commitments; it should be treated as legacy or experimental.
• Architecture scoping: Clarifies that this is a protocol/client library—not a full real-time server—so product decisions still need a delivery backend, authentication model, channel design, and Laravel integration layer.
• Use-case prioritization: Useful only for products with a concrete EPCP/Fanout publishing requirement; not a differentiator for typical Laravel SaaS features.

When to Consider This Package

Consider it only when:

• You have an existing Fanout/EPCP integration in a PHP/Laravel system and need to maintain or temporarily extend it.
• You are doing a short-lived migration or proof of concept where the EPCP protocol is fixed by an existing backend.
• You can vendor/fork the MIT-licensed code and accept ownership of security, compatibility, and PHP/Laravel upgrades.
• The integration surface is small enough to isolate behind an internal interface so it can be replaced later.

Look elsewhere when:

• You are building a new real-time feature in Laravel. Prefer actively maintained options such as Laravel Reverb, Pusher, Ably, Soketi, Mercure, or SSE-based approaches.
• You need community support, frequent releases, or a large ecosystem. This package is archived, has minimal stars, and no dependents.
• You need a Laravel-native package with service providers, configuration publishing, queues, broadcasting integration, and documented upgrade paths.
• You require long-term vendor viability or contractual support. Archived status is a material product risk.
• You need more than publishing: presence, authorization, delivery guarantees, observability, or WebSocket lifecycle management are not solved by this library alone.

How to Pitch It (Stakeholders)

Executive summary: fanout/pubcontrol is an archived MIT-licensed PHP client for Fanout’s EPCP pub/sub protocol. It is not a Laravel-native real-time platform and should not be used as the foundation for new product roadmap commitments. Its value is limited to maintaining or migrating existing EPCP/Fanout integrations. The low adoption and archived status create maintenance and hiring risk with little strategic upside.

Engineering summary: The package provides a small protocol client for publishing messages through EPCP. It does not provide the real-time server, Laravel broadcasting integration, channel authorization, or operational tooling. For new work, evaluate Laravel Reverb or a maintained hosted provider. If the business must retain an existing Fanout dependency, isolate this library behind an internal adapter, budget for fork/maintenance ownership, and plan a migration path rather than expanding its role.