
# Workflow orchestration

Durable execution and orchestration for application workflows.

Canonical page: https://launchinyourcloud.com/categories/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.


Durable execution and orchestration for application workflows.

7 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).







## Camunda 8 Self-Managed

Commercial self-managed process orchestration and workflow automation platform.

- Listing: https://launchinyourcloud.com/directory/camunda-self-managed/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Enterprise license required for production; unlicensed use is limited to non-production conditions.
- Licensing model: commercial-only
- Installation: Official Helm charts on EKS, AKS or GKE
- Architecture: Customer-operated orchestration cluster, connectors, identity services and persistent secondary storage
- Operations: Customer manages Kubernetes, supported databases or search services, storage, ingress, identity, backups, scaling and upgrades.
- Product website: https://camunda.com/platform/
- Source review: 2026-11-19; cloud review: 2026-11-14; licensing review: 2026-11-14; infrastructure review: 2026-11-14

### Scope and qualifications

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 documents unlicensed Self-Managed components as non-production and requires a Camunda Self-Managed Enterprise Edition license for production use.

The documented production topology uses persistent Kubernetes workloads plus databases or search services. Managed provider dependencies do not make the Camunda runtime serverless.


### Category fit

- workflow-automation: Executes modeled business processes, user tasks, connectors and decision-driven automation in customer-operated infrastructure.

- workflow-orchestration: Coordinates durable process instances, service tasks and distributed workers using the Camunda orchestration cluster.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.camunda.io/docs/self-managed/deployment/helm/cloud-providers/amazon/amazon-eks/ (checked 2026-11-14). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.camunda.io/docs/self-managed/deployment/helm/cloud-providers/azure/microsoft-aks/ (checked 2026-11-14). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.camunda.io/docs/self-managed/deployment/helm/cloud-providers/gcp/google-gke/ (checked 2026-11-14). 


### Cloud deployment evidence

- Camunda 8 Self-Managed on Amazon EKS (aws): https://docs.camunda.io/docs/self-managed/deployment/helm/cloud-providers/amazon/amazon-eks/
  Camunda provides current EKS infrastructure and Helm installation guidance for a customer AWS account, including managed persistence dependencies.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.

- Camunda 8 Self-Managed on Microsoft AKS (azure): https://docs.camunda.io/docs/self-managed/deployment/helm/cloud-providers/azure/microsoft-aks/
  Camunda provides current AKS and Helm guidance for a customer Azure subscription, with provider-specific reference infrastructure.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.

- Camunda 8 Self-Managed on Google GKE (gcp): https://docs.camunda.io/docs/self-managed/deployment/helm/cloud-providers/gcp/google-gke/
  Camunda documents its Self-Managed Helm deployment and Google Cloud-specific GKE configuration.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.


### Sources

- Supported self-managed environments: https://docs.camunda.io/docs/reference/supported-environments/

- Amazon EKS deployment: https://docs.camunda.io/docs/self-managed/deployment/helm/cloud-providers/amazon/amazon-eks/

- Microsoft AKS deployment: https://docs.camunda.io/docs/self-managed/deployment/helm/cloud-providers/azure/microsoft-aks/

- Google GKE deployment: https://docs.camunda.io/docs/self-managed/deployment/helm/cloud-providers/gcp/google-gke/

- Self-managed licensing: https://docs.camunda.io/docs/self-managed/components/orchestration-cluster/core-settings/configuration/licensing/

- Camunda security notices: https://docs.camunda.io/docs/reference/notices/

- Camunda Optimize 8.6.30: https://github.com/camunda/camunda/releases/tag/8.6.30-optimize

- Camunda Optimize 8.7.32: https://github.com/camunda/camunda/releases/tag/8.7.32-optimize

- OpenJDK November 2026 advisory: https://openjdk.org/groups/vulnerability/advisories/2026-11-17

### Licensing sources

- https://docs.camunda.io/docs/self-managed/components/orchestration-cluster/core-settings/configuration/licensing/

### Infrastructure sources

- https://docs.camunda.io/docs/self-managed/reference-architecture/kubernetes/

