Workflow orchestration

Durable execution and orchestration for application workflows.

7 listings, including 7 from other publishers. Entries cover the deployment options documented on their individual pages.

Watch this category with RSS · Build a requirements shortlist

Deployment comparison

ListingDocumented cloudsDeployment and infrastructureLicensingInstallationOperations and limitations
Apache AirflowAWS, DigitalOceanCustomer-operated
Servers / containers
Open Source / Open Core

Apache License 2.0 for upstream Airflow; dependencies, provider integrations and external services have their own terms.

Install the Python distribution or official container images; the Apache Airflow Helm chart deploys the platform to a customer-operated Kubernetes cluster.Customer operates Airflow services, database, worker capacity, Dag code, credentials, authorization, logs, backups and version upgrades.
Scope and evidence

The Helm chart is a deployment mechanism, not a managed control plane. Providers and Dag tasks can call external databases, APIs, compute or model services. Review each integration and executor before treating a complete pipeline as contained in the account. Managed Airflow services are separate offerings. Airflow 3.4’s Dag Importer and language-SDK support is experimental; non-Python Dag authoring requires the applicable language runtime and coordinator on Dag processors and workers.

  • Airflow Helm deployment on EKS with IAM roles — The current upstream Amazon provider guide explicitly configures Airflow Helm webserver/worker pods on EKS, including their service account, and links a self-managed Terraform deployment example. S3 logging is optional infrastructure configuration; this is not Amazon Managed Workflows for Apache Airflow. Restrict the example IAM permissions for production.

    Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Apache Airflow full application on DigitalOcean — The provider catalog provisions Airflow on a customer Ubuntu 24.04 Droplet, with the application UI, local PostgreSQL and Redis, or customer-managed database services and Celery workers. This is full application hosting, not a database connector. The catalog does not identify the exact Airflow package release; verify the selected image, compatible dependencies, TLS, access controls, backups and upgrades.

    Provider guide · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-12

Camunda 8 Self-ManagedAWS, Azure, Google CloudCustomer-operated
Servers / containers
Commercial Only

Commercial Enterprise license required for production; unlicensed use is limited to non-production conditions.

Official Helm charts on EKS, AKS or GKECustomer manages Kubernetes, supported databases or search services, storage, ingress, identity, backups, scaling and upgrades.
Scope and evidence

This entry covers Camunda 8 Self-Managed, not Camunda SaaS. Match Helm and component versions, size persistent storage for the workload and review external database/search dependencies. A valid Enterprise license is required for production use. Camunda Notice 80 covers critical eMudhra trust-store issues, including CVE-2026-114820, across multiple 8.6–8.10 components; fixed versions differ by component, and Keycloak requires a sufficiently recent rebuilt image. Notices 81 and 82 also patch Web Modeler HTTP parser and custom HTTP/2 denial-of-service paths. Follow the component matrix instead of treating one Helm version as a universal fix. Camunda Optimize 8.6.30 and 8.7.32 mitigate CVE-2026-114938 by disabling the affected AVX-512 Base64 intrinsic. Apply the branch-specific Optimize update, or move to a fixed JDK when supplied, and do not treat a single Helm version as a universal Camunda fix.

  • Camunda 8 Self-Managed on Amazon EKS — Camunda provides current EKS infrastructure and Helm installation guidance for a customer AWS account, including managed persistence dependencies.

    Vendor / upstream documentation · Reviewed 2026-11-14. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Camunda 8 Self-Managed on Microsoft AKS — Camunda provides current AKS and Helm guidance for a customer Azure subscription, with provider-specific reference infrastructure.

    Vendor / upstream documentation · Reviewed 2026-11-14. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Camunda 8 Self-Managed on Google GKE — Camunda documents its Self-Managed Helm deployment and Google Cloud-specific GKE configuration.

    Vendor / upstream documentation · Reviewed 2026-11-14. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-14

Dagster OSSAWSCustomer-operated
Servers / containers
Open Source / Open Core

Apache License 2.0 for upstream Dagster; Dagster commercial services are separate.

Deploy the documented OSS Docker Compose stack with webserver, daemon, code locations and PostgreSQL run storage.Customer manages orchestration services, code images, run storage, execution capacity, access boundaries and upgrades.
Scope and evidence

