Low latency messaging via persistent open connections to any device, and delivering messaging worldwide in 100ms.
Small, high-volume, low-cost messages for typing indicators, lat/long readings, and more.
Retrieve past messages (like chat history) with a simple API for accessing historical data with EU/US-only storage options.
Combine up to 10,000 individual channels into a single connection so user/device can subscribe to unique combination of message streams.
Combine up to 10,000 individual channels into a single connection for more efficient, and better optimized, messaging.
Filter channels based on message metadata, so each device receives only the messages they need.
Connect existing MQTT-supported devices quickly and leverage the power of PubNub.
Build enterprise applications with confidence, meeting rigorous security and compliance requirements.
The PubNub Data Stream Network is a globally-scaled, battle-tested real-time IaaS, handling 1.3 trillion messages to 330 million devices monthly.
Built-in resilience – message caching and catch up, redundancy, network failover – delivers real-time functionality with confidence.
Multiple global points-of-presence guarantee message delivery no matter how many devices are connected.
Enterprise-grade security, including end-to-end AES-based encryption and mission-critical compliance, including SOC 2 Type II and HIPAA.
Deliver chat messages, alerts, in-app chat, and chatbots for web, iOS, and Android chat.
Track live geo-coordinates and update an interactive map.
Trigger device action and monitor its state.
The immediate and responsive experience created by real-time interactivity had the potential to create an impression that there was a tangible connection between the audience’s personal devices with the billboard, and enhance the urgency and drama of the campaign we had in mind.
Using PubNub was more cost effective than trying to build this capability ourselves. We don’t have to implement, and more importantly, operate a real-time infrastructure meeting high scalability, performance and reliability requirements.
Before we discovered PubNub, we had several engineers spend the better part of a year trying to build the basics of real-time publish-subscribe functionality. It was complicated, expensive to build and maintain, and lacked functionality. We quickly shut that product down when we discovered PubNub because it was clear that PubNub was going to be a more affordable, faster, and more reliable solution.