- https://docs.camunda.io/docs/reference/supported-environments/


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 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: Documented. The current Orchestration Cluster guide documents OIDC for Web UI users and OAuth2 API access through an external IdP, with identity mapping and role/authorization configuration. Basic authentication is a different default. Management Identity/Hub and older component releases have separate configurations; configure the selected self-managed version and licensed components. Scope: Current Camunda 8 Orchestration Cluster authentication; not automatic uniform SSO for every component/version. Source: https://docs.camunda.io/docs/self-managed/concepts/authentication/authentication-to-orchestration-cluster/ (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. Current advisory review: Camunda Notices 80–82 cover critical eMudhra trust-store exposure plus Web Modeler HTTP parser and custom HTTP/2 denial-of-service issues. Use the notice's component-specific fixed versions, ensure Keycloak uses a rebuilt image, or remove the named trust roots where Camunda documents that workaround. Apply the Web Modeler fixes separately. Current review: Optimize 8.6.30 and 8.7.32 mitigate CVE-2026-114938, an AVX-512 Base64 intrinsic memory-corruption issue, by forcing -XX:-UseBASE64Intrinsics. Camunda says Optimize decodes untrusted Base64 while then-current base and customer JDKs lacked the upstream fix. Use the branch-specific Optimize release or a fixed JDK 21.0.13.1 or 25.0.5.1 and restart affected processes. Scope: Camunda Optimize 8.6 and 8.7 on affected x86-64 AVX-512 JDKs; other Camunda components require separate assessment. Source: https://github.com/camunda/camunda/releases/tag/8.7.32-optimize (reviewed 2026-11-19). Supporting source: Prior security-controls source — https://docs.camunda.io/docs/reference/notices/. Supporting source: Optimize 8.6.30 mitigation — https://github.com/camunda/camunda/releases/tag/8.6.30-optimize. Supporting source: OpenJDK fixed versions — https://openjdk.org/groups/vulnerability/advisories/2026-11-17.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Camunda publishes Self-Managed Helm charts. Select a chart/application version combination supported by the deployment guide and account for external services, storage and licensed components. Scope: Camunda 8 Self-Managed chart family; not a SaaS subscription. Source: https://github.com/camunda/camunda-platform-helm (reviewed 2026-11-14). Deployment artifact: https://github.com/camunda/camunda-platform-helm. Artifact reference: repository default branch (moving; select a supported chart release).

- Minimum footprint / sizing: Documented. The manual-deployment reference suggests at least 2 CPU cores, 4 GB RAM and 32 GB SSD per host, then requires workload benchmarking. The 8.10 resource-planning guide separately sizes brokers, secondary storage, identity and optional Optimize; retention and replicas materially change storage. Per-host minima are not a complete 1 TB HA platform bill of materials. Scope: Current manual host floor plus versioned application/component planning; not a throughput guarantee. Source: https://docs.camunda.io/docs/self-managed/reference-architecture/manual/ (reviewed 2026-11-20). Supporting source: Self-Managed resource planning and component baselines — https://docs.camunda.io/docs/components/best-practices/architecture/sizing-self-managed/.

- License pricing: Documented. Camunda 8.6+ compiled platform components use proprietary Self-Managed Non-Production or Enterprise terms; production requires the Enterprise licence. Some SDKs/connectors and Desktop Modeler have different source licences. The free development option is not a production grant; obtain the component-specific self-managed quote and support terms separately from Cloud and infrastructure. Scope: Current Camunda 8 component licensing and self-managed production boundary. Source: https://docs.camunda.io/docs/reference/licenses/ (reviewed 2026-11-20). Supporting source: Self-Managed development versus licensed production pricing — https://camunda.com/pricing/.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.




### Security and lifecycle reviews

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

- Camunda November 2026 component security notices (security-advisory): Camunda Notices 80–82 cover critical eMudhra trust-store exposure plus Web Modeler HTTP parser and custom HTTP/2 denial-of-service issues. Scope: Notice 80 affects listed Orchestration Cluster, Connectors, Management Identity, Hub, Web Modeler, Zeebe, Operate, Tasklist, Optimize, Console, and Keycloak builds. Notices 81 and 82 have separate Web Modeler ranges and fixes. Conditions: Component, branch, bundled Java trust store, Keycloak image build date, and HTTP/2 configuration determine applicability. Action: Use the notice's component-specific fixed versions, ensure Keycloak uses a rebuilt image, or remove the named trust roots where Camunda documents that workaround. Apply the Web Modeler fixes separately. Source: https://docs.camunda.io/docs/reference/notices/; reviewed 2026-11-18.

