New in 5.2AI Transport — durable token streaming

Realtimeinfrastructureyou own.

A high-performance, self-hosted WebSocket server written in Rust. Keep the Pusher clients you already ship — then unlock recovery, history, mutable messages, push and AI streaming the moment you need them.

curl --proto '=https' --tlsv1.2 -sSfL https://sockudo.io/install.sh | sh
  • Pusher Protocol V1 compatible
  • MIT licensed
  • 8 horizontal fanout backends
  • 16 official SDKs

Plugs into the stack you already run

Zero-rewrite migration

Change one hostname.
Keep every client.

Protocol V1 is a strict Pusher compatibility target: same channels, same auth signatures, same HTTP publish API. Point pusher-js or Laravel Echo at Sockudo and ship. Adopt Protocol V2 later, one app at a time.

  • Public, private, presence and encrypted channels
  • Pusher-signed HTTP API, batch triggers and webhooks
  • Opt-in Ably REST + WebSocket compatibility facade
Read the migration guide
realtime.ts+2 −1
1import Pusher from "pusher-js";2 3const pusher = new Pusher("app-key", {4-   cluster: "mt1",4+   cluster: "local",5+   wsHost: "realtime.example.com",6    forceTLS: true,7  });8 9  pusher.subscribe("orders")10    .bind("order.created", render);
Connected to Sockudo · protocol 7 · pusher:connection_established
How it works

One publish.
Every socket, every node.

Live simulation
  1. 01

    Publish once

    Your backend calls the signed HTTP API — or a server SDK — on any node. Idempotency keys make retries safe.

    POST /apps/:id/events
  2. 02

    Fan out across the cluster

    The adapter bus broadcasts to every node: Redis, Redis Cluster, NATS, Kafka, RabbitMQ, Pulsar, Google Pub/Sub or Apache Iggy.

    adapter.driver = "nats"
  3. 03

    Deliver to every socket

    Each node pushes to its local subscribers, applying tag filters and delta compression per connection before bytes hit the wire.

    sockudo:message
  4. 04

    Recover what was missed

    A phone drops into a tunnel. On reconnect, Sockudo replays the gap from the hot buffer or durable history — or fails closed when continuity can’t be proven.

    recover { serial: 1042 }
AI Transport

LLM streams that survive reality.

Built on the same durable primitives as everything else — versioned messages, history, recovery, presence and push — instead of a fragile side-channel. Works with the Vercel AI SDK, OpenAI and Anthropic.

Token streaming with rollupAgents append tokens to a mutable message; egress rollup coalesces bursts so sockets aren’t flooded.
Resume mid-answerReload the tab or lose signal — the stream picks up from durable history, not from scratch.
Agent presenceKnow when an agent is thinking, streaming or idle through V2 presence updates.
Push when they leaveFinished runs can notify devices through the existing push pipeline and push rules.
Explore AI Transport
support-agentstreaming…
private-session-7f2
Why did my order sync fail last night?
● connection lost · resuming from serial 318
ai-output · v1appends 0rollup ×1.0
Horizontal scaling

Scale on the bus you already run.

Add nodes behind any load balancer. Sockudo coordinates fanout, presence and continuity through a pluggable adapter — no sticky-session gymnastics, no proprietary broker.

  • Ready for Kubernetes with a Helm chart and readiness probes
  • Duplicate suppression and continuity checks across nodes
  • App managers on MySQL, PostgreSQL, DynamoDB, ScyllaDB or SurrealDB
Scaling guide
RedisPub/Sub
Redis ClusterCluster mode
NATSSubjects
KafkaTopics
RabbitMQAMQP
PulsarTopics
Google Pub/SubManaged
Apache IggySingle or VSR cluster
MemorySingle node
Official SDKs

Subscribe anywhere.
Publish from anything.

Six realtime clients and ten server SDKs, all living in one monorepo and tested against the same server.

Realtime clientsBrowser, mobile, desktop
import Sockudo from "@sockudo/client";
const client = new Sockudo("app-key", {
wsHost: "realtime.example.com",
protocolVersion: 2,
});
client
.subscribe("orders")
.bind("order.created", (order) => render(order));
JavaScript guide
Server SDKsSigned HTTP publishing
import Sockudo from "sockudo";
const sockudo = new Sockudo({ appId, key, secret, host: "realtime.example.com" });
await sockudo.trigger("orders", "order.created", { id: "ord_123" }, {
idempotency_key: "order-created-ord_123",
});
Node guide
Choose per app

Compatible today. Native tomorrow.

CapabilityProtocol V1Protocol V2
Event prefixespusher:sockudo:
Pusher wire compatibilityStrictSockudo-native
serial + message_id—✓
Recovery & rewind—Hot replay + durable history
Mutable messages—✓
Annotations—✓
Tag filtering & deltas—✓
AI Transport—Optional feature
843 developers starred Sockudo

Ship realtime tonight.

One binary. Your infrastructure. Your data. Start with Docker in under a minute.