Most automation tools ask you to trust their cloud with your keys and your data. FlowForge takes a different position: the safest place for your data is the machine you already own.
API keys, tokens, and passwords are encrypted at rest with the macOS Keychain (Apple's safeStorage). They're decrypted only in the app's main process, at the moment a step needs them — and never returned to the interface, exports, or logs.
Your workflows run inside the app on your Mac. There is no FlowForge server that sees your data, because there is no FlowForge server in the loop at all. The app keeps working with no internet connection.
Every use of a credential is written to a hash-chained log. If any entry is altered, the chain breaks and verification fails — so you always have a trustworthy record of what accessed what.
The editor watches for a dangerous shape — untrusted input flowing into private data and then out to the internet — and warns you before you turn such a workflow on, suggesting an approval gate.
Outbound HTTP is protected against server-side request forgery: addresses are resolved and validated before connecting, redirects are re-checked, and cloud-metadata endpoints are always blocked.
Human-approval steps pause risky runs until you say go. Every workflow change is versioned, so you can roll back instantly. Nothing important happens without you.
We think you should know this precisely. FlowForge only reaches the network when a step you configured needs to — for example:
That's it. No analytics on your workflows, no telemetry on your data, no account syncing in the background.
Try FlowForge free for 14 days and keep your data where it belongs.