Internal tools on Google Cloud

Low-code applications, operational interfaces and internal business tools.

6 documented options on Google Cloud. Provider coverage reflects reviewed evidence, not an exhaustive compatibility claim.

ListingDocumented cloudsDeployment and infrastructureLicensingInstallationOperations and limitations
Appsmith Self-HostedAWS, Azure, Google Cloud, DigitalOceanCustomer-operated
Servers / containers
Open Source / Open Core

Apache-2.0 Community core; commercial edition and plan-dependent features

Docker Compose or Kubernetes; documented cloud VM/managed-container installation guidesCustomer manages deployment, persistent databases, backups, networking and upgrades; confirm edition-specific vendor connectivity.
Scope and evidence

Community and commercial images differ. Documentation requires outbound HTTPS to cs.appsmith.com for self-hosted license/template services and describes separate air-gapped arrangements. Official setup guides name AWS, Azure and Google Cloud. Fargate and Cloud Run are long-running container hosting options, not evidence that the entire stack is function-based. Appsmith v2.7.0 fixes app and datasource authorization issues, extends restricted-host enforcement to S3-compatible and DynamoDB sources, and updates vulnerable dependencies.

  • Appsmith provider-specific installation index — The vendor documents AWS AMI and ECS, Azure Container Instances and Google Cloud Run installation of the application. These are self-hosted installations, with edition-specific licensing and vendor connectivity requirements described separately.

    Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Appsmith on a customer DigitalOcean Droplet — The vendor walks through choosing the Appsmith Marketplace image, creating a Droplet in the customer account and registering its application administrator. Free and licensed features have separate entitlements; configure domain, TLS, email and recovery for production.

    Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-12

Decisions Self-HostedAWS, Azure, Google CloudCustomer-operated
Servers / containers
Commercial Only

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

Docker / Compose; Kubernetes manifestsCustomer 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 evidence

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.

  • AWS ECS Deploy — 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.

    Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Azure Deploy — 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.

    Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.

  • GCP Deploy — 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.

    Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-19

Mendix on KubernetesAWS, Azure, Google Cloud, STACKITCustomer-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 manifestsCustomer operates the application runtime; the documented connected deployment also depends on the Mendix management portal and its configured access.
Scope and evidence

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

    Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-19

NocoDB Self-HostedAWS, Google Cloud, DigitalOcean, RailwayCustomer-operated
Servers / containers
Source Available

Current upstream master/develop code uses the Sustainable Use License: internal business or noncommercial/personal use is permitted, with distribution and other restrictions. Paid self-hosted features require a separate license.

Run the official Docker image with persistent storage or use its documented Compose-based server installer.Customer manages app services, databases, access rules, secrets, backups, upgrades and any paid license.
Scope and evidence

The upstream license changed in January 2026; this is classified as source-available. Internal-tool Interfaces are a licensed feature, while AI apps have separate availability. Connected databases, AI providers and integrations can send data outside the account. NocoDB 2026.10.2 restricts shared views and dashboards to displayed fields, limits forms to their own fields, prevents Editors from reading workflow-step secrets and caps workflow webhook bodies at 1 MB. It also restores NC_SSO=oidc, requires unchanged RelayState for SAML IdP-initiated login and repairs air-gapped license refresh. Retest public shares, forms, workflow permissions and SSO after upgrading.

  • NocoDB community cloud installation methods — The upstream community-methods guide includes full application deployment on DigitalOcean App Platform and a Railway template alongside AWS ECS/Fargate and Google Cloud Run. NocoDB explicitly does not maintain these methods or give them first-class installation support. Review image licensing, database configuration, persistence and production requirements.

    Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-12

Retool Self-Hosted, Self-ManagedAWS, Azure, Google CloudCustomer-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 clusterCustomer manages Kubernetes, PostgreSQL, object storage, DNS, TLS, secrets, networking, backups, capacity, upgrades and the Retool license.
Scope and evidence

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

    Vendor / upstream documentation · Reviewed 2026-11-16. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-16

ToolJet Self-HostedAWS, Azure, Google Cloud, DigitalOceanCustomer-operated
Servers / containers
Open Source / Open Core

AGPL-3.0 open-source foundation; commercial self-hosted editions/plans