- Camunda Optimize CVE-2026-114938 mitigation (security-advisory): Optimize 8.6.30 and 8.7.32 disable the affected AVX-512 Base64 intrinsic for CVE-2026-114938. Scope: Camunda Optimize 8.6 and 8.7 on affected x86-64 AVX-512 JDKs; other components require separate assessment. Conditions: Camunda states Optimize decodes untrusted Base64 while then-current base and customer JDKs lacked the upstream fix. Action: Apply the branch-specific Optimize release or a fixed JDK, restart affected processes and verify the mitigation. Source: https://github.com/camunda/camunda/releases/tag/8.7.32-optimize; reviewed 2026-11-19. Supporting source: Optimize 8.6.30 — https://github.com/camunda/camunda/releases/tag/8.6.30-optimize. Supporting source: OpenJDK fixed versions — https://openjdk.org/groups/vulnerability/advisories/2026-11-17.




## Dagster OSS

Data orchestration platform for developing, scheduling and observing data-asset workflows.

- Listing: https://launchinyourcloud.com/directory/dagster/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for upstream Dagster; Dagster commercial services are separate.
- Licensing model: open-source
- Installation: Deploy the documented OSS Docker Compose stack with webserver, daemon, code locations and PostgreSQL run storage.
- Architecture: Customer-operated orchestration services, code servers and run storage with configured run-launcher containers
- Operations: Customer manages orchestration services, code images, run storage, execution capacity, access boundaries and upgrades.
- Product website: https://dagster.io/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

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.

Apache License 2.0 for upstream Dagster; Dagster commercial services are separate. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.

Customer-operated orchestration services, code servers and run storage with configured run-launcher containers. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.


### Category fit

- workflow-orchestration: Orchestrates data assets and jobs with schedules, sensors, run tracking and separately configured execution code.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/dagster-io/dagster/blob/master/docs/docs/deployment/oss/deployment-options/docker.md (checked 2026-11-12). 


### Cloud deployment evidence

- Dagster OSS Docker Compose deployment on EC2 (aws): https://github.com/dagster-io/dagster/blob/master/docs/docs/deployment/oss/deployment-options/docker.md
  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.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

The upstream release stream records continuing November 2026 fixes and credits external contributors. Dagster also publishes named organization case studies; those demonstrate ecosystem adoption rather than a specific OSS deployment boundary.

Reviewed 2026-11-10.

- Current maintenance and contributor credits: https://github.com/dagster-io/dagster/releases

- Named organization case studies: https://dagster.io/customers

### Sources

- Official installation and runtime: https://github.com/dagster-io/dagster/blob/master/docs/docs/deployment/oss/deployment-options/docker.md

- Upstream project and capabilities: https://github.com/dagster-io/dagster

- Current upstream license: https://raw.githubusercontent.com/dagster-io/dagster/master/LICENSE

- OSS deployment scope: https://dagster.io/docs/deployment/oss

### Licensing sources

- https://raw.githubusercontent.com/dagster-io/dagster/master/LICENSE

### Infrastructure sources

- https://github.com/dagster-io/dagster/blob/master/docs/docs/deployment/oss/deployment-options/docker.md


### Buyer diligence


Research coverage: 5/12 fields (42%); 3 documented, 2 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: Sources checked — unresolved. The OSS guide establishes a self-hosted webserver/daemon/code-location deployment, while the vendor pricing page describes SSO/SAML in Dagster+ plans. These sources do not establish a shipped external IdP login for the listed OSS distribution. Verify a version-matched ingress/authentication integration and protect its UI/GraphQL access; hybrid worker deployment alone does not self-host the Dagster+ control plane. Scope: Dagster OSS versus commercial hosted control-plane identity; native/configured OSS federation remains unconfirmed. Source: https://docs.dagster.io/deployment/oss/oss-deployment-architecture (reviewed 2026-11-20). Supporting source: Dagster+ plan-specific SSO, separate from OSS — https://dagster.io/pricing.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The OSS guide links a Compose example with webserver, daemon, user-code containers and PostgreSQL run storage. Runs may launch separate containers; capacity and container access need application-specific planning. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://github.com/dagster-io/dagster/blob/master/docs/docs/deployment/oss/deployment-options/docker.md (reviewed 2026-11-14). Deployment artifact: https://github.com/dagster-io/dagster/tree/master/examples/deploy_docker. Artifact reference: master example (moving).

