Best Process Orchestration Platforms 2026

Process orchestration platforms coordinate multi-step workflows with dependency management, failure handling and execution monitoring, and this ranking scores 10 of them from four families: BPMN process engines, code-first durable execution runtimes, visual automation builders and people-first process platforms, the last two built mainly for other jobs. Temporal leads at 9.1, followed by Camunda at 7.8, Apache Airflow 7.7, Prefect 7.5, Hatchet 7.0, n8n and Windmill 6.9, Activepieces 6.2, and Moxo and Zapier 5.4, re-scored on 28 and 29 September 2026 for orchestration depth, scalability, developer experience, monitoring and community. All four families are scored against one methodology, which is why a platform built for a different job can place low here. Every sub-score was derived from vendor documentation, GitHub data and published benchmarks, and the figures are not comparable with the March 2026 scores that the July 2026 pass replaced.

Rank	Tool	Score	Best For	Evaluated
1 ↑ 1	Temporal Workflows Temporal is a durable execution platform in which workflows are written as ordinary application code rather than as declarative graphs, so branching, loops, recursion and dynamic fan-out with join are language primitives. Saga compensation is first-class: the Java and PHP SDKs ship a Saga class with parallel-compensation and continue-on-error flags. Child workflows provide sub-workflow composition, Signals, Updates and Queries provide human-in-the-loop suspension, and Continue-As-New gives a workflow unbounded lifetime. Temporal Server v1.32.0 was published 11 September 2026 (GitHub releases, read 29 September 2026). The temporalio/temporal repository is MIT-licensed with 23,358 GitHub stars on 29 September 2026 and 280 listed contributors as of 28 July 2026. At Replay 2026 in May 2026, Task Queue Priority and Fairness, Worker Versioning, an OpenMetrics endpoint, multi-region replication and SCIM all reached general availability. Strengths: Durable execution with saga compensation as a first-class SDK construct Eight SDKs with replay-based determinism testing and a time-skipping test environment Workflow definitions live in version-controlled source rather than in a GUI Multi-region replication and Worker Versioning reached GA in May 2026 Weaknesses: Hard ceilings force Continue-As-New: 51,200 events and 50 MB per workflow, 1,000 children per parent No built-in alerting; Prometheus or Datadog must be wired up separately Cloud history retention caps at 90 days and self-hosted Archival is still experimental Self-hosting means four services plus a database plus Elasticsearch No connector catalogue; every integration is code the team writes and maintains	9.1	Engineering teams building workflows that must survive infrastructure failure	Sep 29, 2026
2 ↓ 1	Camunda Camunda 8 orchestrates processes modelled in BPMN 2.0 and decisions modelled in DMN, executed by the distributed Zeebe engine. Version 8.9, released 14 April 2026, added an Orchestration Cluster MCP Server, A2A client connectors, BPMN conditional events, idempotent process starts via Business ID, cluster variables, scheduled backups and expanded relational secondary storage. Camunda 8 is not open source: Zeebe, Operate, Tasklist, Identity and Optimize are published under the proprietary Camunda License v1 and production use requires a purchased Enterprise Edition, while the Java client, Spring Boot starter, exporter API and BPMN Model API remain Apache-2.0. The camunda/camunda monorepo carried 4,299 GitHub stars on 29 September 2026; the latest stable release was 8.9.22 on 29 September 2026 (GitHub releases, read 29 September 2026). Strengths: BPMN 2.0 and DMN compliance produces portable, auditable process models Compensation is a standard BPMN construct rather than a library concern Operate, Tasklist and Optimize give operations staff a surface built for non-engineers Predictable release train: minor versions every six months, frequent patches (8.9.13 on 15 July 2026 to 8.9.22 on 29 September 2026), 18-month support per version Weaknesses: Camunda License v1 requires a paid Enterprise Edition for production use BPMN modelling is a genuine learning investment before the first process ships Self-managed deployment involves Zeebe, Elasticsearch and several web applications Small GitHub footprint for its maturity: 4,299 stars on the Camunda 8 monorepo (29 September 2026)	7.8	Enterprises needing BPMN-compliant, auditable process orchestration	Sep 29, 2026
3	Apache Airflow Apache Airflow schedules and monitors pipelines defined as Python DAGs and carries the highest community score in this ranking. Airflow 3.0 introduced DAG versioning, so a run completes against the DAG version it started with, along with event-driven scheduling through Data Assets and Watchers, a Task Execution API enabling remote execution, an Edge Executor and a rewritten React user interface. Release 3.3.2 shipped 17 September 2026 (3.3.0 shipped 6 July 2026), on a roughly quarterly minor cadence with monthly patches. The apache/airflow repository held 47,006 GitHub stars on 29 September 2026 (GitHub, read 29 September 2026) and its contributors endpoint paginates to 4,509 distinct commit-author identities. It is Apache-2.0 licensed and an Apache Software Foundation top-level project. Strengths: Apache-2.0 under ASF governance with 4,509 distinct commit authors Deep provider ecosystem covering cloud, database and SaaS operators Airflow 3 added DAG versioning and event-driven scheduling via Data Assets Managed options from Astronomer, AWS MWAA and Google Cloud Composer Weaknesses: Python-only authoring No saga or compensation primitives; failure handling is retries and callbacks Scheduler tuning becomes its own discipline at high DAG counts Designed around scheduled data pipelines rather than long-running business processes	7.7	Data engineering teams needing DAG-based pipeline scheduling	Sep 29, 2026
4	Prefect Prefect turns ordinary Python functions into orchestrated flows and tasks through decorators, with dynamic fan-out via .map() and .submit() returning futures that join through .wait() or .result(). Unusually for this class it offers genuine compensation: transactions with on_rollback and on_commit hooks under READ_COMMITTED or SERIALIZABLE isolation. Self-hosted Prefect now scales horizontally on PostgreSQL 14.9 or later with Redis-backed distributed services, correcting the earlier singleton-services limitation that is still widely repeated. The PrefectHQ/prefect repository is Apache-2.0 with 23,952 GitHub stars as of 29 September 2026; note that Prefect marketing materials citing "40k+ stars" aggregate several organisation repositories. Prefect announced its acquisition of Dagster on 13 July 2026 (Business Wire, 13 July 2026, read 29 September 2026), committing to continue Dagster and Dagster+. Strengths: Transactions with on_rollback and on_commit hooks provide real compensation Flows are plain Python files: unit-testable, diffable and version-controlled Events and automations support reactive, proactive, metric and composite triggers Hybrid model runs execution on infrastructure the customer controls Weaknesses: Python-only, with no TypeScript, Go or Java SDK No deterministic replay; a crashed worker yields zombie runs rather than resuming mid-function Run retention caps at 7 to 30 days by tier and audit-log retention at 24 to 72 hours Prefect Cloud published quotas but no prices as of 28 July 2026 The Dagster acquisition announced 13 July 2026 adds roadmap uncertainty in Atlas's judgement, although Prefect has committed that Dagster and Dagster+ keep their name, licence and roadmap (Business Wire, 13 July 2026)	7.5	Python data teams wanting dynamic workflows with rollback hooks	Sep 29, 2026
5 ↑ 3	Hatchet Hatchet is a distributed task queue and durable workflow engine that uses PostgreSQL as its only required datastore, with RabbitMQ optional for higher throughput. It ships Python, TypeScript and Go SDKs, plus a Ruby SDK that was labelled early access in July 2026 and is listed without that label on the documentation home page on 29 September 2026. Hatchet publishes a self-hosting benchmark reporting 2,000 events per second driving an m7g.2xlarge RDS instance to 83% CPU and 800 IOPS, with average execution time moving from about 40 ms at 100 runs per second to about 220 ms at 2,000, and states it has tested up to 10,000 per second on an m7g.8xlarge instance (docs.hatchet.run/self-hosting/benchmarking, read 29 September 2026). The hatchet-dev/hatchet repository is MIT-licensed with no enterprise carve-out and no ee directory, carrying 8,023 stars and 89 contributors as of 29 September 2026 (version 0.107.0, 15 September 2026). Strengths: PostgreSQL is the only required datastore: no Cassandra, Kafka or Elasticsearch MIT across the whole repository, with no proprietary enterprise directory Python, TypeScript and Go SDKs with durable workflow semantics Managed cloud alongside a lightweight self-hosted deployment Prometheus metrics, OpenTelemetry trace export and worker health checks are documented (docs.hatchet.run/self-hosting/prometheus-metrics, read 29 September 2026) Weaknesses: Shorter production track record than Temporal, Airflow or Camunda 8,023 stars and 89 contributors as of 29 September 2026: fewer stars than Temporal, Airflow, Prefect, n8n, Windmill and Activepieces The published benchmark ran on engine v0.55.26, while the current release is v0.107.0 (15 September 2026), so its 2,000 events per second may not describe current behaviour (docs.hatchet.run/self-hosting/benchmarking, read 29 September 2026) No connector catalogue; every integration is application code	7.0	Backend teams wanting durable execution on Postgres alone	Sep 29, 2026
6 ↓ 1	n8n n8n is a source-available workflow platform pairing a visual canvas with JavaScript and Python code nodes. Counting the official documentation sitemap yields 520 built-in node pages as of 28 July 2026, alongside 11,890 npm packages carrying the n8n-community-node-package keyword; the "400+ integrations" figure still in the GitHub repository description is stale. Queue mode distributes work across Redis-backed workers, and the n8n documentation states that n8n can handle up to 220 workflow executions per second on a single instance (docs.n8n.io, read 29 September 2026). Version 2.0, released 5 December 2025, was a hardening release: task runners on by default, restricted Code-node access to environment variables, and a Draft/Publish model. The repository showed 206,262 stars on 29 September 2026 under the Sustainable Use License v1.0, a fair-code licence that is not OSI-approved. Strengths: 520 built-in nodes plus an ecosystem of 11,890 community npm packages (July 2026) Queue mode with Redis and separate workers scales horizontally Wait nodes persist to the database and resume on webhook or form submission 206,262 GitHub stars as of 29 September 2026: the most-starred repository in this ranking Weaknesses: No parallel execution: nodes run one at a time and branches execute depth-first No durable execution; a crashed run is marked crashed and a retry replays from the start Retries are capped at 5 attempts with a fixed 5,000 ms delay and no backoff Git source control, environments and log streaming are Enterprise-only The Sustainable Use License permits internal business and non-commercial use only	6.9	Mixed technical teams orchestrating across many SaaS systems	Sep 29, 2026
7 ↓ 1	Windmill Windmill executes scripts written in TypeScript, Python, Go, Bash and SQL, composes them into flows, and generates user interfaces from function parameters. Flows support retries, error handlers, suspend-and-approve steps, branching, for-loops and concurrency limits. Windmill documentation states that a single worker processes approximately 26 million jobs per month at roughly 100 ms per job, with about 50 ms of added latency between queue pull and result write-back. Licensing is split rather than single-SPDX: backend and frontend are AGPLv3 except code behind the enterprise compile flag, and the GitHub API reports Other (NOASSERTION). The windmill-labs/windmill repository carried 18,060 stars on 29 September 2026 (version 1.819.0), with seven releases published in the four days to 27 July 2026. Strengths: Multi-language scripts (TypeScript, Python, Go, Bash, SQL) in a single engine Suspend-and-approve steps make human-in-the-loop a first-class flow primitive Auto-generated user interfaces remove a separate internal-tools build Release cadence of several versions per week Weaknesses: AGPLv3 with a proprietary enterprise compile flag; GitHub reports no single SPDX licence Smaller documentation surface than the older projects in this ranking The free self-hosted plan allows a maximum of 10 users with SSO (windmill.dev/pricing, read 29 September 2026) On the free Community Edition observability is a dashboard rather than a metrics-and-alerting stack; Prometheus, critical alerts, audit logs and OpenTelemetry export are Enterprise-only (windmill.dev/platform/observability and windmill.dev/pricing, read 29 September 2026)	6.9	Developer teams wanting script-based workflows with generated UIs	Sep 29, 2026
8 ↓ 1	Activepieces Activepieces is a self-hostable visual automation platform whose cloud registry returned 763 pieces covering 5,780 actions and 1,523 triggers on 29 September 2026. Runs are durable to a degree unusual for a visual builder: a compressed run log checkpoints every 15 seconds, work is replayed and skipped on worker death, and DELAY or WEBHOOK waitpoints hold a paused run for up to 30 days. Licensing is a hybrid rather than plain MIT, correcting a claim this page previously carried: the root LICENSE covers the repository under MIT except packages/ee and packages/server/api/src/app/ee, which fall under a proprietary Activepieces Enterprise licence requiring a paid seat licence for production use, and GitHub accordingly reports no SPDX identifier. The repository held 24,786 stars on 29 September 2026 (version 0.91.3). Strengths: 763 pieces covering 5,780 actions as of 29 September 2026 Checkpointed run log with replay-and-skip recovery after worker death Waitpoints hold a paused run for up to 30 days Docker, Compose, Helm and Pulumi deployment with limits set by environment variable Weaknesses: Not plain MIT: packages/ee and the server ee directory are proprietary and need a paid licence Cloud code steps run in isolated-vm at 128 MB with require removed and no npm access No parallel fan-out or join; the tracking issue has been open since May 2023 Key-value state is capped at 512 KB and is not configurable Cloud executions are capped at 10 minutes; the documented remedy is splitting flows	6.2	Teams wanting a self-hostable visual builder with a large connector catalogue	Sep 29, 2026
9	Moxo Moxo is a hosted platform for processes whose steps are mostly people, and its engine carries more pattern depth than the no-code builder suggests: parallel branches that rejoin, jump-back revision loops, for-each iteration, sub-flows that wait on a child flow, and a WAIT step resumed by a callback token (Description of Services and API v2.0.0, read 28 September 2026). It loses ground on what an engine buyer measures next: no compensation construct, no published concurrency benchmark or SLA, and no workflow-as-code. Branching, loops and sub-flows start on the custom-quoted Scale plan; Team is $5,000 a year for 100 flows (moxo.com/pricing, 28 September 2026). Strengths: Parallel branches rejoin when complete, and for-each iteration runs a set of steps once per item (Description of Services, read 28 September 2026) Sub-flows wait on a child flow, and a WAIT step resumes on its callback token with optional result data (Moxo API v2.0.0) Managers can retry a failed automation step or skip one not yet started through the API, and a per-template Process Health score tracks on-time rate, SLA compliance and cycle time A 101-path OpenAPI 3.1 specification and an MCP server expose flows and templates to code and AI clients, from the Scale plan Weaknesses: No saga or compensation construct: a failed later step cannot undo the steps before it No API call moves a running flow onto a newer template version, so a fix reaches new flows while open ones are adjusted by hand No concurrency benchmark, throughput figure or availability SLA is published; the API allows 1,000 requests a minute per key No workflow-as-code, local runtime or self-hosted licence, and branching, loops and sub-flows start on the custom-quoted Scale plan	5.4	Teams orchestrating long, people-heavy processes that cross company lines	Sep 29, 2026
10	Zapier Zapier connects 9,000-plus applications through trigger-action Zaps, with Paths for conditional branching, Sub-Zaps for reusable sub-workflows, Looping, Delay and Code steps. It is evaluated here as the boundary case for this category, because whether an existing Zapier estate can carry orchestration work is a question most teams ask before buying an engine, and it deserves a scored answer. Zapier documentation answers it precisely: Path branches "run one at a time, left to right" with no join step available after them, looping caps at 500 iterations with one Looping step per Zap and no nesting, Delay holds for at most 30 days, and recovery is autoreplay of up to five attempts across roughly 10 hours 35 minutes rather than durable execution. Zapier publishes a Service Level Agreement effective 15 June 2026 committing to at least 99.9% monthly uptime for Workflows and Tables, but only where an Enterprise Agreement or Order Form references it. Strengths: 9,000-plus connected apps: the largest catalogue in this ranking by an order of magnitude Zap History gives step-level input and output data with one-click replay Since 26 March 2026, Code steps on paid plans can import public npm and PyPI packages Enterprise adds SSO, SCIM, RBAC, an audit trail API and log streaming to Datadog or Splunk Weaknesses: No durable execution, saga or compensation: a failed later step cannot roll back earlier ones Path branches run sequentially, with no fan-out and no join No self-hosting; all execution runs in Zapier multi-tenant AWS us-east-1 infrastructure No workflow-as-code: the Platform CLI builds app integrations, not Zaps, and the Workflow API that creates Zaps programmatically is gated to developers with a public integration; a Zapier SDK for TypeScript is labelled open beta (docs.zapier.com/sdk, read 29 September 2026) Run history is retained 29 to 69 days by default, customisable only within 7 to 30 days on Enterprise	5.4	Teams connecting many SaaS systems where breadth of coverage matters more than durable execution	Sep 29, 2026

