
# AI applications & RAG on Railway

Compare documented AI applications & RAG deployments on Railway, including operating responsibility, licensing and deployment evidence.

Canonical page: https://launchinyourcloud.com/clouds/railway/ai-applications-rag/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


## Provider guidance

- Account boundary: Railway workspace, project and environment; platform-managed infrastructure
- Provider group: application-platform
- Provider classification: Hosted application platform; a workspace is not a customer-owned underlying hyperscaler account. Source: https://docs.railway.com/projects (checked 2026-11-20).
- Network: Project/environment private networking with separately exposed public services
- Identity and access: Workspace/project access and scoped deployment tokens
- Installation guidance: Deploy application containers and data services into your project. Community templates require review of source images, credentials, volumes and release compatibility; they do not imply upstream vendor support.
- Guidance source: https://docs.railway.com/projects
- Guidance reviewed: 2026-11-12


### Project networking

Private networking connects services inside a project environment using encrypted tunnels and internal DNS. This project boundary does not give the customer ownership of the underlying infrastructure account.
Source: https://docs.railway.com/networking/private-networking (reviewed 2026-11-14).

The listings below have evidence for Railway. Read each cloud evidence note for the applicable package, edition and support qualifications.

3 listings.


## AnythingLLM Docker

Self-hosted application for document-grounded AI chat, retrieval and agents.

- Listing: https://launchinyourcloud.com/directory/anythingllm/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, gcp, railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT License for upstream AnythingLLM; model weights, connectors and provider services have separate terms.
- Licensing model: open-source
- Installation: Run the official Docker edition on a customer-operated host with persistent application storage and configured model/vector endpoints.
- Architecture: Customer-operated web application and document/retrieval storage with configurable inference providers
- Operations: Customer manages users, documents, persistent storage, model access, integration secrets, backups and upgrades.
- Product website: https://anythingllm.com/
- Source review: 2026-11-18; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

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.

MIT License for upstream AnythingLLM; model weights, connectors and provider services have separate terms. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.

Customer-operated web application and document/retrieval storage with configurable inference providers. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.


### Category fit

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