- Minimum footprint / sizing: Sources checked — unresolved. The OSS architecture specifies long-running webserver, daemon and code-location services plus instance storage and run workers, but not a universal numeric CPU/RAM/storage minimum. Code-location, job and executor demand determine capacity. The daemon and code-location replication constraints must be reviewed before treating extra webserver replicas as complete HA. Scope: Current OSS component topology and replication constraints; numeric workload sizing remains unconfirmed. Source: https://docs.dagster.io/deployment/oss/oss-deployment-architecture (reviewed 2026-11-20).

- License pricing: Documented. The reviewed upstream application uses Apache License 2.0. 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: Dagster 1.13.30 OSS core; not a Dagster+ entitlement; software terms only, excluding infrastructure and operations. Source: https://github.com/dagster-io/dagster/blob/1.13.30/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The publisher-designated GitHub release checked was 1.13.30, published 2026-11-12. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package. Scope: dagster-io/dagster core release; integration libraries use a separate version series and provider packages may differ. Source: https://github.com/dagster-io/dagster/releases/tag/1.13.30 (reviewed 2026-11-14).







## HashiCorp Nomad Enterprise

Commercial workload scheduler and orchestrator deployed as a multi-node cluster on customer cloud virtual machines.

- Listing: https://launchinyourcloud.com/directory/hashicorp-nomad-enterprise/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Nomad Enterprise license required for the selected edition; Community Edition uses separate source-available terms.
- Licensing model: commercial-only
- Installation: HashiCorp Validated Design Terraform modules where available or manual package and binary installation
- Architecture: Customer-operated Nomad server quorum and client nodes with persistent state, networking and workload drivers.
- Operations: Customer manages servers and clients, TLS, gossip encryption, ACLs, snapshots, networking, workload drivers, upgrades and availability.
- Product website: https://www.hashicorp.com/en/products/nomad
- Source review: 2026-11-18; cloud review: 2026-11-17; licensing review: 2026-11-17; infrastructure review: 2026-11-17

### Scope and qualifications

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 is proprietary commercial software. Nomad Community Edition is separately distributed under source-available terms and does not grant Enterprise features or support.

Production Nomad uses persistent server nodes for consensus and state plus client nodes that execute workloads on customer virtual machines.


### Category fit

- devops: Schedules and operates application, batch and system workloads across customer infrastructure.

- workflow-orchestration: Coordinates long-running services, batch jobs and parameterized workload execution through declarative job specifications.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment (checked 2026-11-17). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment (checked 2026-11-17). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment (checked 2026-11-17). 


### Cloud deployment evidence

- Nomad Enterprise validated cloud deployment on AWS, Azure and Google Cloud (aws, azure, gcp): https://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment
  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.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- Nomad validated cloud deployment: https://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment

- Nomad pricing and editions: https://www.hashicorp.com/en/products/nomad/pricing

- HCSEC-2026-51: https://discuss.hashicorp.com/t/hcsec-2026-51-nomad-vulnerable-to-cross-namespace-information-disclosure-in-multiple-endpoints/77929

- HCSEC-2026-52: https://discuss.hashicorp.com/t/hcsec-2026-52-nomad-dispatch-payload-writes-can-escape-the-allocation-directory-through-symlinks/77930

- HCSEC-2026-53: https://discuss.hashicorp.com/t/hcsec-2026-53-nomad-allocation-data-migration-may-allow-host-directory-permission-modification-via-symlink-following/77931

### Licensing sources

- https://www.hashicorp.com/en/products/nomad/pricing

### Infrastructure sources

- https://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment


### Buyer diligence


Research coverage: 12/12 fields (100%); 6 documented, 6 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: Sources checked — unresolved. The Enterprise pricing and deployment material establishes licensed self-management, but not a current Nomad Enterprise-specific Marketplace offer. HCP/Vault offers were excluded. Scope: Reviewed public evidence for HashiCorp Nomad Enterprise; unresolved within this edition/deployment. Source: https://www.hashicorp.com/en/products/nomad/pricing (reviewed 2026-11-17).

- Cloud commitment eligibility: Sources checked — unresolved. Nomad Enterprise pricing did not establish offer-specific eligible charges against the buyer cloud agreement; infrastructure discounts are separate. Scope: Reviewed public evidence for HashiCorp Nomad Enterprise; unresolved within this edition/deployment. Source: https://www.hashicorp.com/en/products/nomad/pricing (reviewed 2026-11-17).