Methodology

Ten platforms scored on orchestration depth (25%), scalability (20%), developer experience (20%), monitoring (20%) and community (15%), from vendor documentation, GitHub data and published benchmarks read on 28 and 29 September 2026. Positions follow total score. Ties are broken by length of documented production track record.

Read full methodology

Scoring Methodology

Each orchestration platform was evaluated across five weighted criteria, scored on a 1-10 scale with the final score as a weighted average.

Orchestration Depth (25%)

The sophistication of workflow patterns the platform can express and execute reliably. Evaluation covers conditional branching (if/else, switch), sub-workflow composition, parallel execution with join semantics, saga patterns with compensation logic, dynamic workflow generation (creating steps at runtime based on data), and timer-based scheduling. Platforms supporting saga compensation natively (Temporal, Camunda) score higher than those requiring manual implementation.

Scalability (20%)

Concurrent workflow capacity under production load, scored from published benchmarks, documented limits and service-level terms (see the re-evaluation and September 2026 re-scoring sections below; sources read 28 July and 28 to 29 September 2026). Evidence considered includes p50/p95/p99 latency, failure rate under load, horizontal scaling behavior, and cluster management complexity. Backpressure handling (queuing with bounded memory vs cascading failures) is assessed.

Developer Experience (20%)

SDK quality across supported languages including type safety, IDE integration, and testing support. Local development experience (can developers run and debug workflows without a server?), documentation completeness, and the presence of production-ready examples. Debugging tools such as workflow visualization, step-level payload inspection, and replay capabilities are evaluated.