- ai-tools: Self-hosted AI application interface and retrieval/agent integrations; model inference is separately configured.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.anythingllm.com/installation-docker/overview (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.anythingllm.com/installation-docker/overview (checked 2026-11-12). 

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.anythingllm.com/installation-docker/overview (checked 2026-11-12). 


### Cloud deployment evidence

- AnythingLLM Docker installation overview (aws, gcp, railway): https://docs.anythingllm.com/installation-docker/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.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

Public release notes credit named contributors and new contributors across multiple releases, alongside an established open contribution process.

Reviewed 2026-11-10.

- Release maintenance and contributor credits: https://github.com/Mintplex-Labs/anything-llm/releases

- Community contribution process: https://github.com/Mintplex-Labs/anything-llm

### Sources

- Official installation and runtime: https://docs.anythingllm.com/installation-docker/overview

- Upstream project and capabilities: https://github.com/Mintplex-Labs/anything-llm

- Current upstream license: https://raw.githubusercontent.com/Mintplex-Labs/anything-llm/master/LICENSE

- AnythingLLM v1.20.0 release: https://github.com/Mintplex-Labs/anything-llm/releases/tag/v1.20.0

### Licensing sources

- https://raw.githubusercontent.com/Mintplex-Labs/anything-llm/master/LICENSE

### Infrastructure sources

- https://docs.anythingllm.com/installation-docker/overview


### Buyer diligence


Research coverage: 6/12 fields (50%); 6 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The self-hosted Docker configuration offers Simple SSO passthrough: a trusted application uses an API key to issue short-lived single-use login links for existing users. It requires multi-user mode and a configured admin. This is a bespoke integration, not native SAML/OIDC federation; the vendor recommends internally exposed instances. Scope: Docker Simple SSO passthrough; not standards-based federation. Source: https://docs.anythingllm.com/configuration (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. Current advisory review: AnythingLLM v1.20.0 hardens embed history, extension API-key authorization, workspace-agent access, password recovery, framing, and document-tool downloads. Upgrade the server and extension to compatible 1.20+ releases and review optional MCP identity forwarding. Scope: Upstream v1.20.0 release notes; no consolidated affected-version range is asserted.. Source: https://github.com/Mintplex-Labs/anything-llm/releases/tag/v1.20.0 (reviewed 2026-11-18).

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The Docker guide documents a prebuilt application image or source-built Compose setup. Persistent storage and user permissions must be configured; local model/vector endpoints and their resources are separate. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://docs.anythingllm.com/installation-docker/local-docker (reviewed 2026-11-14).

- Minimum footprint / sizing: Documented. The Docker requirements list 2 GB RAM, a two-core CPU with AVX2 and 5 GB storage as a small starting profile. Model inference, embeddings, vector storage, documents and concurrency can require much more; verify AVX2 passthrough on virtual machines. This is not an HA or 1-TB production recommendation. Scope: Self-hosted Docker baseline; model services, data and HA additional. Source: https://docs.anythingllm.com/installation-docker/system-requirements (reviewed 2026-11-20).

- License pricing: Documented. The reviewed upstream core is MIT 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. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/Mintplex-Labs/anything-llm/master/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. AnythingLLM v1.20.0 was published November 17, 2026. It includes access and session hardening plus MCP identity forwarding and timeout changes; keep server and extension versions compatible. Scope: Upstream AnythingLLM self-hosted release. Source: https://github.com/Mintplex-Labs/anything-llm/releases/tag/v1.20.0 (reviewed 2026-11-18).




### Security and lifecycle reviews

Selected editorial reviews only; no flag does not mean safe or supported.

- AnythingLLM 1.20.0 access hardening (security-advisory): AnythingLLM v1.20.0 hardens embed history, extension API-key authorization, workspace-agent access, password recovery, framing, and document-tool downloads. Scope: Upstream v1.20.0 release notes; no consolidated affected-version range is asserted. Conditions: Applicability depends on enabled embedding, extensions, agents, recovery, and document tools. Action: Upgrade the server and extension to compatible 1.20+ releases and review optional MCP identity forwarding. Source: https://github.com/Mintplex-Labs/anything-llm/releases/tag/v1.20.0; reviewed 2026-11-18.




## LibreChat Self-Hosted

Self-hosted multi-model AI chat, agent and retrieval platform with documented Railway and DigitalOcean deployments.

- Listing: https://launchinyourcloud.com/directory/librechat/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway, digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT
- Licensing model: open-source
- Installation: Official Railway one-click template or Docker on a DigitalOcean Ubuntu Droplet
- Architecture: Containerized web and API services with application databases, retrieval services and customer-configured model endpoints
- Operations: Customer manages the Railway project or DigitalOcean Droplet, application secrets, model credentials, data services, backups, scaling and upgrades. Railway operates its platform; Droplet users also maintain the operating system and Docker runtime.
- Product website: https://www.librechat.ai/
- Source review: 2026-11-15; cloud review: 2026-11-15; licensing review: 2026-11-15; infrastructure review: 2026-11-15

### Scope and qualifications

The Railway path runs in the customer's project on platform-managed infrastructure; the DigitalOcean path uses a customer-operated Droplet. External model, embedding, search and tool providers receive data according to customer configuration. Review generated secrets, public networking, persistent data services and image updates before production use.

LibreChat is MIT-licensed. The licenses and commercial terms of configured model providers, tools and external services are separate.

LibreChat runs persistent application, database and retrieval containers in a Railway project or on a DigitalOcean Droplet.


### Category fit

- ai-applications-rag: Provides self-hosted multi-model chat, agents, file-backed retrieval and tool use over customer-selected model and data services.

- ai-tools: Provides a self-hosted interface and orchestration layer for model endpoints, agents, MCP tools, authentication and administrative controls.

### Deployment boundaries


- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://www.librechat.ai/docs/remote/railway (checked 2026-11-15). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.librechat.ai/docs/remote/digitalocean (checked 2026-11-15). 


### Cloud deployment evidence

- LibreChat one-click deployment on Railway (railway): https://www.librechat.ai/docs/remote/railway
  LibreChat documents creating a Railway account, reviewing the template's three containers and environment variables, deploying the services and accessing the resulting LibreChat URL in the customer's Railway project.
  Source type: vendor-documentation; reviewed: 2026-11-15; vendor support: not-assessed.

- LibreChat deployment on DigitalOcean (digitalocean): https://www.librechat.ai/docs/remote/digitalocean
  The upstream guide creates an Ubuntu Droplet in the customer DigitalOcean project, configures a user and firewall, then links to the Docker installation steps. The example is for a small personal deployment, not a production sizing guarantee.
  Source type: vendor-documentation; reviewed: 2026-11-15; vendor support: not-assessed.


### Community and maintenance

LibreChat documents a community of hundreds of contributors and maintains its implementation in a public upstream repository. Contributor history establishes active project participation; it does not establish support for a specific Railway template release.

Reviewed 2026-11-15.

- LibreChat project and community: https://www.librechat.ai/about

- LibreChat contributor history: https://github.com/LibreChat-AI/LibreChat/graphs/contributors

### Sources

- LibreChat Railway deployment: https://www.librechat.ai/docs/remote/railway

- LibreChat project, self-hosting and MIT license: https://www.librechat.ai/about

- LibreChat upstream repository: https://github.com/LibreChat-AI/LibreChat

- LibreChat contributor history: https://github.com/LibreChat-AI/LibreChat/graphs/contributors

- LibreChat deployment on DigitalOcean: https://www.librechat.ai/docs/remote/digitalocean

### Licensing sources

- https://www.librechat.ai/about

### Infrastructure sources

- https://www.librechat.ai/docs/remote/railway

- https://www.librechat.ai/docs/remote/digitalocean


### Buyer diligence


Research coverage: 4/12 fields (33%); 4 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The official self-hosted authentication guide documents OAuth2/OpenID Connect and SAML, with separately configured LDAP and local accounts. Configure the selected provider, registration policy, account linking and administrator recovery; external model credentials are a separate authentication surface. Scope: Self-hosted LibreChat user authentication. Source: https://www.librechat.ai/docs/configuration/authentication (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The Railway guide describes its repository deploy button, three-container configuration and required environment variables. Review persistence and optional integrations before production; the one-click recipe does not establish a minimum production footprint. Scope: LibreChat Railway deployment guide; moving template and configured features. Source: https://www.librechat.ai/docs/remote/railway (reviewed 2026-11-16).

- Minimum footprint / sizing: Documented. The Docker guide lists 1 vCPU and 1 GiB RAM minimum for LibreChat containers, recommending at least 2 GB allocated to Docker with the default backing services. MongoDB, search, RAG/pgvector, storage and HA need sizing; locally hosted models require additional compute and often GPUs. Scope: Official Docker starting profile; model inference and production HA excluded. Source: https://www.librechat.ai/docs/local/docker (reviewed 2026-11-20).

- License pricing: Documented. The reviewed upstream core is MIT 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. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/danny-avila/LibreChat/main/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## RAGFlow

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

- Listing: https://launchinyourcloud.com/directory/ragflow/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, alibaba, railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for upstream RAGFlow; models, data assets and dependencies retain their own terms.
- Licensing model: open-source
- Installation: Versioned upstream Docker Compose, provider-specific VM packages or community deployment templates; select a path compatible with the intended RAGFlow release.
- Architecture: Customer-operated document/retrieval application with deployment-specific stateful storage and configured model services
- Operations: Customer manages document storage, indexing, app services, access controls, model endpoints, backups and upgrades.
- Product website: https://ragflow.io/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

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.

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.

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.


### Category fit

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

- ai-tools: Self-hosted document ingestion, retrieval and context infrastructure for AI applications.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/stdapi-ai/samples/tree/main/getting_started_ragflow (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudimg.co.uk/guides/ragflow-on-ubuntu-24-04-azure/ (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.techlatest.net/support/ragflow_support/gcp_gettingstartedguide/index.html (checked 2026-11-12). 

- alibaba: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.aliyun.com/en/compute-nest/use-cases/ragflow-community-edition-service-instance-deployment-document (checked 2026-11-12). 

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://railway.com/deploy/ragflow-ai (checked 2026-11-12). Source: https://github.com/gridalpha/ragflow-railway/blob/main/Dockerfile (checked 2026-11-12). 


### Cloud deployment evidence

- Community RAGFlow deployment on AWS ECS Fargate through stdapi.ai (aws): https://github.com/stdapi-ai/samples/tree/main/getting_started_ragflow
  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.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed. Edition: Community / upstream open-source; third-party distribution where noted. Versions: 0.26.4.

- cloudimg RAGFlow Azure VM deployment and operations guide (azure): https://www.cloudimg.co.uk/guides/ragflow-on-ubuntu-24-04-azure/
  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.
  Source type: third-party-package; reviewed: 2026-11-12; vendor support: not-assessed. Edition: Community / upstream open-source; third-party distribution where noted. Versions: 0.26.4.

- Techlatest RAGFlow VM deployment in a customer Google Cloud project (gcp): https://www.techlatest.net/support/ragflow_support/gcp_gettingstartedguide/index.html
  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.
  Source type: third-party-package; reviewed: 2026-11-12; vendor support: not-assessed. Edition: Community / upstream open-source; third-party distribution where noted.

- RAGFlow Community deployment on Alibaba Cloud Compute Nest (alibaba): https://help.aliyun.com/en/compute-nest/use-cases/ragflow-community-edition-service-instance-deployment-document
  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.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed. Edition: Community / upstream open-source; third-party distribution where noted.

- Community RAGFlow Railway application stack (railway): https://railway.com/deploy/ragflow-ai
  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.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed. Edition: Community / upstream open-source; third-party distribution where noted. Versions: 0.27.1.

- Railway deployment image source and release pin (railway): https://github.com/gridalpha/ragflow-railway/blob/main/Dockerfile
  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.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed. Edition: Community / upstream open-source; third-party distribution where noted. Versions: 0.27.1.


### Community and 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.

Reviewed 2026-11-10.

- Current releases and contributors: https://github.com/infiniflow/ragflow/releases

- Release chronology and deployment instructions: https://raw.githubusercontent.com/infiniflow/ragflow/main/README.md

### Sources

- Upstream project and capabilities: https://github.com/infiniflow/ragflow

- Current upstream license: https://raw.githubusercontent.com/infiniflow/ragflow/main/LICENSE

- RAGFlow 1.0 release and migration requirements: https://ragflow.io/docs/v1.0.0/release_notes

### Licensing sources

- https://raw.githubusercontent.com/infiniflow/ragflow/main/LICENSE

### Infrastructure sources

- https://github.com/infiniflow/ragflow


### Buyer diligence


Research coverage: 5/12 fields (42%); 4 documented, 1 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. 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. Scope: RAGFlow v1.0 Go OSS versus Enterprise federation; current entitlement/configuration unresolved. Source: https://raw.githubusercontent.com/infiniflow/ragflow/v1.0.0/docker/README.md (reviewed 2026-11-20). Supporting source: Vendor-maintainer Enterprise SSO statement — https://github.com/infiniflow/ragflow/issues/15882.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. 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. Scope: Upstream v1.0.0 Compose; not evidence of compatibility with the listed 0.x provider packages. Source: https://github.com/infiniflow/ragflow/blob/v1.0.0/docker/docker-compose.yml (reviewed 2026-11-14). Deployment artifact: https://github.com/infiniflow/ragflow/blob/v1.0.0/docker/docker-compose.yml. Artifact reference: v1.0.0. Supporting source: Versioned RAGFlow 1.0.0 quickstart — https://ragflow.io/docs/v1.0.0/.

- Minimum footprint / sizing: Documented. 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. Scope: Upstream 1.0 quickstart; provider packages may target 0.x. Source: https://ragflow.io/docs/v1.0.0/ (reviewed 2026-11-14).

- License pricing: Documented. 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. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/infiniflow/ragflow/main/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. 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. Scope: Upstream infiniflow/ragflow release record; commercial editions and deployment packages may differ. Source: https://github.com/infiniflow/ragflow/releases/tag/v1.0.0 (reviewed 2026-11-14).






