AI applications & RAG on Google Cloud

AI application builders, chat interfaces, agents and retrieval-augmented generation.

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

ListingDocumented cloudsDeployment and infrastructureLicensingInstallationOperations and limitations
AnythingLLM DockerAWS, Google Cloud, RailwayCustomer-operated
Servers / containers
Open Source / Open Core

MIT License for upstream AnythingLLM; model weights, connectors and provider services have separate terms.

Run the official Docker edition on a customer-operated host with persistent application storage and configured model/vector endpoints.Customer manages users, documents, persistent storage, model access, integration secrets, backups and upgrades.
Scope and evidence

The Docker edition supports multi-user operation and differs from the desktop application. Local inference is an option; configured external LLMs, embeddings, vector stores and agent tools can send data outside the account. AnythingLLM v1.20.0 hardens embed history, extension API-key authorization, workspace-agent access, password recovery, framing, and document-tool downloads. Optional MCP identity forwarding creates a new outbound identity path; keep the server and extension on compatible 1.20+ versions.

  • AnythingLLM Docker installation overview — The project explicitly names AWS, Google Cloud and Railway for self-hosting the Docker edition, paired with its Docker installation workflow. This is an upstream hosting compatibility statement. Model endpoints, embeddings and external vector stores are separately configured and can have different data boundaries.

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

Cloud evidence reviewed 2026-11-12

Langflow Self-HostedAWS, Azure, Google CloudCustomer-operated
Servers / containers
Open Source / Open Core

MIT for the upstream project; connected models, providers and bundles have their own terms.

Official Docker image or Docker Compose; Python installation and Kubernetes options are also documented.Customer manages the application, database, access controls, installed components, backups and version upgrades.
Scope and evidence

The reviewed model-component docs support Ollama and configurable OpenAI-compatible endpoints as well as commercial providers. External models, embeddings, tools or custom components can move data beyond the host. Hosting Langflow is distinct from hosting those dependencies and from any vendor-managed service. Langflow 1.13.3 enforces custom-component policy in background workflows, invalidates native sessions after password changes, updates security dependencies, and aligns Docker and wheel packaging. Recheck custom components and session behavior after upgrading.

  • Langflow Kubernetes deployment architecture — The project explicitly identifies EKS, AKS and GKE for its Helm deployment. Separate the development IDE from the production runtime, and review PostgreSQL, model endpoints and external vector stores.

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

Cloud evidence reviewed 2026-11-12

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

MIT Community Edition; Business and Enterprise features use separate commercial terms.

Docker Compose on a VM or official Kubernetes and Terraform deploymentCustomer manages application services, databases, search, object storage, connectors, model credentials, backups, scaling and upgrades.
Scope and evidence

This entry covers self-hosted Onyx, not a vendor-hosted environment. External LLM, embedding and connector services receive data according to the customer's configuration. Business and Enterprise features and support require separate commercial entitlements.

  • Onyx on AWS — Onyx documents self-hosting on a customer EC2 instance and links a production EKS architecture using AWS managed dependencies.

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

  • Onyx on Azure — Onyx documents self-hosting on an Azure VM and an AKS Terraform path using customer Azure managed services.

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

  • Onyx on Google Cloud — Onyx documents Compute Engine and production GKE deployment paths in the customer's Google Cloud project.

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

  • Onyx on DigitalOcean — Onyx documents installing its self-hosted stack on a customer DigitalOcean Droplet.

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

Cloud evidence reviewed 2026-11-14

Open WebUI Self-HostedAWS, Azure, Google CloudCustomer-operated
Servers / containers
Source Available

Open WebUI license based on BSD-style terms with additional branding restrictions and defined exceptions; enterprise terms may be required for rebranding.

Official Docker image, Python installation or Kubernetes deployment.Customer runs application storage, authentication, provider configuration, updates and backups.
Scope and evidence

