
# Workflow orchestration on DigitalOcean

Compare documented Workflow orchestration deployments on DigitalOcean, including operating responsibility, licensing and deployment evidence.

Canonical page: https://launchinyourcloud.com/clouds/digitalocean/workflow-orchestration/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


## Provider guidance

- Account boundary: DigitalOcean team/account and project
- Provider group: cloud-infrastructure
- Provider classification: Droplets and managed Kubernetes use the customer infrastructure account. App Platform is a separate platform-workspace path and is identified per listing. Source: https://docs.digitalocean.com/products/droplets/how-to/create/ (checked 2026-11-20).
- Network: VPC and Cloud Firewalls; review public endpoints
- Identity and access: Team roles, scoped API tokens and SSH keys
- Installation guidance: Provision Droplets or Kubernetes in your account; review the application image, storage, updates and firewall rules.
- Guidance source: https://docs.digitalocean.com/products/droplets/how-to/create/
- Guidance reviewed: 2026-11-12


### Private networking

DigitalOcean VPCs isolate resource traffic from the public internet; VPC peering can connect VPCs. Confirm the selected service can join the intended VPC and configure application access controls.
Source: https://docs.digitalocean.com/products/networking/vpc/ (reviewed 2026-11-14).

The listings below have evidence for DigitalOcean. Read each cloud evidence note for the applicable package, edition and support qualifications.

2 listings.


## Apache Airflow

Workflow orchestration platform for scheduling and monitoring data pipelines and other task workflows authored in Python or supported non-Python formats.

- Listing: https://launchinyourcloud.com/directory/apache-airflow/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for upstream Airflow; dependencies, provider integrations and external services have their own terms.
- Licensing model: open-source
- Installation: Install the Python distribution or official container images; the Apache Airflow Helm chart deploys the platform to a customer-operated Kubernetes cluster.
- Architecture: Scheduler, Dag processor, API server and metadata database, with executor-dependent workers and optional triggerers
- Operations: Customer operates Airflow services, database, worker capacity, Dag code, credentials, authorization, logs, backups and version upgrades.
- Product website: https://airflow.apache.org/
- Source review: 2026-11-14; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

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.

The reviewed upstream project uses Apache License 2.0. This classification covers the upstream software; third-party components and separately operated services retain their own terms.

Airflow components are Python services that run on servers or Kubernetes pods with persistent metadata storage. Worker layout depends on the selected executor; a serverless task executor does not make the Airflow control plane serverless.


### Category fit

- workflow-orchestration: 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.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://airflow.apache.org/docs/apache-airflow-providers-amazon/stable/logging/s3-task-handler.html (checked 2026-11-12). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.digitalocean.com/products/marketplace/catalog/airflow/ (checked 2026-11-12). 


### Cloud deployment evidence

- Airflow Helm deployment on EKS with IAM roles (aws): https://airflow.apache.org/docs/apache-airflow-providers-amazon/stable/logging/s3-task-handler.html
  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.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Apache Airflow full application on DigitalOcean (digitalocean): https://docs.digitalocean.com/products/marketplace/catalog/airflow/
  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.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

The official announcement feed records Airflow 3.4.0 released on November 6, 2026. Stable 1.0.0 TypeScript, Java and Go SDKs followed on November 13, confirming maintained non-Python Dag authoring. The project publishes a named Adyen case study describing production orchestration across more than 20 teams and maintains a broad self-reported organization list; these establish adoption beyond repository popularity.

Reviewed 2026-11-14.

- Current release announcements: https://airflow.apache.org/announcements/

- Adyen production case study: https://airflow.apache.org/use-cases/adyen/

- Project-maintained organization list: https://github.com/apache/airflow/blob/main/INTHEWILD.md

- Airflow 3.4 whole-Dag authoring beyond Python: https://airflow.apache.org/blog/airflow-3.4.0/

- Stable TypeScript SDK 1.0.0: https://github.com/apache/airflow/releases/tag/ts-sdk/1.0.0

