Worker Protocol

Status: internal-only today; public specification is a deferred follow-up.

If you operate a Sogni worker node today, you do so as a partnered operator with direct support from the Sogni team. This page exists so the gap is visible — there is currently no published protocol specification that an external operator could implement against.

#What's published

The high-level Supernet overview describes worker registration, app-ID derivation, project lifecycle, and the role of sogni-socket (the WebSocket job network) and sogni-api (the REST + run-state surface) at a conceptual level. That is sufficient to understand how workers participate, but not to implement a new worker.

#What's not published (yet)

The following components define the wire-level worker contract and are currently internal:

• sogni-socket message format — the JSON envelope and event lifecycle for job messages, progress updates, project state transitions, and cancellation signals.
• sogni-llm-nvidia worker contract — the supervisor protocol for multi-GPU vLLM workers (process supervision, model loading, per-GPU socket attachment).
• ComfyUI/worker image/video render contract — the ComfyUI-derived inference protocol used by image and video workers.

#Why deferred

Opening the worker protocol to external implementations is a meaningful platform commitment: protocol changes become a public API surface that operators depend on, and abuse/sybil resistance considerations multiply. The Sogni team has scoped this as a future phase rather than rolling it out implicitly through documentation. The current generation of workers ships with the Sogni node software directly.

#When the spec will land

There is no committed date. The deferral is tracked internally; this page will be replaced with the protocol specification once it ships.

#If you want to operate a worker today

Reach out to the Sogni team at [email protected] — partnered operators get direct guidance on the current protocol shape and any safety/compliance considerations.