Soketi

Soketi implements the Pusher Channels HTTP API: POST /apps/{app_id}/events (trigger event), POST /apps/{app_id}/batch_events (batch), GET /apps/{app_id}/channels, GET /apps/{app_id}/channels/{channel_name}, GET /apps/{app_id}/channels/{channel_name}/users. Authentication follows the Pusher server-auth scheme (HMAC-SHA256 signature). Any Pusher server SDK (Node, PHP, Python, Ruby, Go) works with Soketi by pointing to the Soketi server host. The protocol compatibility is the key value proposition.

Soketi returns Pusher-compatible JSON responses and error formats. Event trigger success returns { ok: true }; failures return Pusher-style error objects. HTTP 400 for malformed requests, 403 for auth failures, 200 for successful publishes. Self-hosted reliability depends on your deployment; no SLA. Scale-out is possible via Redis adapter for multi-node deployments. Maintenance mode uncertainty (2026) is the primary operational risk.

Soketi is an open-source, self-hosted Pusher Channels-compatible WebSocket server. It implements the Pusher API protocol, meaning any app using the Pusher client SDK can switch to Soketi by changing the host configuration — no code changes required. Agents can publish events to Soketi using the standard Pusher server-side API (same endpoint structure, same auth). This is useful for teams that want Pusher's real-time event model without Pusher's per-message billing. Self-hosted via Docker or Node.js. Maintenance activity in 2026 should be verified — the project's pace varied in 2023-2024. Confidence is docs-derived.

Authentication mirrors Pusher's security model: app_id, app_key, and app_secret are configured server-side. Server-to-server API calls use Pusher's HMAC signature scheme (the Pusher SDK handles this). Client WebSocket connections authenticate via signed tokens from your backend. The Soketi server config controls app credentials; secrets must be managed in your deployment environment. No centralized credential management — self-hosted deployments own their security posture.

Documentation at docs.soketi.app covers installation, configuration, Pusher SDK usage, and deployment guides. The documentation is clear for the core use case (drop-in Pusher replacement). Advanced configuration (custom adapters, Redis scaling) is documented. Community support via GitHub and Discord. Documentation quality is good for the primary use case. Given potential reduced maintenance activity, the official Pusher documentation serves as a useful secondary reference for the API protocol.