- Stable Java SDK 1.0.0: https://github.com/apache/airflow/releases/tag/java-sdk/1.0.0

- Stable Go SDK 1.0.0: https://github.com/apache/airflow/releases/tag/go-sdk/v1.0.0

### Sources

- What Apache Airflow does: https://airflow.apache.org/docs/apache-airflow/stable/

- Component architecture and deployment: https://airflow.apache.org/docs/apache-airflow/stable/core-concepts/overview.html

- Official Apache Airflow Helm chart: https://airflow.apache.org/docs/helm-chart/stable/index.html

- Upstream Apache-2.0 and subcomponent licenses: https://github.com/apache/airflow/blob/main/LICENSE

- DigitalOcean Airflow application deployment: https://docs.digitalocean.com/products/marketplace/catalog/airflow/

- Airflow 3.4 whole-Dag authoring beyond Python: https://airflow.apache.org/blog/airflow-3.4.0/

- Airflow TypeScript SDK 1.0.0: https://github.com/apache/airflow/releases/tag/ts-sdk/1.0.0

- Airflow Java SDK 1.0.0: https://github.com/apache/airflow/releases/tag/java-sdk/1.0.0

- Airflow Go SDK 1.0.0: https://github.com/apache/airflow/releases/tag/go-sdk/v1.0.0

### Licensing sources

- https://github.com/apache/airflow/blob/main/LICENSE

### Infrastructure sources

- https://airflow.apache.org/docs/apache-airflow/stable/core-concepts/overview.html

- https://airflow.apache.org/docs/helm-chart/stable/index.html


### Buyer diligence


Research coverage: 6/12 fields (50%); 6 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Documented. DigitalOcean provides an Airflow Droplet 1-Click package and separately links a Terraform Blueprint for production. The reviewed image is 3.3.2, not the upstream 3.4 release snapshot; a 4 GB API example is not a production sizing guarantee. Scope: DigitalOcean-listed package; Apache commercial support is not established. Source: https://docs.digitalocean.com/products/marketplace/catalog/airflow/ (reviewed 2026-11-14). Offer airflow: Not identified on the reviewed marketplace page; Droplet 1-Click; package 3.3.2; https://marketplace.digitalocean.com/apps/airflow.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The FAB Auth Manager provider documents OAuth login with named IdPs and custom provider configuration. Enable the compatible FAB auth manager, configure provider credentials/callbacks and user/role mapping; the default authentication manager and API/execution-token paths differ. This is an optional configured integration, not automatic SSO in every Airflow image. Scope: Airflow web-user authentication through the FAB provider; verify Airflow/provider version compatibility. Source: https://airflow.apache.org/docs/apache-airflow-providers-fab/stable/auth-manager/webserver-authentication.html (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Apache publishes an Airflow Helm chart with configurable executors and supporting services. Database migrations, chart/application compatibility, secrets and persistent logs require explicit planning. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://airflow.apache.org/docs/helm-chart/stable/index.html (reviewed 2026-11-14).

- Minimum footprint / sizing: Documented. The upstream prerequisites recommend at least 4 GB memory but explicitly make capacity deployment-dependent. Scheduler/API, metadata database, triggerer and executor/workers have different resource needs. Task concurrency, DAG parsing, logs, database I/O and replicas must be sized separately; the 4 GB floor is not an HA workload allocation. Scope: Current application installation floor; full service/worker and HA capacity is workload-specific. Source: https://airflow.apache.org/docs/apache-airflow/stable/installation/prerequisites.html (reviewed 2026-11-20).

- License pricing: Documented. The reviewed upstream application uses Apache License 2.0 with separately identified bundled-component notices. Review the licence and bundled-component notices for your use and distribution. Hosting, databases, delivery services, commercial support and any separately licensed additions have their own costs and terms; no hosted-plan price is treated as a self-hosted quote. Scope: Apache Airflow 3.4.0 application; not a provider-hosted service; software terms only, excluding infrastructure and operations. Source: https://github.com/apache/airflow/blob/3.4.0/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The publisher-designated GitHub release checked was 3.4.0, published 2026-11-06. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package. Scope: Upstream apache/airflow release record; commercial editions and deployment packages may differ. Source: https://github.com/apache/airflow/releases/tag/3.4.0 (reviewed 2026-11-14).







