Iliad: Fully editable procedural pipelines, radically faster

What

Iliad is a texture and material creation platform focused on procedural and diffusion-based workflows for visual asset production. Based on the page, it serves users who need seamlessly tileable textures, PBR material maps, and reference-driven texture generation, likely including 3D artists, material artists, game teams, and digital content creators.

Its new engine, Aqueduct, is presented as a node-based procedural material system that is fully editable, transparent, and designed for faster pipeline building. The core workflow appears to combine manual graph editing with AI assistance that can interpret references, connect nodes, and organize complex procedural graphs, positioning Iliad as a modern material-authoring tool with both hands-on control and automation.

Features

• Node-based procedural material engine: Aqueduct provides a graph-based system for building procedural materials, giving users a structured way to create and modify material logic.
• Fully editable white-box workflows: The engine is described as transparent and editable, which is useful for teams that need visibility into how outputs are built rather than relying on opaque generation.
• AI-assisted graph construction: Aqueduct’s AI assistant can understand references, wire up nodes, and organize complex graphs, helping reduce setup time in procedural authoring.
• Seamless texture creation: Texture Canvas is designed to create custom tileable textures, addressing a common need in environment art and material design.
• PBR map generation: Material Generator creates PBR material maps from a texture, which can help convert source imagery into usable material components for rendering workflows.
• Reference-to-texture conversion: The Reference to Texture tool turns a reference image into a seamless texture, supporting asset ideation and texture extraction from visual inspiration.

Helpful Tips

• Validate editability claims in practice: For procedural tools, confirm how easily teams can inspect, modify, and version node graphs before adopting them as a core production workflow.
• Check output fit for your pipeline: If your team depends on specific map types, export formats, or DCC/game-engine handoff steps, verify those details because the page does not specify them.
• Use AI assistance for acceleration, not blind automation: Tools that wire nodes from references can speed initial setup, but production teams should still review graph structure for consistency and maintainability.
• Assess hardware requirements early: The demo requires WebGPU for GPU rendering of procedural textures, so browser and device compatibility may affect evaluation and onboarding.
• Treat early access carefully: Since Aqueduct early access is scheduled for March 2026, buyers should expect some uncertainty around maturity, stability, and broader feature depth until more documentation is available.

OpenClaw Skills

Iliad could fit well into the OpenClaw ecosystem as part of asset-generation and material-ops workflows. Likely OpenClaw skills could include a reference intake agent that classifies incoming images and routes them to seamless texture generation, a material packaging agent that organizes outputs for downstream art teams, and a graph documentation agent that explains procedural node setups for easier collaboration. These are likely use cases rather than confirmed native integrations, since the page does not mention APIs or OpenClaw support.

In a broader production setting, combining Iliad with OpenClaw could help studios or design teams standardize how texture references become reusable materials. For example, an OpenClaw workflow might collect concept references, generate candidate textures, request PBR outputs, and tag assets into a searchable library for environment artists. If supported operationally, this kind of setup could reduce repetitive material-prep work and make procedural asset creation more accessible across art, visualization, and interactive media teams.