Monitoring (20%)

Built-in observability features: workflow execution history, step-level status tracking, duration metrics, failure alerting, and audit trails. Speed of identifying a failing step, inspecting input/output payloads, and retrying or skipping. Integration with external monitoring systems (Prometheus, Datadog, Grafana) alongside native dashboards.

Community (15%)

GitHub activity (stars, contributors, commit frequency, issue response time), documentation contributions, community-maintained extensions, and commercial support availability. Ecosystem sustainability (funded company vs volunteer-maintained) and quality of learning resources (tutorials, courses, conference talks).

Re-evaluation — 28 July 2026

This page was re-scored against the same five weighted criteria. Every sub-score was re-derived from vendor documentation, GitHub API responses and published benchmarks retrieved on 28 July 2026, rather than adjusted from the previous figures.

Scope change

Zapier was added at position 9. It is an active tool in this ranking's own category and previously appeared in the page's "not yet evaluated" transparency block. It is included as the category boundary case: the question of whether an existing Zapier estate can carry orchestration work is one most teams ask before buying an engine, and it deserves a scored answer rather than an omission. Inngest and Trigger.dev were assessed for inclusion in the same pass and were not added; both have a stronger claim to this category than Zapier on orchestration depth, and both remain candidates for the next review.

Ties

In the July 2026 totals, n8n and Hatchet both scored 6.9, and n8n was placed higher on the published tiebreak, length of documented production track record. The September 2026 ties are set out below.

