LiquiFire OS is not a 3D configurator. It is headless visualization infrastructure that generates textures, materials, and scene data for any viewer, any engine, and any CPQ, using the same LiquiFire Chains™ that power 2D imaging.
The viewers work. The models look good. The problems start when the 3D stack needs to connect to the systems that run the business.
A 3D artist creates material maps, exports them, uploads them to the viewer platform, and repeats for every color and material variant. When the PLM material library changes, the cycle starts over.
The team producing product images works from the same PLM data as the team producing 3D textures. They use different tools, different vendors, and different delivery infrastructure. Changes in one pipeline do not propagate to the other.
Connecting a CPQ system to a 3D viewer means building a translation layer that maps configuration rules to material IDs in the viewer's format. Every product change requires engineering involvement on both sides. The viewer platform becomes the lock-in.
Once LiquiFire OS is integrated, the front-end configurator and its UI are fully connected to every upstream system. Nothing is static. Nothing requires manual intervention to propagate.
A material is revised in the PLM. The next time the viewer requests that texture, LiquiFire OS renders it from the updated source. Every product using that material reflects the change instantly, across 2D images, 3D textures, and AR previews.
A product specification changes in the ERP and flows through the CPQ. LiquiFire OS receives the updated payload, adjusts the model geometry, regenerates selection volumes, and recalculates texture parameters. The configurator reflects the new product state without a deployment.
Updated PBR, bump, or normal maps become available from the asset library. Chains reference these maps by URL. The 3D scene picks them up at the next render request. No re-export, no upload to the viewer platform.
A new handle design is added to the component library. LiquiFire OS adds it to the scene at the anchor points defined by the payload. The configurator offers it as an option without any 3D modeling work beyond the component model itself.
Embroidery simulations, hotstamp effects, engraving, and text personalization are rendered as supporting texture layers by the chain. When a visitor types their initials or selects a thread color, the texture regenerates and the 3D scene updates.
A pricing rule, a dimensional constraint, or a material restriction is updated in the CPQ. The next payload carries the new rules. Selection volumes, anchor constraints, and available options update instantly. No integration ticket. No engineering sprint.
LiquiFire OS is a stateless execution layer. It reads from your data systems, renders textures and scene data on demand, and delivers the result to whatever consumes it.
LiquiFire OS does not store your assets. It reads from wherever they already live, renders the requested output, and returns it. No asset migration. No vendor lock-in.
The output is a texture, a material definition, a USDZ file, or a complete scene, delivered over HTTPS. LiquiFire Surround is included for teams that want a turnkey viewer, but any WebGL viewer or AR framework can consume the output.
User interactions in the 3D viewer feed back into CPQ rules, which direct LiquiFire OS to render the new state. This is the architecture being deployed with Infor CPQ for windows, marine, and industrial manufacturing.
Chains are a rendering language with 142+ commands. When the output is a diffuse map, a normal map, or a PBR material, the chain handles it the same way it handles a product image.
Product image for website or catalog.
Normal map for a 3D model. Material map regenerated from the new texture content.
Tint any texture with a color value from CPQ, PIM, or a RAL/Pantone lookup table.
Layer grain, weave, or finish effects over base materials using 30+ blend modes.
Simulate embroidery, hotstamp, and other personalization effects on any surface.
Add text, lettering, and monograms to textures from product configuration data.
Regenerate normal, PBR, and bump maps based on the new texture content.
Correct material properties for physically accurate rendering across viewers.
LiquiFire OS reads a structured payload from a CPQ or any JSON source. It manipulates the model geometry, generates all textures through chains, and delivers the result to the viewer with every material surface backed by a LiquiFire URL that renders on demand.
Anchor positions, snap radii, movement bounds, and distribution areas are computed from the payload and applied as invisible interaction geometry. A new product variant requires a new JSON payload, not a new 3D model.
Every material surface on the delivered model is backed by a LiquiFire URL. When the visitor changes a color or material, the URL parameters change and LiquiFire OS returns new diffuse, normal, and PBR maps. The textures are never static files.
The geometry is manipulated by the payload, the textures are generated by the chains, and the interaction is constrained by the rules. A hinged door and a glazed variant are the same model with different payloads and different chain parameters.
This separation means that creative teams focus on what they do best: building high-quality 3D models and designing compelling product experiences. The mechanical work of rigging interaction zones, generating texture variants, wiring CPQ rules to viewer state, and syncing materials from PLM is handled by the platform. A 3D artist designs one model. LiquiFire OS makes it configurable.
For teams that want a complete viewer, LiquiFire Surround provides interactive 3D with camera control, animation playback, and native iOS AR handoff through USDZ export. It consumes chain-rendered textures automatically. Below are live instances running in your browser.
Single constructor. AR, shadow maps, HiDPI configurable at init.
USDZ/glTF export, camera control, animation playback at variable speeds.
The 3D rendering pipeline is available across all LiquiFire OS deployment models, including air-gapped appliances with zero external data egress for defense, aerospace, pharmaceutical, and financial services organizations.
We work with teams to integrate LiquiFire OS into existing 3D workflows, whether that means connecting a CPQ system, replacing a manual texture pipeline, or deploying LiquiFire Surround as a complete viewer solution.