RAGFlow

Document processing and retrieval platform for building RAG and agentic knowledge applications.

  • AWS
  • Azure
  • Google Cloud
  • Alibaba Cloud
  • Railway
Customer-operated Servers / containers Open Source / Open Core

3 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

What lands where

  1. Supplied by

    Vendor or project

    Versioned upstream Docker Compose, provider-specific VM packages or community deployment templates; select a path compatible with the intended RAGFlow release.

  2. Operated by

    Your team

    Customer manages document storage, indexing, app services, access controls, model endpoints, backups and upgrades.

Deployment boundaries by provider

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodVersioned upstream Docker Compose, provider-specific VM packages or community deployment templates; select a path compatible with the intended RAGFlow release.
InfrastructureServers / containers
Customer-operated document/retrieval application with deployment-specific stateful storage and configured model services. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.
Licensing modelOpen Source / Open Core
Apache License 2.0 for upstream RAGFlow; models, data assets and dependencies retain their own terms. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.
LicenseApache License 2.0 for upstream RAGFlow; models, data assets and dependencies retain their own terms.

Buyer diligence

Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.

How to read these facts

Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.

5 of 12 fields researched (42%) · 4 documented · 1 unresolved. Evidence coverage is not a feature score.

Single sign-on
Not confirmedEvidence and scope for Single sign-on

A vendor maintainer identifies OAuth2/OIDC SSO in Enterprise, while the reviewed v1.0.0 Go deployment reference does not establish a supported federation configuration for that OSS release. Older OAuth configuration examples must not be assumed compatible with the new backend. Confirm edition, release and identity-provider configuration.

RAGFlow v1.0 Go OSS versus Enterprise federation; current entitlement/configuration unresolved · Source ↗ · Vendor-maintainer Enterprise SSO statement ↗ · Reviewed 2026-11-20

Sources checked — unresolved · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

The v1.0.0 Compose file includes a separate dependency configuration and reads its image selection from the release environment. Use the matching release configuration; this artifact does not establish a migration path or compatibility for older provider packages.

Upstream v1.0.0 Compose; not evidence of compatibility with the listed 0.x provider packages · Deployment artifact ↗ (v1.0.0) · Versioned RAGFlow 1.0.0 quickstart ↗ · Reviewed 2026-11-14

Documented · Editor reviewed.

Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing

The 1.0 quickstart recommends a starting point of 4 CPU cores, 16 GB RAM and 50 GB free disk. Models, document engines and concurrency can require more; this does not size the older third-party cloud packages.

Upstream 1.0 quickstart; provider packages may target 0.x · Source ↗ · Reviewed 2026-11-14

Documented · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

The reviewed upstream core is Apache-2.0 licensed. Optional services, bundled dependencies, commercial distributions and support can have separate terms. This records the source licence, not an infrastructure or operating-cost estimate. Model weights and external model APIs require their own review.

Upstream core licence; commercial features, support and hosting priced separately · Source ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence

The publisher-designated GitHub release checked was v1.0.0, published 2026-11-06. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package.

Upstream infiniflow/ragflow release record; commercial editions and deployment packages may differ · Source ↗ · Reviewed 2026-11-14

Documented · Editor reviewed.

Show all fields (7 not researched)
Marketplace delivery
Not researched Supply a public source.
Cloud commitment eligibility
Not researched Supply a public source.
SCIM provisioning
Not researched Supply a public source.
Compliance attestations
Not researched Supply a public source.
Security controls
Not researched Supply a public source.
Air-gapped operation
Not researched Supply a public source.
Operating cost estimate
Not researched Supply a public source.

Scope & considerations

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 & maintenance

Current release notes document continued 2026 releases and dozens of named contributors across successive versions; the upstream README records a 1.0.0 release on 6 November 2026.

Category fit

AI applications & RAG
Document understanding, knowledge ingestion and retrieval-augmented/agentic question answering with configurable LLM, embedding and reranking endpoints.
AI tools & infrastructure
Self-hosted document ingestion, retrieval and context infrastructure for AI applications.

Compare within AI applications & RAG

  • AnythingLLM DockerSelf-hosted application for document-grounded AI chat, retrieval and agents.
    • AWS
    • Google Cloud
    • Railway
    Customer-operated · Open Source / Open Core
  • Dify Self-HostedVisual AI application and RAG workflow platform available as a self-hosted container stack.
    • Alibaba Cloud
    Customer-operated · Source Available
  • Langflow Self-HostedVisual AI workflow and agent builder with Docker and persistent PostgreSQL deployment.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Open Source / Open Core
  • LibreChat Self-HostedSelf-hosted multi-model AI chat, agent and retrieval platform with documented Railway and DigitalOcean deployments.
    • DigitalOcean
    • Railway
    Customer-operated · Open Source / Open Core
  • MaxKB Community EditionOpen-source knowledge-base, RAG and agent-workflow platform deployable into an Alibaba Cloud account.
    • Alibaba Cloud
    Customer-operated · Open Source / Open Core
  • Onyx Self-HostedSelf-hosted enterprise search and AI assistant platform with connectors and retrieval infrastructure.
    • AWS
    • Azure
    • Google Cloud
    • DigitalOcean
    Customer-operated · Open Source / Open Core
  • Open WebUI Self-HostedSelf-hosted AI chat and knowledge interface for local model servers and cloud APIs.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Source Available

These products address related workflows; read their category-fit notes before comparing scope. See all of AI applications & RAG →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • Community RAGFlow deployment on AWS ECS Fargate through stdapi.ai ↗ · AWS

      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.

      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.

    • cloudimg RAGFlow Azure VM deployment and operations guide ↗ · Azure

      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.

      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.

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

      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.

    • RAGFlow Community deployment on Alibaba Cloud Compute Nest ↗ · Alibaba Cloud

      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.

      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.

    • Community RAGFlow Railway application stack ↗ · Railway

      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.

      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.

    • Railway deployment image source and release pin ↗ · Railway

      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.

      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.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked
  5. Community & maintenance evidenceChecked

Suggest a correction · Back to directory