Corrections applied

Three defects in the March 2026 state were corrected rather than carried forward:

Claim previously published	Verified position, 28 July 2026
Activepieces: "MIT license (most permissive)"	The root LICENSE carves out `packages/ee` and `packages/server/api/src/app/ee` under a proprietary Activepieces Enterprise licence; the GitHub API reports no SPDX identifier. Temporal and Hatchet are the only whole-repository MIT projects in this list.
Activepieces: "200+ connectors"	The vendor cloud registry returned 756 pieces, 5,549 actions and 1,482 triggers.
n8n: "400+ integrations"	The documentation sitemap yields 520 built-in node pages; the n8n homepage says "over 500". The 400+ figure survives only in the GitHub repository description.

Positions were also re-sequenced. Hatchet had been appended at position 8 carrying a score of 7.70, above positions 5 to 7 at 7.50, 7.20 and 6.80, so the rendered score column read out of order.

Choosing between these platforms

Diagram source (Mermaid)

flowchart TD
  A[Choosing a process orchestrator] --> B{Must a run survive a crash mid-execution?}
  B -- No --> C{Mostly SaaS-to-SaaS steps?}
  C -- Yes --> D[Zapier or Activepieces]
  C -- Mixed, some code --> E[n8n or Windmill]
  B -- Yes --> F{Is the process modelled by non-engineers?}
  F -- Yes --> G[Camunda, BPMN]
  F -- No --> H{Scheduled data pipelines?}
  H -- Yes --> I[Airflow or Prefect]
  H -- No --> J[Temporal or Hatchet]

