Choose a runtime

The runtime executes your graph. Select it before testing a workflow that depends on network access, local files, credentials, or persistent State.

Browser#

Use Browser for a quick start and ordinary in-page execution. Core examples run without installing anything. The page and browser must remain available for browser execution and scheduling.

HTTP requests are subject to browser CORS, mixed-content, and private-network restrictions. A request blocked by those rules may need a different runtime even when the URL and credentials are correct.

Desktop#

Desktop runs through the paired local runtime and supports capabilities unavailable to a browser page. Email delivery requires Desktop because a browser cannot open an authenticated SMTP connection.

Check Get the app for release availability and pairing instructions. Desktop downloads are being prepared; development builds can be run from the project. The runtime process and its device must remain available when work is due.

Extension#

Extension is another local execution option. Get the app shows browser-store availability and instructions for loading a development build. Connect the extension from the app and confirm it is available before starting a run. Local file access and SMTP require Desktop.

RPC and saved workflows#

Blokboard Cloud RPC requires sign-in. You can configure a Custom RPC, or use Desktop or Extension with Public RPC where supported. The network selected for a blockchain node must agree with the workflow’s Test mode.

Saving a workflow to an account does not by itself provide an always-running execution host. Runtime availability still determines whether it can run.

Moving between runtimes#

Recheck connection setup, file access, wallet access, and State after changing runtimes. Values stored locally in one runtime are not automatically transferred to another.

Next: connections and scheduling.