
# Workflow automation on Google Cloud

Compare documented Workflow automation deployments on Google Cloud, including operating responsibility, licensing and deployment evidence.

Canonical page: https://launchinyourcloud.com/clouds/gcp/workflow-automation/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




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


## Provider guidance

- Account boundary: Google Cloud project
- Provider group: cloud-infrastructure
- Provider classification: Navigation group for the documented infrastructure offering; read each application path for its actual account boundary. Source: https://docs.cloud.google.com/resource-manager/docs/creating-managing-projects (checked 2026-11-20).
- Network: VPC network
- Identity and access: IAM policies and service accounts
- Installation guidance: Terraform, optionally using Infrastructure Manager for resource provisioning; deploy the application separately.
- Guidance source: https://docs.cloud.google.com/infrastructure-manager/docs/overview
- Guidance reviewed: 2026-11-10


### Private offers

Cloud Marketplace vendors can negotiate a private offer for a specified Cloud Billing account. Check duration, renewal terms and commitment treatment in the actual agreement.
Source: https://docs.cloud.google.com/marketplace/docs/offers/discover-private-offers (reviewed 2026-11-14).

### Private connectivity

Private Service Connect connects VPC consumers to supported managed or producer services. Confirm the actual product endpoint and network/DNS architecture.
Source: https://docs.cloud.google.com/vpc/docs/private-service-connect (reviewed 2026-11-14).

### External workload access

Workload Identity Federation can grant external workloads scoped Google Cloud access without long-lived service-account keys. Validate the trust configuration and exact roles.
Source: https://docs.cloud.google.com/iam/docs/workload-identity-federation (reviewed 2026-11-14).

### Regulated environments

Assured Workloads applies control packages for residency and access boundaries. Confirm supported services, regions and the product deployment; it is not automatic product certification.
Source: https://docs.cloud.google.com/assured-workloads/docs/overview (reviewed 2026-11-14).

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

14 listings.


## Activepieces Self-Hosted

Self-hosted workflow automation platform with integrations, triggers, actions and worker execution.

- Listing: https://launchinyourcloud.com/directory/activepieces/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, gcp, railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT-licensed Community Edition core; enterprise and cloud feature directories use commercial terms.
- Licensing model: open-source
- Installation: Official AWS Pulumi stack, Google Cloud VM guide or Railway template; Docker Compose and Kubernetes/Helm are also documented.
- Architecture: Application and worker containers with deployment-specific database and queue services
- Operations: Customer manages application configuration, secrets, integrations, backups and upgrades. AWS and Google Cloud paths require customer-managed infrastructure; Railway operates the underlying platform within the customer project.
- Product website: https://www.activepieces.com/
- Source review: 2026-11-13; cloud review: 2026-11-13; licensing review: 2026-11-13; infrastructure review: 2026-11-13

### Scope and qualifications

This entry covers self-hosted Activepieces, not Activepieces Cloud. The AWS template can provision RDS PostgreSQL, Redis, load balancing and Route 53 integration. The Google Cloud guide uses a VM/container example with SQLite and in-memory Redis; confirm release compatibility and use the current production database and queue requirements. Railway deploys into a customer project on platform-managed infrastructure. Enterprise features require a separate license.

Activepieces Community Edition core is MIT licensed. Enterprise and cloud feature directories use a commercial license; confirm the selected edition and entitlements.

The documented deployments run long-lived application and worker containers with persistent data services. Railway operates the underlying platform; managed databases and load balancers do not make the application runtime serverless.


### Category fit

- workflow-automation: Builds event-driven business automations from triggers and actions, with customer-operated workers and integrations.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.activepieces.com/docs/install/options/aws (checked 2026-11-13). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.activepieces.com/docs/install/options/gcp (checked 2026-11-13). 

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://www.activepieces.com/docs/install/options/railway (checked 2026-11-13). 


### Cloud deployment evidence

- Activepieces deployment into a customer AWS account with Pulumi (aws): https://www.activepieces.com/docs/install/options/aws
  The vendor-maintained Pulumi template deploys Activepieces into the operator's AWS account and can create VPC, compute, RDS PostgreSQL, Redis, load-balancing, ECR and Route 53 resources. Review template defaults, image versions, IAM permissions, secrets and production hardening.
  Source type: vendor-documentation; reviewed: 2026-11-13; vendor support: not-assessed.

- Google Cloud VM deployment (gcp): https://www.activepieces.com/docs/install/options/gcp
  The vendor documents running the Activepieces application container on a Google Cloud VM or instance group. Its example uses SQLite and in-memory Redis; confirm compatibility with the selected release and follow current production database, queue and security requirements.
  Source type: vendor-documentation; reviewed: 2026-11-13; vendor support: not-assessed.

- Railway project deployment (railway): https://www.activepieces.com/docs/install/options/railway
  The vendor documents a Railway template that deploys the Activepieces application with PostgreSQL and Redis into the operator's project. Railway manages the underlying infrastructure; the operator configures secrets, application access, persistence and backups. This is separate from Activepieces Cloud and does not establish ownership of an underlying hyperscaler account.
  Source type: vendor-documentation; reviewed: 2026-11-13; vendor support: not-assessed.


### Sources

- Self-hosting and installation options: https://www.activepieces.com/docs/install/overview

- Official AWS Pulumi deployment: https://www.activepieces.com/docs/install/options/aws

- Community and enterprise licensing: https://github.com/activepieces/activepieces/blob/main/docs/about/license.mdx

- Google Cloud VM deployment: https://www.activepieces.com/docs/install/options/gcp

- Railway project deployment: https://www.activepieces.com/docs/install/options/railway

### Licensing sources

- https://github.com/activepieces/activepieces/blob/main/LICENSE

- https://github.com/activepieces/activepieces/blob/main/docs/about/license.mdx

### Infrastructure sources

- https://www.activepieces.com/docs/install/overview

- https://www.activepieces.com/docs/install/options/aws

- https://www.activepieces.com/docs/install/options/gcp

- https://www.activepieces.com/docs/install/options/railway


### 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: Edition-dependent. The paid SSO guide explicitly documents SAML for self-hosted Enterprise. Company-domain verification and identity-provider setup are required; Google sign-in has separate self-hosted credentials. Scope: Self-hosted Enterprise SAML; not the free hobbyist mode. Source: https://www.activepieces.com/docs/admin-guide/guides/sso (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 Compose workflow generates secrets and runs application/worker/database/cache services. Its worker replica count needs sizing and encryption keys need backup; the hobbyist single-container mode has different limits. Scope: Compose deployment; not the embedded-database hobbyist mode. Source: https://www.activepieces.com/docs/install/options/docker-compose (reviewed 2026-11-14). Deployment artifact: https://github.com/activepieces/activepieces. Artifact reference: repository default branch (moving; select matching application release).

- Minimum footprint / sizing: Documented. The Compose guide requires at least 2 vCPU and 4 GB RAM. Workflow concurrency and the default worker replica count require workload-specific sizing; the hobbyist embedded-database install is a different topology. Scope: Activepieces Compose baseline; not guaranteed workflow throughput. Source: https://www.activepieces.com/docs/install/options/docker-compose (reviewed 2026-11-14).

- License pricing: Documented. The 0.93.0 licensing guide identifies the core as MIT-licensed and enterprise/cloud feature code as commercially licensed. Using those enterprise features in a self-hosted installation requires an Activepieces licence obtained from sales. Scope: Self-hosted core versus commercially entitled enterprise features; no hosted-plan price used as a self-hosted quote. Source: https://github.com/activepieces/activepieces/blob/0.93.0/docs/about/license.mdx (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The publisher-designated GitHub release checked was 0.93.0, published 2026-11-08. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package. Scope: Upstream activepieces/activepieces release record; commercial editions and deployment packages may differ. Source: https://github.com/activepieces/activepieces/releases/tag/0.93.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.




## Decisions Self-Hosted

Commercial rules and workflow platform with provider-specific container deployments.

- Listing: https://launchinyourcloud.com/directory/decisions-platform/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
- Licensing model: commercial-only
- Installation: Docker / Compose; Kubernetes manifests
- Architecture: Licensed Decisions application containers and required database/cache services on AWS, Azure or GCP.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://documentation.decisions.com/docs/deploying-containers-on-aws-1.md
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The platform can implement lending workflows, but deployment of the platform does not install a complete loan-origination product. Container licences, application versions and cloud infrastructure are separate scopes.

Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.

Licensed Decisions application containers and required database/cache services on AWS, Azure or GCP. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- workflow-automation: Commercial rules and workflow platform with provider-specific container deployments.

