Workflow Infrastructure

Automation systems you own — not workflow tools you rent.

The platforms underneath operating teams' automation: n8n, Make, Zapier, Pipedream, Activepieces, Windmill. Treated as infrastructure, not a catalog — with the trade-offs that actually matter at scale: ownership, operational cost, migration risk, and the workflow ceiling.

Workflow complexity — where each system tops out

Real automation systems aren't measured in “triggers connected”. They're measured in branches, retries, sub-workflows, memory, and how gracefully the platform fails when something does.

L1

Linear glue: trigger → step → action

One-shot integrations between SaaS apps. Every platform handles this; the question is what they cost when there are 50 of them.
L2

Branching, retries, sub-workflows

Compare how each platform expresses branches, retries, and reusable flows, then model the current billing unit against the representative workload.
L3

AI-augmented workflows with memory and retrieval

Embeddings, vector stores, RAG, and classification can live in workflow nodes or code. Compare model control, observability, failure recovery, and cost boundaries.
L4

Operational automation systems

Production workloads need error paths, queueing, cost ceilings, observability, and access control. Select the system whose operating boundary the team can own.

By system role

Pick by what each platform is actually for, not by feature checklist.

Self-hosted visual + code

n8n. A strong candidate when self-hosting, code escape hatches, and AI workflow nodes outweigh the operational and migration costs.

Code-first cloud

Pipedream. When your team writes JS/Python anyway and wants workflow scaffolding around it — not a canvas to drag.

Self-hosted developer platform

Windmill. Internal tools + workflows + scripts in one self-hostable platform. Heavier than n8n, more code-native.

No-code visual canvas

Make. Fits non-technical operators who need visual routers and scenario control. Model current credit rules against the actual workload.

Quick prototype / niche SaaS glue

Zapier. Fits teams that prioritize managed operations, guided setup, and connector coverage. Test governance and task economics for load-bearing workflows.

Open-source n8n alternative

Activepieces. True OSI-licensed self-host with a Make-like canvas. Smaller ecosystem, friendlier license.

Human-in-the-loop SaaS

Relay.app. Workflows that explicitly pause for human review. Niche, but the right shape for some compliance-bound flows.

Migration paths

Migration difficulty is part of the infrastructure decision. Compare exports, credentials, platform-specific nodes, runtime assumptions, and the rebuild path before committing.

Operational realities (every platform answers these)

If a workflow is going to run unattended in production, these are the questions that quietly decide the platform for you.

Workflow ownership
Can you export, version, and rebuild your workflows somewhere else — or does the vendor own the artifact?
Self-hosting + data residency
Does customer data ever traverse a third-party SaaS workflow runtime?
Cost model under complexity
Does adding a step multiply the bill, or is the unit “execution”, not “task”?
Error paths and observability
What happens when a workflow fails at 03:00, and who finds out?
Code escape hatch
When the canvas runs out, can you drop into JS or Python without leaving the workflow?
Access control + audit
Can ops, engineering, and external reviewers each see what they need — and nothing else?