/// Realtime infrastructure · Dubai
Pusher-compatible WebSockets with WhatsApp bots on the same channels. Point your existing Pusher SDK at PubSub and ship chat, notifications and live tracking today.
No credit card / Pusher protocol
/// What you can build
Bidirectional communication for live chats, in-app notifications and user tracking — without polling overhead.
Instantly see who is online and when they are typing, making conversations feel lively and connected.
Deliver events and updates the moment they happen — no polling, no delay.
Stream locations and status changes in real time for couriers, fleets and dashboards.
pubsub.trigger( "orders", "updated", { id: 4821 } )
/// Pusher protocol
One publish fans out to every subscribed client. Your existing Pusher libraries work as-is — change the host, keep the code.
/// Capabilities
Presence, typing, notifications and live updates — on one Pusher-compatible API.
Track who's online across channels for seamless team coordination
See when users are composing messages for natural conversation flow
Receive instant alerts for messages and system updates without polling
Monitor real-time locations and status changes with low latency
Drop-in replacement for existing libraries with zero code changes
Send messages to public/private channels with presence support
/// WhatsApp automation
Offer WhatsApp chat with bots on top of a socket-to-socket connection. Every message flows through the same real-time layer — no polling, no delay.
Connect your WhatsApp Business number and let bots handle conversations around the clock.
Design flows that greet, qualify, answer, and hand off to a human agent when it matters.
Messages travel over the same low-latency socket layer that powers the rest of PubSub.
/// Pricing
Choose a plan that fits your needs. Upgrade, downgrade, or cancel anytime with no hidden fees.
/// Dubai
Dubai-based hosting for <50ms latency to GCC users, bypassing international Pusher routing delays. Complies with UAE data residency for fintech and e-commerce apps.
PubSub holds a persistent WebSocket connection to every client, so events are pushed the moment they happen instead of being polled for. Messages typically reach connected users in under 100ms.