Workflow automation on Google Cloud
Business automation, integrations, scripts and API workflows.
14 documented options on Google Cloud. 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 |
|---|---|---|---|---|---|
| Activepieces Self-Hosted | AWS, Google Cloud, Railway | Customer-operated Servers / containers | Open Source / Open Core MIT-licensed Community Edition core; enterprise and cloud feature directories use commercial terms. | Official AWS Pulumi stack, Google Cloud VM guide or Railway template; Docker Compose and Kubernetes/Helm are also documented. | 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.Scope and evidenceThis 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.
Cloud evidence reviewed 2026-11-13 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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
Activepieces Self-Hosted
Builds event-driven business automations from triggers and actions, with customer-operated workers and integrations.
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.
- Google Cloud VM deployment ↗
Vendor / upstream documentation · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Cloud evidence reviewed 2026-11-13. 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 Google GKE ↗
Vendor / upstream documentation · Reviewed 2026-11-14. Vendor support commitment: not assessed; confirm the selected release and contract.
Camunda documents its Self-Managed Helm deployment and Google Cloud-specific GKE configuration.
Cloud evidence reviewed 2026-11-14. 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.
- GCP 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 Google Cloud Run 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 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.
Cloud evidence reviewed 2026-11-13. 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
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 Google Cloud ↗
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 Google Cloud project with GKE, Cloud SQL, Redis, storage 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 Google Cloud Run ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
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.
- GKE 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
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
- 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. Provider source ↗ · 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. Provider source ↗ · 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. Provider source ↗ · 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. 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: Google Cloud project. Access: IAM policies and service accounts. Network: VPC network.
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