This listing covers fully self-hosted OSS Dagster, not the commercial hybrid control plane. Integrations, run launchers and user code can use external services. Secure network access to the OSS management services.

  • Dagster OSS Docker Compose deployment on EC2 — The project explicitly identifies an AWS EC2 host for its OSS Docker Compose deployment, including webserver, daemon and code-location containers. Review current images, persistence, secrets and production hardening; this is separate from Dagster Plus and its customer-cloud agent.

    Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-12

HashiCorp Nomad EnterpriseAWS, Azure, Google CloudCustomer-operated
Servers / containers
Commercial Only

Commercial Nomad Enterprise license required for the selected edition; Community Edition uses separate source-available terms.

HashiCorp Validated Design Terraform modules where available or manual package and binary installationCustomer manages servers and clients, TLS, gossip encryption, ACLs, snapshots, networking, workload drivers, upgrades and availability.
Scope and evidence

This entry scopes Nomad Enterprise rather than the separately licensed Community Edition. HashiCorp's validated cloud design requires a production multi-node topology, enterprise license, TLS and gossip encryption, protected snapshots and provider-specific infrastructure. Confirm the current validated module release and supported operating systems before deployment. HCSEC-2026-51, 52, and 53 cover cross-namespace information disclosure plus symlink-based allocation-directory escape and host permission modification. Fixed Enterprise builds are 2.1.0, 1.11.12, and 1.10.18.

  • Nomad Enterprise validated cloud deployment on AWS, Azure and Google Cloud — HashiCorp's Validated Design documents production Nomad deployment on customer AWS, Azure and Google Cloud infrastructure. The operator supplies the Enterprise license and manages the resulting cluster.

    Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-17

Kestra Self-HostedAWS, Azure, Google Cloud, DigitalOceanCustomer-operated
Servers / containers
Open Source / Open Core

Apache License 2.0 for the open-source Kestra platform; commercial Enterprise features and support are separate.

Docker on AWS EC2 or DigitalOcean Droplets, or Helm on AWS EKS, Google GKE or Azure AKS, with documented database and object storage services.Customer manages server and worker capacity, PostgreSQL, object storage, plugins, credentials, network access, backups and upgrades.
Scope and evidence

Vendor guides cover AWS, Azure, Google Cloud and DigitalOcean deployments, including single-VM starting points and distributed Kubernetes installations. Customers operate the application, database and storage configuration; production ingress, authentication, credentials and high availability depend on the selected topology. Enterprise features and support are separately licensed. Kestra v2.0.11 updates dependencies for CVE-2026-45292 and other vulnerable libraries and adds CSRF tokens to Basic-auth browser requests. Recheck browser automation and authenticated API clients after upgrading.

  • Kestra on Amazon EC2 with RDS and S3 — The vendor documents deploying Kestra on a customer EC2 instance and moving database and internal storage to customer RDS PostgreSQL and S3. Secure the application endpoint and replace example broad credentials with least-privilege IAM.

    Vendor / upstream documentation · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Kestra on Amazon EKS with RDS and S3 — The vendor documents a distributed Helm deployment on customer EKS with RDS PostgreSQL, S3 storage and an AWS load balancer. Review cluster sizing, ingress, workload identity, backups and high-availability configuration.

    Vendor / upstream documentation · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Kestra on Google GKE with Cloud SQL and Cloud Storage — The vendor documents creating a GKE cluster, installing the Kestra Helm chart, configuring Cloud SQL PostgreSQL and Cloud Storage, and using Workload Identity. The operator manages the application and cluster configuration, access, persistence and availability.

    Vendor / upstream documentation · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Kestra on Azure AKS with PostgreSQL and Blob Storage — The vendor documents installing Kestra with Helm on a customer AKS cluster and configuring Azure Database for PostgreSQL, Blob Storage and ingress. Configure identities, secrets, network access and production availability for the selected deployment.

    Vendor / upstream documentation · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Kestra on DigitalOcean Droplets with Managed Database and Spaces — The vendor documents creating a customer Droplet, installing Docker and Kestra, and connecting DigitalOcean Managed PostgreSQL and Spaces storage. The customer operates the application and configures network access, credentials, persistent storage and backups.

    Vendor / upstream documentation · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-13