The UI sends messages to the model endpoint selected for a conversation. Local Ollama or vLLM endpoints can keep inference on customer infrastructure; cloud APIs, embeddings, tools and plugins have separate data flows. The current license restricts branding removal in larger deployments, with small-deployment, permission and enterprise-license exceptions; review the actual terms. Open WebUI v0.13.4 replaces Direct Connections and Integrations with Tether and migrates image settings. Deployments using Terminals server connections require Terminals 0.4.0 or later; upgrading that server from 0.3.x requires manual migration. Open Terminal and Tether terminal connections are unaffected by this migration. Tether introduces user-device and local-command paths that require explicit trust review.

  • Open WebUI deployment on AWS ECS / Fargate — Project deployment instructions cover the application on AWS ECS / Fargate with external database, Redis and file storage. Model inference is separate; review model endpoints, egress and WebSocket/runtime limits.

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

  • Open WebUI deployment on Azure Container Apps — Project deployment instructions cover the application on Azure Container Apps with external database, Redis and file storage. Model inference is separate; review model endpoints, egress and WebSocket/runtime limits.

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

  • Open WebUI deployment on Google Cloud Run — Project deployment instructions cover the application on Google Cloud Run with external database, Redis and file storage. Model inference is separate; review model endpoints, egress and WebSocket/runtime limits.

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

Cloud evidence reviewed 2026-11-12

RAGFlowAWS, Azure, Google Cloud, Alibaba Cloud, RailwayCustomer-operated
Servers / containers
Open Source / Open Core

Apache License 2.0 for upstream RAGFlow; models, data assets and dependencies retain their own terms.

Versioned upstream Docker Compose, provider-specific VM packages or community deployment templates; select a path compatible with the intended RAGFlow release.Customer manages document storage, indexing, app services, access controls, model endpoints, backups and upgrades.
Scope and evidence

Deployment options include customer AWS, Azure and Google Cloud infrastructure, Alibaba Compute Nest, and a Railway project. The evidence trail identifies the publishers and template versions. Hosting RAGFlow does not automatically self-host its LLM, embeddings or reranker; choose private or local model endpoints where required.

  • Community RAGFlow deployment on AWS ECS Fargate through stdapi.ai — The sample provisions the RAGFlow application and workers, OpenSearch, Aurora PostgreSQL, Valkey, S3 and a Bedrock gateway in the customer AWS account. Source inspection confirms the v0.26.4 Python image pin; it does not establish compatibility with the 1.0 Go rewrite. This community integration also requires the separately billed stdapi.ai gateway and Bedrock access. Review its documented networking, client-security, availability and cost limitations before use.

    Community template · Reviewed 2026-11-12 · Scope: Community / upstream open-source; third-party distribution where noted · Version: 0.26.4. Vendor support commitment: not assessed; confirm the selected release and contract.

  • cloudimg RAGFlow Azure VM deployment and operations guide — The image publisher documents an Azure VM in the customer subscription running the complete Compose stack, including Elasticsearch, MySQL, MinIO, Redis and a local embedding service. Its guide pins RAGFlow v0.26.4, not 1.0. This is a third-party repackaged image with additional support charges, not an upstream-endorsed distribution. Confirm image access, current patch/migration requirements, TLS configuration and the separately configured chat-model endpoint.

    Third party package · Reviewed 2026-11-12 · Scope: Community / upstream open-source; third-party distribution where noted · Version: 0.26.4. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Techlatest RAGFlow VM deployment in a customer Google Cloud project — The image publisher documents selecting the customer project, deployment service account, zone, network and Compute Engine VM, then completing RAGFlow initialization and configuring its bundled Ollama models. This is a third-party packaged deployment; the guide does not establish a specific current RAGFlow release or 1.0 compatibility. Confirm the image version, support charges, model licenses, resource sizing and network exposure before use.

    Third party package · Reviewed 2026-11-12 · Scope: Community / upstream open-source; third-party distribution where noted. Vendor support commitment: not assessed; confirm the selected release and contract.

  • RAGFlow Community deployment on Alibaba Cloud Compute Nest — Alibaba Cloud documents provisioning a RAGFlow Community service instance with customer ECS, VPC and vSwitch parameters. This is distinct from the managed AI-Native Database Service integration. Review image version, access controls, model endpoints and the broad example RAM permissions before production.

    Provider guide · Reviewed 2026-11-12 · Scope: Community / upstream open-source; third-party distribution where noted. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Community RAGFlow Railway application stack — This community template deploys the application, Elasticsearch, MySQL, Redis, a local embedding service and object storage into the customer Railway project. Its linked Dockerfile pins upstream RAGFlow v0.27.1 with a Railway startup/configuration wrapper. The template is not proof of 1.0 compatibility or upstream support; review migrations and the separately configured chat-model endpoint. Railway manages the underlying infrastructure.

    Community template · Reviewed 2026-11-12 · Scope: Community / upstream open-source; third-party distribution where noted · Version: 0.27.1. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Railway deployment image source and release pin — Source inspection confirms the v0.27.1 base image and the custom configuration, nginx and startup wrapper used by the linked Railway template. The upstream 1.0 release changes the architecture and requires its documented migration path; do not substitute a new image tag without reviewing the complete stack.

    Community template · Reviewed 2026-11-12 · Scope: Community / upstream open-source; third-party distribution where noted · Version: 0.27.1. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-12