- Single sign-on: Documented. Nomad documents OIDC SSO through external IdPs with ACL policies, roles and binding rules. Human and machine authentication are different flows; short-lived ACL tokens replace distributing static tokens. Scope: Self-managed Nomad Enterprise identity design. Source: https://developer.hashicorp.com/validated-designs/nomad/administration-guide/identity-access-management (reviewed 2026-11-17).

- SCIM provisioning: Sources checked — unresolved. Nomad OIDC maps identity claims to short-lived ACL tokens. A Nomad Enterprise SCIM lifecycle service was not established; HCP Terraform SCIM is a different product. Scope: Reviewed public evidence for HashiCorp Nomad Enterprise; unresolved within this edition/deployment. Source: https://developer.hashicorp.com/validated-designs/nomad/administration-guide/identity-access-management (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. The reviewed HashiCorp Nomad Enterprise material establishes configuration/operating controls, but not an independent current attestation covering this edition and customer deployment. Obtain the actual report/certificate, audit period and scope before claiming coverage. Scope: Customer deployment attestation; vendor SaaS, cloud-provider and component certifications are not automatically inherited. Source: https://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment (reviewed 2026-11-17).

- Security controls: Documented. The validated identity design requires appropriate ACL policies and mapped roles. Protect management tokens, configure TLS/gossip and snapshot recovery, and isolate workload client permissions from server administration. Current advisory review: HCSEC-2026-51 through 53 cover cross-namespace information disclosure and two symlink-based host or allocation escalation paths. Upgrade the installed maintained Enterprise branch to the listed fixed or later build. Scope: Nomad customer-managed cluster controls Fixed in Nomad Enterprise 2.1.0, 1.11.12, and 1.10.18.. Source: https://discuss.hashicorp.com/t/hcsec-2026-51-nomad-vulnerable-to-cross-namespace-information-disclosure-in-multiple-endpoints/77929 (reviewed 2026-11-18). Supporting source: Identity and access management — https://developer.hashicorp.com/validated-designs/nomad/administration-guide/identity-access-management. Supporting source: Prior security-controls source — https://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment. Supporting source: HCSEC-2026-52 — https://discuss.hashicorp.com/t/hcsec-2026-52-nomad-dispatch-payload-writes-can-escape-the-allocation-directory-through-symlinks/77930. Supporting source: HCSEC-2026-53 — https://discuss.hashicorp.com/t/hcsec-2026-53-nomad-allocation-data-migration-may-allow-host-directory-permission-modification-via-symlink-following/77931.

- Air-gapped operation: Sources checked — unresolved. The Enterprise licence-reporting guide explicitly allows manual utilization reporting for isolated installations. This resolves the reporting dependency, but the complete offline licence-renewal, identity, package and upgrade procedure for the selected deployment still needs confirmation. Scope: Self-managed Nomad Enterprise reporting; not blanket isolation of integrations. Source: https://developer.hashicorp.com/nomad/docs/enterprise/license/utilization-reporting (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. The validated design documents customer-cloud Nomad installation on AWS, Azure and Google Cloud with servers, clients, networking and enterprise licensing. Review the design and pin the chosen deployment tooling before applying it. Scope: Self-managed Enterprise validated cloud design. Source: https://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment (reviewed 2026-11-17).

- Minimum footprint / sizing: Documented. The cloud design separates voting/non-voting servers from workload clients across availability zones. Server count alone does not size user jobs, 1 TB application data, storage plugins or client failover capacity. Scope: Nomad cluster topology versus workload capacity. Source: https://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment (reviewed 2026-11-17).

- License pricing: Documented. Nomad Enterprise is proprietary commercial software. Nomad Community Edition is separately distributed under source-available terms and does not grant Enterprise features or support. Scope: HashiCorp Nomad Enterprise: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://www.hashicorp.com/en/products/nomad/pricing (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. Illustrative priced infrastructure subtotal: USD 864.96/month. Six 4-vCPU/16-GiB server VMs follow the validated three-voting/three-non-voting design, with 50 GB gp3 each. This prices the control plane only; workload clients and their 1 TB data are unpriced. This is not a complete operating-cost estimate or a validated capacity/SLA claim. Scope: Nomad Enterprise server control-plane subtotal; 100 identities do not size jobs, task concurrency or workload clients. Price applications and replicated workload storage separately.. Source: https://b0.p.awsstatic.com/pricing/2.0/meteredUnitMaps/ec2/USD/current/ec2-ondemand-without-sec-sel/US%20East%20%28N.%20Virginia%29/Linux/index.json (reviewed 2026-11-17). Supporting source: Product topology/sizing basis — https://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment. Supporting source: Current AWS documentation: us-east-1 gp3 capacity example — https://docs.aws.amazon.com/solutions/latest/cloud-migration-factory-on-aws/cost.html. Supporting source: EBS performance and charging qualifications — https://aws.amazon.com/ebs/pricing/.