Prefect ServerNorthflank, AWS, Azure, Google CloudCustomer-operated
Servers / containers
Open Source / Open Core

Apache License 2.0 for upstream Prefect. Prefect Cloud is a separate managed offering.

Install Prefect and start its server; use the documented PostgreSQL/Redis architecture when scaling multiple API and background-service instances.Customer manages server services, database, queue/cache, worker pools, secrets, access controls and upgrades.
Scope and evidence

Configure clients and workers against the self-hosted API. Task code and worker integrations can still use external compute and services. Self-hosted control-plane capacity is separate from any serverless execution target. Prefect 3.9.4.dev6 is a prerelease that stops GitRepository from exposing URL-embedded credentials in DEBUG logs and repr output and adds same-origin validation for UI v2 post-login redirects. No stable fixed release was published at review time. Avoid credential-bearing repository URLs, restrict DEBUG logs, rotate exposed tokens and validate the eventual stable release before production rollout.

  • Self-hosted Prefect server and worker on Northflank — Northflank documents the Prefect server/API/UI, PostgreSQL and worker in a customer project, with flow runs launched as separate jobs. This covers the self-hosted control plane, not a worker connected to Prefect Cloud. The hosted platform manages underlying infrastructure; customer project ownership does not imply ownership of its underlying hyperscaler account.

    Provider guide · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Prefect deployment through Northflank BYOC — The provider guide installs the self-hosted Prefect server/API/UI, PostgreSQL and worker and explicitly offers AWS, Google Cloud or Azure through Northflank Bring Your Own Cloud. These hyperscaler badges require the BYOC deployment option and its commercial/access prerequisites; a default Northflank hosted project does not run in the customer hyperscaler account. This is a Northflank deployment recipe, not a claim of Prefect vendor-managed BYOC.

    Provider guide · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-12

Temporal Self-HostedAWSCustomer-operated
Servers / containers
Open Source / Open Core

MIT-licensed Temporal Server; managed Cloud offering is separate

Production Docker/Kubernetes or manual server deployment with persistence and application workersCustomer configures service security, persistence, worker capacity, monitoring, upgrades and disaster recovery.
Scope and evidence

The local CLI development server is not a production installation. Self-hosted Temporal requires substantial operational ownership; the production guide notes that RBAC and audit logging are not provided out of the box. This entry excludes Temporal Cloud and does not describe a packaged end-user workflow application. Temporal v1.32.2 includes security fixes and changes ValidateWorkerDeploymentVersionComputeConfig to require namespace Write access; matching security patches are available as v1.31.5 and v1.30.9. Review namespace permissions before upgrading.

  • Temporal server Helm chart on Amazon EKS — The upstream Temporal server Helm chart explicitly identifies AWS EKS as a target cluster. The current V3 chart deploys server components and requires separately provisioned persistence; it no longer installs database sub-charts. Review schema management, credentials, access controls and production operations. This is separate from Temporal Cloud.

    Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-12

Choose 2–4 listings to compare

Browse listing cards

How these listings fit

Apache Airflow
Directed workflows with task dependencies, scheduling, execution and monitoring. Python remains the traditional authoring language; Airflow 3.4 adds experimental whole-Dag authoring in TypeScript, Java, Go and YAML. Executor and provider configuration determine where work runs.
Camunda 8 Self-Managed
Coordinates durable process instances, service tasks and distributed workers using the Camunda orchestration cluster.
Dagster OSS
Orchestrates data assets and jobs with schedules, sensors, run tracking and separately configured execution code.
HashiCorp Nomad Enterprise
Coordinates long-running services, batch jobs and parameterized workload execution through declarative job specifications.
Kestra Self-Hosted
Orchestrates scheduled and event-driven data, infrastructure, business and AI workflows with customer-operated execution workers.
Prefect Server
Python flow/task orchestration with retries, scheduling, state tracking and workers that execute deployments on configured infrastructure.
Temporal Self-Hosted
Developer-oriented durable workflow execution and retry/state orchestration; application workers and code must be supplied.

Review dates and sources appear on each listing. Functionality, edition, deployment and licensing must be checked together. Filter this category with cloud and deployment controls →

All categories · Suggest a listing or correction