September 2026 re-scoring

On 28 and 29 September 2026 every entry was re-scored against the published criteria from vendor pricing, documentation, trust and status pages read on those dates, and each entry now shows its per-criterion scores. Two pairs of entries display the same total: n8n and Windmill at 6.9, and Moxo and Zapier at 5.4. Neither is a true tie. Unrounded, n8n scores 6.90 against Windmill's 6.85, and Moxo 5.40 against Zapier's 5.35, so both pairs are ordered by unrounded total and the published tiebreak, length of documented production track record, is not needed.

What the July 2026 pass corrected

The July 2026 pass lowered eight of the nine scores then on the page. It was a re-baselining of the whole scale rather than a judgement on individual products: the March 2026 figures had been generous across the board, and the September 2026 scores for all 10 entries were re-derived from vendor documentation. The same pass withdrew a licensing claim. The page had described Activepieces as "MIT license (most permissive)"; its root LICENSE places two enterprise directories under a proprietary licence, and the two whole-repository MIT projects in this list are Temporal and Hatchet (28 July 2026).

Zapier's 5.4 comes from criteria that give 45 percent of the weight to orchestration depth and developer experience, where a platform with no durable state and no workflow-as-code has least to offer. Zapier's documentation sets the limits: Path branches run one at a time with no join, Delay caps at 30 days, and a failed run is replayed rather than resumed. That describes this category's rubric, not the product's value for the SaaS-to-SaaS work it was built for.

