# Worker node

It is where the actual rendering takes place. Each Worker Node is equipped with a tool called the Render Engine Controller, along with one or several render software or render engines, such as Blender Cycles, V-Ray, Keyshot, D5 Render, Octane, etc. See the [rendering flow](https://docs.inferix.io/inferix-whitepaper/decentralized-visual-computing/pages/Di2djAZNb70Mcrxp34yf##fig_rendering_flow) for more details.

The render engines utilized by Worker Nodes typically rely on path-tracing/ray-tracing techniques, which demand substantial compute resources. Some of these engines are open-source and free, such as Cycles, while others, like V-Ray, are paid software. If there are any render engine costs, they will be factored into the rendering price that the Inferix network charges users.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.inferix.io/inferix-whitepaper/decentralized-visual-computing/worker-node.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
