Runtime requirements stay with the Flow

Before a run starts, Flow-Like's pre-run analysis walks the complete Flow and reports the runtime variables, OAuth requirements, local-only nodes, and WebAssembly permissions it finds.

The App Event and Board modes currently select local or remote execution. Pre-run reports when any node, including one inside a nested layer, requires local access. The current dispatcher does not yet reject every incompatible remote selection from that aggregate flag. A single run remains in one environment, and device-local secret values stay outside the Board and remote payloads.

A Board can run in Studio or on configured remote runtimes. The maintained self-hosting guides cover Docker Compose and Kubernetes. Backend directories also contain deployment work for AWS, Azure, and GCP; check each target's documentation and status before relying on equivalent behavior.

Build from source

Install Git, mise, Tauri 2 system dependencies, protoc, and a C/C++ toolchain. Run these commands from the repository root:

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 declared in mise.toml. mise run dev:desktop detects the current platform and starts Studio.

Useful tasks:

mise tasks
mise run dev:web
mise run dev:docs
mise run dev:book
mise run check
mise run fix

The detailed setup guide lives at docs.flow-like.com/dev/build.

Self-host with Docker Compose

The checked-in Compose directory builds the browser app, API gateway and API replicas, Rust runtime workers, WASM compiler, realtime signaling, server-side Event services, PostgreSQL, Redis, and database initialization on one host. Studio remains the desktop application and can connect to that backend.

<p align="center"> <img src="apps/docs/src/assets/DockerComposeArchitecture.svg" alt="The Docker Compose stack connects browser and desktop clients to the web app, API, execution workers, persistence, collaboration, and optional monitoring services." width="100%" /> </p>

Start with these files:

The documented installation path is:

```bash git clone --branch dev https://github.com/Rheosoph/flow-like.git cd flow-like/apps/backend/docker-compose cp .env.example .env cp flow-like.config.example.json flow-like.config.json

../../../tools/gen-execution-keys.sh --export

Add the generated keys, OIDC settings, public URLs, and storage configuration to .env.

Point FLOW_LIKE_RUNTIME_CONFIG_FILE at ./flow-like.config.json.

The API and sink services read this mounted file at startup.

docker compose config --quiet docker compose up -d --build docker compose ps --all ```

The stack expects external object storage and does not create its buckets or containers. The copied environment template currently selects AWS, while the stock API image omits the AWS runtime-credential feature. Select a provider supported by that image or rebuild the API target with the required feature. Read the complete Docker Compose installation guide before exposing the stack publicly. The optional monitoring profile adds Prometheus, Grafana, Tempo, and PostgreSQL and Redis exporters.