Flowdrome is a workflow platform that runs your flows on your own fleet — not in somebody's cloud queue. Build visually, test live against real data, then deploy to a host: a bare server, a container, or a VM that boots straight into being a host. The editor and the fleet share one engine.
A -drome is a place where things run — velodrome, aerodrome, Flowdrome.
The Studio editor: typed ports, live validation, single-step debugging and the whole run envelope on every wire.
The exact engine that powers Test workflow in the editor is embedded in every host. Deploy
pushes the same flowdrome.workflow.v1 document you tested — no conversion, no
"works in the editor" class of bug, no rows in someone else's queue.
The Nucleus manages workflows, credentials, users and deployments; hosts execute. Enroll a host, push a build, watch every deployment from one place — the Nucleus itself never runs a workflow.
Triggers, flow control, list tools, SQL/S3/Redis/Mongo/FTP/IMAP wire clients, Telegram,
Slack, Discord, Google Sheets/Docs/Drive/Gmail, Notion, HubSpot, Outlook, AI nodes — plus
universal {{ }} expressions in every string field.
The Approval node pauses a run until a person decides. Pending gates from every host land in one fleet-wide inbox in the Nucleus — approve, reject, or let the configured timeout policy decide.
Credentials are encrypted at rest in the Nucleus, with OAuth2 connect flows for Google, Notion, Microsoft and HubSpot. Deployed apps lease secret values at run start over a scoped token — nothing is ever baked into an artifact.
Every run records the whole envelope on every wire — inspect any node's exact input and output, per port. Hosts keep a run ledger and resource telemetry; retry a failed run from the node that broke.
The API node speaks 100 services from declarative recipes — pick service + operation, fill the parameters, done. Got an OpenAPI spec? The connector factory turns it into a verified connector, proven against a generated mock before you ever call the real API.
A typed, durable database inside the Nucleus: grid UI, REST API, a Table node for workflows, and a record-change trigger that starts flows when rows land. Lead queues, dedupe registries, approval ledgers — no Postgres to run.
Package workflows into hosted pages: forms, run
buttons, live table views, chat — composed as blocks, served at /if/your-page.
Visitors need no account, and the page never holds a credential.
Tell the Copilot what you want — it creates and rewires real nodes on your open canvas with surgical edits, scaffolds multi-endpoint APIs, and reports exactly what it changed. Bring your own model; a 200-scenario regression suite keeps it honest.
OIDC single sign-on against Okta, Entra, Google or any standard issuer — and an append-only audit log of every login, credential change, save, and deploy, with filters and ndjson export.
Drop your Zapier export or n8n workflow JSON on the Studio and it becomes real Flowdrome workflows — steps mapped to native nodes, anything unmappable preserved for one-click conversion, credentials never imported.
Most platforms execute your flows inside their cloud, forever. A Flowdrome host is a single self-contained agent with the engine embedded — run it on a bare server, in a container, or air-gapped. What you tested is what serves: same document, same engine.
The live appliance ISO is the operating system: boot it and the machine is a
Flowdrome host in seconds — no installer. It adopts a data disk labelled
FLOWDROME_DATA (or provably blank) for persistence and dials home to your
Nucleus.
One Nucleus manages many hosts; hosts run workflows and keep running if the Nucleus goes away. Management traffic and workflow traffic never share a process — or a failure domain.
Deployed apps hold credential references, never values. At run start they fetch the real values from the Nucleus over a short-lived, deployment-scoped lease and keep them only in memory.
Drag nodes onto the canvas, wire typed ports, template any field with
{{ expressions }}. Validation lights up problems before you ever run.
Run against real services from the editor. Inspect the full envelope on every wire, single-step the debugger, edit data mid-run, retry from any node.
One click pushes the exact document you tested to a host in your fleet, stamped with its version. Real triggers take over; the Nucleus watches every deployment.
From git clone to a deployed workflow in one sitting.