Workflow orchestration on DigitalOcean

Durable execution and orchestration for application workflows.

2 documented options on DigitalOcean. Provider coverage reflects reviewed evidence, not an exhaustive compatibility claim.

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

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

Deployment evidence and category 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.

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.

  • Apache Airflow full application on DigitalOcean ↗

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

    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.

Cloud evidence reviewed 2026-11-12. Full listing and qualifications

Kestra Self-Hosted

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

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 DigitalOcean Droplets with Managed Database and Spaces ↗

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

    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.

Cloud evidence reviewed 2026-11-13. Full listing and qualifications

Deployment and procurement checks

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. Provider source ↗ · Reviewed 2026-11-14

For every provider, confirm marketplace/private-offer terms, commitment eligibility, regional service availability, private connectivity and any vendor access against your selected deployment. Provider capabilities do not automatically establish application support.

Plan this deployment

Account boundary: DigitalOcean team/account and project. Access: Team roles, scoped API tokens and SSH keys. Network: VPC and Cloud Firewalls; review public endpoints.

Provider documentation ↗ · Guidance reviewed 2026-11-12. Confirm the application edition, region, support access, backup locations and operating responsibilities before choosing.

Compare this category across clouds · Search these listings · Compare 2–4 listings