Deployment evidence and category fit

AnythingLLM Docker

Multi-user application for document-grounded chat, RAG and agents with configurable model and vector-database integrations.

The Docker edition supports multi-user operation and differs from the desktop application. Local inference is an option; configured external LLMs, embeddings, vector stores and agent tools can send data outside the account. AnythingLLM v1.20.0 hardens embed history, extension API-key authorization, workspace-agent access, password recovery, framing, and document-tool downloads. Optional MCP identity forwarding creates a new outbound identity path; keep the server and extension on compatible 1.20+ versions.

  • AnythingLLM Docker installation overview ↗

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

    The project explicitly names AWS, Google Cloud and Railway for self-hosting the Docker edition, paired with its Docker installation workflow. This is an upstream hosting compatibility statement. Model endpoints, embeddings and external vector stores are separately configured and can have different data boundaries.

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

Langflow Self-Hosted

Visual builder and runtime for AI flows, agents and model integrations. Local model endpoints are configurable; a flow can also call externally hosted providers.

The reviewed model-component docs support Ollama and configurable OpenAI-compatible endpoints as well as commercial providers. External models, embeddings, tools or custom components can move data beyond the host. Hosting Langflow is distinct from hosting those dependencies and from any vendor-managed service. Langflow 1.13.3 enforces custom-component policy in background workflows, invalidates native sessions after password changes, updates security dependencies, and aligns Docker and wheel packaging. Recheck custom components and session behavior after upgrading.

  • Langflow Kubernetes deployment architecture ↗

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

    The project explicitly identifies EKS, AKS and GKE for its Helm deployment. Separate the development IDE from the production runtime, and review PostgreSQL, model endpoints and external vector stores.

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

Onyx Self-Hosted

Provides enterprise search, connectors and retrieval-augmented AI assistants over customer-selected knowledge sources.

This entry covers self-hosted Onyx, not a vendor-hosted environment. External LLM, embedding and connector services receive data according to the customer's configuration. Business and Enterprise features and support require separate commercial entitlements.

  • Onyx on Google Cloud ↗

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

    Onyx documents Compute Engine and production GKE deployment paths in the customer's Google Cloud project.

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

Open WebUI Self-Hosted

Deployable team chat and model-access interface with retrieval features. It is an interface and application layer, not an included license or runtime for every connected model.

The UI sends messages to the model endpoint selected for a conversation. Local Ollama or vLLM endpoints can keep inference on customer infrastructure; cloud APIs, embeddings, tools and plugins have separate data flows. The current license restricts branding removal in larger deployments, with small-deployment, permission and enterprise-license exceptions; review the actual terms. Open WebUI v0.13.4 replaces Direct Connections and Integrations with Tether and migrates image settings. Deployments using Terminals server connections require Terminals 0.4.0 or later; upgrading that server from 0.3.x requires manual migration. Open Terminal and Tether terminal connections are unaffected by this migration. Tether introduces user-device and local-command paths that require explicit trust review.

  • Open WebUI deployment on Google Cloud Run ↗

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

    Project deployment instructions cover the application on Google Cloud Run with external database, Redis and file storage. Model inference is separate; review model endpoints, egress and WebSocket/runtime limits.

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

RAGFlow

Document understanding, knowledge ingestion and retrieval-augmented/agentic question answering with configurable LLM, embedding and reranking endpoints.

Deployment options include customer AWS, Azure and Google Cloud infrastructure, Alibaba Compute Nest, and a Railway project. The evidence trail identifies the publishers and template versions. Hosting RAGFlow does not automatically self-host its LLM, embeddings or reranker; choose private or local model endpoints where required.

  • Techlatest RAGFlow VM deployment in a customer Google Cloud project ↗

    Third party package · Reviewed 2026-11-12 · Scope: Community / upstream open-source; third-party distribution where noted. Vendor support commitment: not assessed; confirm the selected release and contract.

    The image publisher documents selecting the customer project, deployment service account, zone, network and Compute Engine VM, then completing RAGFlow initialization and configuring its bundled Ollama models. This is a third-party packaged deployment; the guide does not establish a specific current RAGFlow release or 1.0 compatibility. Confirm the image version, support charges, model licenses, resource sizing and network exposure before use.

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