- Release snapshot / cadence: Documented. The vendor release API identifies 2.1.1+ent as a supported, non-prerelease Enterprise build. Its record was created 2026-10-29. This is the API record-creation date, not a separately established publication date; verify the licensed release/support path before upgrading. Scope: Enterprise-filtered release API snapshot; community and HCP releases excluded. Source: https://api.releases.hashicorp.com/v1/releases/nomad/latest?license_class=enterprise (reviewed 2026-11-17). Supporting source: Versioned Enterprise binaries and checksums — https://releases.hashicorp.com/nomad/2.1.1+ent/.




### Security and lifecycle reviews

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

- HashiCorp Nomad Enterprise October 2026 security updates (security-advisory): HCSEC-2026-51 through 53 cover cross-namespace information disclosure and two symlink-based host or allocation escalation paths. Scope: Fixed in Nomad Enterprise 2.1.0, 1.11.12, and 1.10.18. Conditions: Namespace permissions, dispatch payload writes, allocation migration, and symlink handling determine exposure. Action: Upgrade the installed maintained Enterprise branch to the listed fixed or later build. Source: https://discuss.hashicorp.com/t/hcsec-2026-51-nomad-vulnerable-to-cross-namespace-information-disclosure-in-multiple-endpoints/77929; reviewed 2026-11-18. Supporting source: HCSEC-2026-52 — https://discuss.hashicorp.com/t/hcsec-2026-52-nomad-dispatch-payload-writes-can-escape-the-allocation-directory-through-symlinks/77930. Supporting source: HCSEC-2026-53 — https://discuss.hashicorp.com/t/hcsec-2026-53-nomad-allocation-data-migration-may-allow-host-directory-permission-modification-via-symlink-following/77931.




## 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.




## Prefect Server

Self-hosted workflow server and Python framework for resilient task and data pipelines.

- Listing: https://launchinyourcloud.com/directory/prefect/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: northflank, aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for upstream Prefect. Prefect Cloud is a separate managed offering.
- Licensing model: open-source
- Installation: Install Prefect and start its server; use the documented PostgreSQL/Redis architecture when scaling multiple API and background-service instances.
- Architecture: Customer-operated API/UI, background services, database and execution workers
- Operations: Customer manages server services, database, queue/cache, worker pools, secrets, access controls and upgrades.
- Product website: https://www.prefect.io/
- Source review: 2026-11-19; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

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.

Apache License 2.0 for upstream Prefect. Prefect Cloud is a separate managed offering. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.

Customer-operated API/UI, background services, database and execution workers. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.


### Category fit

- workflow-orchestration: Python flow/task orchestration with retries, scheduling, state tracking and workers that execute deployments on configured infrastructure.

### Deployment boundaries


- northflank: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://northflank.com/guides/how-to-deploy-prefect (checked 2026-11-12). 

- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://northflank.com/guides/how-to-deploy-prefect (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://northflank.com/guides/how-to-deploy-prefect (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://northflank.com/guides/how-to-deploy-prefect (checked 2026-11-12). 


### Cloud deployment evidence

- Self-hosted Prefect server and worker on Northflank (northflank): https://northflank.com/guides/how-to-deploy-prefect
  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.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed.

- Prefect deployment through Northflank BYOC (aws, azure, gcp): https://northflank.com/guides/how-to-deploy-prefect
  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.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

The official release history records November 2026 maintenance, multiple named contributors and first-time contributions across successive releases.

Reviewed 2026-11-10.

- Release history and named contributor participation: https://github.com/PrefectHQ/prefect/releases

- Public project and self-hosted server usage: https://github.com/PrefectHQ/prefect

### Sources

- Official installation and runtime: https://raw.githubusercontent.com/PrefectHQ/prefect/main/docs/v3/advanced/self-hosted.mdx

- Upstream project and capabilities: https://github.com/PrefectHQ/prefect

- Current upstream license: https://raw.githubusercontent.com/PrefectHQ/prefect/main/LICENSE

- Self-hosted startup and workflow functionality: https://raw.githubusercontent.com/PrefectHQ/prefect/main/README.md

