Jul 21, 2026
Sandbox the code node
A code node is an escape hatch. It still has to run somewhere that cannot take down the host.
Technical builders need a code node. Visual tools that pretend otherwise get thin the first time a step needs real logic: a transform that is ugly in a mapping UI, a branch that is clearer as ten lines of TypeScript, a call that does not fit the node's schema.
We treat that as expected, not as a confession. The graph should be allowed to drop into code.
The cost is where that code runs. A function in your own process is a function that can take the process down. A container you operate is a container you patch, scale, and wake up for. Most teams accept this because the alternative looks like giving up control.
The alternative is a sandbox on the host. You write the function. The runtime keeps it in a box. It can fail without taking the rest of the graph with it, and it can be replayed against the same input as any other node.
That is a narrower promise than "run any code, anywhere." It is also the only version we are willing to operate. If the escape hatch can crash the host, it is not an escape hatch. It is a second product you did not mean to ship.