Docker Compose or Kubernetes; optional Terraform provisioning for AWS/Azure/GCP VMsCustomer operates application, database, credentials, backups and upgrades; vendor license activation applies to paid features.
Scope and evidence

The self-hosted Basic tier and paid editions have different limits and governance features. Official Docker documentation includes customer VM provisioning paths for AWS, Azure and Google Cloud. AI features require additional outbound vendor endpoints; self-hosting does not imply air-gapped operation. ToolJet v3.21.96-lts lets administrators revoke any workspace personal access token, applies configured rate limits to workflow webhooks, and updates vulnerable dependencies. Self-hosted operators should use v3.21.96-lts or later.

  • ToolJet application deployment on cloud VMs — The current vendor Docker guide links optional Terraform VM provisioning on AWS, Azure and Google Cloud, followed by ToolJet server deployment. Configure the application databases, image edition and production settings separately; AI features can use vendor endpoints.

    Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

  • ToolJet on a customer DigitalOcean Droplet — The vendor guide creates an Ubuntu Droplet, configures its firewall and installs Docker and Compose, then follows the ToolJet Docker deployment. The current instructions include LTS and enterprise image guidance; license and AI endpoint requirements remain edition-dependent.

    Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-12

Deployment evidence and category fit

Appsmith Self-Hosted

Low-code development of dashboards, admin panels and internal apps connected to databases/APIs; not a turnkey business application.

Community and commercial images differ. Documentation requires outbound HTTPS to cs.appsmith.com for self-hosted license/template services and describes separate air-gapped arrangements. Official setup guides name AWS, Azure and Google Cloud. Fargate and Cloud Run are long-running container hosting options, not evidence that the entire stack is function-based. Appsmith v2.7.0 fixes app and datasource authorization issues, extends restricted-host enforcement to S3-compatible and DynamoDB sources, and updates vulnerable dependencies.

  • Appsmith provider-specific installation index ↗

    Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

    The vendor documents AWS AMI and ECS, Azure Container Instances and Google Cloud Run installation of the application. These are self-hosted installations, with edition-specific licensing and vendor connectivity requirements described separately.

Cloud evidence reviewed 2026-11-12. 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

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

NocoDB Self-Hosted

Interfaces build focused internal pages, dashboards and approval views on base data. The reviewed release limits Interfaces to licensed self-hosted Business plans and above.

The upstream license changed in January 2026; this is classified as source-available. Internal-tool Interfaces are a licensed feature, while AI apps have separate availability. Connected databases, AI providers and integrations can send data outside the account. NocoDB 2026.10.2 restricts shared views and dashboards to displayed fields, limits forms to their own fields, prevents Editors from reading workflow-step secrets and caps workflow webhook bodies at 1 MB. It also restores NC_SSO=oidc, requires unchanged RelayState for SAML IdP-initiated login and repairs air-gapped license refresh. Retest public shares, forms, workflow permissions and SSO after upgrading.

  • NocoDB community cloud installation methods ↗

    Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

    The upstream community-methods guide includes full application deployment on DigitalOcean App Platform and a Railway template alongside AWS ECS/Fargate and Google Cloud Run. NocoDB explicitly does not maintain these methods or give them first-class installation support. Review image licensing, database configuration, persistence and production requirements.

Cloud evidence reviewed 2026-11-12. Full listing and qualifications

Retool Self-Hosted, Self-Managed

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

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

ToolJet Self-Hosted

Visual internal app development with database/API connections, dashboards and workflows; access and governance depend on edition.

The self-hosted Basic tier and paid editions have different limits and governance features. Official Docker documentation includes customer VM provisioning paths for AWS, Azure and Google Cloud. AI features require additional outbound vendor endpoints; self-hosting does not imply air-gapped operation. ToolJet v3.21.96-lts lets administrators revoke any workspace personal access token, applies configured rate limits to workflow webhooks, and updates vulnerable dependencies. Self-hosted operators should use v3.21.96-lts or later.

  • ToolJet application deployment on cloud VMs ↗

    Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

    The current vendor Docker guide links optional Terraform VM provisioning on AWS, Azure and Google Cloud, followed by ToolJet server deployment. Configure the application databases, image edition and production settings separately; AI features can use vendor endpoints.

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