- Prefect deployment through Northflank BYOC: https://northflank.com/guides/how-to-deploy-prefect

- Prefect 3.9.4.dev6 prerelease: https://github.com/PrefectHQ/prefect/releases/tag/3.9.4.dev6

- GitRepository credential-log fix: https://github.com/PrefectHQ/prefect/pull/23969

- UI v2 redirect hardening: https://github.com/PrefectHQ/prefect/pull/23980

### Licensing sources

- https://raw.githubusercontent.com/PrefectHQ/prefect/main/LICENSE

### Infrastructure sources

- https://raw.githubusercontent.com/PrefectHQ/prefect/main/docs/v3/advanced/self-hosted.mdx


### Buyer diligence


Research coverage: 6/12 fields (50%); 4 documented, 2 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: Sources checked — unresolved. The self-hosted security guide documents shared Basic authentication, proxy configuration and client headers, not a specific SAML/OIDC user federation integration. Prefect Cloud API keys and Cloud SSO are separate. An identity-aware proxy design would need verified UI/API coverage, individual account mapping and client/worker authorization. Scope: Prefect Server security settings; external user federation remains unconfirmed. Source: https://docs.prefect.io/v3/advanced/security-settings (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. Prefect 3.9.4.dev6 prevents GitRepository credentials embedded in URLs from appearing in DEBUG logs or repr output and validates same-origin UI v2 post-login redirects. No stable fixed release was available at review time; avoid credential-bearing URLs, protect logs and rotate exposed tokens. Scope: Prefect GitRepository logging and UI v2 redirect behavior; remediation was prerelease-only when reviewed. Source: https://github.com/PrefectHQ/prefect/pull/23969 (reviewed 2026-11-19). Supporting source: 3.9.4.dev6 prerelease — https://github.com/PrefectHQ/prefect/releases/tag/3.9.4.dev6. Supporting source: Same-origin redirect hardening — https://github.com/PrefectHQ/prefect/pull/23980.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The self-hosted scaling guide supplies Compose with multiple API/background services, PostgreSQL, Redis and migrations. This scaled architecture is distinct from a single local SQLite instance and requires coordinated versions and persistence. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://raw.githubusercontent.com/PrefectHQ/prefect/main/docs/v3/advanced/self-hosted.mdx (reviewed 2026-11-14).

- Minimum footprint / sizing: Sources checked — unresolved. The scaling guide specifies multiple API/background-service instances, PostgreSQL and persistent Redis coordination, but no numeric whole-stack CPU/RAM/storage minimum. Workflow workers and execution infrastructure are separate. Size run/event rate, queues, database history/retention and failover before estimating the requested HA workload. Scope: Current multi-server topology; numeric production/worker sizing remains unconfirmed. Source: https://docs.prefect.io/v3/advanced/self-hosted (reviewed 2026-11-20).

- License pricing: Documented. The reviewed upstream application uses Apache License 2.0. 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: Prefect 3.9.3 upstream Server; not a Prefect Cloud subscription; software terms only, excluding infrastructure and operations. Source: https://github.com/PrefectHQ/prefect/blob/3.9.3/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The publisher-designated GitHub release checked was 3.9.3, published 2026-11-13. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package. The prerelease 3.9.4.dev6 contains credential-log and same-origin redirect hardening; it is not a stable upgrade target. Scope: Upstream PrefectHQ/prefect release record; commercial editions and deployment packages may differ. Source: https://github.com/PrefectHQ/prefect/releases/tag/3.9.3 (reviewed 2026-11-19). Supporting source: Prerelease-only security fixes — https://github.com/PrefectHQ/prefect/releases/tag/3.9.4.dev6.




### Security and lifecycle reviews

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

- Prefect GitRepository credential-log fix is prerelease-only (security-advisory): Prefect 3.9.4.dev6 stops GitRepository URL credentials from appearing in DEBUG logs and repr output and adds same-origin UI redirect validation. Scope: Prefect GitRepository logging and UI v2 redirects; no stable remediated release was available when reviewed. Conditions: Credential-bearing repository URLs, DEBUG logging and the UI v2 login redirect path determine exposure. Action: Avoid credentials in repository URLs, restrict logs, rotate exposed tokens and validate the eventual stable fixed release before production use. Source: https://github.com/PrefectHQ/prefect/releases/tag/3.9.4.dev6; reviewed 2026-11-19. Supporting source: Credential-log fix — https://github.com/PrefectHQ/prefect/pull/23969. Supporting source: Same-origin redirect validation — https://github.com/PrefectHQ/prefect/pull/23980.




