> 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/how-to-build-assembly-pipelines-with-octane-and-the-render-network.md).

# How to Build Assembly Pipelines with Octane & the Render Network

Leveraging the Assembly Pipeline with Octane and the Render Network

Octane Standalone is more than just a render engine-it’s a powerful assembly tool capable of streamlining production workflows for visual effects studios and artists working across multiple DCCs. In this series, award-winning director and VFX supervisor Andrey Lebrov walks through his latest pipeline architecture built around **Octane Standalone + The Render Network**, using assembly workflow theory and his studio's LMI Tools for Houdini, Blender, and C4D.<br>

Introductory tutorials previewing this Assembly workflow using Octane Standalone as a scene compiler were released in early 2025.

{% embed url="<https://know.rendernetwork.com/getting-started/render-network-tutorials/lmi-houdini-tools-or-unlocking-octane-and-render-network-capabilities-with-andrey-lebrov>" %}

This series of expanded guides follows up with a multi-part comprehensive tour exploring the structure and benefits of this workflow, providing a digestible breakdown of the series for those looking to enhance scalability, efficiency, and team collaboration.

<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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://know.rendernetwork.com/getting-started/how-to-build-assembly-pipelines-with-octane-and-the-render-network.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.