Engine criteria set both ends of this list

Orchestration depth carries 25 percent of the weight, and scalability, developer experience and community together carry 55 percent. Those three reward a code-first engine with published load figures, SDKs, local development and a public repository. That is why Temporal leads at 9.1 with no criterion below 8, and why the two entries built for other work close the list: Moxo scores 4 on scalability and 3 on community, and Zapier scores 3 on orchestration depth and 4 on developer experience (28 and 29 September 2026).

One rule on outside evidence applies to every vendor. Customer logos, case-study figures and user counts count only where a criterion covers track record, and none of the five criteria here does, so they enter this page only through the tiebreak. Compliance attestations such as SOC 2 are named in no criterion and earn no points for any entry. Features sold on a higher plan count toward a score, and the entry names the plan that carries them.

When this rubric is the wrong lens

This page scores the engine under a process: pattern depth, concurrency, code-level tooling, observability and project activity. It under-measures two kinds of product that readers often shortlist beside an engine. Visual SaaS builders such as Zapier are scored here as the category's boundary case, because most teams ask whether an existing estate can carry orchestration work before they buy an engine. People-first process platforms such as Moxo, where most steps are approvals, forms and hand-offs across company lines, meet much of the orchestration-depth criterion (Moxo scores 7, level with Windmill) but publish no concurrency benchmark, local runtime or core repository (28 and 29 September 2026). The decision tree above has no branch for a process that is mostly people.

Readers whose question is how a person enters an automated path, and what the record proves afterwards, should read the ranking of human-in-the-loop platforms, which scores that mechanism on its own criteria.

Verification

Every figure on this page was read from a vendor-owned surface, with 28 and 29 September 2026 as the retrieval dates unless another date is stated against the figure. The surfaces checked were vendor pricing, documentation, trust and status pages and release histories: the GitHub release pages for Temporal, Camunda and Apache Airflow, docs.n8n.io, docs.hatchet.run, windmill.dev, the Activepieces documentation, docs.zapier.com and Zapier's Service Level Agreement, and for Moxo its Description of Services, API specification and changelog, and its pricing, security and status pages. Figures carried from the 28 July 2026 pass are dated where they appear.

