Workflow automation on Azure
Business automation, integrations, scripts and API workflows.
19 documented options on Microsoft Azure. Provider coverage reflects reviewed evidence, not an exhaustive compatibility claim.
Read this page as JSON or Markdown.
| Listing | Documented clouds | Deployment and infrastructure | Licensing | Installation | Operations and limitations |
|---|---|---|---|---|---|
| Apryse Fluent | AWS, Azure | Customer-operated Servers / containers | Commercial Only Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. | Package / binary installer; Docker / Compose | 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.Scope and evidenceThis is a template and document-generation layer. A separate case, CRM or correspondence application supplies intake, assignment and response deadlines. The documented Azure scaling examples are starting configurations; component licensing and a production HA design require their own review.
Cloud evidence reviewed 2026-11-19 |
| Camunda 8 Self-Managed | AWS, Azure, Google Cloud | Customer-operated Servers / containers | Commercial Only Commercial Enterprise license required for production; unlicensed use is limited to non-production conditions. | Official Helm charts on EKS, AKS or GKE | Customer manages Kubernetes, supported databases or search services, storage, ingress, identity, backups, scaling and upgrades.Scope and evidenceThis 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.
Cloud evidence reviewed 2026-11-14 |
| CloudBolt Cloud Management Platform | AWS, Azure | Customer-operated Servers / containers | Commercial Only Commercial license with a full-featured free tier limited to 100 managed resources for up to one year | Official AWS Marketplace AMI, or vendor installer on supported RHEL or Oracle Linux virtual machines | Customer secures and maintains deployment infrastructure, database, storage, certificates, backups, upgrades, integrations and availability; CloudBolt maintains the appliance software.Scope and evidenceThe free tier is a capped and time-limited commercial entitlement, not an open-source edition. Clouds connected as managed resource handlers are distinct from the cloud account hosting the CMP application.
Cloud evidence reviewed 2026-11-19 |
| Decisions Self-Hosted | AWS, Azure, Google Cloud | Customer-operated Servers / containers | Commercial Only Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. | Docker / Compose; Kubernetes manifests | 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.Scope and evidenceThe 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.
Cloud evidence reviewed 2026-11-19 |
| DocuSeal Self-Hosted | AWS, DigitalOcean, Linode, Vultr, Hostinger, LumaDock, Azure, Google Cloud, Railway, Heroku, Render | Customer-operated Servers / containers | Open Source / Open Core AGPL-3.0 core; Pro features and the private Pro image use separate commercial terms. | Vendor Azure, Google Cloud, DigitalOcean, Railway, Heroku and Render deployment paths, or a Cloudron package on a customer VM. | 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.Scope and evidenceReviewed 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.
Cloud evidence reviewed 2026-11-13 |
| DocuWare On-Premise | Azure | Customer-operated Servers / containers | Commercial Only Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. | Licensed DocuWare installation on Azure Windows Server VMs | 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.Scope and evidenceThe Azure knowledge-base article excludes Azure SQL and Azure Blob Storage. Its MSMQ/Azure Service Bus workaround applies to older versions; the vendor's clarification says messaging changed in 7.13 and later. This is a configurable document workflow, rather than a packaged public-correspondence case system.
Cloud evidence reviewed 2026-11-19 |
| Flowable Enterprise Platform | AWS, Azure | Customer-operated Servers / containers | Commercial Only Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. | Terraform; Kubernetes manifests | 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.Scope and evidenceThe Apache-licensed open-source engine and commercial Work/Platform distribution are different scopes. Supplier-onboarding examples require application modeling and do not establish a packaged supplier-qualification system. The commercial application requires its own licence file.
Cloud evidence reviewed 2026-11-19 |
| Hyland OnBase On-Premise | AWS, Azure, Google Cloud | Customer-operated Servers / containers | Commercial Only Commercial OnBase licenses and separately scoped modules | Vendor or partner-assisted on-premises installation | Customer maintains on-premises infrastructure and backups; agree implementation, upgrades and support responsibilities with Hyland or its partner.Scope and evidenceThis 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.
Cloud evidence reviewed 2026-11-12 |
| Laserfiche Self-Hosted | AWS, Azure | Customer-operated Servers / containers | Commercial Only Commercial self-hosted software; license and module entitlements apply | Licensed Laserfiche 12 Windows installers | Customer operates supported Windows servers, repository/database backups and product updates; follow the chosen modules installation requirements.Scope and evidenceScope is the self-hosted product. Use-case pages describe platform workflows; confirm availability and licensing for the chosen version and modules. The current support matrix requires Windows Server Desktop Experience and explicitly excludes Docker and Kubernetes deployment for self-hosted applications.
Cloud evidence reviewed 2026-11-12 |
| Medplum Self-Hosted | AWS, Azure, Google Cloud | Customer-operated Hybrid | Open Source / Open Core Apache-2.0 Community software; an optional commercial Enterprise Self-Hosted support plan is separate. | AWS CDK, or Terraform and Helm on Azure AKS or Google GKE | Customer operates the cloud infrastructure and application lifecycle; Medplum offers an Enterprise Self-Hosted support plan.Scope and evidenceThe 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.
Cloud evidence reviewed 2026-11-19 |
| Mendix on Kubernetes | AWS, Azure, Google Cloud, STACKIT | Customer-operated · vendor control plane Servers / containers | Commercial Only Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. | Helm / Kubernetes operator; Kubernetes manifests | Customer operates the application runtime; the documented connected deployment also depends on the Mendix management portal and its configured access.Scope and evidenceThe 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.
Cloud evidence reviewed 2026-11-19 |
| n8n Self-Hosted | AWS, Azure, Google Cloud, DigitalOcean, Heroku, Hetzner | Customer-operated Servers / containers | Source Available Sustainable Use License for covered code; separate commercial Enterprise license for enterprise components | Docker Compose with persistent data; database and worker topology selected for workload | Customer manages servers/containers, secrets, database, backup/restore, scaling and upgrades.Scope and evidenceThis 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.
Cloud evidence reviewed 2026-11-12 |
| Pega Platform Client-Managed | AWS, Azure, Google Cloud | Customer-operated Servers / containers | Commercial Only Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. | Helm / Kubernetes operator; Kubernetes manifests | 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.Scope and evidenceThis 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.
Cloud evidence reviewed 2026-11-19 |
| Red Hat Ansible Automation Platform Self-Managed | AWS, Azure, Google Cloud | Customer-operated Servers / containers | Commercial Only Commercial Red Hat Ansible Automation Platform subscription required. | Containerized installer on RHEL with Podman or the OpenShift Operator | Customer manages the platform, execution capacity, infrastructure, secrets, backups and upgrades; Red Hat supplies subscribed software updates and support.Scope and evidenceThis 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.
Cloud evidence reviewed 2026-11-17 |
| Retool Self-Hosted, Self-Managed | AWS, Azure, Google Cloud | Customer-operated Servers / containers | Commercial Only Commercial Enterprise subscription with custom annual pricing and a self-hosted license key. | Official Terraform blueprints for Amazon EKS, Azure AKS or Google GKE, or Helm into an existing supported Kubernetes cluster | Customer manages Kubernetes, PostgreSQL, object storage, DNS, TLS, secrets, networking, backups, capacity, upgrades and the Retool license.Scope and evidenceThis 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.
Cloud evidence reviewed 2026-11-16 |
| Spacelift Self-Hosted | AWS, Azure, Google Cloud | Customer-operated Servers / containers | Commercial Only Commercial Spacelift Self-Hosted Enterprise subscription and license token required. | Official Terraform/OpenTofu reference architectures and Helm charts for EKS/ECS, AKS or GKE | Customer manages compute or Kubernetes, database and object storage, networking, secrets, workers, backups, scaling, upgrades and licensing.Scope and evidenceThis 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.
Cloud evidence reviewed 2026-11-18 |
| SuperPlane Enterprise Self-Hosted | AWS, Azure, Google Cloud | Customer-operated Servers / containers | Commercial Only Commercial SuperPlane Enterprise license required for the documented Kubernetes deployment. | Vendor Terraform modules provision EKS, AKS or GKE, managed data services and the SuperPlane Helm release | Customer manages the cloud account, cluster, database, object storage, runner images and VMs, DNS, TLS, backups, upgrades and connected model or tool credentials.Scope and evidenceThis 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.
Cloud evidence reviewed 2026-11-17 |
| UiPath Automation Suite | AWS, Azure | Customer-operated Hybrid | Commercial Only Commercial UiPath Unified Pricing or Flex plans and applicable product SKUs | uipathctl on customer-managed Amazon EKS or Azure AKS | Customer provisions, patches and operates the cloud infrastructure; UiPath supplies and supports Automation Suite and its upgrade tooling.Scope and evidenceAutomation Suite contains UiPath server products supported by that release, not every Automation Cloud service. The selected 2.2510 EKS/AKS documentation covers online and offline customer-managed infrastructure; verify the licensed product set and supported component versions.
Cloud evidence reviewed 2026-11-19 |
| Windmill Self-Hosted | AWS, Azure, Google Cloud, DigitalOcean, Render, Hetzner, Fly.io, Ubicloud | Customer-operated Servers / containers | Open Source / Open Core AGPLv3 open-source components; commercial Enterprise licensing and plan-dependent limits | Docker Compose or Kubernetes/Helm with PostgreSQL and worker replicas | Customer operates server/worker containers, PostgreSQL, TLS, job isolation, backups and upgrades.Scope and evidenceThis 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.
Cloud evidence reviewed 2026-11-12 |
Deployment evidence and category fit
Apryse Fluent
Customer-hosted document-template management and rendering software for automated business output.
This is a template and document-generation layer. A separate case, CRM or correspondence application supplies intake, assignment and response deadlines. The documented Azure scaling examples are starting configurations; component licensing and a production HA design require their own review.
- Azure Container Apps ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Fluent Manager or RESTful Engine with a database on AWS EC2, Azure Container Apps or Azure App Service. This is a template and document-generation layer. A separate case, CRM or correspondence application supplies intake, assignment and response deadlines. The documented Azure scaling examples are starting configurations; component licensing and a production HA design require their own review.
Cloud evidence reviewed 2026-11-19. Full listing and qualifications
Camunda 8 Self-Managed
Executes modeled business processes, user tasks, connectors and decision-driven automation in customer-operated infrastructure.
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 8 Self-Managed on Microsoft AKS ↗
Vendor / upstream documentation · Reviewed 2026-11-14. Vendor support commitment: not assessed; confirm the selected release and contract.
Camunda provides current AKS and Helm guidance for a customer Azure subscription, with provider-specific reference infrastructure.
Cloud evidence reviewed 2026-11-14. Full listing and qualifications
CloudBolt Cloud Management Platform
Blueprints and automation coordinate infrastructure requests, approvals, provisioning and lifecycle actions.
The free tier is a capped and time-limited commercial entitlement, not an open-source edition. Clouds connected as managed resource handlers are distinct from the cloud account hosting the CMP application.
- CloudBolt CMP Azure VM and HA deployment ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
The official guide installs CMP on customer Azure VMs and builds the full HA topology with Azure Load Balancer, Azure Database for PostgreSQL Flexible Server, Azure Files and customer virtual networks.
Cloud evidence reviewed 2026-11-19. Full listing and qualifications
Decisions Self-Hosted
Commercial rules and workflow platform with provider-specific container deployments.
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.
- Azure Deploy ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Cloud evidence reviewed 2026-11-19. Full listing and qualifications
DocuSeal Self-Hosted
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.
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.
- Vendor Azure Web Apps deployment ↗
Vendor / upstream documentation · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Cloud evidence reviewed 2026-11-13. Full listing and qualifications
DocuWare On-Premise
Customer-operated document repository, email capture and document-workflow platform on Azure VMs.
The Azure knowledge-base article excludes Azure SQL and Azure Blob Storage. Its MSMQ/Azure Service Bus workaround applies to older versions; the vendor's clarification says messaging changed in 7.13 and later. This is a configurable document workflow, rather than a packaged public-correspondence case system.
- Azure VM KBA-37193 ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Windows Server application VMs and a database on the same or separate VM. The Azure knowledge-base article excludes Azure SQL and Azure Blob Storage. Its MSMQ/Azure Service Bus workaround applies to older versions; the vendor's clarification says messaging changed in 7.13 and later. This is a configurable document workflow, rather than a packaged public-correspondence case system.
Cloud evidence reviewed 2026-11-19. Full listing and qualifications
Flowable Enterprise Platform
Commercial workflow and case-management platform with vendor Terraform and Helm deployments.
The Apache-licensed open-source engine and commercial Work/Platform distribution are different scopes. Supplier-onboarding examples require application modeling and do not establish a packaged supplier-qualification system. The commercial application requires its own licence file.
- Azure Terraform ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Flowable application services, database, search and persistent storage on EKS or AKS. The Apache-licensed open-source engine and commercial Work/Platform distribution are different scopes. Supplier-onboarding examples require application modeling and do not establish a packaged supplier-qualification system. The commercial application requires its own licence file.
Cloud evidence reviewed 2026-11-19. Full listing and qualifications
Hyland OnBase On-Premise
Content and case workflows with routing, rules and low-code WorkView applications.
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.
- Hyland partner statement on customer-managed OnBase cloud deployments ↗
Partner evidence · Reviewed 2026-11-12 · Version: OnBase 18+ in partner statement; confirm current release. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
- Hyland identification of Reveille as an authorized integration partner ↗
Partner relationship · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Cloud evidence reviewed 2026-11-12. Full listing and qualifications
Laserfiche Self-Hosted
Forms and document workflows for routing, approvals and task automation.
Scope is the self-hosted product. Use-case pages describe platform workflows; confirm availability and licensing for the chosen version and modules. The current support matrix requires Windows Server Desktop Experience and explicitly excludes Docker and Kubernetes deployment for self-hosted applications.
- Laserfiche reseller installation terms for customer AWS and Azure environments ↗
Public procurement record · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
Cities Digital installation terms, published in the municipal meeting packet on PDF page 40, explicitly cover new Azure or AWS environments and exclude Laserfiche Cloud from that section. The client supplies Windows, SQL Server and network configuration and validates workflows. This documents a reseller-assisted self-hosted path; confirm the current server version, license, support scope and implementation fees.
Cloud evidence reviewed 2026-11-12. Full listing and qualifications
Medplum Self-Hosted
Medplum Bots, cron jobs, subscriptions and triggers automate clinical and operational workflows.
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.
- Production-validated Medplum deployment on Azure ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
The official Terraform and Helm workflow deploys Medplum into the customer's Azure subscription with AKS, PostgreSQL, Redis, storage, gateway and frontend resources.
Cloud evidence reviewed 2026-11-19. Full listing and qualifications
Mendix on Kubernetes
Commercial low-code application runtime operated in customer Kubernetes infrastructure.
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.
- Supported Clouds ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Cloud evidence reviewed 2026-11-19. Full listing and qualifications
n8n Self-Hosted
Visual integration/workflow automation with custom code and connectors; connected systems and AI providers may receive workflow data.
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.
- n8n deployment on Azure ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
Project instructions deploy n8n with PostgreSQL on Azure Kubernetes Service in the customer subscription.
Cloud evidence reviewed 2026-11-12. Full listing and qualifications
Pega Platform Client-Managed
Commercial workflow and case-management platform installed in customer-managed Kubernetes infrastructure.
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.
- AKS Runbook ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Cloud evidence reviewed 2026-11-19. Full listing and qualifications
Red Hat Ansible Automation Platform Self-Managed
Controller, event-driven automation and reusable automation content coordinate governed operational workflows.
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.
- Self-managed Ansible Automation Platform in named public clouds ↗
Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Cloud evidence reviewed 2026-11-17. Full listing and qualifications
Retool Self-Hosted, Self-Managed
Runs Retool Workflows and related automation services inside the customer-operated deployment.
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.
- Official Retool Terraform and Helm deployment paths ↗
Vendor / upstream documentation · Reviewed 2026-11-16. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Cloud evidence reviewed 2026-11-16. Full listing and qualifications
Spacelift Self-Hosted
Orchestrates governed infrastructure workflows, approvals and automated runs.
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.
- Spacelift in customer AWS, Azure or GCP infrastructure ↗
Vendor / upstream documentation · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.
Spacelift explicitly documents a customer-maintained self-hosted product for AWS, Azure and GCP and links provider-specific reference architectures.
Cloud evidence reviewed 2026-11-18. Full listing and qualifications
SuperPlane Enterprise Self-Hosted
Defines durable automation lines, approvals, checks and repair loops for recurring engineering work.
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.
- SuperPlane Enterprise on EKS, AKS and GKE ↗
Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Cloud evidence reviewed 2026-11-17. Full listing and qualifications
UiPath Automation Suite
Self-hosted enterprise automation products and shared platform services on a customer-managed Kubernetes environment.
Automation Suite contains UiPath server products supported by that release, not every Automation Cloud service. The selected 2.2510 EKS/AKS documentation covers online and offline customer-managed infrastructure; verify the licensed product set and supported component versions.
- UiPath Automation Suite on customer-managed Azure AKS ↗
Vendor / upstream documentation · Reviewed 2026-11-19 · Version: 2.2510 documentation. Vendor support commitment: not assessed; confirm the selected release and contract.
UiPath documents production architectures for Automation Suite on customer-managed Azure AKS, including required database, storage, cache, networking and secrets services.
Cloud evidence reviewed 2026-11-19. Full listing and qualifications
Windmill Self-Hosted
Code-first scripts, flows, schedules and internal apps with worker execution; enterprise controls and quotas vary.
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.
- Windmill upstream self-hosting provider compatibility ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Cloud evidence reviewed 2026-11-12. Full listing and qualifications
Deployment and procurement checks
- Private offers
- Microsoft Marketplace private offers negotiate product pricing and terms. Confirm the exact offer, billing scope and benefit eligibility rather than assuming all purchases count toward a commitment. Provider source ↗ · Reviewed 2026-11-14
- Private connectivity
- Azure Private Link uses private endpoints in a virtual network for supported Azure and partner services. Check application support, DNS and service availability. Provider source ↗ · Reviewed 2026-11-14
- Cross-tenant operations
- Azure Lighthouse supports delegated management with customer-controlled scopes and actions. Agree the roles, audit requirements and revocation plan for the selected vendor. Provider source ↗ · Reviewed 2026-11-14
- Government environments
- Azure Government uses isolated US datacenters and networks. Commercial Azure documentation alone does not establish a product path or compliance in Government. Provider source ↗ · Reviewed 2026-11-14
For every provider, confirm marketplace/private-offer terms, commitment eligibility, regional service availability, private connectivity and any vendor access against your selected deployment. Provider capabilities do not automatically establish application support.
Plan this deployment
Account boundary: Subscription and resource group. Access: Microsoft Entra identities and Azure RBAC. Network: Virtual Network (VNet).
Provider documentation ↗ · Guidance reviewed 2026-11-10. Confirm the application edition, region, support access, backup locations and operating responsibilities before choosing.
Compare this category across clouds · Search these listings · Compare 2–4 listings