Private workflow automation.
Without a cloud middleman.
FlowForge executes workflows on your Mac. Workflow definitions and run history stay local, while credentials use the macOS Keychain. A step reaches the network only when the action you configure requires it.
Know where your automation runs
Hosted automation platforms process each run on infrastructure you do not control. FlowForge takes a different approach: the runtime lives on the Mac where you installed it.
Local workflow files
Your workflow configuration remains on your machine rather than being stored in a FlowForge cloud account.
macOS Keychain
Credentials are stored using the operating system’s protected credential facility.
No usage telemetry
The published privacy model states that FlowForge does not collect workflow usage analytics or telemetry.
Explicit network actions
Email, webhooks, APIs, hosted AI, and third-party connectors use the network only because you configured those steps.
Human approvals
Pause sensitive runs and require a person to approve the next action.
Audit and versions
Review local execution history and restore earlier workflow versions when a change needs to be reversed.
Keep sensitive context close to the work
Local execution is useful when automating internal files, operational inboxes, client processes, development tasks, or other workflows where unnecessary data replication creates risk.