What you can build

Consider an order desk: look up a customer, check stock through an API, show exceptions for an operator to review, and submit the approved order. A scheduled job or an assistant can reuse the underlying operation.

Hardware access and model execution depend on the selected runtime, installed dependencies, and configured providers; the guides cover those requirements.

<details> <summary><strong>See a ported application: God's Eye View</strong></summary>

<p align="center"> <a href="./assets/complex.png"> <img src="assets/readme-spatial-app.webp" alt="God's Eye View ported to Flow-Like, showing aircraft on a map, source controls, a selected aircraft's details, and a workflow input." width="100%" /> </a> </p>

God's Eye View, ported to Flow-Like: a spatial interface with map layers, aircraft details, and workflow controls.

</details>

<details> <summary><strong>How the platform fits together</strong></summary>

<p align="center"> <a href="./assets/readme-platform.svg"> <img src="assets/readme-platform.svg" alt="Flow-Like connects databases, APIs, files, and devices to a shared platform for applications, automation, data analysis, and AI, then delivers team tools, APIs, and automated processes." width="100%" /> </a> </p>

</details>

Build from source

Install Git, mise, Tauri 2 system dependencies, protoc, a C/C++ toolchain, and on Linux the unixODBC headers (unixodbc-dev). Then run:

git clone --branch dev https://github.com/Rheosoph/flow-like.git
cd flow-like
mise trust
mise install
bun install
cp apps/desktop/.env.example apps/desktop/.env
mise run dev:desktop

mise install supplies the toolchain in mise.toml, and dev:desktop detects your platform and starts Studio. Use mise tasks to list development commands, or read the build guide for the full setup.

<a id="repository-map"></a>

<details> <summary><strong>Repository map</strong></summary>

Flow-Like is a Rust and TypeScript monorepo. Bun manages the JavaScript workspace, Tauri hosts the desktop client, and the runtime and core application model live in Rust.

</details>

1,900+ nodes and reusable packages

The node catalog covers SQL and databases, APIs, documents, media, UI, desktop automation, AI, and machine learning. Each node reference shows its inputs and outputs, so you can check the operation you need before building around it. Available nodes depend on the execution environment and enabled integrations.

Package your own capabilities for others to use. A package can bundle custom nodes and UI widgets together. Explore packages, inspect their nodes and permissions, then install and link a version to an App, your Flow-Like project. Use the package workspace to develop, test, and publish your own. Each App records its package dependencies and versions.

<p align="center"> <a href="./assets/packages.png"> <img src="assets/readme-packages.webp" alt="Flow-Like's package browser showing Code Interpreter, Typst Documents, PDF Tools, YouTube Tools, and other extensions with versions and requested permissions." width="100%" /> </a> </p>

<p align="center">_{Discover packages for code execution, documents, media, and more. Review their versions and requested permissions before installing.}</p>

The Sales Insights example combines Rust WebAssembly nodes with a React chart and filter panel in one package. Its guide shows how to build it and wire widget events to workflows that update the chart.

<details> <summary><strong>Build your own nodes and widgets</strong></summary>

Add a native Rust node to the built-in catalog, or create a package with the WebAssembly templates for fifteen source languages. WebAssembly extensions are in beta; host API support varies by language and template maturity.

Bring a custom interface through package widgets. Start with the TypeScript counter tutorial, which includes a browser preview and input, event, and query inspection. Framework templates are available for React, Vue, Svelte, and other supported options.

</details>

Edit the same workflow visually or in text

A Flow is an executable workflow. Its canvas and FlowScript, the typed text form, edit the same saved graph, called a Board. Use the canvas to follow a branch; use text for broad edits and code review. FlowPilot can help create and edit workflows, interfaces, and data from a conversation.

<p align="center"> <a href="./apps/website/src/images/parallax/workflow-core.png"> <img src="assets/readme-workflow.webp" alt="Flow-Like's workflow canvas showing connected typed nodes beside the FlowScript text editor." width="100%" /> </a> </p>

<p align="center">_{Edit workflow logic on the canvas or in FlowScript.}</p>

<details> <summary><strong>See the full Studio workspace</strong></summary>

<p align="center"> <a href="./assets/flowscript.png"> <img src="assets/readme-studio.webp" alt="Flow-Like Studio with a workflow canvas beside its FlowScript editor, project assets on the left, and recorded runs below." width="100%" /> </a> </p>

<p align="center">_{The workflow canvas and FlowScript editor share a workspace with project assets and recorded runs.}</p>

</details>

<details> <summary><strong>Walk through a FlowScript example</strong></summary>

This entry receives an incident report and chooses the log path:

use log::*

eventsGeneric triageIncident(payload: Struct, report: string) {
    const normalized = report.trim()
    if (normalized.contains({ substring: "production is on hold", ignoreCase: true })) {
        error({ message: normalized, toast: false })
    } else {
        info({ message: normalized, toast: false })
    }
}

<p align="center"> <a href="./apps/book/src/assets/workflows/incident-triage.webp"> <img src="apps/book/src/assets/workflows/incident-triage.webp" alt="The incident triage workflow rendered as Generic Event, Trim String, Contains, Branch, Log Error, and Print Info nodes." width="100%" /> </a> </p>

The image is generated from the checked-in example with the real reconciler and Studio auto-layout. When you apply a text edit, Studio checks it against the node catalog and updates the Board. The Rust runtime executes that Board.

Read FlowBook for worked examples and current round-trip boundaries.

</details>