ArchitectureA supervised JVM-class runtime — OLTP on seven engines, OLAP on three. AI-native, MCP-native, observable as plain SQL.Read the architecture
Está viendo la edición Perú. Está viendo la edición Colombia. You're viewing the Pakistan edition. Cambiar a la edición global →Cambiar a la edición global →Switch to the global edition →

A visual workflow editor that compiles to server-side JavaScript

Workflows are drawn as nodes and edges in a canvas editor and compiled to server-side JavaScript the runtime executes: condition, note, model, calendar, integration, transform and custom-code nodes.

Some logic is better drawn than written: an approval chain, an integration that branches on a response, a scheduled hand-off. This release adds a canvas editor for that logic and a compiler that turns the drawing into the same server-side JavaScript everything else runs.

The editor

  • A canvas Built on a flow library: zoom controls, multi-node selection, auto-layout in graph and tree modes, a resizable node detail panel, and a variable picker filtered by type.
  • Nodes An end node with validation errors, rich-text notes, a condition node with true and false edges, a language-model node with an output schema editor, a calendar node, integration nodes, transform nodes, and a custom-code node with a slotted editor.
  • Live wiring Port connections resolve in the input and output panel as they are drawn.

The compiler

  • Workflow JSON to JavaScript The server parses the workflow document and compiles it; the compiled script runs through the ordinary script connection with its security and transaction. A 555-line document describes the pipeline.
  • Cached A workflow bean caches the compiled form.

The drawing is the source. The script is the build artefact. Nothing about how it runs is new.