Same wires. Different ownership.

Node graphs used to signal the unruly end of generative imaging: noodles everywhere, missing models, one red box whose repository vanished. Chaos has now put a graph inside Veras 5.3. It can combine image, video and 3D operations, expose selected settings as controls and bake geometry into architectural hosts.

That does not make Veras a tidier ComfyUI. It makes graph design a product category architects must learn to read.

What is the real difference between the graphs?

Ownership. In Veras NODES, Chaos defines the available nodes, hosts cloud workflows, supplies generation engines and manages the product's BIM outputs. In ComfyUI, the graph can be saved as JSON, run locally or through hosted services, and extended with custom nodes. The operator has far more say over the stack and far more responsibility for it.

These are product and documentation distinctions, not a quality verdict. ArchiGen has not run a paired output test. A beautiful graph can still make a bad image with enviable efficiency.

Veras makes the graph into a managed tool

Chaos published Veras 5.3 NODES on 19 October. Its release page describes nodes for inputs, values, generators, analysis, geometry and outputs. A Nodes Agent can assemble and alter a workflow from a description. Any setting can be pinned into a CONTROLS view, while an OUTPUT view can hide the canvas from the person running it.

That separation matters in practice. The workflow author sees the machinery. A colleague sees the source image, material prompt, seed or output size that the author has chosen to expose. This is closer to issuing a small internal application than handing somebody a diagram and wishing them luck.

The managed boundary also limits surprise. A vendor-curated node catalog cannot promise perfect stability, especially while NODES is labelled beta, but it does establish one accountable product surface. Cost estimates appear before graph runs, according to Chaos, and unchanged nodes can reuse prior results. Cloud versions are saved at runs and other milestones.

Our first report on Veras 5.3 NODES covers what a practice should standardize inside that surface. The procurement question is what happens outside it.

ComfyUI makes the graph into an environment

ComfyUI's official repository describes reusable subgraphs, templates, App Mode, a local API, custom nodes and workflows saved as JSON. Its official documentation distinguishes the editable save format from the API format used for programmatic execution. Same extension. Different job.

That openness is substantial. A practice can inspect the graph, keep it in version control, select models, use local hardware and build procedures that are not tied to one rendering vendor. It can also import a graph whose custom nodes, model files and Python dependencies are absent. The JSON is a map, not the territory.

The ComfyUI workflow JSON guide explains what the graph records. A credible handoff also names model files, custom-node sources, versions and expected inputs. Without those, portability becomes an archaeological exercise conducted during a deadline.

ComfyUI now spans local, desktop and managed cloud routes, so “ComfyUI” does not mean one maintenance arrangement. Official support documentation says the Custom Nodes Manager is available in local and desktop environments, while Comfy Cloud provides a managed set of preinstalled custom nodes. Record the environment before promising that a graph will run.

Who should be allowed to edit the graph?

Fewer people than should be allowed to run it. A production graph needs an owner who understands structure control, model compatibility, cost and failure recovery. Most users need named inputs and a clear output, not permission to reroute the depth map five minutes before a review.

Veras addresses this with pinned controls and its output view. ComfyUI offers reusable subgraphs, templates and App Mode, according to its repository. The interfaces differ, but the governance principle is the same: separate authoring from operating.

Set three roles. The author changes nodes and dependencies. The operator runs approved inputs and controls. The reviewer judges geometry, intent and delivery fitness. That is genuinely a list, and every item earns its chair.

Use the render preservation brief to define what the operator may change. A simplified front end does not rescue a vague contract.

Which graph is more portable?

ComfyUI offers stronger file-level portability because the graph can be saved as inspectable JSON and can run outside one architectural vendor's application. That advantage is conditional. A portable graph with unavailable weights or abandoned nodes is a postcard from a working computer.

Veras offers stronger product-level continuity for teams already inside supported Chaos and BIM tools. Its workflow library carries uploads, shared workflows and version history, based on the vendor's release documentation. The trade is obvious: the practice relies on Chaos to keep that hosted system, catalog and commercial access available.

Test both exit paths. For ComfyUI, rebuild the environment on a second machine from the saved package. Our workflow portability test names the dependencies to capture. For Veras, export results, share a workflow to another authorized account and document which host receives the BIM output. A cloud library is convenient custody, not independent custody.

How should a practice choose?

Start with the output that must survive. If the graph needs to place generated or parametric geometry directly into Revit, Rhino or SketchUp, Veras has named product paths worth testing. If it needs a particular ControlNet, local checkpoint, LoRA or experimental image processor, ComfyUI's extensibility is the stronger proposition.

Then price ownership. Count subscription or credit spend for the managed route. Count hardware, setup, updates and specialist attention for the open route. “Free software” and “one subscription” are equally weak cost models when staff time is missing.

Finally, stage the failure. Disconnect the network. Remove a node. Open the graph under a colleague's account. Change the source resolution. The winner is the route whose failure your practice can explain and recover, not the one with the most theatrical canvas.

ArchiGen's take: choose the burden on purpose

Veras NODES validates something ComfyUI users already knew: graphs are an excellent way to make generative work visible, repeatable and adjustable. It also exposes the decision hidden beneath the wires.

A managed graph buys a narrower, supported operating surface. An open graph buys control and inspectability. Neither removes maintenance; each assigns it differently.

Choose who owns the broken node before admiring the working one.

Evidence note: product facts were checked on 24 October 2026 against Chaos's official Veras 5.3 NODES release and current Veras updates page, plus ComfyUI's official repository and workflow-format documentation. Vendor capabilities remain vendor claims. ArchiGen did not run or score either product for this article.