Weave Code
Brain Socket Laravel Package
brainboxlabs/brain-socket
BrainSocket adds real-time WebSockets to Laravel apps. Run a dedicated socket server, broadcast server-side events to connected clients, and handle client messages through a simple Laravel-friendly API—ideal for live notifications, chat, and dashboards without a third-party service.
Websockets for event-driven laravel apps.
Frequently asked questions about Brain Socket
- Is brainboxlabs/brain-socket still maintained?
- No. The repository is archived, so there is no active maintenance, no security patches, and no compatibility work for recent Laravel or PHP releases. Treat it as frozen software and expect no upstream response if a protocol or dependency breaks. For new work, evaluate Laravel Reverb, Soketi, or Pusher first.
- How do I install brain-socket in a Laravel application?
- Install it with Composer, register the package service provider, and add a brain-socket connection to config/broadcasting.php. Point that connection at Redis, run the standalone Node.js socket server, and switch your front end to the package client. This is only low-friction on the exact Laravel, PHP, Node, and Redis versions the package was frozen against.
- Does BrainSocket support Laravel 11 or Laravel 12?
- There is no evidence of Laravel 11 or Laravel 12 support. The repository is archived, and the evaluation notes that no compatibility work has been done for recent Laravel and PHP releases. Pin and verify the exact versions before any spike, and assume unsupported on anything newer.
- Do I need Redis to use BrainSocket?
- Yes. The Laravel-side broadcast driver publishes events into Redis pub/sub, and the Node process fans those events out to connected clients. Redis is often already present for queues and cache, which lowers marginal cost, but it becomes a new failure domain for real-time traffic. Plan for how the UI degrades if Redis or the socket tier fails.
- Do I need to run a Node.js server with BrainSocket?
- Yes. BrainSocket is a two-part system: a standalone Node.js WebSocket server plus a Laravel broadcast driver. That means a long-lived Node process on your platform, which fits poorly with PHP-only shops, shared hosting, and some serverless PHP runtimes. You also need to keep the client JavaScript version-aligned with the server.
- What is BrainSocket used for?
- It adds real-time WebSockets to event-driven Laravel apps without a third-party service. Typical uses are live notifications, chat, and dashboards, with server-side events broadcast to connected clients and client messages handled through a Laravel-friendly API. The architectural cost is a second runtime and a Redis pub/sub channel on your critical path.
- What are the best alternatives to BrainSocket for Laravel WebSockets?
- Laravel Reverb is the first-party option, with Soketi and Pusher as other common choices. Reverb has a similar Redis pub/sub shape and an Echo client that is a near-conceptual match, so a spike is measured in hours. BrainSocket uses a bespoke client contract, so moving away later is not a drop-in swap.
- Can I use BrainSocket in production?
- Only with high caution. The dominant risks are abandonment, missing PHP 8.3/8.4 and Laravel 11/12 support, protocol lock-in, and no vendor or SLA to escalate to. If you must run it, pin the full stack, document an internal owner willing to fork and maintain the Node server, and define the blast radius when the WebSocket tier fails.
- How does BrainSocket work architecturally?
- A Laravel broadcast driver publishes server-side events into Redis pub/sub. A standalone Node.js WebSocket server consumes those messages and fans them out to connected clients. The front end uses the package's client JavaScript, which must stay version-aligned with the server.
- How do I test a Laravel app that uses BrainSocket?
- There are no maintained first-party testing helpers described, and the Node server plus Redis pub/sub are part of the real-time path. Unit tests can fake events and broadcaster calls, but end-to-end verification needs the Node process and Redis running. Because the package is archived, budget for writing and owning those tests yourself.
Weaver
How can I help you explore Laravel packages today?