Source: https://docs.sogni.ai/run-a-worker/supernet/worker-protocol/

# 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.

## [#](https://docs.sogni.ai/run-a-worker/supernet/worker-protocol/#whats-published)What's published

The high-level [Supernet overview](https://docs.sogni.ai/run-a-worker/supernet/about-sogni-supernet/) 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.

## [#](https://docs.sogni.ai/run-a-worker/supernet/worker-protocol/#whats-not-published-yet)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.

## [#](https://docs.sogni.ai/run-a-worker/supernet/worker-protocol/#why-deferred)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.

## [#](https://docs.sogni.ai/run-a-worker/supernet/worker-protocol/#when-the-spec-will-land)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.

## [#](https://docs.sogni.ai/run-a-worker/supernet/worker-protocol/#if-you-want-to-operate-a-worker-today)If you want to operate a worker today

Reach out to the Sogni team at [hello@sogni.ai](mailto:hello@sogni.ai) — partnered operators get direct guidance on the current protocol shape and any safety/compliance considerations.