Sockudo documentationSupport the project

Own realtime infrastructure without giving up Pusher compatibility.

Sockudo is a Rust realtime server for teams that want the familiar Pusher protocol, Protocol V2 durability, horizontal fanout, recovery, push, SDKs, and AI transport in one self-hosted control plane.

Start building First connection Protocol reference

sockudo-control

localhost:6001

Online

Quick start

Run the servercargo run --release --features full

Connect a clientprotocolVersion: 2

Publish safelyidempotency_key: order-created

Live delivery

Presence synccluster registry4 nodeshealthy

Order fanoutcross-node publish18.4k/sfanout

History rewindcontinuity check12 msgapless

Push publishprovider queuequeueddurable

Documentation map

Start with the decision you are making.

The homepage routes operators, backend teams, client developers, and AI product teams into the part of the docs that answers their next production question.

Start here

Launch the server

Install Sockudo, choose a runtime, configure apps, and get a local realtime endpoint running.

Open guide Realtime SDKs

Connect clients

Use JavaScript, Swift, Kotlin, Flutter, and .NET clients with Protocol V1 or Protocol V2.

Open guide Production ops

Operate the cluster

Plan scaling, metrics, webhooks, rate limits, queues, durable history, and recovery paths.

Open guide AI native

Build AI transport

Layer agent streams, rollups, push, annotations, and recovery on the same durable primitives.

Open guide

Runtime architecture

A compatibility layer that grows into a durable platform.

Sockudo keeps the Protocol V1 contract stable while Protocol V2 unlocks history, recovery, annotations, push delivery, and AI stream primitives on the same fanout core.

Read history and recovery

Sockudo architecture diagram showing clients, adapters, queues, cache, app manager, metrics, webhooks, and storage.

Production surface

Everything operators expect before realtime becomes critical path.

Compatibility is the on-ramp. The docs also cover the stateful, distributed, and observable pieces that make Sockudo viable when missed events are not acceptable.

Pusher-compatible edge

Protocol V1 keeps Channels clients, Laravel Echo, and server SDK expectations intact.

Protocol V2 control

Native prefixes, message IDs, serial continuity, filters, deltas, annotations, and rewind.

Horizontal fanout

Redis, Redis Cluster, NATS, Kafka, RabbitMQ, Pulsar, Google Pub/Sub, Iggy, or memory.

Durable recovery

Hot replay buffers, durable history, opaque cursors, presence history, and mutable messages.

Push and webhooks

Device registration, provider status, scheduled notifications, retries, and delivery signals.

Operator visibility

Health probes, readiness, Prometheus metrics, webhooks, auth, quotas, and failure surfaces.

SDK shelf

Client and server SDKs stay close to the protocol.

Every official SDK path includes installation, configuration, authentication, publish flows, history, and production guidance for teams adopting Sockudo incrementally.

@sockudo/client