6Flow Studio
Tokenization Workflow Platform for CRE. Like n8n for CRE.
What it is
6Flow = a programmable, low-code orchestration layer for the Chainlink Runtime Environment (CRE)
Problem
Smart contract is getting more complex. Banks need to maintain the smart contract engineers, auditors, and customize the workflow for different stakeholders. Many of the medium-sized banks wouldn't pay for that.
Solution
We provide a simple/friendly UI platform to enable everyone to be able to design the smart contract workflow.
We abstract the complexity so that they can focus on their use cases.
We believe that 6Flow can unlock medium-sized banks to CRE because it can
- Reduce cost = No need to maintain smart contract engineers or auditors.
- Highly Customizable = Workflow that normal people can design with ease.
6Flow can provide
- Visual Workflow Builder = Drag, connect, and configure nodes like a game.
- Predefined Nodes = Template nodes that you can easily use it eg. Gemini API call
- Developer Experience = Programmable node, so that you can inject custom JavaScript code into it.
How it works
- Create the workflow and arrange the business logic
- Click compile
- Add the secret keys in TUI
- Click simulate or deploy
How it Works
Stack
- Frontend (frontend/) — Next.js + React Flow. Users design non-linear workflows as node-edge graphs, inspired by n8n's UX.
- Compiler (compiler/) — Rust-based transpiler using a 4-phase pipeline:
a. Parse — reads the visual workflow JSON
b. Validate — graph-level and node-level checks
c. IR — converts to a semantic Intermediate Representation
d. Codegen — emits a complete deployable CRE project bundle (main.ts, config.json, workflow.yaml, etc.)
- Shared (shared/) — TypeScript helpers and data models used across the TS codebase.
- TUI (tools/tui) — Go + Bubble Tea terminal tool that syncs compiled bundles and manages local secrets/simulation, consuming frontend/src/app/api/tui/* endpoints.
Architecture
https://github.com/6flow-studio/6flow-convergence/blob/main/6Flow-diagram.jpg
Key Design Principle
Workflows are compiled, not interpreted — the visual graph is transpiled into native, deployable CRE TypeScript executables that run on the Chainlink Runtime Environment. The
frontend exposes three WASM APIs (validate_workflow, validate_node, compile_workflow) so the Rust compiler runs client-side with errors mapped back to React Flow node
highlights.
Links
Created by
- Sitthavee
- Nonthakon