## Kestra Self-Hosted

Self-hosted orchestration platform for scheduled and event-driven workflows across data, infrastructure and applications.

- Listing: https://launchinyourcloud.com/directory/kestra/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for the open-source Kestra platform; commercial Enterprise features and support are separate.
- Licensing model: open-source
- Installation: Docker on AWS EC2 or DigitalOcean Droplets, or Helm on AWS EKS, Google GKE or Azure AKS, with documented database and object storage services.
- Architecture: Customer-operated Kestra server and workers with PostgreSQL queue/repository state and object storage
- Operations: Customer manages server and worker capacity, PostgreSQL, object storage, plugins, credentials, network access, backups and upgrades.
- Product website: https://kestra.io/
- Source review: 2026-11-18; cloud review: 2026-11-13; licensing review: 2026-11-13; infrastructure review: 2026-11-13

### Scope and qualifications

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.

The reviewed Kestra platform is Apache-2.0 licensed. Commercial Enterprise features and support are separately licensed and do not change the upstream open-source classification.

Kestra runs long-lived server and worker processes backed by PostgreSQL and object storage. The documented cloud paths use customer-configured compute or Kubernetes and managed database/storage services.


### Category fit

- workflow-orchestration: Orchestrates scheduled and event-driven data, infrastructure, business and AI workflows with customer-operated execution workers.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://kestra.io/docs/installation/aws-ec2 (checked 2026-11-13). Source: https://kestra.io/docs/installation/kubernetes-aws-eks (checked 2026-11-13). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://kestra.io/docs/installation/kubernetes-azure-aks (checked 2026-11-13). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://kestra.io/docs/installation/kubernetes-gcp-gke (checked 2026-11-13). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://kestra.io/docs/installation/digitalocean-droplet (checked 2026-11-13). 


### Cloud deployment evidence

- Kestra on Amazon EC2 with RDS and S3 (aws): https://kestra.io/docs/installation/aws-ec2
  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.
  Source type: vendor-documentation; reviewed: 2026-11-13; vendor support: not-assessed.

- Kestra on Amazon EKS with RDS and S3 (aws): https://kestra.io/docs/installation/kubernetes-aws-eks
  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.
  Source type: vendor-documentation; reviewed: 2026-11-13; vendor support: not-assessed.

- Kestra on Google GKE with Cloud SQL and Cloud Storage (gcp): https://kestra.io/docs/installation/kubernetes-gcp-gke
  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.
  Source type: vendor-documentation; reviewed: 2026-11-13; vendor support: not-assessed.

- Kestra on Azure AKS with PostgreSQL and Blob Storage (azure): https://kestra.io/docs/installation/kubernetes-azure-aks
  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.
  Source type: vendor-documentation; reviewed: 2026-11-13; vendor support: not-assessed.

- Kestra on DigitalOcean Droplets with Managed Database and Spaces (digitalocean): https://kestra.io/docs/installation/digitalocean-droplet
  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.
  Source type: vendor-documentation; reviewed: 2026-11-13; vendor support: not-assessed.


### Sources

- AWS EC2 deployment with RDS and S3: https://kestra.io/docs/installation/aws-ec2

- AWS EKS deployment with RDS and S3: https://kestra.io/docs/installation/kubernetes-aws-eks

- Apache 2.0 project license: https://github.com/kestra-io/kestra/blob/develop/LICENSE

- Kestra on Google GKE with Cloud SQL and Cloud Storage: https://kestra.io/docs/installation/kubernetes-gcp-gke

- Kestra on Azure AKS with PostgreSQL and Blob Storage: https://kestra.io/docs/installation/kubernetes-azure-aks

