About QPub
QPub is a cloud messaging platform for real-time publish/subscribe and durable job queues. You create a project, issue API keys, then connect clients over WebSocket or call the REST API.
Use QPub when you need:
- Live updates to browsers or devices (notifications, dashboards, chat)
- Server-side publish without maintaining a WebSocket connection
- Background jobs with pull-based workers
Products
| Product | Transport | Typical use |
|---|---|---|
| Channels | WebSocket + REST publish | Real-time pub/sub fan-out |
| Queues | REST | Durable jobs, delayed/scheduled work |
How it fits together
- A user signs into QPub Cloud and belongs to an account.
- The account owns projects. Each project is isolated.
- Projects have API keys. Keys authenticate client apps.
- Clients use a key (or a short-lived JWT) to:
- Connect to the Socket API and subscribe/publish on channels
- Call the REST API to publish, issue tokens, or manage queues
Default cloud hosts:
- REST:
https://rest.qpub.io/v1 - WebSocket:
wss://socket.qpub.io/v1
Official SDKs
QPub ships official clients for JavaScript/TypeScript, React, and Go. All expose the same surfaces:
QPub.Socket— WebSocket client (subscribe + publish)QPub.Rest— HTTP client (publish, tokens, queues)
See Quickstart and SDKs.
Scope
- QPub authenticates your apps to messaging APIs. End-user login for your product is your responsibility.
- Channels are named topics — there is no separate create-channel step.
- Cloud login (email/password or OAuth) is separate from API key / JWT auth.