top of page

WHAT MAKES IT DIFFERENT

Build for pipelines, not demos

Most node tools hide execution order and obscure data dependencies.

FlowPins makes both explicit - if you can read the graph, you can read the code.

Pin-level graph model

Connections are pin-to-pin, not node-to-node. This
enables precise control, better validation, and  exports that match the graph exactly.

Readable output

Generated scripts look like something a person wrote - because they  are structured that way internally. No spaghetti.

Pin-to-pin connections. Real control flow. Readable output. One graph,

seven scripting targets.

Visual scripting, 
done right

FlowPins_grid-0001.png

TECHNOLOGY

Real control flow

Branches, merges and execution paths behave exactly as they do in code. No surprises at compile time.

Target-aware compilation

One visual graph compiles cleanly to Maya Python, Houdini Python, Harmony JS, Fusion Lua, Unity C#. GameMaker GML or standard Python with more languages to come.

PHILOSOPHY

If you can read the graph, you can read the code

Clarity over cleverness

- every node does one thing and its connections say exactly what that thing is.

Explicit flow over hidden magic

- execution order is visible in the graph, not inferred by the runtime.

Stability over shortcuts

- the compiler is conservative. It generates code that works, not code that's clever.

Extensibility over lock-in

- new language targets, new node types, new backends - the architecture is built to
grow.

bottom of page