Appearance
Real-time Laravel with Reverb: live orders, a notification bell and edit locks, without code
A shop owner keeps the order list open all morning and sees nothing new until they press F5. An editor fixes a typo in a post while a colleague rewrites its second half, saves last, and the typo is back. A customer waits on their account page for "Shipped" that came an hour ago. Every one of these is a page that does not know the site has changed.
Laravel has had the answer for a while: broadcasting, and since 2024 its own WebSocket server, Reverb. What it does not give you is the wiring — which events go out, on which channels, who may listen to which, what the browser does with them, what happens when the WebSocket server is down during a checkout. That wiring is the same work in every project. kitloom/ is that work done once, for every module of the site.
What changes on its own
With the Live module on and Reverb running beside the site:
| Where | What updates without a reload |
|---|---|
| The admin's bell | Each notice of an Admin channel — a new order, a booking request, a comment waiting — rings the bell of everyone who may see it, the moment it comes |
| The shop's order list | A new order is at the top of the list with "New order #1043" in the corner; an order completed elsewhere changes its status in the list |
| A post open twice | Whoever opens it second sees "Anna is editing this" and reads it; Take over gives it to them and turns Anna's form read-only, her unsaved text still there |
| The AI assistant | An answer goes on when you move to another page, and the chat there picks it up where it is |
| Pages of the site | A comment approved in the admin appears under the post; a customer's order that ships, and a client's booking that is confirmed or moved, show in their account |
The pages of the site update on the Vue and React themes, through Inertia's live props: a part of the page says which event refreshes it, and Inertia asks for that part again when the event arrives. A Blade theme draws the same page as before and shows the change on a reload.
Nobody's data on the wire
A broadcast says that something changed, never what. The order list hears "order 1043, processing, new" — no name, no address, no total — and reads its rows again itself, with the rights of whoever is looking. A comment's page hears that the post has a new comment and asks for the comments as that visitor sees them: the author of a held comment sees it, nobody else does.
Every private channel is checked against the site's own permissions: the order list's channel is for whoever may manage orders, a post's editing channel for whoever may edit that post, a bell and an account for their owner alone. Channel names carry the site's prefix, so the sites of a multisite, or a hundred sandboxes on one server, never hear each other.
When Reverb is not there
Nothing breaks. A broadcast goes out after the database commits and never at the cost of the write: Reverb down during a checkout costs the live update, not the order. The bell looks for news every 30 seconds, the order list shows what was there when it was opened, and the assistant streams its answer in the request as it always did.
The protection against overwriting does not need Reverb at all. Every edit form remembers the version of the post it opened, and a save over a newer one is refused with the name of who saved it and when:
Not saved: Anna Berg changed this record at 10:42, after you opened it. Reload the page to see the new version.
What you typed stays on the form. The same check holds for an AI agent: get_ hands it the record's version, and update_ with an old one is refused, naming who saved since — the agent reads the record again and redoes its change instead of undoing someone's work.
Setting it up
- Switch the module on (Modules screen, or
composer require kitloom/).live kitloom/ live- filament - Keep
php artisan reverb:running: supervisor, systemd, Forge's daemons.start - Let the web server pass
/on to Reverb, so browsers connect to the site's own address — no second port, no second certificate.app/ …
There are no keys to type: the site and Reverb make them from the application key. php artisan kitloom: writes the Reverb process, the nginx lines and the restart after a deploy for a plain server, Forge, Ploi, Docker or DigitalOcean's App Platform. The admin's Live section says whether Reverb answers — running, not running — and php artisan live: says the same on the server.
Your own live part
A module of your own makes a part of its page live with one interface: Live answers the event whose broadcast refreshes the part there. The event is an ordinary Laravel Should on a channel from Live, sent through Broadcasts:: — after the commit, failures reported and swallowed. No JavaScript: the theme's build adds the listening part by itself while the module is installed. The rules are in the Live guide.
Watch it
Four short lessons from the admin, narrated:
Try it
Everything above — the server, the settings, the channels, the parts of every module — is in the Live guide. How the notification channels work outside the admin is in Telegram and Slack notifications in Laravel.