{"catalog":"https://launchinyourcloud.com/api/v1/catalog.json","catalogRevision":"170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde","category":{"description":"Durable execution and orchestration for application workflows.","id":"workflow-orchestration","name":"Workflow orchestration"},"kind":"category","listings":[{"architecture":"Scheduler, Dag processor, API server and metadata database, with executor-dependent workers and optional triggerers","categories":["workflow-orchestration"],"category":"Workflow orchestration","categoryFit":{"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."},"cloudEvidence":[{"clouds":["aws"],"notes":"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.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Airflow Helm deployment on EKS with IAM roles","url":"https://airflow.apache.org/docs/apache-airflow-providers-amazon/stable/logging/s3-task-handler.html","vendorSupport":"not-assessed"},{"clouds":["digitalocean"],"notes":"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.","reviewed":"2026-11-12","sourceType":"provider-guide","title":"Apache Airflow full application on DigitalOcean","url":"https://docs.digitalocean.com/products/marketplace/catalog/airflow/","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-12","clouds":["aws","digitalocean"],"communityAcceptance":{"reviewed":"2026-11-14","sources":[{"title":"Current release announcements","url":"https://airflow.apache.org/announcements/"},{"title":"Adyen production case study","url":"https://airflow.apache.org/use-cases/adyen/"},{"title":"Project-maintained organization list","url":"https://github.com/apache/airflow/blob/main/INTHEWILD.md"},{"title":"Airflow 3.4 whole-Dag authoring beyond Python","url":"https://airflow.apache.org/blog/airflow-3.4.0/"},{"title":"Stable TypeScript SDK 1.0.0","url":"https://github.com/apache/airflow/releases/tag/ts-sdk/1.0.0"},{"title":"Stable Java SDK 1.0.0","url":"https://github.com/apache/airflow/releases/tag/java-sdk/1.0.0"},{"title":"Stable Go SDK 1.0.0","url":"https://github.com/apache/airflow/releases/tag/go-sdk/v1.0.0"}],"summary":"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."},"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"digitalocean","controlPlane":"not-assessed","evidence":[1],"operator":"customer"}],"description":"Workflow orchestration platform for scheduling and monitoring data pipelines and other task workflows authored in Python or supported non-Python formats.","diligence":{"footprint":{"reviewed":"2026-11-20","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","status":"documented","summary":"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."},"iac":{"reviewed":"2026-11-14","scope":"Upstream self-hosted deployment; not a provider support or production-readiness certification","source":"https://airflow.apache.org/docs/helm-chart/stable/index.html","status":"documented","summary":"Apache publishes an Airflow Helm chart with configurable executors and supporting services. Database migrations, chart/application compatibility, secrets and persistent logs require explicit planning."},"licensePricing":{"reviewed":"2026-11-20","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","status":"documented","summary":"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."},"marketplace":{"availability":"available","offers":[{"cloud":"digitalocean","delivery":"Droplet 1-Click","id":"airflow","publisher":"Not identified on the reviewed marketplace page","url":"https://marketplace.digitalocean.com/apps/airflow","version":"3.3.2"}],"reviewed":"2026-11-14","scope":"DigitalOcean-listed package; Apache commercial support is not established","source":"https://docs.digitalocean.com/products/marketplace/catalog/airflow/","status":"documented","summary":"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."},"release":{"releasePublishedAt":"2026-11-06T13:08:22Z","releaseTag":"3.4.0","reviewed":"2026-11-14","scope":"Upstream apache/airflow release record; commercial editions and deployment packages may differ","source":"https://github.com/apache/airflow/releases/tag/3.4.0","status":"documented","summary":"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."},"sso":{"availability":"available","reviewed":"2026-11-20","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","status":"documented","summary":"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."}},"id":"apache-airflow","infrastructure":["servers"],"infrastructureNotes":"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.","infrastructureReviewed":"2026-11-10","infrastructureSources":["https://airflow.apache.org/docs/apache-airflow/stable/core-concepts/overview.html","https://airflow.apache.org/docs/helm-chart/stable/index.html"],"install":"Install the Python distribution or official container images; the Apache Airflow Helm chart deploys the platform to a customer-operated Kubernetes cluster.","installMethods":["helm","docker","source"],"kind":"product","license":"Apache License 2.0 for upstream Airflow; dependencies, provider integrations and external services have their own terms.","licenseModel":"open-source","licenseModelNotes":"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.","licenseModelSources":["https://github.com/apache/airflow/blob/main/LICENSE"],"licenseReviewed":"2026-11-10","model":"Fully in your account","modelLabel":"Customer-operated","name":"Apache Airflow","notes":"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.","operations":"Customer operates Airflow services, database, worker capacity, Dag code, credentials, authorization, logs, backups and version upgrades.","publisher":false,"reviewed":"2026-11-14","sources":[{"title":"What Apache Airflow does","url":"https://airflow.apache.org/docs/apache-airflow/stable/"},{"title":"Component architecture and deployment","url":"https://airflow.apache.org/docs/apache-airflow/stable/core-concepts/overview.html"},{"title":"Official Apache Airflow Helm chart","url":"https://airflow.apache.org/docs/helm-chart/stable/index.html"},{"title":"Upstream Apache-2.0 and subcomponent licenses","url":"https://github.com/apache/airflow/blob/main/LICENSE"},{"title":"DigitalOcean Airflow application deployment","url":"https://docs.digitalocean.com/products/marketplace/catalog/airflow/"},{"title":"Airflow 3.4 whole-Dag authoring beyond Python","url":"https://airflow.apache.org/blog/airflow-3.4.0/"},{"title":"Airflow TypeScript SDK 1.0.0","url":"https://github.com/apache/airflow/releases/tag/ts-sdk/1.0.0"},{"title":"Airflow Java SDK 1.0.0","url":"https://github.com/apache/airflow/releases/tag/java-sdk/1.0.0"},{"title":"Airflow Go SDK 1.0.0","url":"https://github.com/apache/airflow/releases/tag/go-sdk/v1.0.0"}],"url":"https://launchinyourcloud.com/directory/apache-airflow/","website":"https://airflow.apache.org/"},{"advisories":[{"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.","conditions":"Component, branch, bundled Java trust store, Keycloak image build date, and HTTP/2 configuration determine applicability.","disclosedOn":"2026-11-04","id":"camunda-november-2026-security-notices","listingIds":["camunda-self-managed"],"reviewed":"2026-11-18","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.","source":"https://docs.camunda.io/docs/reference/notices/","summary":"Camunda Notices 80–82 cover critical eMudhra trust-store exposure plus Web Modeler HTTP parser and custom HTTP/2 denial-of-service issues.","title":"Camunda November 2026 component security notices","type":"security-advisory"},{"action":"Apply the branch-specific Optimize release or a fixed JDK, restart affected processes and verify the mitigation.","conditions":"Camunda states Optimize decodes untrusted Base64 while then-current base and customer JDKs lacked the upstream fix.","disclosedOn":"2026-11-19","id":"camunda-optimize-cve-2026-114938","listingIds":["camunda-self-managed"],"reviewed":"2026-11-19","scope":"Camunda Optimize 8.6 and 8.7 on affected x86-64 AVX-512 JDKs; other components require separate assessment.","source":"https://github.com/camunda/camunda/releases/tag/8.7.32-optimize","summary":"Optimize 8.6.30 and 8.7.32 disable the affected AVX-512 Base64 intrinsic for CVE-2026-114938.","supportingSources":[{"title":"Optimize 8.6.30","url":"https://github.com/camunda/camunda/releases/tag/8.6.30-optimize"},{"title":"OpenJDK fixed versions","url":"https://openjdk.org/groups/vulnerability/advisories/2026-11-17"}],"title":"Camunda Optimize CVE-2026-114938 mitigation","type":"security-advisory"}],"architecture":"Customer-operated orchestration cluster, connectors, identity services and persistent secondary storage","categories":["workflow-automation","workflow-orchestration"],"category":"Workflow orchestration","categoryFit":{"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."},"cloudEvidence":[{"clouds":["aws"],"notes":"Camunda provides current EKS infrastructure and Helm installation guidance for a customer AWS account, including managed persistence dependencies.","reviewed":"2026-11-14","sourceType":"vendor-documentation","title":"Camunda 8 Self-Managed on Amazon EKS","url":"https://docs.camunda.io/docs/self-managed/deployment/helm/cloud-providers/amazon/amazon-eks/","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"Camunda provides current AKS and Helm guidance for a customer Azure subscription, with provider-specific reference infrastructure.","reviewed":"2026-11-14","sourceType":"vendor-documentation","title":"Camunda 8 Self-Managed on Microsoft AKS","url":"https://docs.camunda.io/docs/self-managed/deployment/helm/cloud-providers/azure/microsoft-aks/","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"Camunda documents its Self-Managed Helm deployment and Google Cloud-specific GKE configuration.","reviewed":"2026-11-14","sourceType":"vendor-documentation","title":"Camunda 8 Self-Managed on Google GKE","url":"https://docs.camunda.io/docs/self-managed/deployment/helm/cloud-providers/gcp/google-gke/","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-14","clouds":["aws","azure","gcp"],"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"azure","controlPlane":"not-assessed","evidence":[1],"operator":"customer"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"not-assessed","evidence":[2],"operator":"customer"}],"description":"Commercial self-managed process orchestration and workflow automation platform.","diligence":{"footprint":{"reviewed":"2026-11-20","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/","status":"documented","summary":"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.","supportingSources":[{"title":"Self-Managed resource planning and component baselines","url":"https://docs.camunda.io/docs/components/best-practices/architecture/sizing-self-managed/"}]},"iac":{"artifactRef":"repository default branch (moving; select a supported chart release)","artifactUrl":"https://github.com/camunda/camunda-platform-helm","reviewed":"2026-11-14","scope":"Camunda 8 Self-Managed chart family; not a SaaS subscription","source":"https://github.com/camunda/camunda-platform-helm","status":"documented","summary":"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."},"licensePricing":{"reviewed":"2026-11-20","scope":"Current Camunda 8 component licensing and self-managed production boundary","source":"https://docs.camunda.io/docs/reference/licenses/","status":"documented","summary":"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.","supportingSources":[{"title":"Self-Managed development versus licensed production pricing","url":"https://camunda.com/pricing/"}]},"securityControls":{"reviewed":"2026-11-19","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","status":"documented","summary":"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.","supportingSources":[{"title":"Prior security-controls source","url":"https://docs.camunda.io/docs/reference/notices/"},{"title":"Optimize 8.6.30 mitigation","url":"https://github.com/camunda/camunda/releases/tag/8.6.30-optimize"},{"title":"OpenJDK fixed versions","url":"https://openjdk.org/groups/vulnerability/advisories/2026-11-17"}]},"sso":{"availability":"available","reviewed":"2026-11-20","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/","status":"documented","summary":"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."}},"id":"camunda-self-managed","infrastructure":["servers"],"infrastructureNotes":"The documented production topology uses persistent Kubernetes workloads plus databases or search services. Managed provider dependencies do not make the Camunda runtime serverless.","infrastructureReviewed":"2026-11-14","infrastructureSources":["https://docs.camunda.io/docs/self-managed/reference-architecture/kubernetes/","https://docs.camunda.io/docs/reference/supported-environments/"],"install":"Official Helm charts on EKS, AKS or GKE","installMethods":["helm"],"kind":"product","license":"Commercial Enterprise license required for production; unlicensed use is limited to non-production conditions.","licenseModel":"commercial-only","licenseModelNotes":"Camunda documents unlicensed Self-Managed components as non-production and requires a Camunda Self-Managed Enterprise Edition license for production use.","licenseModelSources":["https://docs.camunda.io/docs/self-managed/components/orchestration-cluster/core-settings/configuration/licensing/"],"licenseReviewed":"2026-11-14","model":"Fully in your account","modelLabel":"Customer-operated","name":"Camunda 8 Self-Managed","notes":"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.","operations":"Customer manages Kubernetes, supported databases or search services, storage, ingress, identity, backups, scaling and upgrades.","publisher":false,"reviewed":"2026-11-19","sources":[{"title":"Supported self-managed environments","url":"https://docs.camunda.io/docs/reference/supported-environments/"},{"title":"Amazon EKS deployment","url":"https://docs.camunda.io/docs/self-managed/deployment/helm/cloud-providers/amazon/amazon-eks/"},{"title":"Microsoft AKS deployment","url":"https://docs.camunda.io/docs/self-managed/deployment/helm/cloud-providers/azure/microsoft-aks/"},{"title":"Google GKE deployment","url":"https://docs.camunda.io/docs/self-managed/deployment/helm/cloud-providers/gcp/google-gke/"},{"title":"Self-managed licensing","url":"https://docs.camunda.io/docs/self-managed/components/orchestration-cluster/core-settings/configuration/licensing/"},{"title":"Camunda security notices","url":"https://docs.camunda.io/docs/reference/notices/"},{"title":"Camunda Optimize 8.6.30","url":"https://github.com/camunda/camunda/releases/tag/8.6.30-optimize"},{"title":"Camunda Optimize 8.7.32","url":"https://github.com/camunda/camunda/releases/tag/8.7.32-optimize"},{"title":"OpenJDK November 2026 advisory","url":"https://openjdk.org/groups/vulnerability/advisories/2026-11-17"}],"url":"https://launchinyourcloud.com/directory/camunda-self-managed/","website":"https://camunda.com/platform/"},{"architecture":"Customer-operated orchestration services, code servers and run storage with configured run-launcher containers","categories":["workflow-orchestration"],"category":"Workflow orchestration","categoryFit":{"workflow-orchestration":"Orchestrates data assets and jobs with schedules, sensors, run tracking and separately configured execution code."},"cloudEvidence":[{"clouds":["aws"],"notes":"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.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Dagster OSS Docker Compose deployment on EC2","url":"https://github.com/dagster-io/dagster/blob/master/docs/docs/deployment/oss/deployment-options/docker.md","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-12","clouds":["aws"],"communityAcceptance":{"reviewed":"2026-11-10","sources":[{"title":"Current maintenance and contributor credits","url":"https://github.com/dagster-io/dagster/releases"},{"title":"Named organization case studies","url":"https://dagster.io/customers"}],"summary":"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."},"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"not-assessed","evidence":[0],"operator":"customer"}],"description":"Data orchestration platform for developing, scheduling and observing data-asset workflows.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Current OSS component topology and replication constraints; numeric workload sizing remains unconfirmed","source":"https://docs.dagster.io/deployment/oss/oss-deployment-architecture","status":"inconclusive","summary":"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."},"iac":{"artifactRef":"master example (moving)","artifactUrl":"https://github.com/dagster-io/dagster/tree/master/examples/deploy_docker","reviewed":"2026-11-14","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","status":"documented","summary":"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."},"licensePricing":{"reviewed":"2026-11-20","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","status":"documented","summary":"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."},"release":{"releasePublishedAt":"2026-11-12T21:04:51Z","releaseTag":"1.13.30","reviewed":"2026-11-14","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","status":"documented","summary":"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."},"sso":{"reviewed":"2026-11-20","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","status":"inconclusive","summary":"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.","supportingSources":[{"title":"Dagster+ plan-specific SSO, separate from OSS","url":"https://dagster.io/pricing"}]}},"id":"dagster","infrastructure":["servers"],"infrastructureNotes":"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.","infrastructureReviewed":"2026-11-10","infrastructureSources":["https://github.com/dagster-io/dagster/blob/master/docs/docs/deployment/oss/deployment-options/docker.md"],"install":"Deploy the documented OSS Docker Compose stack with webserver, daemon, code locations and PostgreSQL run storage.","installMethods":["docker"],"kind":"product","license":"Apache License 2.0 for upstream Dagster; Dagster commercial services are separate.","licenseModel":"open-source","licenseModelNotes":"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.","licenseModelSources":["https://raw.githubusercontent.com/dagster-io/dagster/master/LICENSE"],"licenseReviewed":"2026-11-10","model":"Fully in your account","modelLabel":"Customer-operated","name":"Dagster OSS","notes":"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.","operations":"Customer manages orchestration services, code images, run storage, execution capacity, access boundaries and upgrades.","publisher":false,"reviewed":"2026-11-12","sources":[{"title":"Official installation and runtime","url":"https://github.com/dagster-io/dagster/blob/master/docs/docs/deployment/oss/deployment-options/docker.md"},{"title":"Upstream project and capabilities","url":"https://github.com/dagster-io/dagster"},{"title":"Current upstream license","url":"https://raw.githubusercontent.com/dagster-io/dagster/master/LICENSE"},{"title":"OSS deployment scope","url":"https://dagster.io/docs/deployment/oss"}],"url":"https://launchinyourcloud.com/directory/dagster/","website":"https://dagster.io/"},{"advisories":[{"action":"Upgrade the installed maintained Enterprise branch to the listed fixed or later build.","conditions":"Namespace permissions, dispatch payload writes, allocation migration, and symlink handling determine exposure.","disclosedOn":"2026-10-29","id":"hashicorp-nomad-hcsec-2026-51-53","listingIds":["hashicorp-nomad-enterprise"],"reviewed":"2026-11-18","scope":"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","summary":"HCSEC-2026-51 through 53 cover cross-namespace information disclosure and two symlink-based host or allocation escalation paths.","supportingSources":[{"title":"HCSEC-2026-52","url":"https://discuss.hashicorp.com/t/hcsec-2026-52-nomad-dispatch-payload-writes-can-escape-the-allocation-directory-through-symlinks/77930"},{"title":"HCSEC-2026-53","url":"https://discuss.hashicorp.com/t/hcsec-2026-53-nomad-allocation-data-migration-may-allow-host-directory-permission-modification-via-symlink-following/77931"}],"title":"HashiCorp Nomad Enterprise October 2026 security updates","type":"security-advisory"}],"architecture":"Customer-operated Nomad server quorum and client nodes with persistent state, networking and workload drivers.","categories":["devops","workflow-orchestration"],"category":"DevOps","categoryFit":{"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."},"cloudEvidence":[{"clouds":["aws","azure","gcp"],"notes":"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.","reviewed":"2026-11-17","sourceType":"vendor-documentation","title":"Nomad Enterprise validated cloud deployment on AWS, Azure and Google Cloud","url":"https://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-17","clouds":["aws","azure","gcp"],"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"azure","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"not-assessed","evidence":[0],"operator":"customer"}],"description":"Commercial workload scheduler and orchestrator deployed as a multi-node cluster on customer cloud virtual machines.","diligence":{"airGap":{"reviewed":"2026-11-17","scope":"Self-managed Nomad Enterprise reporting; not blanket isolation of integrations","source":"https://developer.hashicorp.com/nomad/docs/enterprise/license/utilization-reporting","status":"inconclusive","summary":"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."},"commitments":{"reviewed":"2026-11-17","scope":"Reviewed public evidence for HashiCorp Nomad Enterprise; unresolved within this edition/deployment","source":"https://www.hashicorp.com/en/products/nomad/pricing","status":"inconclusive","summary":"Nomad Enterprise pricing did not establish offer-specific eligible charges against the buyer cloud agreement; infrastructure discounts are separate."},"compliance":{"reviewed":"2026-11-17","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","status":"inconclusive","summary":"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."},"cost":{"estimate":{"currency":"USD","exclusions":["Software licence and support","Operating labor","Backups and recovery testing","Load balancing, NAT/endpoints, IPv4 and all data transfer","Monitoring, mail and other services","Taxes and discounts","All workload/client compute and the requested 1 TB workload data","Optional Consul/Vault and storage/network plugins"],"kind":"partial-infrastructure","period":"month","region":"AWS us-east-1","rows":[{"description":"6 Linux m5.xlarge VMs × 730 hours; capacity is an editorial planning choice, not a vendor 100-user benchmark","id":"compute","quantity":4380,"rate":0.192},{"description":"300 GB provisioned gp3 capacity, including stated boot/data allowance; base IOPS/throughput only","id":"storage","quantity":300,"rate":0.08},{"description":"Unpriced; include if required by the selected topology","id":"database","quantity":1,"rate":""},{"description":"Unpriced; see scope/exclusions; do not assume zero","id":"backup","quantity":1,"rate":""},{"description":"Unpriced; see scope/exclusions; do not assume zero","id":"network","quantity":1,"rate":""},{"description":"Unpriced; see scope/exclusions; do not assume zero","id":"license","quantity":1,"rate":""},{"description":"Unpriced; see scope/exclusions; do not assume zero","id":"labor","quantity":1,"rate":""}],"workload":"100 internal users; 1 TB (1,000 GB) logical data; HA target; average usage unmeasured; 730 h/month. Nomad control plane only; workload clients and data unpriced."},"reviewed":"2026-11-17","scenario":{"availability":"HA","dataGB":1000,"hoursPerMonth":730,"provider":"aws","region":"us-east-1","usage":"Average usage; no measured concurrency/throughput supplied","users":100},"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","status":"inconclusive","summary":"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.","supportingSources":[{"title":"Product topology/sizing basis","url":"https://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment"},{"title":"Current AWS documentation: us-east-1 gp3 capacity example","url":"https://docs.aws.amazon.com/solutions/latest/cloud-migration-factory-on-aws/cost.html"},{"title":"EBS performance and charging qualifications","url":"https://aws.amazon.com/ebs/pricing/"}]},"footprint":{"reviewed":"2026-11-17","scope":"Nomad cluster topology versus workload capacity","source":"https://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment","status":"documented","summary":"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."},"iac":{"reviewed":"2026-11-17","scope":"Self-managed Enterprise validated cloud design","source":"https://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment","status":"documented","summary":"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."},"licensePricing":{"reviewed":"2026-11-17","scope":"HashiCorp Nomad Enterprise: software entitlement and edition boundary; infrastructure and operating costs are separate","source":"https://www.hashicorp.com/en/products/nomad/pricing","status":"documented","summary":"Nomad Enterprise is proprietary commercial software. Nomad Community Edition is separately distributed under source-available terms and does not grant Enterprise features or support."},"marketplace":{"reviewed":"2026-11-17","scope":"Reviewed public evidence for HashiCorp Nomad Enterprise; unresolved within this edition/deployment","source":"https://www.hashicorp.com/en/products/nomad/pricing","status":"inconclusive","summary":"The Enterprise pricing and deployment material establishes licensed self-management, but not a current Nomad Enterprise-specific Marketplace offer. HCP/Vault offers were excluded."},"release":{"reviewed":"2026-11-17","scope":"Enterprise-filtered release API snapshot; community and HCP releases excluded","source":"https://api.releases.hashicorp.com/v1/releases/nomad/latest?license_class=enterprise","status":"documented","summary":"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.","supportingSources":[{"title":"Versioned Enterprise binaries and checksums","url":"https://releases.hashicorp.com/nomad/2.1.1+ent/"}]},"scim":{"reviewed":"2026-11-17","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","status":"inconclusive","summary":"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."},"securityControls":{"reviewed":"2026-11-18","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","status":"documented","summary":"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.","supportingSources":[{"title":"Identity and access management","url":"https://developer.hashicorp.com/validated-designs/nomad/administration-guide/identity-access-management"},{"title":"Prior security-controls source","url":"https://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment"},{"title":"HCSEC-2026-52","url":"https://discuss.hashicorp.com/t/hcsec-2026-52-nomad-dispatch-payload-writes-can-escape-the-allocation-directory-through-symlinks/77930"},{"title":"HCSEC-2026-53","url":"https://discuss.hashicorp.com/t/hcsec-2026-53-nomad-allocation-data-migration-may-allow-host-directory-permission-modification-via-symlink-following/77931"}]},"sso":{"availability":"available","reviewed":"2026-11-17","scope":"Self-managed Nomad Enterprise identity design","source":"https://developer.hashicorp.com/validated-designs/nomad/administration-guide/identity-access-management","status":"documented","summary":"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."}},"id":"hashicorp-nomad-enterprise","infrastructure":["servers"],"infrastructureNotes":"Production Nomad uses persistent server nodes for consensus and state plus client nodes that execute workloads on customer virtual machines.","infrastructureReviewed":"2026-11-17","infrastructureSources":["https://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment"],"install":"HashiCorp Validated Design Terraform modules where available or manual package and binary installation","installMethods":["terraform","package"],"kind":"platform","license":"Commercial Nomad Enterprise license required for the selected edition; Community Edition uses separate source-available terms.","licenseModel":"commercial-only","licenseModelNotes":"Nomad Enterprise is proprietary commercial software. Nomad Community Edition is separately distributed under source-available terms and does not grant Enterprise features or support.","licenseModelSources":["https://www.hashicorp.com/en/products/nomad/pricing"],"licenseReviewed":"2026-11-17","model":"Fully in your account","modelLabel":"Customer-operated","name":"HashiCorp Nomad Enterprise","notes":"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.","operations":"Customer manages servers and clients, TLS, gossip encryption, ACLs, snapshots, networking, workload drivers, upgrades and availability.","publisher":false,"reviewed":"2026-11-18","sources":[{"title":"Nomad validated cloud deployment","url":"https://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment"},{"title":"Nomad pricing and editions","url":"https://www.hashicorp.com/en/products/nomad/pricing"},{"title":"HCSEC-2026-51","url":"https://discuss.hashicorp.com/t/hcsec-2026-51-nomad-vulnerable-to-cross-namespace-information-disclosure-in-multiple-endpoints/77929"},{"title":"HCSEC-2026-52","url":"https://discuss.hashicorp.com/t/hcsec-2026-52-nomad-dispatch-payload-writes-can-escape-the-allocation-directory-through-symlinks/77930"},{"title":"HCSEC-2026-53","url":"https://discuss.hashicorp.com/t/hcsec-2026-53-nomad-allocation-data-migration-may-allow-host-directory-permission-modification-via-symlink-following/77931"}],"url":"https://launchinyourcloud.com/directory/hashicorp-nomad-enterprise/","website":"https://www.hashicorp.com/en/products/nomad"},{"advisories":[{"action":"Upgrade to v2.0.11 or later and retest browser and API authentication flows.","conditions":"Browser behavior changes when Basic authentication is used; dependency exposure depends on the deployed components.","id":"kestra-2-0-11-security-update","listingIds":["kestra"],"reviewed":"2026-11-18","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","summary":"Kestra v2.0.11 updates dependencies for CVE-2026-45292 and enforces CSRF tokens for Basic-auth browser requests.","title":"Kestra 2.0.11 dependency and CSRF update","type":"security-advisory"}],"architecture":"Customer-operated Kestra server and workers with PostgreSQL queue/repository state and object storage","categories":["workflow-orchestration"],"category":"Workflow orchestration","categoryFit":{"workflow-orchestration":"Orchestrates scheduled and event-driven data, infrastructure, business and AI workflows with customer-operated execution workers."},"cloudEvidence":[{"clouds":["aws"],"notes":"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.","reviewed":"2026-11-13","sourceType":"vendor-documentation","title":"Kestra on Amazon EC2 with RDS and S3","url":"https://kestra.io/docs/installation/aws-ec2","vendorSupport":"not-assessed"},{"clouds":["aws"],"notes":"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.","reviewed":"2026-11-13","sourceType":"vendor-documentation","title":"Kestra on Amazon EKS with RDS and S3","url":"https://kestra.io/docs/installation/kubernetes-aws-eks","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"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.","reviewed":"2026-11-13","sourceType":"vendor-documentation","title":"Kestra on Google GKE with Cloud SQL and Cloud Storage","url":"https://kestra.io/docs/installation/kubernetes-gcp-gke","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"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.","reviewed":"2026-11-13","sourceType":"vendor-documentation","title":"Kestra on Azure AKS with PostgreSQL and Blob Storage","url":"https://kestra.io/docs/installation/kubernetes-azure-aks","vendorSupport":"not-assessed"},{"clouds":["digitalocean"],"notes":"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.","reviewed":"2026-11-13","sourceType":"vendor-documentation","title":"Kestra on DigitalOcean Droplets with Managed Database and Spaces","url":"https://kestra.io/docs/installation/digitalocean-droplet","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-13","clouds":["aws","azure","gcp","digitalocean"],"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"not-assessed","evidence":[0,1],"operator":"customer"},{"boundary":"cloud-account","cloud":"azure","controlPlane":"not-assessed","evidence":[3],"operator":"customer"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"not-assessed","evidence":[2],"operator":"customer"},{"boundary":"cloud-account","cloud":"digitalocean","controlPlane":"not-assessed","evidence":[4],"operator":"customer"}],"description":"Self-hosted orchestration platform for scheduled and event-driven workflows across data, infrastructure and applications.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Official AWS application starting point with separately configured database and object storage","source":"https://kestra.io/docs/installation/aws-ec2","status":"documented","summary":"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."},"iac":{"artifactRef":"develop (moving branch); development example","artifactUrl":"https://raw.githubusercontent.com/kestra-io/kestra/develop/docker-compose.yml","reviewed":"2026-11-14","scope":"Upstream self-hosted deployment; not a provider support or production-readiness certification","source":"https://kestra.io/docs/installation/docker-compose","status":"documented","summary":"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."},"licensePricing":{"reviewed":"2026-11-20","scope":"Published Kestra OSS core versus self-hosted Enterprise features","source":"https://github.com/kestra-io/kestra/blob/v2.0.11/LICENSE","status":"documented","summary":"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.","supportingSources":[{"title":"Self-managed Enterprise SSO scope","url":"https://kestra.io/docs/enterprise/auth/sso"}]},"release":{"releasePublishedAt":"2026-11-17T14:26:39Z","releaseTag":"v2.0.11","reviewed":"2026-11-18","scope":"Upstream Kestra 2.0 release","source":"https://github.com/kestra-io/kestra/releases/tag/v2.0.11","status":"documented","summary":"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."},"securityControls":{"reviewed":"2026-11-18","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","status":"documented","summary":"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."},"sso":{"availability":"edition-dependent","reviewed":"2026-11-14","scope":"Self-managed Kestra Enterprise","source":"https://kestra.io/docs/enterprise/auth/sso","status":"documented","summary":"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."}},"id":"kestra","infrastructure":["servers"],"infrastructureNotes":"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.","infrastructureReviewed":"2026-11-13","infrastructureSources":["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"],"install":"Docker on AWS EC2 or DigitalOcean Droplets, or Helm on AWS EKS, Google GKE or Azure AKS, with documented database and object storage services.","installMethods":["helm","docker"],"kind":"product","license":"Apache License 2.0 for the open-source Kestra platform; commercial Enterprise features and support are separate.","licenseModel":"open-source","licenseModelNotes":"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.","licenseModelSources":["https://github.com/kestra-io/kestra/blob/develop/LICENSE"],"licenseReviewed":"2026-11-13","model":"Fully in your account","modelLabel":"Customer-operated","name":"Kestra Self-Hosted","notes":"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.","operations":"Customer manages server and worker capacity, PostgreSQL, object storage, plugins, credentials, network access, backups and upgrades.","publisher":false,"reviewed":"2026-11-18","sources":[{"title":"AWS EC2 deployment with RDS and S3","url":"https://kestra.io/docs/installation/aws-ec2"},{"title":"AWS EKS deployment with RDS and S3","url":"https://kestra.io/docs/installation/kubernetes-aws-eks"},{"title":"Apache 2.0 project license","url":"https://github.com/kestra-io/kestra/blob/develop/LICENSE"},{"title":"Kestra on Google GKE with Cloud SQL and Cloud Storage","url":"https://kestra.io/docs/installation/kubernetes-gcp-gke"},{"title":"Kestra on Azure AKS with PostgreSQL and Blob Storage","url":"https://kestra.io/docs/installation/kubernetes-azure-aks"},{"title":"Kestra on DigitalOcean Droplets with Managed Database and Spaces","url":"https://kestra.io/docs/installation/digitalocean-droplet"},{"title":"Kestra v2.0.11 release","url":"https://github.com/kestra-io/kestra/releases/tag/v2.0.11"}],"url":"https://launchinyourcloud.com/directory/kestra/","website":"https://kestra.io/"},{"advisories":[{"action":"Avoid credentials in repository URLs, restrict logs, rotate exposed tokens and validate the eventual stable fixed release before production use.","conditions":"Credential-bearing repository URLs, DEBUG logging and the UI v2 login redirect path determine exposure.","disclosedOn":"2026-11-19","id":"prefect-3-9-4-dev6-credential-log-exposure","listingIds":["prefect"],"reviewed":"2026-11-19","scope":"Prefect GitRepository logging and UI v2 redirects; no stable remediated release was available when reviewed.","source":"https://github.com/PrefectHQ/prefect/releases/tag/3.9.4.dev6","summary":"Prefect 3.9.4.dev6 stops GitRepository URL credentials from appearing in DEBUG logs and repr output and adds same-origin UI redirect validation.","supportingSources":[{"title":"Credential-log fix","url":"https://github.com/PrefectHQ/prefect/pull/23969"},{"title":"Same-origin redirect validation","url":"https://github.com/PrefectHQ/prefect/pull/23980"}],"title":"Prefect GitRepository credential-log fix is prerelease-only","type":"security-advisory"}],"architecture":"Customer-operated API/UI, background services, database and execution workers","categories":["workflow-orchestration"],"category":"Workflow orchestration","categoryFit":{"workflow-orchestration":"Python flow/task orchestration with retries, scheduling, state tracking and workers that execute deployments on configured infrastructure."},"cloudEvidence":[{"clouds":["northflank"],"notes":"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.","reviewed":"2026-11-12","sourceType":"provider-guide","title":"Self-hosted Prefect server and worker on Northflank","url":"https://northflank.com/guides/how-to-deploy-prefect","vendorSupport":"not-assessed"},{"clouds":["aws","azure","gcp"],"notes":"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.","reviewed":"2026-11-12","sourceType":"provider-guide","title":"Prefect deployment through Northflank BYOC","url":"https://northflank.com/guides/how-to-deploy-prefect","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-12","clouds":["northflank","aws","azure","gcp"],"communityAcceptance":{"reviewed":"2026-11-10","sources":[{"title":"Release history and named contributor participation","url":"https://github.com/PrefectHQ/prefect/releases"},{"title":"Public project and self-hosted server usage","url":"https://github.com/PrefectHQ/prefect"}],"summary":"The official release history records November 2026 maintenance, multiple named contributors and first-time contributions across successive releases."},"deploymentPaths":[{"boundary":"platform-workspace","cloud":"northflank","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"aws","controlPlane":"not-assessed","evidence":[1],"operator":"customer"},{"boundary":"cloud-account","cloud":"azure","controlPlane":"not-assessed","evidence":[1],"operator":"customer"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"not-assessed","evidence":[1],"operator":"customer"}],"description":"Self-hosted workflow server and Python framework for resilient task and data pipelines.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Current multi-server topology; numeric production/worker sizing remains unconfirmed","source":"https://docs.prefect.io/v3/advanced/self-hosted","status":"inconclusive","summary":"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."},"iac":{"reviewed":"2026-11-14","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","status":"documented","summary":"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."},"licensePricing":{"reviewed":"2026-11-20","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","status":"documented","summary":"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."},"release":{"releasePublishedAt":"2026-11-13T19:24:07Z","releaseTag":"3.9.3","reviewed":"2026-11-19","scope":"Upstream PrefectHQ/prefect release record; commercial editions and deployment packages may differ","source":"https://github.com/PrefectHQ/prefect/releases/tag/3.9.3","status":"documented","summary":"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.","supportingSources":[{"title":"Prerelease-only security fixes","url":"https://github.com/PrefectHQ/prefect/releases/tag/3.9.4.dev6"}]},"securityControls":{"reviewed":"2026-11-19","scope":"Prefect GitRepository logging and UI v2 redirect behavior; remediation was prerelease-only when reviewed","source":"https://github.com/PrefectHQ/prefect/pull/23969","status":"documented","summary":"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.","supportingSources":[{"title":"3.9.4.dev6 prerelease","url":"https://github.com/PrefectHQ/prefect/releases/tag/3.9.4.dev6"},{"title":"Same-origin redirect hardening","url":"https://github.com/PrefectHQ/prefect/pull/23980"}]},"sso":{"reviewed":"2026-11-20","scope":"Prefect Server security settings; external user federation remains unconfirmed","source":"https://docs.prefect.io/v3/advanced/security-settings","status":"inconclusive","summary":"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."}},"id":"prefect","infrastructure":["servers"],"infrastructureNotes":"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.","infrastructureReviewed":"2026-11-10","infrastructureSources":["https://raw.githubusercontent.com/PrefectHQ/prefect/main/docs/v3/advanced/self-hosted.mdx"],"install":"Install Prefect and start its server; use the documented PostgreSQL/Redis architecture when scaling multiple API and background-service instances.","installMethods":["other"],"kind":"product","license":"Apache License 2.0 for upstream Prefect. Prefect Cloud is a separate managed offering.","licenseModel":"open-source","licenseModelNotes":"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.","licenseModelSources":["https://raw.githubusercontent.com/PrefectHQ/prefect/main/LICENSE"],"licenseReviewed":"2026-11-10","model":"Fully in your account","modelLabel":"Customer-operated","name":"Prefect Server","notes":"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.","operations":"Customer manages server services, database, queue/cache, worker pools, secrets, access controls and upgrades.","publisher":false,"reviewed":"2026-11-19","sources":[{"title":"Official installation and runtime","url":"https://raw.githubusercontent.com/PrefectHQ/prefect/main/docs/v3/advanced/self-hosted.mdx"},{"title":"Upstream project and capabilities","url":"https://github.com/PrefectHQ/prefect"},{"title":"Current upstream license","url":"https://raw.githubusercontent.com/PrefectHQ/prefect/main/LICENSE"},{"title":"Self-hosted startup and workflow functionality","url":"https://raw.githubusercontent.com/PrefectHQ/prefect/main/README.md"},{"title":"Prefect deployment through Northflank BYOC","url":"https://northflank.com/guides/how-to-deploy-prefect"},{"title":"Prefect 3.9.4.dev6 prerelease","url":"https://github.com/PrefectHQ/prefect/releases/tag/3.9.4.dev6"},{"title":"GitRepository credential-log fix","url":"https://github.com/PrefectHQ/prefect/pull/23969"},{"title":"UI v2 redirect hardening","url":"https://github.com/PrefectHQ/prefect/pull/23980"}],"url":"https://launchinyourcloud.com/directory/prefect/","website":"https://www.prefect.io/"},{"advisories":[{"action":"Patch the deployed supported line and review namespace authorizations before upgrading.","conditions":"The permission change affects callers of that API. The release notes do not establish a shared affected range for every security fix.","id":"temporal-1-32-2-security-review","listingIds":["temporal"],"reviewed":"2026-11-17","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.","source":"https://github.com/temporalio/temporal/releases/tag/v1.32.2","summary":"The patch includes security fixes and requires namespace Write access for ValidateWorkerDeploymentVersionComputeConfig.","supportingSources":[{"title":"Temporal 1.31 security patch","url":"https://github.com/temporalio/temporal/releases/tag/v1.31.5"},{"title":"Temporal 1.30 security patch","url":"https://github.com/temporalio/temporal/releases/tag/v1.30.9"}],"title":"Temporal security patches and namespace permissions","type":"security-advisory"}],"architecture":"Customer-operated Temporal Service, persistence/visibility stores and worker services","categories":["workflow-orchestration"],"category":"Workflow orchestration","categoryFit":{"workflow-orchestration":"Developer-oriented durable workflow execution and retry/state orchestration; application workers and code must be supplied."},"cloudEvidence":[{"clouds":["aws"],"notes":"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.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Temporal server Helm chart on Amazon EKS","url":"https://github.com/temporalio/helm-charts","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-12","clouds":["aws"],"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"not-assessed","evidence":[0],"operator":"customer"}],"description":"Orchestrate durable application workflows with a customer-operated Temporal Service.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Official production planning requirements; numeric whole-stack and worker sizing remains unconfirmed","source":"https://docs.temporal.io/self-hosted-guide/production-checklist","status":"inconclusive","summary":"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."},"iac":{"artifactRef":"repository default branch (moving; select matching application release)","artifactUrl":"https://github.com/temporalio/samples-server","reviewed":"2026-11-14","scope":"Upstream self-hosted deployment; not a provider support or production-readiness certification","source":"https://docs.temporal.io/self-hosted-guide/deployment","status":"documented","summary":"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."},"licensePricing":{"reviewed":"2026-11-20","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","status":"documented","summary":"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."},"release":{"releasePublishedAt":"2026-11-02T18:38:48Z","releaseTag":"v1.32.2","reviewed":"2026-11-14","scope":"Upstream temporalio/temporal release record; commercial editions and deployment packages may differ","source":"https://github.com/temporalio/temporal/releases/tag/v1.32.2","status":"documented","summary":"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."},"sso":{"availability":"available","reviewed":"2026-11-14","scope":"Temporal Web UI only; not automatic service/worker access control","source":"https://docs.temporal.io/references/web-ui-configuration","status":"documented","summary":"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."}},"id":"temporal","infrastructure":["servers"],"infrastructureNotes":"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.","infrastructureReviewed":"2026-11-10","infrastructureSources":["https://docs.temporal.io/self-hosted-guide"],"install":"Production Docker/Kubernetes or manual server deployment with persistence and application workers","installMethods":["docker"],"kind":"product","license":"MIT-licensed Temporal Server; managed Cloud offering is separate","licenseModel":"open-source","licenseModelNotes":"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.","licenseModelSources":["https://github.com/temporalio/temporal/blob/main/LICENSE","https://docs.temporal.io/self-hosted-guide"],"licenseReviewed":"2026-11-10","model":"Fully in your account","modelLabel":"Customer-operated","name":"Temporal Self-Hosted","notes":"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.","operations":"Customer configures service security, persistence, worker capacity, monitoring, upgrades and disaster recovery.","publisher":false,"reviewed":"2026-11-17","sources":[{"title":"Production self-hosted service guide","url":"https://docs.temporal.io/self-hosted-guide"},{"title":"Production responsibilities and limitations","url":"https://docs.temporal.io/self-hosted-guide/production-checklist"},{"title":"Official server license","url":"https://github.com/temporalio/temporal/blob/main/LICENSE"},{"title":"Durable workflow platform","url":"https://docs.temporal.io/"},{"title":"Temporal v1.32.2 security and permission changes","url":"https://github.com/temporalio/temporal/releases/tag/v1.32.2"}],"url":"https://launchinyourcloud.com/directory/temporal/","website":"https://temporal.io/"}],"schemaVersion":1,"url":"https://launchinyourcloud.com/categories/workflow-orchestration/"}