Several figures a buyer might expect are not published, and the page states the gap rather than estimating a number. Moxo publishes no concurrency benchmark, throughput figure or availability SLA, and its Scale and Enterprise plans are custom quotes. Prefect Cloud published quotas but no prices as of 28 July 2026. Zapier's 99.9 percent monthly uptime commitment applies only where an Enterprise Agreement or Order Form references it. Hatchet's published benchmark ran on engine v0.55.26 while the current release is v0.107.0, and the entry says so.

Where a vendor's own surfaces disagree, both readings appear on the page and the disagreement is stated, rather than the more flattering figure being chosen. n8n's GitHub repository description still says "400+ integrations" while its homepage says "over 500" and its documentation sitemap yields 520 node pages (28 July 2026). Prefect marketing that cites "40k+ stars" aggregates several repositories, against 23,952 on the core repository (29 September 2026). Moxo's served OpenAPI description still lists step.activated and step.failed as webhook events, while its API changelog says both were dropped from webhooks and are sent only as server-sent events, so neither is cited here as a webhook.

Prices, plan gates and release numbers move faster than engine mechanics. Before relying on a cost figure, re-read the vendor's pricing page and confirm which plan still carries the feature, because on this list observability, audit logs and APIs are often sold on a higher plan than the builder itself.

Editor's Note: These criteria were shaped by 9 production deployments managing workflows from 50 daily runs (startup) to 15,000 daily runs (fintech data platform). The orchestration depth score reflects actual pattern support: Temporal and Camunda handle saga compensation natively, while simpler tools require manual implementation. Monitoring scores reflect real debugging sessions: how quickly we could identify the failing step, inspect payloads, and retry. That test is why Zapier scores 8 on monitoring despite a 3 on orchestration depth: Zap History shows step-level input and output with one-click replay. — Rafal Fila, ShadowGen

Common Questions

How do banks and wealth firms use Moxo for client onboarding?

Moxo's financial-services page (read 13 October 2026) pitches account opening and KYC reviews as shared work: the client gets a secure link to see what is needed and sign, while relationship managers, compliance and operations staff review and approve inside one tracked flow. The…

Can healthcare teams run patient-facing workflows on Moxo?

Yes for coordination work, once a signed BAA is in hand: Moxo told Automation Atlas in writing on 6 October 2026 that it signs BAAs, but it publishes none and did not say which plans the agreement covers or whether it reaches Moxo AI. Moxo says it has no native EHR, HL7 or FHIR…

Who is accountable when an AI agent acts in a Moxo workflow?

The company that deploys the agent is accountable: Moxo's Terms and Conditions (read 13 October 2026) make the customer "solely responsible for any AI Content, including the accuracy, quality, appropriateness, and legality thereof". In the workflow, a named person owns each human…

How does Moxo keep humans in control when AI agents run a workflow?

Moxo keeps people on the decisions by design: approvals and other human steps are ones its product page says "only a person can close", and AI agents can fill preparer, advisor or reviewer slots around them (both read 15 September 2026). The checks on AI output are opt-in…

comparison

Moxo vs Gumloop in 2026: Texting the Client, or Building the Agent

Gumloop (founded 2023) builds AI agents a company's own staff run; Moxo, whose predecessor Moxtra was co-founded in 2012, runs processes that wait on people outside the company. Gumloop wins three rounds to two: the way in, per-tool gating and a priced overage. Moxo wins on…

comparison

Moxo vs Relay.app in 2026: Where Relay's Approval Workflows Can Go Next

Relay.app, founded in 2021, shut down in September 2026 and deleted every account, workflow and run history; Moxo, whose predecessor Moxtra was co-founded in 2012, is one destination for its human-in-the-loop users. Relay.app takes two rounds, Moxo one, and vendor risk is a draw…

comparison

Moxo vs Workato in 2026: The Integration Estate, or the Approval Inside It

Workato, founded in 2013, is an enterprise integration platform whose Workflow apps add human tasks to recipes; Moxo, whose predecessor Moxtra was co-founded in 2012, ships the human step itself. Workato wins three rounds to two: connector reach, change control and the way in…

Best Process Orchestration Platforms 2026

Common Questions

Related Guides