LOCAL-FIRST AUTOMATION

Automate your machine, visually.

Build a workflow by connecting nodes in the browser editor, export it as a portable package, and run it natively on your own machine. No cloud. No account.

❯curl -fsSL https://get.baudbound.app/linux | sh

Open the Editor →Read the Wiki →

SEE IT IN ACTION

From canvas to machine

editor.baudbound.app

BaudBound Runner

HOW IT WORKS

Build once, run with explicit trust

Build

Add triggers, actions, and control-flow nodes on the canvas in the browser editor.

Verify

The editor checks graph structure, node configuration, and target compatibility.

Export

Download a portable package containing the workflow, metadata, and declared assets.

Run

Import it into the runner, approve the exact revision, then run it locally.

WHAT YOU CAN AUTOMATE

Nodes for real machines, not just APIs

Schedule & file triggers

Kick off a workflow on a timer or the moment a watched file changes.

Local webhooks

Receive an HTTP request on your own machine and react to it immediately.

Serial devices

Talk to serial hardware directly: read, write, and route the data.

HTTP requests

Call external APIs and use the response anywhere else in the graph.

Files & processes

Read, write, and move files, or launch and manage local processes.

Desktop app control

Drive supported desktop applications as part of a larger workflow.

LOCAL BY DESIGN

Nothing runs until you approve it

Local execution

Workflows run on a runner you control. There's no hosted execution service in between.

Explicit approval

Every package revision is reviewed and approved by hash before the runner will touch it.

Nothing trusted by default

A package isn't trusted just because the editor created it.