Base
Hardened build
minimal ports, security patches applied at build time
Sockudo on Ubuntu 24.04 LTS
Azure
Streaming & Messaging
Sockudo is a realtime WebSocket server that speaks the Pusher protocol, so the browser and server SDKs your application already uses connect to infrastructure you own.
Overview
Sockudo is a realtime messaging server written in Rust that implements the Pusher protocol end to end. Browser clients open a WebSocket, subscribe to channels and receive events as they happen, while your backend publishes those events over a signed HTTP API, which is the same shape of integration teams already write against hosted realtime services. Because the protocol matches, existing client and server libraries connect to it without being rewritten, and the messaging your application depends on moves onto infrastructure you control and can put inside your own network. It carries public, private and presence channels, client events, channel and presence introspection, and a Prometheus metrics endpoint, and it is deliberately lean: a single compiled binary holding all of its state in process, with no database, no broker and no cache server to operate alongside it.
Why the cloudimg image
Sockudo ships upstream with a working application whose id, key and secret are published in its own repository and documentation, which on a public network means anyone who has read those docs can publish to and subscribe from every channel. This image ships no application at all, so that credential never exists here. Your machine generates its own application key and secret from system entropy on first boot, along with its own TLS certificate, and the server is gated so that it physically cannot start until those exist; it also refuses to start at all if it ever finds one of the published credentials in effect. The server itself listens only on loopback, TLS terminates in front of it, and the unauthenticated metrics and usage endpoints upstream exposes by default are closed or bound to loopback. Every one of those claims is proven on each fresh machine by an end to end check that publishes an event over the signed API and confirms it arrives at a separately connected subscriber, then confirms that forged signatures and the published credentials are rejected while yours still works. A paired deployment guide and 24/7 support are included.
Common uses
- Live dashboards, notifications and activity feeds pushed to browsers as events happen
- Collaborative and multiplayer features needing presence and low latency channels
- Moving an application off a hosted realtime service onto infrastructure you control
More in Streaming & Messaging
AKHQ for Apache Kafka on Ubuntu 24.04 LTS
Streaming & Messaging
AKHQ for Apache Kafka on Ubuntu 24.04 LTS preconfigured machine image for Microsoft Azure, hardened and verified with 24...
Apache ActiveMQ Artemis on Ubuntu 24.04 LTS
Streaming & Messaging
Apache ActiveMQ Artemis is the next generation, high performance, multi protocol Java message broker that implements the...
Apache BifroMQ (Incubating) MQTT Broker
Streaming & Messaging
Apache BifroMQ (Incubating) is a distributed MQTT broker written in Java, built around native multi tenancy.
Apache Iggy on Ubuntu 24.04 LTS
Streaming & Messaging
Apache Iggy is a persistent message streaming platform written in Rust that moves millions of messages per second over T...
Apache Kafka 4.2 on Ubuntu 22.04
Streaming & Messaging
This image runs Apache Kafka 4.2.0 as a single node KRaft broker on Ubuntu 22.04 LTS. The broker process combines the co...
Apache Kafka 4.2 Ubuntu 24.04
Streaming & Messaging
Apache Kafka 4.2 Ubuntu 24.04 preconfigured machine image for Microsoft Azure, hardened and verified with 24/7 support b...