See every event your app broadcasts
Your app pushes live updates through Laravel Reverb, Pusher or soketi: «order shipped», «new message». When the browser shows the wrong thing, you want to see what the server actually sent. Point your backend at Buggregator, and every broadcast shows up with its channel and data. It can pass each event on to your real server, so the browser keeps getting live updates.

Channels on the left, their events on the right. Open an event for its payload, what changed and the signature check.
What your backend really sent
Each broadcast is one event in Buggregator, grouped by channel, updated live.
Every broadcast, as sent
Event name, channels (public, private, presence, encrypted or user), data and socket id. A batch gives one event per item, marked with the same batch.
A console per channel
Channels on the left, with their kind and number of events; type to filter them. Their events on the right, newest or oldest first: time, name, size, payload.
What changed
Open an event to see what changed since the previous event of the same name on that channel, who sent it and to whom.
Live updates keep working
With upstream set, each event goes on to your real Reverb or Pusher server and your app gets its answer. Real server down? Your app gets 502 with the reason, and the event is still stored.
Signature check
List your app keys and secrets, and each event says valid or invalid. The secret is never stored; a user name and password in the upstream address are not shown.
Warnings and cURL
Warnings for data over 10 KB, more than 100 channels, no channel, data that is not JSON and a wrong signature. Copy as cURL gives the request to send it again.
The order page didn’t update. Was the event sent?
Open the orders channel in Buggregator. If App\Events\OrderShipped is there, the backend did its part: look at the payload and at what changed since the previous one. If it is not there, it never reached Buggregator: look at the backend first. With upstream set, the event also shows the real server’s answer.
Setup in 60 seconds
No registration. No account. Start it and point your app at it.
Start Buggregator
Requires Buggregator v2.13.0 or later. Broadcasts arrive on port 8000, the same port as the UI. Nothing to turn on. One file, about 40 MB, installed with one command. Prefer containers? Use the Docker tab.
$ curl -fsSL https://raw.githubusercontent.com/buggregator/server/master/scripts/install.sh | sh $ HTTP_ADDR=127.0.0.1:8000 \ SMTP_ADDR=127.0.0.1:1025 \ VAR_DUMPER_ADDR=127.0.0.1:9912 \ MONOLOG_ADDR=127.0.0.1:9913 \ PROXY_ADDR=127.0.0.1:8080 \ ~/.local/bin/buggregator
The script picks the file for your CPU: Intel/AMD or ARM.
One file for Linux, macOS and Windows, about 40 MB. Nothing else to install.
Runs on Windows, macOS and Linux, on Intel/AMD and ARM.
Prefer not to do it yourself? Your AI agent can set Buggregator up for you →
Send your broadcasts to Buggregator
Only the server side changes: your backend sends broadcasts to Buggregator. The browser keeps connecting to the real Reverb or Pusher.
BROADCAST_CONNECTION=reverb REVERB_APP_ID=... REVERB_APP_KEY=... REVERB_APP_SECRET=... # Laravel sends broadcasts to Buggregator REVERB_HOST=127.0.0.1 # host.docker.internal when Laravel runs in Docker and Buggregator on the host REVERB_PORT=8000 # Buggregator's HTTP port REVERB_SCHEME=http # Echo in the browser connects to Reverb directly VITE_REVERB_APP_KEY="${REVERB_APP_KEY}" VITE_REVERB_HOST=localhost VITE_REVERB_PORT=8080 # Reverb's port VITE_REVERB_SCHEME=http
php artisan install:broadcasting writes VITE_REVERB_HOST="${REVERB_HOST}". Once REVERB_HOST points at Buggregator, the browser would go there too, and Buggregator does not speak WebSocket. Keep VITE_REVERB_HOST and VITE_REVERB_PORT on Reverb itself, as above. Older Laravel apps use BROADCAST_DRIVER instead of BROADCAST_CONNECTION.
Keep live updates working: pass events on
Without this, Buggregator only captures: your app gets «ok», and browsers get nothing. Set upstream to your real server, and each event is stored and then sent on. Keep your real app id, key and secret in the app: Buggregator sends the same path, query and body, so the real server accepts the signature.
$ BROADCAST_UPSTREAM=http://localhost:8080 ./buggregator
Optional: check signatures
List your apps, and Buggregator checks each event’s signature with the secret. The event then says valid, or invalid with a warning. Keys not in the list say not_checked.
broadcast:
apps:
- key: app-key
secret: app-secret
Broadcast an event — open Broadcast in the menu
Trigger the event in your app. It shows up under its channel, with its name and payload. In Buggregator the event name is the full class name, for example App\Events\OrderShipped; Echo’s .listen('OrderShipped') keeps working.
Works with the Pusher HTTP API
Your backend sends each broadcast as an HTTP request to the broadcast server. Buggregator answers those requests in its place.
What it does not do
- It does not speak WebSocket. Browsers still connect to the real Reverb or Pusher.
- Without upstream, live updates stop while your app points at Buggregator.
- Channel queries (GET /apps/<id>/channels) are not supported: send them to the real server.
- Data on encrypted channels is stored as sent; Buggregator cannot decrypt it.
- Only signed POST requests count as broadcasts. A POST without a signature is stored as an HTTP dump.
Ready to try it?
One command to start. No account needed.
Also built into Buggregator