PubNub review

PubNub is a hosted real-time communications platform and managed messaging infrastructure, not a database library or a server you run in your own environment. An application publishes messages to named channels; subscribed clients receive them through PubNub’s global network. The service sits between your application clients and the real-time delivery layer, so your team does not have to build and operate that layer itself.

Its surrounding services include message persistence for clients reconnecting to missed messages, presence for tracking who is online, and data sync to keep application state consistent across users, devices and networks. Security features include per-user and per-channel permissions, encryption, audit logs and SSO. The platform also offers event forwarding and integrations with external systems. This fits chat, collaboration, live audience features and device control, where clients need shared updates without waiting for a polling loop. Your application still needs to define its data model and decide what belongs in PubNub versus its own database.

The programming model is publish/subscribe: call publish() to send a message and subscribe() to receive messages on a channel. The homepage also shows hereNow() and fetchMessages() alongside examples of filtering, grouping, annotating, persisting and moderating messages. PubNub’s site links to documentation, tutorials, demos and SDKs, and presents an MCP Server for real-time coding with AI. It does not name SDK languages in the homepage text, so confirm the SDK and platform support you need in the vendor’s docs before choosing an implementation.

Integrations extend the message path: the vendor lists mobile push notifications, event forwarding to Kafka, SQS, Kinesis, S3 and webhooks, plus a Kafka connector. Security features include expiring access tokens and per-user, per-channel permissions. The homepage also shows code for a Function, but teams should check the docs for its deployment and runtime details. Treat the publish/subscribe API, Functions and listed integrations as the integration surface; verify exact methods, platform support and behavior in the docs.

The Free plan costs $0 per month and covers up to 200 MAU or 1 million monthly transactions, with 1GB of storage for seven days. Starter is $98 per month and includes 1,000 MAU and up to six months of data storage, plus BizOps Workspace and Insights. Pro uses custom MAU packages and volume discounts; the pricing page gives 10,000 MAU at $550 per month and lists 50,000 MAU at $2,100, while also saying 50,000+ is custom.

That makes MAU and transaction usage the key budget checks as an app grows. Pro includes unlimited data storage and up to a 99.999% uptime SLA. The vendor mentions annual discounts for Pro but doesn't publish annual Pro rates or prices for Events & Actions, PubNub Insights, BizOps Workspace or Illuminate. Ask for an estimate based on your expected MAU, transaction volume, retention and required add-ons. Free and Starter prices are monthly; do not assume the displayed Pro examples establish the cost of every production workload.

PubNub is presented as managed infrastructure, so design for it as a hosted service rather than a server you can take over. The vendor doesn't publish an open-source license, a self-hosting option or a data-export procedure on its product pages; ask directly about export formats, retention and exit support before storing application-critical state there.

Migration effort depends on how much of the application uses PubNub-specific channels, permissions, persistence, presence and Functions. A replacement would need to provide the message delivery and any surrounding capabilities your code relies on, or you would need to rebuild those pieces. Keep durable business records in a system you control where appropriate, and isolate PubNub calls behind an application interface. That does not remove the dependency, but it gives you a clearer boundary if you later move to another hosted provider or operate your own messaging stack.

PubNub’s production case rests on managed global delivery, multi-region deployment, failover and region pinning. Its site lists an uptime SLA of up to 99.999% for Pro; confirm the contractual scope, exclusions and remedies with the vendor. Security features include TLS by default, end-to-end payload encryption, expiring access tokens, audit logs, SSO and data deletion on request. Check how those controls map to your compliance requirements rather than treating them as a certification.

Before launch, confirm transaction limits, rate limits, overage behavior, storage retention and the operational impact of outages or reconnects. Reddit reports are mixed and include user complaints about slow responses in Wink-connected devices and duplicate messages in a React Native chat integration. Those reports are anecdotal and do not establish a general service failure, but they make message handling, retry behavior and support escalation worth testing in your own design. Wink-related discussion also illustrates the risk of a third-party application changing its integration endpoint: your team may depend on both PubNub and the application provider.