Open protocols, so you can leave
Every connection is a published protocol — MCP, OAuth, webhooks, OpenAPI, IMAP, CalDAV — not a proprietary connector only we can build. Your data leaves by the same doors it came in. That is the point: a tool you can walk away from is one you can safely try.
Every connection is an open protocol
One open pipe from AI to the outside world
Plays well with the open-source automation world
Because it speaks standards, WorkflowHub sits alongside the tools your team may already run — as a source of events, a consumer of them, or the human-approval gate in front of them.
- n8n — trigger and receive flows over webhooks
- Activepieces — exchange events via CloudEvents
- Apache Camel / EIP — integrate via standard endpoints
- Any OpenAPI-described service — describe it, the AI consumes it
Inspect the client yourself
The desktop agent runs in your own environment, holds your credentials locally, and talks to the platform over the same public API you can call yourself. Source opens at general availability; until then, the protocol between the two is documented and inspectable.
This is the lean agent-only download — a single self-contained binary for Windows, macOS, or Linux. Nothing to provision: no database, no server, just the edge process that holds your credentials while the platform stays managed in our cloud.
Open standards, no lock-in.
Open standards mean your integrations are never hostage: everything you build exports as lineage-stamped JSON, and the full API is described at a machine-readable OpenAPI endpoint.