- internal-tools: Commercial rules and workflow platform with provider-specific container deployments.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.decisions.com/docs/deploying-containers-on-aws-1.md (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.decisions.com/docs/deploying-containers-on-azure-1.md (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.decisions.com/docs/deploying-containers-on-gcp-1.md (checked 2026-11-19). 


### Cloud deployment evidence

- AWS ECS Deploy (aws): https://documentation.decisions.com/docs/deploying-containers-on-aws-1.md
  Licensed Decisions application containers and required database/cache services on AWS, Azure or GCP. The platform can implement lending workflows, but deployment of the platform does not install a complete loan-origination product. Container licences, application versions and cloud infrastructure are separate scopes.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Azure Deploy (azure): https://documentation.decisions.com/docs/deploying-containers-on-azure-1.md
  Licensed Decisions application containers and required database/cache services on AWS, Azure or GCP. The platform can implement lending workflows, but deployment of the platform does not install a complete loan-origination product. Container licences, application versions and cloud infrastructure are separate scopes.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- GCP Deploy (gcp): https://documentation.decisions.com/docs/deploying-containers-on-gcp-1.md
  Licensed Decisions application containers and required database/cache services on AWS, Azure or GCP. The platform can implement lending workflows, but deployment of the platform does not install a complete loan-origination product. Container licences, application versions and cloud infrastructure are separate scopes.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- AWS ECS Deploy: https://documentation.decisions.com/docs/deploying-containers-on-aws-1.md

- Azure Deploy: https://documentation.decisions.com/docs/deploying-containers-on-azure-1.md

- GCP Deploy: https://documentation.decisions.com/docs/deploying-containers-on-gcp-1.md

- AWS EKS Deploy: https://documentation.decisions.com/docs/deploying-an-aws-kubernetes-cluster.md

- Azure AKS Deploy: https://documentation.decisions.com/docs/deploying-azure-kubernetes-services-aks.md

- Financial Services: https://decisions.com/solutions/industry/financial-services

- Terms of Use: https://decisions.com/terms-of-use

- Container Licensing: https://documentation.decisions.com/docs/licensing-a-container.md

- v10.4.x Release Notes: https://documentation.decisions.com/v99/docs/version-104x-release-notes.md

### Licensing sources

- https://decisions.com/terms-of-use

- https://documentation.decisions.com/docs/licensing-a-container.md

### Infrastructure sources

- https://documentation.decisions.com/docs/deploying-containers-on-aws-1.md

- https://documentation.decisions.com/docs/deploying-containers-on-azure-1.md

- https://documentation.decisions.com/docs/deploying-containers-on-gcp-1.md


### Buyer diligence


Research coverage: 4/12 fields (33%); 4 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 vendor documents SAML login through an installed identity-provider module, certificate and IdP settings, with accounts updated before enforcement and at least one working admin SSO account. It warns that Active Directory Sync cannot run simultaneously with SAML/OpenID SSO modules. Scope: Self-hosted application user SSO; module/release and IdP configuration required. Source: https://documentation.decisions.com/docs/saml (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. The installation guide provides the v10.x installer and supported database setup. The ECS guide documents task definitions using the vendor container image, environment variables and persistent file storage; it is a console recipe rather than a supplied Terraform/CloudFormation stack. Pin a compatible released image rather than copying latest. Scope: Licensed self-hosted installer/container workflow; application, database and HA setup are separate. Source: https://documentation.decisions.com/docs/deploying-containers-on-aws-1 (reviewed 2026-11-20). Supporting source: v10 installation guide and release download — https://documentation.decisions.com/version-10/docs/installation-guide.

- Minimum footprint / sizing: Documented. The installation requirements list an AWS production example using t3.xlarge (4 vCPU, 16 GB RAM) and 100 GB storage. Database requirements are separate, and enterprise/HA topology and workload can require larger or multiple servers. This server example does not include 1 TB of application data. Scope: General self-hosted application-server guidance; not a cost estimate or validated reference-workload HA design. Source: https://documentation.decisions.com/docs/installation-requirements (reviewed 2026-11-20).

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: Decisions Self-Hosted; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://decisions.com/terms-of-use (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## DocuSeal Self-Hosted

Self-hosted document forms and electronic-signature workflows with API and webhook integration.

- Listing: https://launchinyourcloud.com/directory/docuseal/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, linode, vultr, hostinger, lumadock, azure, gcp, railway, heroku, render
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: AGPL-3.0 core; Pro features and the private Pro image use separate commercial terms.
- Licensing model: open-source
- Installation: Vendor Azure, Google Cloud, DigitalOcean, Railway, Heroku and Render deployment paths, or a Cloudron package on a customer VM.
- Architecture: Rails web application and document-processing jobs with a database, attachments and signing configuration
- Operations: Customer manages administrator access, signing workflows, HTTPS, secrets, database networking, mail, durable attachment storage, database/file/key recovery and image upgrades. Platform providers operate the underlying managed services. For 3.3.8 security remediation, restart every Ruby web and background process after deployment.
- Product website: https://www.docuseal.com/
- Source review: 2026-11-19; cloud review: 2026-11-13; licensing review: 2026-11-13; infrastructure review: 2026-11-13

### Scope and qualifications

Reviewed core 3.3.7 includes security hardening, bug fixes, and performance improvements. The separately reviewed Cloudron package snapshot is 1.21.3 with core 3.3.6; pin a current image and confirm package lag before upgrading. Back up the database and attachments, and preserve SECRET_KEY_BASE. Native deployment examples need production configuration: restrict database access and configure durable storage; Heroku/Render app filesystems are ephemeral, and the free Render database expires. Paid features require appropriate entitlements; Pro uses a license/usage connection to DocuSeal. Qualified electronic signatures are not available in the on-premises edition. Cloudron runs the application and its persistent data on a customer-controlled server. Its platform has separate plans and requires a Cloudron account for installation/updates; account, server and app-installation metadata reaches Cloudron. Remote support requires customer-granted access. The customer chooses DNS, mail and backup destinations. DocuSeal 3.3.8 fixes GHSA-78g6-f52x-q3jx, a High-severity unauthenticated denial of service in Ruby versions used by earlier DocuSeal builds. Versions before 3.3.8 are affected and no workaround is documented. Upgrade, restart every Ruby web and background process, and verify all workers use the updated runtime.

AGPL-3.0 core; Pro features and the private Pro image use separate commercial terms. Cloudron packaging and platform plans have separate terms; the application license does not grant a free platform subscription.

Web application containers and document-processing jobs with durable database and attachment storage on Cloudron or managed application platforms. Cloud Run container hosting does not establish event-driven function deployment support.


### Category fit

- workflow-automation: Automates document form filling, signature collection and completion workflows through a self-hosted application, API and webhooks. This does not establish full contract lifecycle management or regulated-record compliance.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://aws.amazon.com/marketplace/pp/prodview-aep3gt5elubci (checked 2026-11-13). 

- digitalocean: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://marketplace.digitalocean.com/apps/cloudron (checked 2026-11-13). Source: https://github.com/docusealco/docuseal-digitalocean/blob/master/.do/deploy.template.yaml (checked 2026-11-13). 

- linode: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.linode.com/docs/marketplace-docs/guides/cloudron/ (checked 2026-11-13). 

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

- hostinger: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.hostinger.com/support/8637788-how-to-use-the-cloudron-vps-template-at-hostinger/ (checked 2026-11-13). 

- lumadock: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://lumadock.com/vps-hosting/cloudron (checked 2026-11-13). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.docuseal.com/docs/deploying-docuseal-on-azure-web-apps (checked 2026-11-13). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.docuseal.com/docs/deploying-docuseal-on-google-cloud-run (checked 2026-11-13). 

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://railway.com/deploy/IGoDnc (checked 2026-11-13). 

- heroku: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://github.com/docusealco/docuseal-heroku/blob/master/app.json (checked 2026-11-13). 

- render: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://github.com/docusealco/docuseal-render/blob/master/render.yaml (checked 2026-11-13). 


### Cloud deployment evidence

- Cloudron EC2 AMI and application installation (aws): https://aws.amazon.com/marketplace/pp/prodview-aep3gt5elubci
  DocuSeal Self-Hosted 3.3.6 is available as Cloudron package 1.21.3. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established.
  Source type: marketplace-offer; reviewed: 2026-11-13; vendor support: not-assessed.

- Cloudron customer Droplet deployment (digitalocean): https://marketplace.digitalocean.com/apps/cloudron
  DocuSeal Self-Hosted 3.3.6 is available as Cloudron package 1.21.3. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established.
  Source type: marketplace-offer; reviewed: 2026-11-13; vendor support: not-assessed.

- Cloudron customer Linode deployment (linode): https://www.linode.com/docs/marketplace-docs/guides/cloudron/
  DocuSeal Self-Hosted 3.3.6 is available as Cloudron package 1.21.3. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established.
  Source type: provider-guide; reviewed: 2026-11-13; vendor support: not-assessed.

- Cloudron named-provider installation and Marketplace availability (vultr): https://docs.cloudron.io/installation/
  DocuSeal Self-Hosted 3.3.6 is available as Cloudron package 1.21.3. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established. Cloudron currently names the Vultr Marketplace offer; use current Cloudron OS requirements, not the historical Ubuntu 20.04 tutorial.
  Source type: package-platform-documentation; reviewed: 2026-11-13; vendor support: not-assessed.

- Hostinger customer VPS Cloudron template (hostinger): https://www.hostinger.com/support/8637788-how-to-use-the-cloudron-vps-template-at-hostinger/
  DocuSeal Self-Hosted 3.3.6 is available as Cloudron package 1.21.3. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established.
  Source type: provider-guide; reviewed: 2026-11-13; vendor support: not-assessed.

- LumaDock customer VPS Cloudron template (lumadock): https://lumadock.com/vps-hosting/cloudron
  DocuSeal Self-Hosted 3.3.6 is available as Cloudron package 1.21.3. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established.
  Source type: provider-guide; reviewed: 2026-11-13; vendor support: not-assessed.

- Vendor Azure Web Apps deployment (azure): https://www.docuseal.com/docs/deploying-docuseal-on-azure-web-apps
  Installs the actual application container in a customer Azure resource group with PostgreSQL and Blob Storage. Configure secrets, storage and production database network restrictions rather than retaining permissive example firewall rules.
  Source type: vendor-documentation; reviewed: 2026-11-13; vendor support: not-assessed.

- Vendor Google Cloud Run deployment (gcp): https://www.docuseal.com/docs/deploying-docuseal-on-google-cloud-run
  Installs the actual application container in a customer project with Cloud SQL and Google Cloud Storage. Configure keys, bucket access and production database network restrictions. This is application hosting, not a storage-only integration.
  Source type: vendor-documentation; reviewed: 2026-11-13; vendor support: not-assessed.

- Vendor DigitalOcean application specification (digitalocean): https://github.com/docusealco/docuseal-digitalocean/blob/master/.do/deploy.template.yaml
  Creates the vendor application container and PostgreSQL in a customer App Platform account. Database persistence does not preserve attachments: configure durable object storage and back up both. Pin the application image and configure real mail.
  Source type: vendor-documentation; reviewed: 2026-11-13; vendor support: not-assessed.

- Vendor-linked Railway application template (railway): https://railway.com/deploy/IGoDnc
  Installs the vendor application and PostgreSQL in a customer Railway project. The database volume alone does not preserve attachments: configure an application volume at the image data path or durable object storage. Review secrets, SMTP and backups.
  Source type: community-template; reviewed: 2026-11-13; vendor support: not-assessed.

- Vendor Heroku application specification (heroku): https://github.com/docusealco/docuseal-heroku/blob/master/app.json
  Creates a container application and PostgreSQL add-on in a customer Heroku account. Dyno filesystems are ephemeral: configure durable object storage for documents, retain encryption keys and back up the database.
  Source type: vendor-documentation; reviewed: 2026-11-13; vendor support: not-assessed.

- Vendor Render application blueprint (render): https://github.com/docusealco/docuseal-render/blob/master/render.yaml
  Creates the application and PostgreSQL in a customer Render account. The example selects free services; Render does not recommend those for production and the free database expires after 30 days. Use suitable paid compute/database, durable attachment storage, secrets and working outbound mail.
  Source type: vendor-documentation; reviewed: 2026-11-13; vendor support: not-assessed.


### Community and maintenance

The current core has sustained work by two principal maintainers, external code contributions and continuing security releases. Public contributor and release histories establish ongoing maintenance; they do not independently validate every paid feature or customer deployment.

Reviewed 2026-11-19.

- Contributor history: https://github.com/docusealco/docuseal/graphs/contributors

- Reviewed maintenance and security release 3.3.8: https://github.com/docusealco/docuseal/releases/tag/3.3.8

- Release history: https://www.docuseal.com/changelog

### Sources

- Self-hosted edition and boundaries: https://www.docuseal.com/on-premises

- Vendor installation options: https://www.docuseal.com/install

- Production runtime requirements: https://www.docuseal.com/docs/on-premises-server-requirements

- Configuration, secrets and storage: https://www.docuseal.com/docs/configuring-docuseal-via-environment-variables

- Cloudron application operations: https://docs.cloudron.io/packages/docuseal/

- Core application and installation: https://github.com/docusealco/docuseal/blob/3.3.6/README.md

- Attachment storage configuration: https://github.com/docusealco/docuseal/blob/3.3.6/config/storage.yml

- Default storage selection: https://github.com/docusealco/docuseal/blob/3.3.6/config/environments/production.rb

- Pro image, licensing and usage connection: https://www.docuseal.com/docs/on-premises-pro-installation

- Qualified signature edition limitation: https://www.docuseal.com/faq/how-to-use-qes-signing-with-docuseal-on-premises

- Current security release: https://github.com/docusealco/docuseal/releases/tag/3.3.7

- Release and security history: https://www.docuseal.com/changelog

- Core AGPL license: https://github.com/docusealco/docuseal/blob/3.3.6/LICENSE

- Contributor history: https://github.com/docusealco/docuseal/graphs/contributors

- Cloudron application packages and persistent data: https://docs.cloudron.io/apps/

- Cloudron application updates: https://docs.cloudron.io/updates/

- Cloudron database and application-data backups: https://docs.cloudron.io/backups/

- Cloudron platform plans: https://www.cloudron.io/pricing.html

- Cloudron account and platform terms: https://www.cloudron.io/legal/terms.html

- Cloudron account and installation metadata: https://www.cloudron.io/legal/privacy.html

- Exact Cloudron application package versions: https://www.cloudron.io/store/index.html

- Cloudron EC2 AMI and application installation: https://aws.amazon.com/marketplace/pp/prodview-aep3gt5elubci

- Cloudron customer Droplet deployment: https://marketplace.digitalocean.com/apps/cloudron

- Cloudron customer Linode deployment: https://www.linode.com/docs/marketplace-docs/guides/cloudron/

- Cloudron named-provider installation and Marketplace availability: https://docs.cloudron.io/installation/

- Hostinger customer VPS Cloudron template: https://www.hostinger.com/support/8637788-how-to-use-the-cloudron-vps-template-at-hostinger/

- LumaDock customer VPS Cloudron template: https://lumadock.com/vps-hosting/cloudron

- Vendor Azure Web Apps deployment: https://www.docuseal.com/docs/deploying-docuseal-on-azure-web-apps

- Vendor Google Cloud Run deployment: https://www.docuseal.com/docs/deploying-docuseal-on-google-cloud-run

- Vendor DigitalOcean application specification: https://github.com/docusealco/docuseal-digitalocean/blob/master/.do/deploy.template.yaml

- Vendor-linked Railway application template: https://railway.com/deploy/IGoDnc

- Vendor Heroku application specification: https://github.com/docusealco/docuseal-heroku/blob/master/app.json

- Vendor Render application blueprint: https://github.com/docusealco/docuseal-render/blob/master/render.yaml

- Railway application Docker source: https://github.com/docusealco/docuseal-railway

- Railway volume persistence: https://docs.railway.com/volumes/reference

- Heroku ephemeral dyno filesystem: https://devcenter.heroku.com/articles/dyno-isolation

- Render free-service production limitations: https://render.com/docs/free

- Vendor application upgrade instructions: https://www.docuseal.com/docs/update-docuseal-to-the-latest-version

- Security-hardening changes in 3.3.7: https://github.com/docusealco/docuseal/compare/3.3.6...3.3.7

- DocuSeal 3.3.8 security release: https://github.com/docusealco/docuseal/releases/tag/3.3.8

- GHSA-78g6-f52x-q3jx: https://github.com/docusealco/docuseal/security/advisories/GHSA-78g6-f52x-q3jx

### Licensing sources

- https://github.com/docusealco/docuseal/blob/3.3.6/LICENSE

- https://www.docuseal.com/docs/on-premises-pro-installation

- https://www.cloudron.io/legal/terms.html

- https://www.cloudron.io/pricing.html

### Infrastructure sources

- https://docs.cloudron.io/packages/docuseal/

- https://docs.cloudron.io/installation/

- https://www.docuseal.com/docs/deploying-docuseal-on-azure-web-apps

- https://www.docuseal.com/docs/deploying-docuseal-on-google-cloud-run


### Buyer diligence


Research coverage: 7/12 fields (58%); 7 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. AWS delivery uses Cloudron’s platform AMI and a separate application package. Cloudron publishes the platform offer; application versions, licensing and support are separate. Scope: Cloudron platform plus separate application package. Source: https://aws.amazon.com/marketplace/pp/prodview-aep3gt5elubci (reviewed 2026-11-14). Supporting source: Cloudron application package — https://docs.cloudron.io/packages/docuseal/. Offer prodview-aep3gt5elubci: Cloudron UG; Platform AMI; external Cloudron license; package Cloudron 10.0.5 (platform, not application); https://aws.amazon.com/marketplace/pp/prodview-aep3gt5elubci.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Edition-dependent. SAML SSO appears in the self-hosted Pro feature list. It is not established here for the free edition. Scope: Self-hosted Pro. Source: https://www.docuseal.com/on-premises (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. GHSA-78g6-f52x-q3jx affects DocuSeal before 3.3.8. A single unauthenticated request can crash a Ruby application worker before routing or authentication. No workaround is documented; update and restart every web and background process. Scope: DocuSeal versions earlier than 3.3.8. Source: https://github.com/docusealco/docuseal/security/advisories/GHSA-78g6-f52x-q3jx (reviewed 2026-11-19). Supporting source: 3.3.8 security release — https://github.com/docusealco/docuseal/releases/tag/3.3.8.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The upstream Compose example defines DocuSeal, PostgreSQL and Caddy with persistent storage. It uses moving application/proxy images and example database credentials; pin compatible versions and replace credentials before deployment. Scope: Upstream Compose example; not a hardened production baseline. Source: https://github.com/docusealco/docuseal/blob/master/docker-compose.yml (reviewed 2026-11-14). Deployment artifact: https://github.com/docusealco/docuseal/blob/master/docker-compose.yml. Artifact reference: master (moving branch).

- Minimum footprint / sizing: Documented. The vendor sizes examples for 10,000 signed documents. For one-off templates with one signer and 500-KB average files it lists 1 vCPU, 1 GB RAM and 12 GB disk; larger files, reused templates and multiple signers have different storage needs. PostgreSQL is recommended for heavy production/API use. Scope: Approximate document-based examples, not a 1-TB or HA installation baseline. Source: https://www.docuseal.com/docs/on-premises-server-requirements (reviewed 2026-11-20).

- License pricing: Documented. The 3.3.8 core is AGPLv3. The on-premises page offers free self-hosting and separately prices Pro at $240 per user/year plus $0.20 per document signed through API or embedding. Confirm billable user/document definitions, currency and current terms before quoting. Scope: Self-hosted core versus paid Pro; advertised amounts are not a 100-user total or infrastructure cost. Source: https://www.docuseal.com/on-premises (reviewed 2026-11-20). Supporting source: Versioned core licence — https://github.com/docusealco/docuseal/blob/3.3.8/LICENSE.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. DocuSeal 3.3.8 was published November 19, 2026. It updates Ruby to address GHSA-78g6-f52x-q3jx; all web and background processes must be restarted so the fixed runtime is active. Scope: Upstream DocuSeal core release; separately packaged provider images may lag. Source: https://github.com/docusealco/docuseal/releases/tag/3.3.8 (reviewed 2026-11-19). Supporting source: Prior reviewed release context — https://github.com/docusealco/docuseal/releases/tag/3.3.7. Supporting source: Security advisory — https://github.com/docusealco/docuseal/security/advisories/GHSA-78g6-f52x-q3jx.



### Vendor alternative positioning

Positioning is not a finding of feature parity.

- docusign: The publisher positions DocuSeal as an alternative for document-signing workflows. Source: https://www.docuseal.com/; reviewed 2026-11-16.

- pandadoc: The publisher positions DocuSeal as an alternative for document-signing workflows. Source: https://www.docuseal.com/; reviewed 2026-11-16.


### Security and lifecycle reviews

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

- DocuSeal 3.3.8 unauthenticated denial-of-service fix (security-advisory): GHSA-78g6-f52x-q3jx allows one unauthenticated request to crash a Ruby application worker before routing or authentication. Scope: DocuSeal versions earlier than 3.3.8. Conditions: Every web and background process still using the affected Ruby runtime remains exposed; the advisory documents no workaround. Action: Upgrade to 3.3.8 or later, restart every Ruby process and verify the active runtime. Source: https://github.com/docusealco/docuseal/security/advisories/GHSA-78g6-f52x-q3jx; reviewed 2026-11-19. Supporting source: 3.3.8 security release — https://github.com/docusealco/docuseal/releases/tag/3.3.8.




## Hyland OnBase On-Premise

Customer-hosted enterprise content and case platform for document-heavy business processes.

- Listing: https://launchinyourcloud.com/directory/onbase/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial OnBase licenses and separately scoped modules
- Licensing model: commercial-only
- Installation: Vendor or partner-assisted on-premises installation
- Architecture: Customer-hosted enterprise application, document storage and database; deployment sizing and modules require implementation planning.
- Operations: Customer maintains on-premises infrastructure and backups; agree implementation, upgrades and support responsibilities with Hyland or its partner.
- Product website: https://www.hyland.com/
- Source review: 2026-11-13; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

This entry covers licensed OnBase on-premises deployments. Category memberships describe documented platform configurations and integrations, not separately included turnkey applications. Loan tracking, claims integrations and other service solutions need scope and licensing confirmation.

The selected OnBase on-premises product is commercially licensed. Its current on-premises terms restrict production copies and require applicable fees for additional environments and certain access; modules and integrations follow the contracted scope.

Customer-hosted enterprise application, document storage and database; deployment sizing and modules require implementation planning.


### Category fit

- document-management: Enterprise content repository with capture, document workflows and integration with business applications.

- records-management: Retention and destruction workflows for electronic documents; WorkView also supports tracking physical records.

- contract-management: Configurable WorkView contract applications and document workflows; confirm modules and implementation scope.

- financial-application-management: Loan-document tracking and integration with loan origination systems; this supports the document process rather than replacing a lending core.

- case-management: Configurable case applications connect case data, documents, tasks and approvals.

- correspondence-management: Configurable OnBase workflows can store and route correspondence documents with related case work; implementation is solution-specific.

- vendor-supplier-document-management: Vendor case records and supporting documents in WorkView and accounts-payable workflows; not a dedicated supplier-risk service.

- hr-employee-records-management: Employee-file access, applicant-document routing and employee onboarding/offboarding workflows.

- policy-procedure-management: Electronic policy distribution and policy/procedure sign-off workflows in the HR document-management scope.

- claims-management: Document capture and workflows integrated with insurance claims systems; not a replacement for claims adjudication software.

- workflow-automation: Content and case workflows with routing, rules and low-code WorkView applications.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.reveillesoftware.com/solutions/reveille-for-hyland-onbase/ (checked 2026-11-12). Source: https://www.hyland.com/en/partners/reveille (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.reveillesoftware.com/solutions/reveille-for-hyland-onbase/ (checked 2026-11-12). Source: https://www.hyland.com/en/partners/reveille (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.reveillesoftware.com/solutions/reveille-for-hyland-onbase/ (checked 2026-11-12). Source: https://www.hyland.com/en/partners/reveille (checked 2026-11-12). 


### Cloud deployment evidence

- Hyland partner statement on customer-managed OnBase cloud deployments (aws, azure, gcp): https://www.reveillesoftware.com/solutions/reveille-for-hyland-onbase/
  Hyland-authorized integration partner Reveille explicitly describes OnBase 18+ in customer-managed AWS, Azure and Google Cloud environments, separately from OnBase Cloud. This is the partner's compatibility statement, not a Hyland installation guide or cloud-support certification. Confirm the current OnBase release, Windows/database topology, licenses and vendor support agreement; Reveille itself is not required for self-hosting.
  Source type: partner-evidence; reviewed: 2026-11-12; vendor support: not-assessed. Versions: OnBase 18+ in partner statement; confirm current release.

- Hyland identification of Reveille as an authorized integration partner (aws, azure, gcp): https://www.hyland.com/en/partners/reveille
  Hyland identifies Reveille as an authorized build partner for OnBase and other Hyland platforms. This corroborates the source relationship, not an independent certification of every deployment listed by the partner; use its customer-managed-cloud statement together with OnBase installation and commercial requirements.
  Source type: partner-relationship; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- OnBase platform capabilities: https://www.hyland.com/en/solutions/products/onbase

- On-premises product terms: https://legal.hyland.com/pst-on-premise-multi-products

- WorkView business application examples: https://www.hyland.com/en/resources/articles/workview-product-overview

- HR files and policy sign-offs: https://www.hyland.com/en/resources/terminology/human-resources/document-management

- OnBase workflow routing: https://docs.hyland.com/r/OnBase/Workflow/Foundation-23.1/Workflow/Overview/Workflow-Overview

- Correspondence document integration: https://docs.hyland.com/r/OnBase/Application-Client-Connector/Foundation-24.1/Application-Client-Connector/Overview/Introduction

- Loan-document tracking solution: https://community.hyland.com/kb/articles/1332-hyland-services-loan-document-tracking

- Insurance claims integration case study: https://www.hyland.com/en/customers/p-c-insurer

### Licensing sources

- https://legal.hyland.com/pst-on-premise-multi-products

### Infrastructure sources

- https://legal.hyland.com/pst-on-premise-multi-products


### Buyer diligence


Research coverage: 4/12 fields (33%); 4 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 Foundation 26.1 Web Client documents Integration for Single Sign-On and configuration of automatic login. Hyland identity-service authentication is also module-specific; confirm client coverage, identity-provider compatibility and licensed integrations for the selected solution. Scope: OnBase Foundation 26.1 Web Client configuration; not a blanket claim for every module. Source: https://docs.hyland.com/r/OnBase/Web-Server/Foundation-26.1/Web-Server/Configuration/Web.config-Configuration/appSettings?contentId=stz0b9kK0lYB~c4sf1hbkA (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. The Foundation 26.1 Web Server is delivered through vendor setup.exe/MSI installation media with documented interactive and silent configuration. Application Server installation is a prerequisite; no public cloud-provisioning template is established by this installer guide. Scope: Vendor-supplied OnBase Web Server installation media, not public IaC. Source: https://docs.hyland.com/r/OnBase/Web-Server/Foundation-26.1/Web-Server/Installation/Installation/Running-the-Installer?contentId=6JGslGq~Cra0GizajFYkbA (reviewed 2026-11-20).

- Minimum footprint / sizing: Documented. Foundation 26.1 lists a 2.4-GHz dual-core minimum, 4 GB RAM for Web Server and 8 GB for 64-bit Application Server, with 16 GB recommended for each. These are dedicated-role requirements; database, files, other modules, HA and workload capacity are additional. Scope: OnBase Foundation 26.1 Web/Application role minima; not the complete solution. Source: https://docs.hyland.com/r/OnBase/Technical-Requirements-Overview-for-New-Installations-and-Upgrades/Foundation-26.1/Technical-Requirements-Overview-for-New-Installations-and-Upgrades/Part-6-Web/Application-Server-and-Core-Services-Hardware-Requirements/64-Bit-Server-Hardware-Requirements?contentId=UToZTDrd9HvkQpjb7tURJQ (reviewed 2026-11-20).

- License pricing: Documented. The current on-premises terms distinguish production, disaster-recovery and separately licensed non-production use. Confirm the purchased product/client/API permissions and environments in the agreement; these terms do not supply a public total price. Scope: OnBase on-premises terms v1.2, effective 2026-06-23; customer order may add conditions. Source: https://legal.hyland.com/pst-on-premise-multi-products (reviewed 2026-11-16).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Medplum Self-Hosted

Open-source FHIR healthcare backend, clinical application and automation platform deployed in customer cloud infrastructure.

- Listing: https://launchinyourcloud.com/directory/medplum-self-hosted/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: hybrid
- License: Apache-2.0 Community software; an optional commercial Enterprise Self-Hosted support plan is separate.
- Licensing model: open-source
- Installation: AWS CDK, or Terraform and Helm on Azure AKS or Google GKE
- Architecture: Containerized API and web application with PostgreSQL, cache, object storage, secrets and load-balancing or CDN services
- Operations: Customer operates the cloud infrastructure and application lifecycle; Medplum offers an Enterprise Self-Hosted support plan.
- Product website: https://www.medplum.com/
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The official AWS, Azure and GCP guides deploy both backend and frontend components. Enterprise support is optional and does not change the Apache-2.0 classification of the selected Community software; validate healthcare compliance scope and local operating controls separately. The v5.2.17 release strips ClientApplication secrets from auth/me responses and changes on-behalf-of identity and delegation handling. Upgrade a compatible server/application bundle to v5.2.17 or later and test identity/delegation flows. Assess whether application secrets were exposed and rotate them where appropriate.

The Community software is Apache-2.0; Enterprise Self-Hosted support is a separate commercial service.

The deployment combines customer Kubernetes or container compute with managed database, cache, storage, secrets and network services.


### Category fit

- backend-platforms: Provides a FHIR datastore, APIs, OAuth identity, application SDKs and clinical backend services on customer infrastructure.

- workflow-automation: Medplum Bots, cron jobs, subscriptions and triggers automate clinical and operational workflows.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.medplum.com/docs/self-hosting/install-on-aws (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.medplum.com/docs/self-hosting/install-on-azure (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.medplum.com/docs/self-hosting/install-on-gcp (checked 2026-11-19). 


### Cloud deployment evidence

- Complete Medplum installation in a customer AWS account (aws): https://www.medplum.com/docs/self-hosting/install-on-aws
  Medplum describes a complete production-ready installation in the customer's AWS environment and deploys the application and supporting AWS resources with CDK.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Production-validated Medplum deployment on Azure (azure): https://www.medplum.com/docs/self-hosting/install-on-azure
  The official Terraform and Helm workflow deploys Medplum into the customer's Azure subscription with AKS, PostgreSQL, Redis, storage, gateway and frontend resources.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Production-validated Medplum deployment on Google Cloud (gcp): https://www.medplum.com/docs/self-hosting/install-on-gcp
  The official Terraform and Helm workflow deploys Medplum into the customer's Google Cloud project with GKE, Cloud SQL, Redis, storage and frontend resources.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes codyebberson, mattwiller, ThatOneBro, with sustained contributions alongside the dated application release and public installation history. This establishes maintained community participation, not a commercial support, compliance or capacity guarantee.

Reviewed 2026-11-19.

- Upstream contributor history: https://github.com/medplum/medplum/graphs/contributors

- Reviewed upstream application release: https://github.com/medplum/medplum/releases/tag/v5.2.17

### Sources

- Medplum production installation on AWS: https://www.medplum.com/docs/self-hosting/install-on-aws

- Medplum production installation on Azure: https://www.medplum.com/docs/self-hosting/install-on-azure

- Medplum production installation on Google Cloud: https://www.medplum.com/docs/self-hosting/install-on-gcp

- Medplum open-source terms: https://www.medplum.com/open-source

- Medplum self-hosted support plans: https://www.medplum.com/pricing

- Reviewed deployment artifact reference: https://github.com/medplum/medplum/tree/v5.2.17/packages/cdk

- Buyer evidence: release: https://github.com/medplum/medplum/releases/tag/v5.2.17

- Upstream contributor history: https://github.com/medplum/medplum/graphs/contributors

### Licensing sources

- https://www.medplum.com/open-source

- https://www.medplum.com/pricing

### Infrastructure sources

- https://www.medplum.com/docs/self-hosting/install-on-aws

- https://www.medplum.com/docs/self-hosting/install-on-azure

- https://www.medplum.com/docs/self-hosting/install-on-gcp


### Buyer diligence


Research coverage: 12/12 fields (100%); 4 documented, 8 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 reviewed deployment and licensing sources did not establish a public cloud-marketplace offer that unambiguously entitles the selected self-hosted edition. Obtain the exact offer ID, seller, delivery artifact and edition terms before treating marketplace procurement as available. Scope: Medplum Self-Hosted: selected customer-operated edition. Source: https://www.medplum.com/docs/self-hosting/install-on-aws (reviewed 2026-11-19).

- Cloud commitment eligibility: Sources checked — unresolved. Customer-cloud deployment or marketplace delivery does not by itself establish cloud-spend commitment eligibility. Confirm the exact offer, billed dimensions, private-offer terms and buyer agreement. Scope: Medplum Self-Hosted: selected customer-operated edition. Source: https://www.medplum.com/docs/self-hosting/install-on-aws (reviewed 2026-11-19).

- Single sign-on: Sources checked — unresolved. The reviewed installation and edition sources did not establish the exact SSO protocols, identity-provider support and entitlement for this selected edition. Confirm authentication, role mapping and break-glass access before deployment. Scope: Medplum Self-Hosted: selected customer-operated edition. Source: https://www.medplum.com/docs/self-hosting/install-on-aws (reviewed 2026-11-19).

- SCIM provisioning: Sources checked — unresolved. The reviewed sources did not establish a SCIM endpoint or automated user and group lifecycle for this selected edition. SSO, directory authentication or just-in-time account creation would not by themselves establish SCIM. Scope: Medplum Self-Hosted: selected customer-operated edition. Source: https://www.medplum.com/docs/self-hosting/install-on-aws (reviewed 2026-11-19).

- Compliance attestations: Sources checked — unresolved. The reviewed product and deployment sources did not establish an independent compliance attestation whose assessed scope covers this customer-operated edition and its local infrastructure. Obtain the current report and map customer responsibilities. Scope: Medplum Self-Hosted: selected customer-operated edition. Source: https://www.medplum.com/docs/self-hosting/install-on-aws (reviewed 2026-11-19).

- Security controls: Edition-dependent. The production guides deploy secrets, TLS termination, identity and private data services within the customer's cloud environment. Healthcare compliance still depends on the buyer's configuration, agreements, audit controls and operating procedures. Scope: Medplum Self-Hosted: selected customer-operated edition. Source: https://www.medplum.com/docs/self-hosting/install-on-aws (reviewed 2026-11-19).

- Air-gapped operation: Sources checked — unresolved. The reviewed sources did not establish a fully disconnected installation, update and license workflow for this selected edition. Identify required registries, package repositories, telemetry, identity, activation and support endpoints before claiming air-gapped operation. Scope: Medplum Self-Hosted: selected customer-operated edition. Source: https://www.medplum.com/docs/self-hosting/install-on-aws (reviewed 2026-11-19).

- Deployment artifact / IaC: Documented. The tagged @medplum/cdk 5.2.17 source supplies the AWS CDK application used by the installation guide. The CLI, server image, frontend build and Azure/GCP Terraform/Helm packages remain separately selected artifacts; one CDK tag does not pin the whole stack. Scope: Medplum Community AWS IaC source, independently versioned from other deployment components. Source: https://www.medplum.com/docs/self-hosting/install-on-aws (reviewed 2026-11-19). Deployment artifact: https://github.com/medplum/medplum/tree/v5.2.17/packages/cdk. Artifact reference: @medplum/cdk 5.2.17 at upstream tag v5.2.17.

- Minimum footprint / sizing: Sources checked — unresolved. The reviewed sources describe the deployment components but do not provide one complete production sizing model for the buyer's users, data volume, traffic, retention and availability target. Size every application and managed-service dependency. Scope: Medplum Self-Hosted: selected customer-operated edition. Source: https://www.medplum.com/docs/self-hosting/install-on-aws (reviewed 2026-11-19).

- License pricing: Documented. Medplum Community is Apache-2.0 and can be self-hosted without a software license fee; the Enterprise Self-Hosted support plan is separately commercial. Infrastructure, support and healthcare compliance work are separate. Scope: Medplum Self-Hosted: selected customer-operated edition. Source: https://www.medplum.com/open-source (reviewed 2026-11-19). Supporting source: Commercial support plans — https://www.medplum.com/pricing.

- Operating cost estimate: Sources checked — unresolved. No complete dated operating-cost estimate is established. Define provider and region, workload, availability, retention, storage growth, network transfer, support, software entitlement and operating labor before estimating total cost. Scope: Medplum Self-Hosted: selected customer-operated edition. Source: https://www.medplum.com/docs/self-hosting/install-on-aws (reviewed 2026-11-19).

- Release snapshot / cadence: Documented. The reviewed upstream v5.2.17 release was published 2026-11-11. Provider images and installer/component packages can differ; this snapshot does not promise a support window or future cadence. It includes authentication-response secret removal and on-behalf-of delegation hardening. Scope: Medplum Self-Hosted upstream application, independently versioned from provider packages. Source: https://github.com/medplum/medplum/releases/tag/v5.2.17 (reviewed 2026-11-19).




### Security and lifecycle reviews

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

- Medplum 5.2.17 authentication and delegation hardening (security-advisory): The v5.2.17 release strips ClientApplication secrets from auth/me responses and changes on-behalf-of identity and delegation handling. Scope: The authentication/me and delegation paths named in the v5.2.17 release; no universal affected-version range or CVE is asserted. Conditions: Applicability depends on the installed server build and use of the affected authentication/delegation endpoints. Action: Upgrade a compatible server/application bundle to v5.2.17 or later and test identity/delegation flows. Assess whether application secrets were exposed and rotate them where appropriate. Source: https://github.com/medplum/medplum/releases/tag/v5.2.17; reviewed 2026-11-19.




## Mendix on Kubernetes

Commercial low-code application runtime operated in customer Kubernetes infrastructure.

- Listing: https://launchinyourcloud.com/directory/mendix-private-cloud/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp, stackit
- Operating model: Customer-operated · vendor control plane
- Infrastructure IDs: servers
- License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
- Licensing model: commercial-only
- Installation: Helm / Kubernetes operator; Kubernetes manifests
- Architecture: Mendix Operator, application runtimes, database and file storage on the documented managed-Kubernetes providers.
- Operations: Customer operates the application runtime; the documented connected deployment also depends on the Mendix management portal and its configured access.
- Product website: https://docs.mendix.com/developerportal/deploy/private-cloud-supported-environments/
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The selected connected deployment registers the cluster with the external Mendix Portal control plane. A customer cluster is not a packaged insurance-claims application. Runtime licences, operator versions and application versions have different lifecycles; standalone modes need their own review.

Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.

Mendix Operator, application runtimes, database and file storage on the documented managed-Kubernetes providers. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- internal-tools: Commercial low-code application runtime operated in customer Kubernetes infrastructure.

- workflow-automation: Commercial low-code application runtime operated in customer Kubernetes infrastructure.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: vendor-hosted. Source: https://docs.mendix.com/developerportal/deploy/private-cloud-supported-environments/ (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: vendor-hosted. Source: https://docs.mendix.com/developerportal/deploy/private-cloud-supported-environments/ (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: vendor-hosted. Source: https://docs.mendix.com/developerportal/deploy/private-cloud-supported-environments/ (checked 2026-11-19). 

- stackit: Customer cloud account; Customer-operated; control plane: vendor-hosted. Source: https://docs.mendix.com/developerportal/deploy/private-cloud-supported-environments/ (checked 2026-11-19). 

Operating responsibility: In the selected Connected mode the customer supplies and operates the Kubernetes runtime, database, storage and backups. The Mendix Portal controls deployments through an in-cluster agent. This is not a vendor-operated application service. Source: https://docs.mendix.com/developerportal/deploy/private-cloud/ (checked 2026-11-20).


### Cloud deployment evidence

- Supported Clouds (aws, azure, gcp, stackit): https://docs.mendix.com/developerportal/deploy/private-cloud-supported-environments/
  Mendix Operator, application runtimes, database and file storage on the documented managed-Kubernetes providers. The selected connected deployment registers the cluster with the external Mendix Portal control plane. A customer cluster is not a packaged insurance-claims application. Runtime licences, operator versions and application versions have different lifecycles; standalone modes need their own review.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- Supported Clouds: https://docs.mendix.com/developerportal/deploy/private-cloud-supported-environments/

- Private Cloud Deploy: https://docs.mendix.com/developerportal/deploy/private-cloud-deploy/

- Insurance Claims: https://www.mendix.com/industries/insurance/

- Outside-Cloud Licensing: https://docs.mendix.com/developerportal/deploy/licensing-apps-outside-mxcloud/

- Mendix Legal: https://www.mendix.com/legal/

- Mendix on K8s RN: https://docs.mendix.com/releasenotes/developer-portal/mendix-for-private-cloud/

### Licensing sources

- https://docs.mendix.com/developerportal/deploy/licensing-apps-outside-mxcloud/

- https://www.mendix.com/legal/

### Infrastructure sources

- https://docs.mendix.com/developerportal/deploy/private-cloud-supported-environments/


### Buyer diligence


Research coverage: 4/12 fields (33%); 4 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. Mendix documents SAML and OIDC modules for end-users of deployed apps, with module/runtime compatibility and app-level configuration. The SAML guide explicitly addresses apps outside Mendix Cloud and requires external file storage. This is separate from developer-portal or Private Mendix Platform login. Scope: Application end-user federation on a compatible Mendix runtime; verify module dependencies and app configuration. Source: https://docs.mendix.com/appstore/modules/saml/ (reviewed 2026-11-20). Supporting source: OIDC module and supported runtime versions — https://docs.mendix.com/appstore/modules/oidc/.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The Kubernetes deployment guides register a cluster/namespace, install the Mendix Operator and deploy app environments from the Mendix Portal or Kubernetes custom resources. Database, file storage, registry, network access and licensed runtime configuration remain deployment inputs. Scope: Mendix on Kubernetes deployment workflow; operator, runtime and application releases are separate. Source: https://docs.mendix.com/developerportal/deploy/private-cloud-deploy/ (reviewed 2026-11-20). Supporting source: Cluster and operator setup — https://docs.mendix.com/developerportal/deploy/private-cloud-cluster/.

- Minimum footprint / sizing: Documented. The supported-provider guide requires at least 2 CPU cores, 2 GB memory and 3 GB ephemeral storage available on a node for one simple app, excluding Kubernetes core components. Production databases, file storage, image building and multiple replicas need additional sizing; experimental ARM64 support is limited to non-production Connected Mode. Scope: One simple app baseline, excluding cluster overhead and HA/1-TB workload capacity. Source: https://docs.mendix.com/developerportal/deploy/private-cloud-supported-environments/ (reviewed 2026-11-20).

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: Mendix on Kubernetes; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://docs.mendix.com/developerportal/deploy/licensing-apps-outside-mxcloud/ (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## n8n Self-Hosted

Automate integrations and business processes with a customer-hosted workflow editor and runtime.

- Listing: https://launchinyourcloud.com/directory/n8n/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, digitalocean, heroku, hetzner
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Sustainable Use License for covered code; separate commercial Enterprise license for enterprise components
- Licensing model: source-available
- Installation: Docker Compose with persistent data; database and worker topology selected for workload
- Architecture: Customer-operated workflow runtime, credentials store and persistent execution data
- Operations: Customer manages servers/containers, secrets, database, backup/restore, scaling and upgrades.
- Product website: https://n8n.io/
- Source review: 2026-11-19; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

This entry excludes n8n Cloud. The Sustainable Use License has use restrictions and should not be described as unrestricted open-source licensing. Enterprise components require the appropriate commercial license. External integrations, AI providers and optional assistant services require separate data-flow review. n8n@2.48.6 and the maintained n8n@1.123.99 line move official images to patched Node runtimes carrying a V8 process-abort fix. The 1.x image also moves to Node 24.22.3, while 2.x pins a patched Node 26.13.0. Update the selected line and verify custom images use the fixed runtime.

The core is under the Sustainable Use License with use restrictions, not an OSI open-source license. Enterprise-marked code requires a separate commercial Enterprise license. A free self-hosted option does not change the core license model.

Reviewed topology runs long-lived containers and persistent workflow/credential storage. Event triggers do not make the self-hosted control/runtime stack function-based serverless.


### Category fit

- workflow-automation: Visual integration/workflow automation with custom code and connectors; connected systems and AI providers may receive workflow data.

- ai-tools: Orchestrates AI providers, agents, tools and memory as workflows. Model inference and external service dependencies are configured separately.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-aws (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-azure (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-google-cloud-run (checked 2026-11-12). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-digital-ocean (checked 2026-11-12). 

- heroku: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-heroku (checked 2026-11-12). 

- hetzner: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-hetzner (checked 2026-11-12). 


### Cloud deployment evidence

- n8n deployment on AWS (aws): https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-aws
  Project instructions deploy n8n and PostgreSQL on customer-operated EKS. Review persistence, ingress and production scaling requirements.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- n8n deployment on Azure (azure): https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-azure
  Project instructions deploy n8n with PostgreSQL on Azure Kubernetes Service in the customer subscription.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- n8n deployment on Google Cloud Run (gcp): https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-google-cloud-run
  The project documents Cloud Run deployment. Its easy mode is not the production configuration; follow the durable-mode guidance for production and review execution and persistence constraints.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- n8n self-hosted deployment on DigitalOcean (digitalocean): https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-digital-ocean
  The project provides a provider-specific application deployment guide, including customer project/server creation, persistent application data and n8n configuration. DigitalOcean and Hetzner use customer-operated servers; Heroku uses a customer app and PostgreSQL service on platform-managed infrastructure. This is separate from n8n Cloud.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- n8n self-hosted deployment on Heroku (heroku): https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-heroku
  The project provides a provider-specific application deployment guide, including customer project/server creation, persistent application data and n8n configuration. DigitalOcean and Hetzner use customer-operated servers; Heroku uses a customer app and PostgreSQL service on platform-managed infrastructure. This is separate from n8n Cloud.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- n8n self-hosted deployment on Hetzner (hetzner): https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-hetzner
  The project provides a provider-specific application deployment guide, including customer project/server creation, persistent application data and n8n configuration. DigitalOcean and Hetzner use customer-operated servers; Heroku uses a customer app and PostgreSQL service on platform-managed infrastructure. This is separate from n8n Cloud.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Current self-hosted Docker Compose guide: https://docs.n8n.io/deploy/host-n8n/install-options/install-using-docker-compose

- Official license boundaries: https://github.com/n8n-io/n8n/blob/master/LICENSE.md

- Workflow automation project: https://github.com/n8n-io/n8n

- AI workflow components and integrations: https://docs.n8n.io/build/integrate-ai.md

- n8n self-hosted deployment on DigitalOcean: https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-digital-ocean

- n8n self-hosted deployment on Heroku: https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-heroku

- n8n self-hosted deployment on Hetzner: https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-hetzner

- n8n@2.48.6 release: https://github.com/n8n-io/n8n/releases/tag/n8n%402.48.6

- n8n@1.123.99 release: https://github.com/n8n-io/n8n/releases/tag/n8n%401.123.99

- Patched V8 runtime integration: https://github.com/n8n-io/n8n/pull/43703

### Licensing sources

- https://github.com/n8n-io/n8n/blob/master/LICENSE.md

### Infrastructure sources

- https://docs.n8n.io/deploy/host-n8n/install-options/install-using-docker-compose


### 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: Edition-dependent. SAML or OIDC SSO is documented for self-hosted Business and Enterprise. Instance-owner or administrator privileges are required to configure it. Scope: Self-hosted Business and Enterprise; not the unlicensed Community edition. Source: https://docs.n8n.io/deploy/host-n8n/configure-n8n/security/configure-sso.md (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 vendor documents Linux Compose installation and links n8n-hosting configurations for different architectures. Configure persistent data, database, encryption key, domain and TLS; choose the production topology rather than treating the minimal single-server recipe as HA. Scope: Official self-hosted Compose deployment. Source: https://docs.n8n.io/hosting/installation/server-setups/docker-compose/ (reviewed 2026-11-20). Deployment artifact: https://github.com/n8n-io/n8n-hosting. Artifact reference: Select and pin a compatible versioned application image.

- Minimum footprint / sizing: Sources checked — unresolved. The self-hosted memory guide ties RAM usage to execution concurrency, JSON/binary payload size and workflow behavior. It does not establish one safe server minimum. Size main processes, workers/task runners, PostgreSQL, queue-mode Redis, binary storage and HA after measuring representative workflows. Scope: Self-hosted workflow-dependent sizing; complete production footprint unresolved. Source: https://docs.n8n.io/hosting/scaling/memory-errors/ (reviewed 2026-11-20). Supporting source: Production topology and dependencies — https://docs.n8n.io/deploy/host-n8n/install-options/production-requirements.md.

- License pricing: Documented. The Sustainable Use License permits internal business or non-commercial/personal use under its conditions. Enterprise files are separately licensed, and other branches have specific restrictions. Commercial redistribution or embedded use must be checked against vendor terms; self-hosting does not grant every Enterprise feature. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/n8n-io/n8n/master/LICENSE.md (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. n8n n8n@2.48.6 was published November 19, 2026. Official 2.x images use a patched Node 26.13.0 runtime carrying a V8 process-abort fix. Maintained 1.x users should use n8n@1.123.99 or later, which moves to Node 24.22.3. Scope: Upstream n8n 2.x release; the 1.x maintenance line has a separate fixed build. Source: https://github.com/n8n-io/n8n/releases/tag/n8n%402.48.6 (reviewed 2026-11-19). Supporting source: Prior reviewed release context — https://github.com/n8n-io/n8n/releases/tag/n8n%402.47.7. Supporting source: Maintained 1.x runtime fix — https://github.com/n8n-io/n8n/releases/tag/n8n%401.123.99. Supporting source: Patched V8 runtime integration — https://github.com/n8n-io/n8n/pull/43703.







## Pega Platform Client-Managed

Commercial workflow and case-management platform installed in customer-managed Kubernetes infrastructure.

- Listing: https://launchinyourcloud.com/directory/pega-platform-client-managed/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
- Licensing model: commercial-only
- Installation: Helm / Kubernetes operator; Kubernetes manifests
- Architecture: Pega application Helm charts, supported database and runtime dependencies on EKS, AKS or GKE.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://docs.pega.com/bundle/platform/page/platform/deployment/client-managed-cloud/containerized-deployments-kubernetes.html
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

This listing covers the platform established by the deployment runbooks. It does not imply that a separately licensed Pega Government Platform package or municipal-permit application is installed. The chart's open-source licence does not license the Pega runtime.

Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.

Pega application Helm charts, supported database and runtime dependencies on EKS, AKS or GKE. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- workflow-automation: Commercial workflow and case-management platform installed in customer-managed Kubernetes infrastructure.

- case-management: Commercial workflow and case-management platform installed in customer-managed Kubernetes infrastructure.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://raw.githubusercontent.com/pegasystems/pega-helm-charts/master/docs/Deploying-Pega-on-EKS.md (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://raw.githubusercontent.com/pegasystems/pega-helm-charts/master/docs/Deploying-Pega-on-AKS.md (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://raw.githubusercontent.com/pegasystems/pega-helm-charts/master/docs/Deploying-Pega-on-GKE.md (checked 2026-11-19). 


### Cloud deployment evidence

- EKS Runbook (aws): https://raw.githubusercontent.com/pegasystems/pega-helm-charts/master/docs/Deploying-Pega-on-EKS.md
  Pega application Helm charts, supported database and runtime dependencies on EKS, AKS or GKE. This listing covers the platform established by the deployment runbooks. It does not imply that a separately licensed Pega Government Platform package or municipal-permit application is installed. The chart's open-source licence does not license the Pega runtime.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- AKS Runbook (azure): https://raw.githubusercontent.com/pegasystems/pega-helm-charts/master/docs/Deploying-Pega-on-AKS.md
  Pega application Helm charts, supported database and runtime dependencies on EKS, AKS or GKE. This listing covers the platform established by the deployment runbooks. It does not imply that a separately licensed Pega Government Platform package or municipal-permit application is installed. The chart's open-source licence does not license the Pega runtime.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- GKE Runbook (gcp): https://raw.githubusercontent.com/pegasystems/pega-helm-charts/master/docs/Deploying-Pega-on-GKE.md
  Pega application Helm charts, supported database and runtime dependencies on EKS, AKS or GKE. This listing covers the platform established by the deployment runbooks. It does not imply that a separately licensed Pega Government Platform package or municipal-permit application is installed. The chart's open-source licence does not license the Pega runtime.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- EKS Runbook: https://raw.githubusercontent.com/pegasystems/pega-helm-charts/master/docs/Deploying-Pega-on-EKS.md

- AKS Runbook: https://raw.githubusercontent.com/pegasystems/pega-helm-charts/master/docs/Deploying-Pega-on-AKS.md

- GKE Runbook: https://raw.githubusercontent.com/pegasystems/pega-helm-charts/master/docs/Deploying-Pega-on-GKE.md

- Pega Terms: https://www.pega.com/terms

- PGP Release Notes: https://docs.pega.com/bundle/pega-government-platform/page/pega-government-platform/releasenotes/constellation/cons-newfeatures.html

- Helm Releases: https://github.com/pegasystems/pega-helm-charts/releases

### Licensing sources

- https://www.pega.com/terms

### Infrastructure sources

- https://raw.githubusercontent.com/pegasystems/pega-helm-charts/master/docs/Deploying-Pega-on-EKS.md

- https://raw.githubusercontent.com/pegasystems/pega-helm-charts/master/docs/Deploying-Pega-on-AKS.md

- https://raw.githubusercontent.com/pegasystems/pega-helm-charts/master/docs/Deploying-Pega-on-GKE.md


### Buyer diligence


Research coverage: 4/12 fields (33%); 4 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. Pega Platform documents SAML 2.0 and OIDC authentication services for user SSO. A security administrator creates the service and configures identity/claim mapping and any operator provisioning; token credentials for API integrations are a separate authentication type. Scope: Pega Platform application user federation; confirm the chosen client-managed release and identity-service configuration. Source: https://docs.pega.com/bundle/platform/page/platform/security/create-authentication-service.html (reviewed 2026-11-20). Supporting source: Public documentation API with article body — https://docs-be.pega.com/api/bundle/platform/page/platform/security/create-authentication-service.html.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Pega publishes Helm charts and EKS/AKS/GKE runbooks for client-managed Kubernetes. The EKS guide requires separately obtained Pega images, registry access and a supported database. Match chart, application, search and database versions; chart source access does not grant platform software rights. Scope: Client-managed licensed platform deployment; no ECS support inferred from generic container capability. Source: https://github.com/pegasystems/pega-helm-charts/blob/master/docs/Deploying-Pega-on-EKS.md (reviewed 2026-11-20). Deployment artifact: https://github.com/pegasystems/pega-helm-charts/tree/master/charts/pega. Artifact reference: master (moving branch); select a chart compatible with the licensed Pega release.

- Minimum footprint / sizing: Documented. The reviewed upstream chart gives the web-user tier a per-pod request of 3 CPU and 12 GiB memory, with limits of 4 CPU and 12 GiB. These are configurable chart defaults; background/search tiers, database, autoscaling, replica counts and cluster overhead are additional. Scope: Moving chart web-tier defaults, not a vendor-certified minimum or a complete 100-user/1-TB HA sizing. Source: https://github.com/pegasystems/pega-helm-charts/blob/master/charts/pega/values.yaml (reviewed 2026-11-20).

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: Pega Platform Client-Managed; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://www.pega.com/terms (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Red Hat Ansible Automation Platform Self-Managed

Enterprise IT automation platform installed and managed by the customer in a public-cloud environment.

- Listing: https://launchinyourcloud.com/directory/ansible-automation-platform-self-managed/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Red Hat Ansible Automation Platform subscription required.
- Licensing model: commercial-only
- Installation: Containerized installer on RHEL with Podman or the OpenShift Operator
- Architecture: Customer-operated automation controller, execution and platform services on RHEL or OpenShift.
- Operations: Customer manages the platform, execution capacity, infrastructure, secrets, backups and upgrades; Red Hat supplies subscribed software updates and support.
- Product website: https://www.redhat.com/en/technologies/management/ansible
- Source review: 2026-11-17; cloud review: 2026-11-17; licensing review: 2026-11-17; infrastructure review: 2026-11-17

### Scope and qualifications

This entry covers Red Hat Ansible Automation Platform, not the managed cloud service and not upstream Ansible Core or AWX. Current 2.7 deployment models use the containerized RHEL installer or OpenShift Operator; the RPM installer was removed in 2.7. Validate supported RHEL or OpenShift versions, execution environments and subscription manifests before installation.

The selected Red Hat Ansible Automation Platform requires a commercial subscription and valid manifest. Upstream Ansible Core and AWX do not change this enterprise product's license classification.

Self-managed Ansible Automation Platform uses persistent RHEL containers or customer-operated OpenShift workloads with databases and execution capacity.


### Category fit

- devops: Enterprise configuration, provisioning and operations automation across infrastructure and applications.

- workflow-automation: Controller, event-driven automation and reusable automation content coordinate governed operational workflows.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.redhat.com/en/learn/learning-paths/getting-started-red-hat-ansible-automation-platform/installation-and-key-functionalities (checked 2026-11-17). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.redhat.com/en/learn/learning-paths/getting-started-red-hat-ansible-automation-platform/installation-and-key-functionalities (checked 2026-11-17). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.redhat.com/en/learn/learning-paths/getting-started-red-hat-ansible-automation-platform/installation-and-key-functionalities (checked 2026-11-17). 


### Cloud deployment evidence

- Self-managed Ansible Automation Platform in named public clouds (aws, azure, gcp): https://docs.redhat.com/en/learn/learning-paths/getting-started-red-hat-ansible-automation-platform/installation-and-key-functionalities
  Red Hat documents self-managed Ansible Automation Platform deployments on infrastructure hosted in AWS, Azure and Google Cloud. The customer operates the RHEL or OpenShift environment and supplies the subscription.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- Named-cloud and self-managed installation overview: https://docs.redhat.com/en/learn/learning-paths/getting-started-red-hat-ansible-automation-platform/installation-and-key-functionalities

- Current 2.7 deployment models: https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/plan-ref_installation_deployment_models

- Set up the Ansible Automation Platform subscription: https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/install-set_up_your_subscription

### Licensing sources

- https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/install-set_up_your_subscription

### Infrastructure sources

- https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/plan-ref_installation_deployment_models


### Buyer diligence


Research coverage: 12/12 fields (100%); 7 documented, 5 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. AWS lists Red Hat subscriptions including AAP, alongside a different managed AAP service. Confirm an offer/order explicitly entitling this self-managed 2.7 installation. Scope: Reviewed public evidence for Red Hat Ansible Automation Platform Self-Managed; unresolved within this edition/deployment. Source: https://aws.amazon.com/marketplace/pp/prodview-4hz3uo55uaemk (reviewed 2026-11-17).

- Cloud commitment eligibility: Sources checked — unresolved. Managed AAP Marketplace committed-spend claims do not establish treatment of this self-managed subscription. Obtain the selected offer and buyer-agreement eligibility. Scope: Reviewed public evidence for Red Hat Ansible Automation Platform Self-Managed; unresolved within this edition/deployment. Source: https://aws.amazon.com/marketplace/pp/prodview-4hz3uo55uaemk (reviewed 2026-11-17).

- Single sign-on: Documented. AAP 2.7 documents SAML identity-provider configuration through platform gateway. External authentication must use the gateway; legacy direct component authentication is no longer supported. Scope: Self-managed AAP 2.7 platform gateway. Source: https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/secure-proc_controller_set_up_saml (reviewed 2026-11-17). Supporting source: Mandatory gateway authentication — https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/secure-mandatory_platform_gateway_authentication_in_ansible_automation_platform_2_7.

- SCIM provisioning: Sources checked — unresolved. Platform gateway documents SAML/LDAP/OIDC and group/role mapping, but a supported AAP 2.7 SCIM lifecycle endpoint was not established. Scope: Reviewed public evidence for Red Hat Ansible Automation Platform Self-Managed; unresolved within this edition/deployment. Source: https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/secure-proc_controller_set_up_saml (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. The reviewed Red Hat Ansible Automation Platform Self-Managed 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://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/install-configure_your_ansible_automation_platform_deployment (reviewed 2026-11-17).

- Security controls: Documented. AAP 2.7 centralizes external authentication at platform gateway and documents HTTPS redirects and CSRF settings. Restrict component access and configure the chosen identity provider and role mappings. Scope: AAP 2.7 gateway and deployment configuration. Source: https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/install-configure_your_ansible_automation_platform_deployment (reviewed 2026-11-17).

- Air-gapped operation: Documented. The containerized installer supports disconnected installation using a downloaded setup bundle, local RHEL RPM repositories and bundle_install=true. Required metrics service works without internet access; content and update transfers remain operator responsibilities. Scope: AAP 2.7 containerized disconnected installation. Source: https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/install-assembly_aap_containerized_disconnected_installation (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. The subscription-gated containerized setup bundle uses a configured inventory to install platform components with Podman; OpenShift uses the supported Operator path. AAP 2.7 does not use the removed RPM installer. Scope: AAP 2.7 installation methods; not AWX or Ansible Core. Source: https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/install-con_choosing_installation_type (reviewed 2026-11-17).

- Minimum footprint / sizing: Documented. The containerized system requirements distinguish the supported RHEL host, subscriptions, database and component resources. Use the deployment-model inventory and execution capacity to size each host; portal-only appliance requirements do not size the complete platform. Scope: AAP 2.7 containerized topology, not portal-only sizing. Source: https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/install-ref_cont_aap_system_requirements (reviewed 2026-11-17).

- License pricing: Documented. The selected Red Hat Ansible Automation Platform requires a commercial subscription and valid manifest. Upstream Ansible Core and AWX do not change this enterprise product's license classification. Scope: Red Hat Ansible Automation Platform Self-Managed: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/install-set_up_your_subscription (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. Choose the supported HA inventory and count managed nodes, execution jobs, execution environments, controller/hub/database hosts and RHEL/AAP subscriptions. Human users and data size alone do not size automation capacity. A complete monthly operating estimate is not established. Scope: Requested planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA, average usage; missing workload metrics and commercial terms are explicit. Source: https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/install-ref_cont_aap_system_requirements (reviewed 2026-11-17).

- Release snapshot / cadence: Documented. The reviewed self-managed documentation is the AAP 2.7 line, with separate patch-release notes and component updates. Select a supported patch and matching bundle; this is a version-line review, not a claim about a latest patch timestamp. Scope: Self-managed AAP documentation line and patch index. Source: https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/ (reviewed 2026-11-17).







## Retool Self-Hosted, Self-Managed

Commercial single-tenant Retool deployment installed and operated on customer-managed Kubernetes infrastructure.

- Listing: https://launchinyourcloud.com/directory/retool-self-hosted/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Enterprise subscription with custom annual pricing and a self-hosted license key.
- Licensing model: commercial-only
- Installation: Official Terraform blueprints for Amazon EKS, Azure AKS or Google GKE, or Helm into an existing supported Kubernetes cluster
- Architecture: Distributed Retool containers on Kubernetes with external PostgreSQL, object storage, ingress and optional Temporal services
- Operations: Customer manages Kubernetes, PostgreSQL, object storage, DNS, TLS, secrets, networking, backups, capacity, upgrades and the Retool license.
- Product website: https://retool.com/self-hosted
- Source review: 2026-11-16; cloud review: 2026-11-16; licensing review: 2026-11-16; infrastructure review: 2026-11-16

### Scope and qualifications

This entry covers self-hosted, self-managed Retool, not Retool-managed hosting. Kubernetes with Helm is the supported production path for Retool 4.0 and later; Docker Compose is non-production only. EKS must use EC2-backed workers rather than Fargate for the agent sandbox. The standard deployment requires outbound access for license checks, authentication and usage reporting; Enterprise pricing separately offers air-gapped deployment, requiring the appropriate license and vendor-provided procedure. Workflows and Agents require Temporal, and Retool recommends its managed Temporal Cloud service unless the customer operates a compatible cluster.

Current pricing places self-hosted and air-gapped deployments in Enterprise with custom annual pricing. Product-specific subscription and license-key terms apply; cloud per-seat prices do not price this deployment.

Production deployments run persistent Retool services on customer EKS, AKS or GKE infrastructure with external database and object-storage dependencies.


### Category fit

- internal-tools: Provides a self-hosted low-code platform for building internal applications and operational interfaces.

- workflow-automation: Runs Retool Workflows and related automation services inside the customer-operated deployment.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.retool.com/self-hosted/self-managed/tutorials/kubernetes (checked 2026-11-16). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.retool.com/self-hosted/self-managed/tutorials/kubernetes (checked 2026-11-16). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.retool.com/self-hosted/self-managed/tutorials/kubernetes (checked 2026-11-16). 


### Cloud deployment evidence

- Official Retool Terraform and Helm deployment paths (aws, azure, gcp): https://docs.retool.com/self-hosted/self-managed/tutorials/kubernetes
  Retool provides production Terraform blueprints for AWS, Azure and Google Cloud and explicitly targets Amazon EKS, Azure AKS and Google GKE. Customers may alternatively deploy with Helm into an existing supported cluster.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed.


### Sources

- Self-hosted, self-managed Retool: https://docs.retool.com/self-hosted/self-managed

- Self-managed Retool quickstart: https://docs.retool.com/self-hosted/self-managed/quickstart

- Retool Kubernetes deployment tutorials: https://docs.retool.com/self-hosted/self-managed/tutorials/kubernetes

- Deploy Retool on Kubernetes with Helm: https://docs.retool.com/self-hosted/self-managed/tutorials/kubernetes/kubernetes-helm

- Retool product-specific terms: https://docs.retool.com/legal/product-specific-terms

- Enterprise deployment options and pricing: https://retool.com/pricing

### Licensing sources

- https://docs.retool.com/legal/product-specific-terms

- https://retool.com/pricing

### Infrastructure sources

- https://docs.retool.com/self-hosted/self-managed/quickstart

- https://docs.retool.com/self-hosted/self-managed/tutorials/kubernetes/kubernetes-helm


### Buyer diligence


Research coverage: 11/12 fields (92%); 10 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: Edition-dependent. Retool’s AWS Marketplace listing explicitly describes self-hosted and Retool-managed AWS environments, with private-contract procurement. AWS classifies delivery as a SaaS contract; confirm the self-managed Enterprise entitlement rather than assuming an AMI installer or included infrastructure. Retool also announces Google Cloud private-offer purchasing with the same deployment options; the exact offer and agreement must match the self-hosted subscription. Scope: Vendor-published AWS offer; procurement and application hosting are distinct. Source: https://aws.amazon.com/marketplace/pp/prodview-cqgbgmrm63i4y (reviewed 2026-11-16). Supporting source: Google Cloud Marketplace procurement and commitment conditions — https://retool.com/blog/retool-google-cloud-marketplace-announcement. Offer prodview-cqgbgmrm63i4y: Retool; SaaS contract/private offer; select self-managed Enterprise entitlement; https://aws.amazon.com/marketplace/pp/prodview-cqgbgmrm63i4y.

- Cloud commitment eligibility: Edition-dependent. Retool states that eligible Google Cloud Marketplace purchases can draw down a Google Cloud commitment and that Marketplace procurement preserves deployment options. Purchases use a private offer; the amount credited depends on the buyer’s Google agreement and accepted offer. This is not a blanket credit promise for all purchases or providers. Scope: Google Cloud private-offer procurement; buyer agreement controls eligibility. Source: https://retool.com/blog/retool-google-cloud-marketplace-announcement (reviewed 2026-11-16).

- Single sign-on: Edition-dependent. Retool documents SAML and OIDC providers, including Entra ID and Okta, plus identity-provider group/role mapping. Apply the self-hosted instance configuration and subscription entitlements; Google Group sync is a separate integration. Scope: Retool organization SSO; protocol support does not establish every plan entitlement; current pricing includes this capability in Enterprise. Source: https://docs.retool.com/sso/quickstart (reviewed 2026-11-16). Supporting source: Enterprise entitlement matrix — https://retool.com/pricing.

- SCIM provisioning: Edition-dependent. SCIM provisioning is documented for self-hosted versions 2.32.1+, with bearer-token authentication and /api/scim/v2/* endpoints. The guide covers Okta and Entra ID; the identity provider must reach the instance through its firewall. Scope: Self-hosted technical configuration; selected subscription governs commercial entitlement; current pricing includes this capability in Enterprise. Source: https://docs.retool.com/sso/guides/scim-user-provisioning (reviewed 2026-11-16). Supporting source: Enterprise entitlement matrix — https://retool.com/pricing.

- Compliance attestations: Sources checked — unresolved. Retool’s legal security practices describe independent SOC 2/ISO audits and direct readers to its Trust Center. Those public practices alone do not establish report dates or coverage of the customer-operated self-managed environment. Scope: Vendor controls and audit availability; customer-environment scope/period needs the actual report. Source: https://docs.retool.com/legal/security (reviewed 2026-11-16).

- Security controls: Documented. The code-executor uses nsjail, which needs privileged container access. The documented fallback runs code without sandboxing if that access is unavailable. Review this specific container’s isolation separately from agent and JavaScript executors. Scope: Self-managed code-executor container; not an attestation for every Retool service. Source: https://docs.retool.com/self-hosted/self-managed/quickstart (reviewed 2026-11-16).

- Air-gapped operation: Edition-dependent. Retool’s current Enterprise pricing explicitly offers air-gapped deployments. The standard self-managed guide still requires outbound license/authentication/usage services, so obtain the separate air-gap license, artifacts and procedure from Retool rather than applying the standard online setup unchanged. Scope: Enterprise commercial air-gap option is confirmed; deployment-specific procedure and integration dependencies require account-team coordination. Source: https://retool.com/pricing (reviewed 2026-11-16). Supporting source: Standard deployment outbound requirements — https://docs.retool.com/self-hosted/self-managed/quickstart.

- Deployment artifact / IaC: Documented. Retool provides Terraform blueprints that provision EKS, AKS or GKE and deploy Helm. Kubernetes with Helm is the production path for 4.0 and later; Compose is for development and proofs of concept. AWS agent sandboxes require EC2-backed EKS workers rather than Fargate. Scope: Self-managed Retool 4.0+; select matching chart and application versions. Source: https://docs.retool.com/self-hosted/self-managed/quickstart (reviewed 2026-11-16). Deployment artifact: https://github.com/tryretool/terraform-retool-self-hosted-blueprints/tree/main. Artifact reference: main (moving branch).

- Minimum footprint / sizing: Documented. The current Helm guide calls for at least 32 CPU cores and 64 GiB available across the workload-node pool. Agent sandbox pods scale with builder sessions; the external PostgreSQL database, storage and peak autoscaling capacity must also be planned. Scope: Current production Helm stack with app-builder/agent services; not the older Compose baseline. Source: https://docs.retool.com/self-hosted/self-managed/tutorials/kubernetes/kubernetes-helm (reviewed 2026-11-16).

- License pricing: Documented. Current pricing places self-hosted and air-gapped deployment in Enterprise, with custom annual pricing. Its published cloud per-seat prices do not price a self-hosted Enterprise installation. The subscription and license-key terms govern use. Scope: Self-hosted Enterprise procurement; excludes cloud infrastructure and operating labor. Source: https://retool.com/pricing (reviewed 2026-11-16). Supporting source: Self-hosted legal terms — https://docs.retool.com/legal/product-specific-terms.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The reviewed vendor release is 4.86.0, published 2026-11-11. This is a dated, scoped snapshot; it does not establish compatibility with another chart, cloud package or commercial edition. Retool documents quarterly stable releases and six months of support for each stable version. Scope: Self-hosted stable-channel release, separate from cloud/edge versions; source supplies a publication day, not a timestamp. Source: https://docs.retool.com/releases/stable/version/4.86 (reviewed 2026-11-16).







## Spacelift Self-Hosted

Commercial infrastructure-as-code automation platform deployed to customer AWS, Azure or Google Cloud infrastructure.

- Listing: https://launchinyourcloud.com/directory/spacelift-self-hosted/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Spacelift Self-Hosted Enterprise subscription and license token required.
- Licensing model: commercial-only
- Installation: Official Terraform/OpenTofu reference architectures and Helm charts for EKS/ECS, AKS or GKE
- Architecture: Customer-operated Spacelift backend, gateway, workers and data services on cloud compute or Kubernetes.
- Operations: Customer manages compute or Kubernetes, database and object storage, networking, secrets, workers, backups, scaling, upgrades and licensing.
- Product website: https://spacelift.io/
- Source review: 2026-11-18; cloud review: 2026-11-18; licensing review: 2026-11-18; infrastructure review: 2026-11-18

### Scope and qualifications

This entry covers Spacelift Self-Hosted, not the Spacelift SaaS service. New features can reach SaaS before self-hosted releases; match the deployment artifacts and architecture to the licensed version.

Self-hosting is a commercial Enterprise capability governed by Spacelift subscription and license terms.

Spacelift Self-Hosted runs persistent backend and worker services with database and object-storage dependencies.


### Category fit

- devops: Provides self-hosted infrastructure-as-code runs, policy, state, integrations and private workers.

- workflow-automation: Orchestrates governed infrastructure workflows, approvals and automated runs.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.spacelift.io/self-hosted (checked 2026-11-18). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.spacelift.io/self-hosted (checked 2026-11-18). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.spacelift.io/self-hosted (checked 2026-11-18). 


### Cloud deployment evidence

- Spacelift in customer AWS, Azure or GCP infrastructure (aws, azure, gcp): https://docs.spacelift.io/self-hosted
  Spacelift explicitly documents a customer-maintained self-hosted product for AWS, Azure and GCP and links provider-specific reference architectures.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.


### Sources

- Spacelift Self-Hosted: https://docs.spacelift.io/self-hosted

- Deploy Spacelift to EKS: https://docs.spacelift.io/self-hosted/latest/installing-spacelift/reference-architecture/guides/deploying-to-eks

- Deploy Spacelift to AKS: https://docs.spacelift.io/self-hosted/latest/installing-spacelift/reference-architecture/guides/deploying-to-aks

- Deploy Spacelift to GKE: https://docs.spacelift.io/self-hosted/latest/installing-spacelift/reference-architecture/guides/deploying-to-gke

- Spacelift pricing: https://spacelift.io/pricing

### Licensing sources

- https://docs.spacelift.io/self-hosted/latest/legal/terms

- https://spacelift.io/pricing

### Infrastructure sources

- https://docs.spacelift.io/self-hosted


### Buyer diligence


Research coverage: 12/12 fields (100%); 8 documented, 4 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. Spacelift documents public AWS contracts and a sales-assisted private-offer route. Its pricing FAQ says plans are available through AWS, but the reviewed public offer/registration describes SaaS. A private worker is not a self-hosted backend. Obtain an order/private offer that explicitly entitles Enterprise Self-Hosted, its package and support scope before applying Marketplace availability to this listing. Scope: Spacelift Self-Hosted: selected customer-operated edition. Source: https://docs.spacelift.io/product/billing/aws-marketplace (reviewed 2026-11-18). Supporting source: Plan, Self-Hosted and Marketplace FAQ statements — https://spacelift.io/pricing. Supporting source: Backend versus SaaS/private-worker boundary — https://docs.spacelift.io/self-hosted.

- Cloud commitment eligibility: Sources checked — unresolved. Spacelift’s pricing FAQ says it qualifies as a SaaS partner for AWS PPA commitments. That statement does not identify a Self-Hosted private-offer entitlement or its eligible billed dimensions. Confirm the selected Enterprise Self-Hosted order and buyer agreement; private-worker SaaS procurement is a separate boundary. Scope: Spacelift Self-Hosted: selected customer-operated edition. Source: https://spacelift.io/pricing (reviewed 2026-11-18). Supporting source: AWS commitment qualification is product/agreement-specific — https://docs.aws.amazon.com/marketplace/latest/buyerguide/multi-product-solutions-buyer-faq.html. Supporting source: Public versus sales-assisted private procurement — https://docs.spacelift.io/product/billing/aws-marketplace.

- Single sign-on: Documented. The self-hosted documentation supports SAML 2.0 or OIDC SSO and describes the transition from managed-IdP bootstrap to SSO administration. Login policies are not evaluated for the bootstrap/SSO admin, so protect and govern those accounts explicitly. Scope: Spacelift Self-Hosted: selected customer-operated edition. Source: https://docs.spacelift.io/self-hosted/latest/integrations/single-sign-on/ (reviewed 2026-11-18).

- SCIM provisioning: Documented. The self-hosted SCIM 2.0 integration provisions users/groups with OAuth client credentials and requires configured SSO. Provisioning does not grant roles by itself; the corresponding group claims must also be sent during login. The self-hosted change log confirms availability from v6.1.0. Scope: Spacelift Self-Hosted: selected customer-operated edition. Source: https://docs.spacelift.io/self-hosted/latest/integrations/single-sign-on/scim (reviewed 2026-11-18). Supporting source: Self-hosted v6.1.0 release boundary — https://docs.spacelift.io/self-hosted/latest/installing-spacelift/changelog.

- Compliance attestations: Sources checked — unresolved. Spacelift’s Trust Center says it uses ISO 27001 internally but is not ISO 27001 certified, and instead maintains SOC 2 Type II assurance. The self-hosted security guide also claims SOC 2. Obtain the current report period, system boundary and customer controls before applying that claim to a customer-operated backend; a SaaS/private-worker assessment alone would not settle this boundary. Scope: Spacelift Self-Hosted: selected customer-operated edition. Source: https://trust.spacelift.io/faq (reviewed 2026-11-18). Supporting source: Self-hosted security statement and customer patch responsibilities — https://docs.spacelift.io/self-hosted/latest/product/security.

- Security controls: Documented. Spacelift documents security boundaries for code/state/secrets and integrations. Self-hosting adds customer-managed encryption keys, backend database/object storage and private workers. SSO/SCIM configuration and worker permissions remain distinct from cloud-target authorization. Scope: Spacelift Self-Hosted: selected customer-operated edition. Source: https://docs.spacelift.io/self-hosted/latest/product/security (reviewed 2026-11-18). Supporting source: Customer backend dependencies — https://docs.spacelift.io/self-hosted/latest/installing-spacelift/reference-architecture/environment-requirements. Supporting source: SSO administrator behavior — https://docs.spacelift.io/self-hosted/latest/integrations/single-sign-on/.

- Air-gapped operation: Documented. The vendor documents isolated deployment, local VCS, cached IaC providers/CLI binaries, custom runner images and manual usage/licence handling. EC2 launchers require customer-staged artifacts. Repeat this preparation for upgrades and ensure IdP/cloud targets are reachable within the selected boundary. Scope: Spacelift Self-Hosted: selected customer-operated edition. Source: https://docs.spacelift.io/self-hosted/latest/installing-spacelift/reference-architecture/guides/air-gapped (reviewed 2026-11-18).

- Deployment artifact / IaC: Documented. The self-hosted Helm chart is versioned v7.2.0 and now tracks the application release. Provider-specific Terraform/OpenTofu modules provision backing infrastructure separately. Pin chart, images, modules and worker artifacts as a compatible set; do not confuse old 0.x chart versions with application versions. Scope: Spacelift Self-Hosted: selected customer-operated edition. Source: https://github.com/spacelift-io/spacelift-self-hosted-helm-chart/releases/tag/v7.2.0 (reviewed 2026-11-18). Deployment artifact: https://github.com/spacelift-io/spacelift-self-hosted-helm-chart/releases/tag/v7.2.0. Artifact reference: Spacelift self-hosted Helm chart v7.2.0. Supporting source: EKS reference deployment — https://docs.spacelift.io/self-hosted/latest/installing-spacelift/reference-architecture/guides/deploying-to-eks.

- Minimum footprint / sizing: Documented. The reference architecture requires PostgreSQL 14+, object storage, container orchestration, encryption keys and separate application/worker connectivity. This establishes component dependencies, not a fixed CPU/RAM minimum. Concurrent runs and worker jobs drive capacity independently of user count. Scope: Spacelift Self-Hosted: selected customer-operated edition. Source: https://docs.spacelift.io/self-hosted/latest/installing-spacelift/reference-architecture/environment-requirements (reviewed 2026-11-18).

- License pricing: Documented. Self-Hosted is a commercial Enterprise purchase requiring a quote and licence. Public SaaS plan/worker prices do not price this deployment. Confirm backend, private workers, feature entitlement, usage reporting and renewal terms. Scope: Spacelift Self-Hosted: selected customer-operated edition. Source: https://spacelift.io/pricing (reviewed 2026-11-18). Supporting source: Isolated deployment licence/usage handling — https://docs.spacelift.io/self-hosted/latest/installing-spacelift/reference-architecture/guides/air-gapped.

- Operating cost estimate: Sources checked — unresolved. Specify parallel runs, worker instance sizes and run duration, state/artifact/log retention, HA backend/DB, optional messaging transport, source-control/IdP dependencies and Enterprise pricing. One hundred users do not determine worker concurrency or the cloud resources those jobs manage. Scope: Planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA; average usage without measured concurrency or throughput. Source: https://docs.spacelift.io/self-hosted/latest/installing-spacelift/reference-architecture/environment-requirements (reviewed 2026-11-18). Supporting source: Current AWS Linux EC2 rates; workload/topology still required — 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. Supporting source: Storage performance and charging inputs — https://aws.amazon.com/ebs/pricing/.

- Release snapshot / cadence: Documented. Spacelift self-hosted chart v7.2.0 was published November 11, 2026 and aligns with the application release. Review the self-hosted changelog and upgrade path. The DinD worker chart reaches EOL February 1, 2027; v7 is also the last major with CloudFormation installation support. Scope: Spacelift Self-Hosted: selected customer-operated edition. Source: https://github.com/spacelift-io/spacelift-self-hosted-helm-chart/releases/tag/v7.2.0 (reviewed 2026-11-18). Supporting source: Self-hosted changes and deprecations — https://docs.spacelift.io/self-hosted/latest/installing-spacelift/changelog.




### Security and lifecycle reviews

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

- Spacelift DinD worker Helm chart support ends February 2027 (lifecycle): The Docker-in-Docker worker chart reaches end of life February 1, 2027. Existing charts remain available/runnable, but receive no new versions, fixes or support. Scope: DinD worker Helm chart only; Docker workers on EC2 and the main self-hosted service are not retired by this notice. Conditions: Only installations using the DinD chart require this worker migration. CloudFormation has a separate version-based boundary: v7 is its last supported major. Action: Migrate DinD pools to operator-managed Kubernetes workers. Separately move CloudFormation installations to Terraform/OpenTofu while on v7 before considering v8. Source: https://docs.spacelift.io/self-hosted/latest/installing-spacelift/changelog; reviewed 2026-11-18.

- Spacelift self-hosted component CA trust update (security-advisory): The v7.1.0 changelog updates shipped Go components/images to reject compromised eMudhra intermediate certificate chains and names CVE-2026-111943. Scope: Self-hosted components, launchers/workers and shipped Docker images covered by the vendor’s v7.1.0 security entry; IaC binaries used by stacks are separate. Conditions: TLS trust depends on component/binary version and connection path. The vendor also identifies fixed OpenTofu versions; updating the backend alone does not replace every stack binary. Action: Use a self-hosted release containing the fix, refresh affected worker/launcher images and upgrade stack OpenTofu versions according to the changelog. Source: https://docs.spacelift.io/self-hosted/latest/installing-spacelift/changelog; reviewed 2026-11-18.




## SuperPlane Enterprise Self-Hosted

Enterprise software-factory and agent-workflow platform installed with Terraform and Helm in a customer cloud account.

- Listing: https://launchinyourcloud.com/directory/superplane-self-hosted/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial SuperPlane Enterprise license required for the documented Kubernetes deployment.
- Licensing model: commercial-only
- Installation: Vendor Terraform modules provision EKS, AKS or GKE, managed data services and the SuperPlane Helm release
- Architecture: Customer-operated Kubernetes cluster, managed PostgreSQL and object storage, Fleet Manager and runner virtual machines.
- Operations: Customer manages the cloud account, cluster, database, object storage, runner images and VMs, DNS, TLS, backups, upgrades and connected model or tool credentials.
- Product website: https://superplane.com/
- Source review: 2026-11-17; cloud review: 2026-11-17; licensing review: 2026-11-17; infrastructure review: 2026-11-17

### Scope and qualifications

This entry scopes only the Enterprise Kubernetes deployment on AWS, Azure and Google Cloud. The Apache-2.0 community engine and single-VM Compose installation are separate. Google Cloud public runner images are not yet published and must be built with Packer. Connected source-control, model and workflow services can move code or data outside the cluster according to their own configuration and terms.

The documented AWS, Azure and Google Cloud Kubernetes installation requires a SuperPlane Enterprise license. The Apache-2.0 community engine and single-VM deployment do not grant Enterprise feature or support entitlements.

Terraform provisions persistent Kubernetes application services, managed PostgreSQL and object storage, while Fleet Manager creates runner virtual machines.


### Category fit

- devops: Coordinates coding agents, source control, CI, review and verified software-delivery work.

- workflow-automation: Defines durable automation lines, approvals, checks and repair loops for recurring engineering work.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.superplane.com/self-hosting/overview/ (checked 2026-11-17). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.superplane.com/self-hosting/overview/ (checked 2026-11-17). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.superplane.com/self-hosting/overview/ (checked 2026-11-17). 


### Cloud deployment evidence

- SuperPlane Enterprise on EKS, AKS and GKE (aws, azure, gcp): https://docs.superplane.com/self-hosting/overview/
  SuperPlane documents Terraform-created EKS, AKS and GKE clusters with managed PostgreSQL, object storage and Helm releases in the customer's account. Enterprise licensing is required; Google Cloud runner images must currently be built by the operator with Packer.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- Self-hosted editions and provider architectures: https://docs.superplane.com/self-hosting/overview/

- Provider-specific Enterprise installation: https://docs.superplane.com/self-hosting/install/

- SuperPlane pricing and Enterprise self-hosting: https://superplane.com/pricing/

- Upstream Apache-2.0 project: https://github.com/superplanehq/superplane

### Licensing sources

- https://docs.superplane.com/self-hosting/overview/

- https://superplane.com/pricing/

### Infrastructure sources

- https://docs.superplane.com/self-hosting/overview/

- https://docs.superplane.com/self-hosting/install/


### Buyer diligence


Research coverage: 12/12 fields (100%); 5 documented, 7 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. Enterprise installation and direct commercial terms are documented; a current cloud Marketplace offer for this Kubernetes edition was not established. Scope: Reviewed public evidence for SuperPlane Enterprise Self-Hosted; unresolved within this edition/deployment. Source: https://docs.superplane.com/self-hosting/overview/ (reviewed 2026-11-17).

- Cloud commitment eligibility: Sources checked — unresolved. Enterprise custom terms do not establish an eligible Marketplace offer, qualifying fees or cloud-commitment treatment. Scope: Reviewed public evidence for SuperPlane Enterprise Self-Hosted; unresolved within this edition/deployment. Source: https://docs.superplane.com/self-hosting/overview/ (reviewed 2026-11-17).

- Single sign-on: Edition-dependent. The plan comparison includes SSO in Enterprise together with Enterprise self-hosting. Confirm the required IdP protocol and configuration with the vendor; these entitlements do not apply to the separate community VM edition. Scope: Enterprise self-hosting plan. Source: https://superplane.com/pricing/ (reviewed 2026-11-17).

- SCIM provisioning: Sources checked — unresolved. Enterprise includes automated user provisioning, but the pricing table does not name SCIM or document its endpoint, operations and identity-provider limitations. Scope: Enterprise automated provisioning; protocol not established. Source: https://superplane.com/pricing/ (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. The reviewed SuperPlane Enterprise Self-Hosted 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://docs.superplane.com/self-hosting/install/ (reviewed 2026-11-17).

- Security controls: Documented. The provider installation separates infrastructure provisioning, application secrets and runner management. Protect Terraform state, generated credentials and license material; configure TLS/DNS and restrict the provider permissions used by the installer. Scope: Enterprise Kubernetes provider installation. Source: https://docs.superplane.com/self-hosting/install/ (reviewed 2026-11-17).

- Air-gapped operation: Sources checked — unresolved. The standard installer downloads charts, images and provider tooling and configures public DNS/certificates. A supported offline licensing, dependency-transfer and upgrade workflow was not established in this guide. Scope: Enterprise installation; no inference from running in a private VPC. Source: https://docs.superplane.com/self-hosting/install/ (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. Provider-specific Terraform creates the managed Kubernetes, PostgreSQL and storage dependencies; Helm installs the application and Fleet Manager controls runners. GCP requires building runner images with Packer rather than using the published AWS/Azure images. Scope: Enterprise installer and provider dependencies; community VM is a different path. Source: https://docs.superplane.com/self-hosting/install/ (reviewed 2026-11-17).

- Minimum footprint / sizing: Documented. The Enterprise guide requires managed Kubernetes, PostgreSQL, object storage and separately provisioned runners. Runner defaults and example machine types are component settings, not a measured minimum for the complete Enterprise service. Scope: Enterprise topology requirements; size the cluster and runners separately. Source: https://docs.superplane.com/self-hosting/install/ (reviewed 2026-11-17).

- License pricing: Documented. The documented AWS, Azure and Google Cloud Kubernetes installation requires a SuperPlane Enterprise license. The Apache-2.0 community engine and single-VM deployment do not grant Enterprise feature or support entitlements. Scope: SuperPlane Enterprise Self-Hosted: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://docs.superplane.com/self-hosting/overview/ (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. Price EKS, RDS HA PostgreSQL, storage and runner pools after the Enterprise bill of materials and active-runner concurrency are confirmed. Hosted sandbox/model charges do not price this deployment. A complete monthly operating estimate is not established. Scope: Requested planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA, average usage; missing workload metrics and commercial terms are explicit. Source: https://docs.superplane.com/self-hosting/install/ (reviewed 2026-11-17).

- Release snapshot / cadence: Sources checked — unresolved. The installer names component/chart revisions, while the latest GitHub release is Fleet Manager v0.1.7. Neither alone establishes the current Enterprise application bundle and supported upgrade compatibility. Scope: Reviewed public evidence for SuperPlane Enterprise Self-Hosted; unresolved within this edition/deployment. Source: https://docs.superplane.com/self-hosting/install/ (reviewed 2026-11-17).







## Windmill Self-Hosted

Run scripts and workflows with customer-operated execution workers and an app builder.

- Listing: https://launchinyourcloud.com/directory/windmill/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, digitalocean, render, hetzner, fly, ubicloud
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: AGPLv3 open-source components; commercial Enterprise licensing and plan-dependent limits
- Licensing model: open-source
- Installation: Docker Compose or Kubernetes/Helm with PostgreSQL and worker replicas
- Architecture: Customer-operated server, worker processes and PostgreSQL job/state storage
- Operations: Customer operates server/worker containers, PostgreSQL, TLS, job isolation, backups and upgrades.
- Product website: https://www.windmill.dev/
- Source review: 2026-11-19; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

This entry excludes hosted Windmill Cloud. Review current community limits and Enterprise features rather than assuming all features are included. Workflow code can reach external services; worker sandboxing and credentials need explicit configuration. Official self-hosting documentation gives AWS/Azure/GCP guidance. Windmill v1.877.0 prevents workspace members from bypassing the configured AI-model allowlist through direct proxy or completion API calls. Direct configured-key POSTs must now contain JSON with a string model, and existing GitHub App repository resources remain admin-only until an administrator saves them once. Retest API callers and repository-resource access. v1.878.0 is the reviewed current follow-up release.

Official repository licensing combines AGPLv3/Apache-2.0 components with proprietary Enterprise feature code. The broad listing includes both community and commercial editions; current plan limits must be checked separately.

Classified servers for the documented long-lived server/worker containers and PostgreSQL queue/state. Fargate compatibility is managed-container hosting, not a function-only software stack.


Cloud evidence scope: Documented customer-operated deployment guides for AWS, Azure and Google Cloud

### Category fit

- workflow-automation: Code-first scripts, flows, schedules and internal apps with worker execution; enterprise controls and quotas vary.

### Deployment boundaries


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

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/windmill-labs/windmill (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/windmill-labs/windmill (checked 2026-11-12). 

- digitalocean: Boundary not confirmed; Customer-operated; control plane: not-assessed. Source: https://github.com/windmill-labs/windmill (checked 2026-11-12). 

- render: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://github.com/windmill-labs/windmill (checked 2026-11-12). 

- hetzner: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/windmill-labs/windmill (checked 2026-11-12). 

- fly: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://github.com/windmill-labs/windmill (checked 2026-11-12). 

- ubicloud: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/windmill-labs/windmill (checked 2026-11-12). Source: https://www.ubicloud.com/docs/managed-kubernetes/windmill-tutorial (checked 2026-11-12). 


### Cloud deployment evidence

- Windmill upstream self-hosting provider compatibility (aws, azure, gcp, digitalocean, render, hetzner, fly, ubicloud): https://github.com/windmill-labs/windmill
  The upstream self-hosting section explicitly names AWS EKS/ECS, Google Cloud, Azure, Ubicloud, Fly.io, Render, Hetzner and DigitalOcean, paired with Docker Compose and Helm installation commands. This is an upstream application-hosting compatibility statement; image licensing and enterprise features are separate. Operate the application in a customer cloud account or managed-platform project as appropriate to the selected provider.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Windmill production deployment on Ubicloud Kubernetes (ubicloud): https://www.ubicloud.com/docs/managed-kubernetes/windmill-tutorial
  Ubicloud documents customer account setup, PostgreSQL and Kubernetes provisioning, Windmill Helm deployment, application access and TLS configuration. This is a full customer application deployment, not a PostgreSQL connector or GitHub Actions runner integration.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Self-host architecture, Docker and provider guidance: https://www.windmill.dev/docs/advanced/self_host

- Project capabilities and license files: https://github.com/windmill-labs/windmill

- Self-hosted edition limits: https://www.windmill.dev/pricing

- Licensing and edition terms: https://github.com/windmill-labs/windmill/blob/main/LICENSE

- Windmill production deployment on Ubicloud Kubernetes: https://www.ubicloud.com/docs/managed-kubernetes/windmill-tutorial

- Windmill v1.878.0 release: https://github.com/windmill-labs/windmill/releases/tag/v1.878.0

- Windmill v1.877.0 policy hardening: https://github.com/windmill-labs/windmill/releases/tag/v1.877.0

- Configured AI-key model enforcement: https://github.com/windmill-labs/windmill/pull/12527

- GitHub App repository approval persistence: https://github.com/windmill-labs/windmill/pull/12524

### Licensing sources

- https://github.com/windmill-labs/windmill/blob/main/LICENSE

- https://www.windmill.dev/pricing

### Infrastructure sources

- https://www.windmill.dev/docs/advanced/self_host


### 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 self-hosted OAuth/SSO guide documents user login through Google, Microsoft, GitHub and other configured providers, separately from OAuth resource connections. SAML and SCIM are explicitly Enterprise features; identity-group synchronization and custom claim settings also have edition limits. Scope: Instance user login; built-in SSO and Enterprise SAML have different entitlements. Source: https://www.windmill.dev/docs/advanced/setup_oauth (reviewed 2026-11-20). Supporting source: Enterprise SAML and SCIM — https://www.windmill.dev/docs/advanced/saml_and_scim.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. v1.877.0 blocks workspace members from spending configured workspace or instance AI keys on models outside the admin-enabled list. Direct configured-key calls now require JSON with a string model; retest clients. Existing GitHub App repository resources require one administrator save before non-admin access. Scope: Windmill configured AI-key proxy and GitHub App repository-resource authorization. Source: https://github.com/windmill-labs/windmill/pull/12527 (reviewed 2026-11-19). Supporting source: v1.877.0 release — https://github.com/windmill-labs/windmill/releases/tag/v1.877.0. Supporting source: Repository approval behavior — https://github.com/windmill-labs/windmill/pull/12524.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The upstream Compose stack includes PostgreSQL and application/worker services. Follow its database-major-version migration notes and choose matching application and dependency releases. Scope: Upstream self-hosted stack; database upgrades require explicit migration planning. Source: https://github.com/windmill-labs/windmill/blob/main/docker-compose.yml (reviewed 2026-11-14). Deployment artifact: https://github.com/windmill-labs/windmill/blob/main/docker-compose.yml. Artifact reference: main (moving branch).

- Minimum footprint / sizing: Documented. The self-hosting guide suggests roughly one worker per vCPU with 1–2 GB RAM per worker. PostgreSQL, server, proxy and optional editor services require additional capacity; worker concurrency and job isolation change sizing. Scope: Worker rule of thumb, not a complete host minimum or a 100-user/1-TB HA design. Source: https://www.windmill.dev/docs/advanced/self_host (reviewed 2026-11-20).

- License pricing: Documented. At v1.878.0, compilable non-enterprise source is AGPLv3, with Apache-licensed clients/specifications. Published Community binaries also contain proprietary features with free internal-use rights and restrictions on redistribution, resale and embedding. Enterprise rights require a commercial licence. Scope: Versioned source and distributed-binary terms differ; cloud infrastructure and support are separate. Source: https://github.com/windmill-labs/windmill/blob/v1.878.0/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Windmill v1.878.0 was published November 19, 2026. The preceding v1.877.0 release tightened configured AI-key model authorization and changed direct API validation, while also requiring administrators to resave existing GitHub App repository resources before non-admin use. Scope: Upstream Windmill self-hosted release. Source: https://github.com/windmill-labs/windmill/releases/tag/v1.878.0 (reviewed 2026-11-19). Supporting source: Prior reviewed release context — https://github.com/windmill-labs/windmill/releases/tag/v1.875.0. Supporting source: v1.877.0 policy changes — https://github.com/windmill-labs/windmill/releases/tag/v1.877.0. Supporting source: AI model allowlist enforcement — https://github.com/windmill-labs/windmill/pull/12527. Supporting source: GitHub App repository approvals — https://github.com/windmill-labs/windmill/pull/12524.




### Security and lifecycle reviews

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

- Windmill v1.877.0 configured-AI-key policy hardening (security-advisory): Windmill now rejects direct configured-key calls to provider models outside the administrator-enabled list. Scope: Workspace or instance AI keys and GitHub App repository resources in self-hosted Windmill. Conditions: Workspace members with direct API access could previously spend the configured key on other provider models; direct callers now need JSON with a string model. Action: Upgrade to v1.877.0 or later, retest API clients and have an administrator resave existing GitHub App repository resources. Source: https://github.com/windmill-labs/windmill/pull/12527; reviewed 2026-11-19. Supporting source: v1.877.0 release — https://github.com/windmill-labs/windmill/releases/tag/v1.877.0. Supporting source: Repository approval persistence — https://github.com/windmill-labs/windmill/pull/12524.



