# Using the Dispersed for Dockerized Compute
### Running Houdini and Octane via Dispersed
MHX also shows how the same [**Render Network API**](https://know.rendernetwork.com/getting-started/using-the-render-network-manager-app-and-render-network-api) workflow can be used when **Houdini and Octane are run on** [**Dispersed**](https://dispersed.com/).
In this setup, Houdini is packaged inside a **Docker container** and executed in a virtual compute environment instead of on a local workstation.
**At a high level:**
* Houdini and Octane run inside a Dockerized environment
* Procedural systems generate scenes as they would locally
* Scenes are packaged and submitted via the Render Network API
* The Render Network renders frames on decentralized GPU nodes
* Rendered outputs are retrieved for review or post-processing
The workflow remains artist-driven - the Compute Network simply provides a way to run familiar tools remotely and at scale.
***
### What is the Dispersed Compute Network?
The [**Dispersed**](https://dispersed.com/) compute network is a decentralized network of onboarded nodes designed to run general-purpose compute workloads.
Unlike the Render Network, which is optimized specifically for rendering, Dispersed can run containerized applications such as:
* Houdini
* Python tools
* Procedural systems
* Supporting scripts and services
In MHX’s workflow, the Compute Network is used to run Houdini and Octane virtually, while the Render Network handles the final GPU rendering.
---
# 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://know.rendernetwork.com/getting-started/generative-workflows-on-the-render-network/using-the-dispersed-for-dockerized-compute.md?ask=
```
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.