How client connections flow through the wSocket infrastructure
Event-driven runtime optimized for high-throughput I/O. Handles thousands of concurrent WebSocket connections per instance.
Blazing-fast, production-grade WebSocket implementation for Node.js. Minimal overhead, maximum performance.
In-memory data store used as a distributed pub/sub broker. Routes messages across server instances in microseconds.
Document database for message persistence, accounts, app metadata, analytics, and webhook configurations.
From publish to delivery in under 5ms — here’s how messages travel through the system
A client sends a message over its WebSocket connection to a specific channel. The server validates auth, rate limits, and channel permissions.
The WebSocket handler validates the message, deduplicates it, and routes it to the Channel Manager. If history is enabled, the message is persisted to MongoDB.
The Redis broker broadcasts the message to all server instances in the cluster. Each instance receives the message via Redis pub/sub in microseconds.
If webhooks are configured, the Webhook Manager sends HTTP callbacks with HMAC-SHA256 signatures to your endpoints with automatic retries.
Each server instance delivers the message to locally-connected subscribers on that channel. Delivery happens over WebSocket with zero polling.
A modular, pluggable architecture where each concern is isolated into its own manager
Manages raw WebSocket connections, protocol framing, heartbeat, and connection lifecycle.
Channel subscriptions, multiplexing, and fan-out delivery to subscribers.
JWT token validation, API key verification, and per-channel permission enforcement.
Distributed pub/sub message routing across all server instances in the cluster.
Real-time member tracking with custom state data and join/leave events.
MongoDB-backed message persistence with TTL, pagination, and time-range queries.
Configurable rate limiting per app, per channel, and per user with sliding window algorithm.
HTTP webhook delivery with HMAC signatures, retry policies, and event filtering.
Multi-provider push notification delivery: Web Push (VAPID), FCM, and APNs.
User accounts, teams, roles, and dashboard authentication with JWT sessions.
Multi-app management, API key rotation, and per-app configuration.
Usage enforcement against plan limits with real-time quota tracking.
Add server instances behind a load balancer. Redis broker ensures all instances share messages seamlessly.
Multiple channels over a single WebSocket connection. No per-channel overhead or connection bloat.
SDKs handle disconnects with exponential backoff. Clients resume subscriptions without data loss.
Built-in dedup layer prevents duplicate delivery in multi-node clusters with at-least-once semantics.
Rolling deployments with connection draining. Clients reconnect to new instances transparently.
Run wSocket on your own infrastructure, or use our managed cloud
Clone, install, and start the full stack — backend, Redis, and MongoDB.
Zero-ops deployment with automatic scaling, monitoring, and global edge nodes.
Join developers building the next generation of realtime applications.