## Temporal Self-Hosted

Orchestrate durable application workflows with a customer-operated Temporal Service.

- Listing: https://launchinyourcloud.com/directory/temporal/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT-licensed Temporal Server; managed Cloud offering is separate
- Licensing model: open-source
- Installation: Production Docker/Kubernetes or manual server deployment with persistence and application workers
- Architecture: Customer-operated Temporal Service, persistence/visibility stores and worker services
- Operations: Customer configures service security, persistence, worker capacity, monitoring, upgrades and disaster recovery.
- Product website: https://temporal.io/
- Source review: 2026-11-17; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

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.

This listing covers the MIT-licensed self-hosted Temporal Server. The separately hosted Temporal Cloud service does not turn the listed open-source server into open-core.

Reviewed self-hosted Temporal Service requires long-lived services and persistence. Application workers are separate customer workloads; their possible hosting models do not change this service classification.


### Category fit

- workflow-orchestration: Developer-oriented durable workflow execution and retry/state orchestration; application workers and code must be supplied.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/temporalio/helm-charts (checked 2026-11-12). 


### Cloud deployment evidence

- Temporal server Helm chart on Amazon EKS (aws): https://github.com/temporalio/helm-charts
  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.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Production self-hosted service guide: https://docs.temporal.io/self-hosted-guide

- Production responsibilities and limitations: https://docs.temporal.io/self-hosted-guide/production-checklist

- Official server license: https://github.com/temporalio/temporal/blob/main/LICENSE

- Durable workflow platform: https://docs.temporal.io/

- Temporal v1.32.2 security and permission changes: https://github.com/temporalio/temporal/releases/tag/v1.32.2

### Licensing sources

- https://github.com/temporalio/temporal/blob/main/LICENSE

- https://docs.temporal.io/self-hosted-guide

### Infrastructure sources

- https://docs.temporal.io/self-hosted-guide


### Buyer diligence


Research coverage: 5/12 fields (42%); 4 documented, 1 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: Documented. The self-hosted Web UI supports OIDC login when authentication is enabled. UI login does not by itself secure every Temporal service/API; configure service authentication and authorization separately. Scope: Temporal Web UI only; not automatic service/worker access control. Source: https://docs.temporal.io/references/web-ui-configuration (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official deployment guide links samples-server Compose configurations with persistence and visibility services. Use the server image and explicitly manage schema upgrades; auto-setup/evaluation workflows are separate. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://docs.temporal.io/self-hosted-guide/deployment (reviewed 2026-11-14). Deployment artifact: https://github.com/temporalio/samples-server. Artifact reference: repository default branch (moving; select matching application release).

- Minimum footprint / sizing: Sources checked — unresolved. The self-hosted checklist requires workload testing and explicit persistence, visibility, service-role and shard planning rather than a universal CPU/RAM/storage minimum. Application workers execute separately from the Temporal service. Size workflow/history growth, task/activity rate, retention, database I/O and redundancy; 100 users and 1 TB alone do not specify capacity. Scope: Official production planning requirements; numeric whole-stack and worker sizing remains unconfirmed. Source: https://docs.temporal.io/self-hosted-guide/production-checklist (reviewed 2026-11-20).

- License pricing: Documented. The reviewed upstream application uses MIT licence. 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: Temporal v1.32.2 server; SDKs, UI and provider packages have their own distributions; software terms only, excluding infrastructure and operations. Source: https://github.com/temporalio/temporal/blob/v1.32.2/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

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




### Security and lifecycle reviews

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

- Temporal security patches and namespace permissions (security-advisory): The patch includes security fixes and requires namespace Write access for ValidateWorkerDeploymentVersionComputeConfig. Scope: Temporal 1.32.2; corresponding security patches are available on the 1.31 and 1.30 lines as 1.31.5 and 1.30.9. Conditions: The permission change affects callers of that API. The release notes do not establish a shared affected range for every security fix. Action: Patch the deployed supported line and review namespace authorizations before upgrading. Source: https://github.com/temporalio/temporal/releases/tag/v1.32.2; reviewed 2026-11-17. Supporting source: Temporal 1.31 security patch — https://github.com/temporalio/temporal/releases/tag/v1.31.5. Supporting source: Temporal 1.30 security patch — https://github.com/temporalio/temporal/releases/tag/v1.30.9.