- Kestra on DigitalOcean Droplets with Managed Database and Spaces: https://kestra.io/docs/installation/digitalocean-droplet

- Kestra v2.0.11 release: https://github.com/kestra-io/kestra/releases/tag/v2.0.11

### Licensing sources

- https://github.com/kestra-io/kestra/blob/develop/LICENSE

### Infrastructure sources

- https://kestra.io/docs/installation/aws-ec2

- https://kestra.io/docs/installation/kubernetes-aws-eks

- https://kestra.io/docs/installation/kubernetes-gcp-gke

- https://kestra.io/docs/installation/kubernetes-azure-aks

- https://kestra.io/docs/installation/digitalocean-droplet


### Buyer diligence


Research coverage: 6/12 fields (50%); 6 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Edition-dependent. The Enterprise authentication guide documents OIDC single sign-on with providers such as Google, Microsoft, Okta and Keycloak. This does not establish SSO in the OSS edition. Scope: Self-managed Kestra Enterprise. Source: https://kestra.io/docs/enterprise/auth/sso (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. Current advisory review: Kestra v2.0.11 updates dependencies for CVE-2026-45292 and enforces CSRF tokens for Basic-auth browser requests. Upgrade to v2.0.11 or later and retest browser and API authentication flows. Scope: Upstream v2.0.11 release; consult the dependency advisories for component-specific ranges.. Source: https://github.com/kestra-io/kestra/releases/tag/v2.0.11 (reviewed 2026-11-18).

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The Compose guide provides a standalone server with PostgreSQL and a moving develop-branch recipe. Its root user and Docker socket example is for development; production hardening and licensed images are separate. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://kestra.io/docs/installation/docker-compose (reviewed 2026-11-14). Deployment artifact: https://raw.githubusercontent.com/kestra-io/kestra/develop/docker-compose.yml. Artifact reference: develop (moving branch); development example.

- Minimum footprint / sizing: Documented. The official EC2 guide starts Kestra at 2 vCPUs and 4 GiB RAM, suggesting t3.medium for its example. PostgreSQL, object storage, task execution and redundancy are separate capacities. Validate workflow/task concurrency and data movement; the example host is not a complete 1 TB HA production design. Scope: Official AWS application starting point with separately configured database and object storage. Source: https://kestra.io/docs/installation/aws-ec2 (reviewed 2026-11-20).

- License pricing: Documented. The published v2.0.11 core is Apache-2.0 licensed. Enterprise authentication and other commercial features require their own edition agreement and are not granted by the OSS licence. Infrastructure, database/object storage, task execution and support costs are separate from software licensing. Scope: Published Kestra OSS core versus self-hosted Enterprise features. Source: https://github.com/kestra-io/kestra/blob/v2.0.11/LICENSE (reviewed 2026-11-20). Supporting source: Self-managed Enterprise SSO scope — https://kestra.io/docs/enterprise/auth/sso.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Kestra v2.0.11 was published November 17, 2026. It updates dependencies for CVE-2026-45292 and other vulnerable libraries and enforces CSRF tokens on Basic-auth browser requests. Scope: Upstream Kestra 2.0 release. Source: https://github.com/kestra-io/kestra/releases/tag/v2.0.11 (reviewed 2026-11-18).




### Security and lifecycle reviews

Selected editorial reviews only; no flag does not mean safe or supported.

- Kestra 2.0.11 dependency and CSRF update (security-advisory): Kestra v2.0.11 updates dependencies for CVE-2026-45292 and enforces CSRF tokens for Basic-auth browser requests. Scope: Upstream v2.0.11 release; consult the dependency advisories for component-specific ranges. Conditions: Browser behavior changes when Basic authentication is used; dependency exposure depends on the deployed components. Action: Upgrade to v2.0.11 or later and retest browser and API authentication flows. Source: https://github.com/kestra-io/kestra/releases/tag/v2.0.11; reviewed 2026-11-18.



