Skip to content
JOIN THE BETA

Oro Journalfield note

Oro has 103 nodes. That is not the point.

The current runtime has more than doubled the original node count. The important change is not scale alone, but how the pieces now behave as one production system.

The running Oro build currently registers 103 nodes, sixteen of them through external plugin identities. The first public development record described 48 nodes and ten plugins. That earlier number was accurate for its moment. Oro did not stay still.

A larger tool is only useful when it becomes easier to understand

The node count now spans local image processing, provider generation, compositing, reusable Assets, prompt systems, and a substantial video surface. The work has not been to collect buttons. It has been to keep execution, history, cost, storage, and visual dependencies legible as the system grows.

Focused workspaces still run the same code as the graph. A simple task can stay simple. A technical job can unfold into the full canvas without being rebuilt in another application.

Local first still means something concrete

Depth, pose, selection, transparency, grain, colour, keying, comparison, compositing, and several upscale paths remain close to the source. Provider nodes are visible as provider nodes. Their cost and place in the workflow are decisions rather than ambient behavior.

The number is a snapshot. The production model is the product.