Realtime channel messaging

Pusher pushes messages to connected clients over live channels, and a Beam agent both posts to and listens on those channels. When an upstream event occurs, the agent reads the source record, formats the payload per your rule, and posts it to the channel your app subscribes to, so users see the change at once. It records each message it sent. A payload missing a required field, or aimed at a channel not on your approved list, is withheld and raised to a developer, keeping malformed or misrouted events off your live app.

Presence and membership events

Pusher follows who is present on a channel, and a Beam agent can react as members join or leave. Subscribed to a presence channel, the agent reads each join and leave event, updates your own record of active users, and applies the rule you set, perhaps greeting a new participant or freeing a seat when one exits. Ordinary changes are handled quietly. A pattern that breaks your rules, like a single account holding far more sessions than allowed, is flagged to an operator so a person can judge whether it signals a problem.

Client event broadcasting

Pusher can relay events sent straight from clients, and a Beam agent supervises that traffic against your policy. As client events arrive, the agent reads the type and payload, confirms the sender is allowed to emit it, and forwards the ones that pass to the intended subscribers while recording the exchange. Well-formed, permitted events move through without delay. An event from an unverified client, or one carrying a payload shape your rules do not recognize, is dropped from the live flow and reported to a developer for a closer look rather than reaching users.