> For the complete documentation index, see [llms.txt](https://know.rendernetwork.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://know.rendernetwork.com/getting-started/generative-workflows-on-the-render-network/using-the-render-network-as-a-programmable-rendering-layer.md).

# Using the Render Network as a Programmable Rendering Layer

Across both workflows, the role of the Render Network is consistent:

* The **Render Network** performs GPU-intensive rendering
* The **Render Network API** enables programmatic job submission, tracking, and output retrieval

This allows generative Houdini workflows to scale beyond a single machine while staying integrated with existing creative pipelines.

***

### Generative Workflow Future Directions

<figure><img src="/files/9pPOGmFSHRiBJvIIRBHn" alt=""><figcaption></figcaption></figure>

MHX’s walkthrough shows how the Render Network API can be integrated directly into Houdini-based generative workflows - whether Houdini is running locally or via the Compute Network.

By treating the Render Network as a programmable rendering layer, artists and technical directors can extend procedural workflows while maintaining full creative control.

#### Potential Use Cases

**Large-scale generative art**

Build a single Houdini system, then let it generate hundreds or thousands of unique results. Each variation can be sent to the Render Network to render at scale, freeing artists from hardware limits and letting them focus on creative exploration instead of render management.<br>

<figure><img src="/files/Tx8bBl3Fzw7D7oT5iYYC" alt=""><figcaption></figcaption></figure>

\
**Data-driven visuals**

Scenes don’t have to be static. Data like financial activity, live feeds, or external datasets can drive motion, form, and composition inside Houdini. Using the Render Network, those evolving visuals can be rendered consistently and repeatedly as the data changes.

<figure><img src="/files/w2wXXeYwvTOl1vqwuZj5" alt=""><figcaption></figcaption></figure>

**Working beyond a single machine**

By running Houdini and Octane through the Compute Network, artists can work in virtual environments while still rendering on the Render Network. This makes it easier to work remotely, scale up complex systems, or run heavier workflows without changing how scenes are built.

<figure><img src="/files/fNnW4M2VvBssugBRg4mz" alt=""><figcaption></figcaption></figure>

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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://know.rendernetwork.com/getting-started/generative-workflows-on-the-render-network/using-the-render-network-as-a-programmable-rendering-layer.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.