
# AI tools & infrastructure on Railway

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

Canonical page: https://launchinyourcloud.com/clouds/railway/ai-tools/
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.

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




## Arize Phoenix Self-Hosted

AI observability and evaluation server for traces, datasets and application experiments.

- Listing: https://launchinyourcloud.com/directory/phoenix/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, railway, render
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Elastic License 2.0; includes restrictions on providing the software as a hosted/managed service and on license-key circumvention. This is source-available.
- Licensing model: source-available
- Installation: Use the official self-hosted Docker/Compose or Kubernetes deployment instructions and configure persistent storage and instrumentation endpoints.
- Architecture: Customer-operated trace/evaluation application with persistent trace and dataset storage
- Operations: Customer manages trace capture, storage, authentication, retention, evaluation providers, backups and upgrades.
- Product website: https://arize.com/phoenix/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

The self-hosted product is distinct from commercial Arize offerings. Traces may contain prompts and outputs; evaluation jobs can call separately configured external model services even when trace storage is local.

Elastic License 2.0; includes restrictions on providing the software as a hosted/managed service and on license-key circumvention. This is source-available. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.

Customer-operated trace/evaluation application with persistent trace and dataset storage. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.


### Category fit

- ai-observability: AI trace collection, evaluation, datasets, experiments and prompt analysis for instrumented model applications.

- ai-tools: AI development and operations tooling for tracing and evaluation rather than a model-serving runtime.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://arize.com/docs/phoenix/self-hosting (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://arize.com/docs/phoenix/self-hosting (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://arize.com/docs/phoenix/self-hosting (checked 2026-11-12). 

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://arize.com/docs/phoenix/self-hosting (checked 2026-11-12). 

- render: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://arize.com/docs/phoenix/self-hosting (checked 2026-11-12). 


### Cloud deployment evidence

- Phoenix self-hosting deployment options (aws, azure, gcp, railway): https://arize.com/docs/phoenix/self-hosting
  The current Phoenix self-hosting index includes a Railway one-click template as well as AWS CloudFormation, Azure ARM and Google Cloud Run. These deploy the Phoenix application, not the separately licensed Arize AX product. A Railway project is customer-controlled while Railway manages its infrastructure.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Phoenix self-hosted Render Blueprint (render): https://arize.com/docs/phoenix/self-hosting
  The vendor self-hosting index offers a Render one-click Blueprint for Phoenix alongside its Railway, AWS, Azure and Google Cloud options. This is the self-hosted Phoenix application, separate from Arize AX; customer workspace control does not imply ownership of the platform infrastructure.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

Arize's June 2026 maintainer account describes actual participation outside the core team: it attributes OIDC authentication to users needing Keycloak/Cognito and credits contributors with expanding framework integrations and OpenInference. The upstream release history shows continuing maintenance. This concerns concrete community involvement rather than repository star counts; it does not certify any named customer's deployment model.

Reviewed 2026-11-10.

- Maintainer account of user-contributed authentication and integrations: https://arize.com/blog/phoenix-10k/

- Current Phoenix maintenance releases: https://github.com/Arize-ai/phoenix/releases

### Sources

- Official installation and runtime: https://arize.com/docs/phoenix/self-hosting

- Upstream project and capabilities: https://github.com/Arize-ai/phoenix

- Current upstream license: https://raw.githubusercontent.com/Arize-ai/phoenix/main/LICENSE

### Licensing sources

- https://raw.githubusercontent.com/Arize-ai/phoenix/main/LICENSE

### Infrastructure sources

- https://arize.com/docs/phoenix/self-hosting


### 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: Documented. Phoenix documents OAuth2 authorization-code login with OIDC provider discovery, configured alongside application authentication and secret settings. Configure the trusted provider, callback and account policy; client API keys remain a separate surface. Scope: Self-hosted Phoenix UI OAuth2/OIDC. Source: https://arize.com/docs/phoenix/deployment/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 upstream Phoenix repository provides self-hosting/container documentation for the observability server. Match persistence and authentication settings to the chosen release; instrumented applications and model services remain separate. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://github.com/arize-ai/phoenix (reviewed 2026-11-14). Deployment artifact: https://github.com/arize-ai/phoenix. Artifact reference: repository default branch (moving; select matching application release).

- Minimum footprint / sizing: Sources checked — unresolved. The self-hosting guide documents deployment, storage/database configuration and trace retention, but does not establish a complete CPU/RAM minimum for a specified workload. Size span ingestion, retention, database, evaluation/model dependencies and redundant service instances. Hosted Arize AX sizing is a separate offering. Scope: Phoenix self-hosted application and data services; numeric workload sizing unresolved. Source: https://arize.com/docs/phoenix/self-hosting/deploying-phoenix.md (reviewed 2026-11-20).

- License pricing: Documented. Phoenix uses Elastic License 2.0, including limits on offering substantial hosted/managed functionality and bypassing licence controls. This is not an unrestricted Apache/MIT licence or a hosted-service price; review commercial service/support terms separately. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/Arize-ai/phoenix/main/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The publisher-designated GitHub release checked was arize-phoenix-v21.1.0, published 2026-11-13. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package. Scope: Upstream Arize-ai/phoenix release record; commercial editions and deployment packages may differ. Source: https://github.com/Arize-ai/phoenix/releases/tag/arize-phoenix-v21.1.0 (reviewed 2026-11-14).







## Langfuse Self-Hosted

Self-hosted LLM observability, evaluations and prompt-management platform.

- Listing: https://launchinyourcloud.com/directory/langfuse/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, railway, render
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT core; designated enterprise directories and add-on capabilities use separate license terms or keys.
- Licensing model: open-source
- Installation: Docker Compose for a single VM; Helm/Kubernetes and official AWS, Azure and Google Cloud Terraform modules.
- Architecture: Application and worker containers with PostgreSQL, ClickHouse, Redis/Valkey and object storage
- Operations: Customer operates the deployment, persistence, access policies, retention, backups and scaling.
- Product website: https://langfuse.com/
- Source review: 2026-11-18; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Traces can contain prompts, outputs and other sensitive application data, so configure capture and retention deliberately. Self-hosted trace storage does not move the underlying application model into the same account. Optional model-based evaluators or the gateway use configured providers, which may be external. The single-VM Compose example does not provide production high availability or backups. Langfuse v4.82.0 fixes an SSRF path in GitHub Enterprise SSO and moves audit logs to ClickHouse. Review outbound SSO connectivity and audit-log storage during upgrade.

The main codebase uses MIT terms outside designated enterprise directories. Enterprise code requires a separate valid license, so the directory treats the combined product as open-core.

The documented deployment uses application/worker containers and persistent database, cache and object-storage services. Host/cluster capacity and database operations remain part of the self-hosted system.


Cloud evidence scope: Documented provider-specific deployment

### Category fit

- ai-observability: LLM/agent tracing, evaluation and prompt management deployed with customer-controlled storage. Evaluation and optional gateway providers must be scoped independently.

- ai-tools: Self-hosted LLM observability, evaluations and prompt-management platform.

- observability: Application/model traces and experiment visibility for AI workloads. Infrastructure metrics and broader application monitoring require separately selected tooling.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://langfuse.com/self-hosting/deployment/aws (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://langfuse.com/self-hosting/deployment/azure (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://langfuse.com/self-hosting/deployment/gcp (checked 2026-11-12). 

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://langfuse.com/self-hosting/deployment/railway (checked 2026-11-12). 

- render: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://langfuse.com/self-hosting/deployment/render (checked 2026-11-12). 


### Cloud deployment evidence

- Langfuse customer cloud deployment on AWS (aws): https://langfuse.com/self-hosting/deployment/aws
  The vendor documents deployment of the self-hosted Langfuse application and its backing services in the customer account or project, including provider-specific infrastructure. This is distinct from Langfuse Cloud; database, object storage, model calls and enterprise licensing must be configured for the chosen topology.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Langfuse customer cloud deployment on Azure (azure): https://langfuse.com/self-hosting/deployment/azure
  The vendor documents deployment of the self-hosted Langfuse application and its backing services in the customer account or project, including provider-specific infrastructure. This is distinct from Langfuse Cloud; database, object storage, model calls and enterprise licensing must be configured for the chosen topology.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Langfuse customer cloud deployment on Google Cloud (gcp): https://langfuse.com/self-hosting/deployment/gcp
  The vendor documents deployment of the self-hosted Langfuse application and its backing services in the customer account or project, including provider-specific infrastructure. This is distinct from Langfuse Cloud; database, object storage, model calls and enterprise licensing must be configured for the chosen topology.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Langfuse v3 community Railway deployment (railway): https://langfuse.com/self-hosting/deployment/railway
  The vendor documents a community-maintained Railway template for the complete Langfuse v3 stack. This establishes that version-specific application deployment; the same page explicitly distinguishes the v4 alternatives. The vendor does not systematically test the community template. Review the template services, image tags, database timezones and upgrade path.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Langfuse v4 community Render Blueprint (render): https://langfuse.com/self-hosting/deployment/render
  The vendor documents a community-maintained v4 Blueprint with separate web and worker services, PostgreSQL, Key Value, ClickHouse and MinIO. It creates the full application in the customer Render workspace. Review service plans, persistent disks, object-storage exposure and recovery procedures; community support is best-effort.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Docker Compose on a VM: https://langfuse.com/self-hosting/deployment/docker-compose

- Self-hosting architecture and provider dependencies: https://langfuse.com/self-hosting

- AWS account Terraform deployment: https://langfuse.com/self-hosting/deployment/aws

- Azure account Terraform deployment: https://langfuse.com/self-hosting/deployment/azure

- Google Cloud account Terraform deployment: https://langfuse.com/self-hosting/deployment/gcp

- Core and enterprise licensing: https://github.com/langfuse/langfuse/blob/main/LICENSE

- Licensing and edition terms: https://github.com/langfuse/langfuse/blob/main/ee/LICENSE

- Langfuse v3 community Railway deployment: https://langfuse.com/self-hosting/deployment/railway

- Langfuse v4 community Render Blueprint: https://langfuse.com/self-hosting/deployment/render

- Langfuse v4.82.0 release: https://github.com/langfuse/langfuse/releases/tag/v4.82.0

### Licensing sources

- https://github.com/langfuse/langfuse/blob/main/LICENSE

- https://github.com/langfuse/langfuse/blob/main/ee/LICENSE

### Infrastructure sources

- https://langfuse.com/self-hosting/deployment/docker-compose

- https://langfuse.com/self-hosting/deployment/aws

- https://langfuse.com/self-hosting/deployment/azure

- https://langfuse.com/self-hosting/deployment/gcp


### 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 guide documents OAuth/OIDC providers including Keycloak, Okta, Entra ID and a custom issuer. Configure account linking, email verification and access policy; SCIM and separately licensed enterprise features require their own review. Scope: Self-hosted OAuth/OIDC sign-in. Source: https://langfuse.com/self-hosting/security/authentication-and-sso (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. Current advisory review: Langfuse v4.82.0 fixes a server-side request forgery path in GitHub Enterprise SSO. Upgrade to v4.82.0 or later and restrict outbound SSO connectivity. Scope: Upstream v4.82.0 release; the vendor did not publish an affected-version range in the reviewed note.. Source: https://github.com/langfuse/langfuse/releases/tag/v4.82.0 (reviewed 2026-11-18).

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The upstream Compose recipe defines application services and backing data services. Pin a compatible Langfuse release and review credentials, persistent storage and exposed ports. Scope: Upstream Compose recipe; supporting-service operations remain customer responsibilities. Source: https://github.com/langfuse/langfuse/blob/main/docker-compose.yml (reviewed 2026-11-14). Deployment artifact: https://github.com/langfuse/langfuse/blob/main/docker-compose.yml. Artifact reference: main (moving branch).

- Minimum footprint / sizing: Documented. The vendor recommends at least 2 CPUs and 4 GB RAM for application containers and at least two Web instances for HA. Worker, ClickHouse, PostgreSQL, Redis and blob storage capacity are additional. Confirm per-container resources and retention/ingestion volume rather than treating this as the whole-stack footprint. Scope: Langfuse Web/Worker resource recommendation; backing services additional. Source: https://langfuse.com/self-hosting/deployment/infrastructure/containers (reviewed 2026-11-20).

- License pricing: Documented. Core code is MIT licensed, while ee directories, including application and worker enterprise paths, use a separate enterprise licence. Optional commercial features and support need separate terms; underlying databases, object storage and model services are additional. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/langfuse/langfuse/main/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Langfuse v4.82.0 was published November 17, 2026. It fixes an SSRF path in GitHub Enterprise SSO and moves audit logs to ClickHouse. Scope: Upstream Langfuse self-hosted release. Source: https://github.com/langfuse/langfuse/releases/tag/v4.82.0 (reviewed 2026-11-18).




### Security and lifecycle reviews

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

- Langfuse GitHub Enterprise SSO SSRF fix (security-advisory): Langfuse v4.82.0 fixes a server-side request forgery path in GitHub Enterprise SSO. Scope: Upstream v4.82.0 release; the vendor did not publish an affected-version range in the reviewed note. Conditions: Requires the affected GitHub Enterprise SSO configuration and a reachable outbound target. Action: Upgrade to v4.82.0 or later and restrict outbound SSO connectivity. Source: https://github.com/langfuse/langfuse/releases/tag/v4.82.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.







## LiteLLM Proxy Self-Hosted

Self-hosted AI API gateway providing model routing, access controls and usage tracking.

- Listing: https://launchinyourcloud.com/directory/litellm/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, railway, render
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT outside the enterprise directory; enterprise code and features have separate license terms.
- Licensing model: open-source
- Installation: Official container image, Docker Compose or Kubernetes deployment; production infrastructure examples are documented.
- Architecture: Customer-operated gateway with optional PostgreSQL persistence and configured model endpoints
- Operations: Customer manages gateway availability, credentials, database, access policies, logs and upgrades, including pinning versions and verifying release artifacts with the documented version-appropriate Cosign method; model providers remain separate services.
- Product website: https://www.litellm.ai/
- Source review: 2026-11-19; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

The gateway forwards each request to its configured model provider. Self-hosting the proxy does not ensure prompts stay inside the account: external model APIs, guardrail services and logging integrations can receive data. Use appropriate self-hosted inference endpoints and explicitly review outbound integrations when required. For release integrity, release images and the Helm chart starting with v1.111.0-dev.3 use keyless Cosign signatures bound to LiteLLM's release workflow; earlier releases require the documented historical public keys. The October 21 incident affected PyPI v1.107.0 and Docker Hub/GHCR v1.107.0 plus mutable latest, main-latest and main-stable tags during the documented exposure windows. Check the incident's artifact digests and remediation instructions; the compromised images carried valid historical signatures, so signature verification alone does not establish safety. LiteLLM v1.110.0 changes authentication, guardrail, accounting, and S3 behavior. The 1.108.11 LTS patch also fixes Bedrock guarded_text handling and restricts os.environ team settings to proxy administrators; review both the selected release line and existing incident-response or image-signing guidance. LiteLLM v1.108.12 LTS fixes tool_policy allowing blocked /v1/messages tool names longer than 64 characters. The standard v1.110.1 UI image changes to slim nginx and removes curl while retaining wget and nc, so retest health probes and scripts that assume curl.

The gateway has an MIT-licensed base and separately licensed enterprise features. The enterprise documentation describes a license key enabling restricted capabilities in the gateway, beyond paid hosting or support alone.

The gateway runs as provisioned application containers or Kubernetes workloads; persistent key/spend storage can use PostgreSQL. Inference compute is a separate dependency rather than included in the gateway.


### Category fit

- ai-inference-gateways: Self-hosted model API gateway for routing, virtual keys, spend tracking and policy enforcement. It routes inference requests; it is not an inference engine for all supported models.

- ai-tools: Self-hosted AI API gateway providing model routing, access controls and usage tracking.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.litellm.ai/docs/proxy/deploy (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.litellm.ai/docs/proxy/deploy (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.litellm.ai/docs/proxy/deploy (checked 2026-11-12). 

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.litellm.ai/docs/proxy/deploy (checked 2026-11-12). 

- render: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.litellm.ai/docs/proxy/deploy (checked 2026-11-12). 


### Cloud deployment evidence

- LiteLLM production deployment (aws, azure, gcp): https://docs.litellm.ai/docs/proxy/deploy
  Official production guidance covers EKS, AKS and GKE with Helm, plus Terraform on AWS and Google Cloud. The proxy, database and Redis deployment is separate from the model services it calls.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- LiteLLM Railway and Render deployment options (railway, render): https://docs.litellm.ai/docs/proxy/deploy
  The current upstream deployment guide supplies Railway and Render deployment buttons in addition to its EKS/AKS/GKE instructions, followed by readiness and Admin UI verification. These are customer application deployments on managed platforms; configure persistent data, secrets and external model-provider endpoints separately.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Production deployment: https://docs.litellm.ai/docs/proxy/deploy

- Gateway request flow and functionality: https://docs.litellm.ai/docs/simple_proxy

- MIT core and enterprise exception: https://github.com/BerriAI/litellm/blob/main/LICENSE

- Licensing and edition terms: https://docs.litellm.ai/docs/enterprise

- Supply-chain incident and Cosign verification guidance: https://docs.litellm.ai/blog/security-incident-oct-21-2026

- Canonical LiteLLM incident investigation: https://docs.litellm.ai/blog/security-incident-oct-21-2026-attack-chain

- LiteLLM v1.110.0 release: https://github.com/BerriAI/litellm/releases/tag/v1.110.0

- LiteLLM v1.108.11 LTS release: https://github.com/BerriAI/litellm/releases/tag/v1.108.11

- LiteLLM v1.110.1: https://github.com/BerriAI/litellm/releases/tag/v1.110.1

- LiteLLM v1.108.12 LTS: https://github.com/BerriAI/litellm/releases/tag/v1.108.12

### Licensing sources

- https://github.com/BerriAI/litellm/blob/main/LICENSE

- https://docs.litellm.ai/docs/enterprise

### Infrastructure sources

- https://docs.litellm.ai/docs/proxy/deploy


### 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: Edition-dependent. The Admin UI documents OIDC SSO. From 1.76.0, it is free for up to five users; larger deployments require an Enterprise licence. Configure issuer, callbacks, roles and database/master-key prerequisites. This is Admin UI identity, distinct from model API virtual keys. Scope: LiteLLM Admin UI OIDC; user-count/Enterprise entitlement applies. Source: https://docs.litellm.ai/docs/proxy/admin_ui_sso (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. Release images and Helm charts use keyless Cosign from v1.111.0-dev.3; verify the documented workflow identity and issuer. Earlier releases use historical keys. The October 21 v1.107.0 compromise also affected mutable image tags; compare digests and exposure windows because affected images had valid historical signatures. Follow the incident remediation guidance for executed artifacts. Current advisory review: LiteLLM 1.108.11 LTS fixes Bedrock guarded_text handling and restricts os.environ team settings to proxy administrators. Upgrade the selected release line and recheck guardrail output and proxy-administrator permissions. Current review: v1.108.12 LTS fixes tool_policy allowing a /v1/messages request through when a blocked tool name exceeded 64 characters. Upgrade the maintained LTS line and retest tool-policy enforcement. Scope: LiteLLM 1.108 LTS /v1/messages tool_policy; standard and other maintained lines require their own release review. Source: https://github.com/BerriAI/litellm/releases/tag/v1.108.12 (reviewed 2026-11-19). Supporting source: Prior security-controls source — https://github.com/BerriAI/litellm/releases/tag/v1.108.11. Supporting source: Canonical incident investigation — https://docs.litellm.ai/blog/security-incident-oct-21-2026-attack-chain. Supporting source: Prior security-controls source — https://docs.litellm.ai/blog/security-incident-oct-21-2026.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official Helm guide documents Kubernetes installation and configurable database/secret settings. Select matching chart/image versions and review the separate scaling and production-readiness guidance. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://docs.litellm.ai/docs/proxy/deploy/helm (reviewed 2026-11-14).

- Minimum footprint / sizing: Documented. The current production guide starts load testing at 1 vCPU and 4 GiB per worker, preferably one worker per Kubernetes pod. Memory depends on queued requests, payloads, stream duration and logging. PostgreSQL, Redis for multiple workers/instances, HA and model inference are additional. Scope: Gateway per-worker load-test starting point; backing services and inference excluded. Source: https://docs.litellm.ai/docs/proxy/prod (reviewed 2026-11-20).

- License pricing: Documented. Core code outside litellm/enterprise is MIT licensed; the enterprise directory has separate terms. Enterprise features and support need separate entitlement and pricing. Upstream model APIs, infrastructure and operating labour are additional. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/BerriAI/litellm/main/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. LiteLLM v1.110.1 was published November 19, 2026. It refreshes the Wolfi base and changes the UI image to slim nginx, removing curl. The maintained v1.108.12 LTS line fixes a tool_policy bypass for blocked tool names longer than 64 characters. Scope: Upstream LiteLLM standard release; select and maintain either the standard or LTS line. Source: https://github.com/BerriAI/litellm/releases/tag/v1.110.1 (reviewed 2026-11-19). Supporting source: Prior reviewed release context — https://github.com/BerriAI/litellm/releases/tag/v1.110.0. Supporting source: LiteLLM v1.108.11 LTS — https://github.com/BerriAI/litellm/releases/tag/v1.108.11. Supporting source: v1.108.12 LTS security fix — https://github.com/BerriAI/litellm/releases/tag/v1.108.12.




### Security and lifecycle reviews

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

- LiteLLM LTS proxy security fixes (security-advisory): LiteLLM 1.108.11 LTS fixes Bedrock guarded_text handling and restricts os.environ team settings to proxy administrators. Scope: LiteLLM 1.108 LTS line; standard-line deployments should use their corresponding maintained release. Conditions: Applicability depends on Bedrock guardrails and team-setting permissions. Action: Upgrade the selected release line and recheck guardrail output and proxy-administrator permissions. Source: https://github.com/BerriAI/litellm/releases/tag/v1.108.11; reviewed 2026-11-18.

- LiteLLM 1.108.12 LTS tool-policy fix (security-advisory): LiteLLM 1.108.12 LTS prevents blocked tool names longer than 64 characters from bypassing tool_policy on /v1/messages. Scope: LiteLLM 1.108 LTS /v1/messages tool-policy enforcement. Conditions: The request must use a blocked tool name longer than 64 characters. Action: Upgrade the maintained LTS line to 1.108.12 or later and retest tool-policy enforcement. Source: https://github.com/BerriAI/litellm/releases/tag/v1.108.12; reviewed 2026-11-19.




## OpenSearch

Distributed search and analytics engine with vector retrieval, operational-data analysis and OpenSearch Dashboards visualizations.

- Listing: https://launchinyourcloud.com/directory/opensearch/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for upstream OpenSearch. Separately operated managed services and connected model or data services have their own terms.
- Licensing model: open-source
- Installation: Run official Docker images and customize the documented Docker Compose examples; native package and tarball installations are also documented.
- Architecture: Customer-operated distributed cluster with index shards and replicas on persistent storage, plus optional Dashboards and ingestion components
- Operations: Customer manages cluster sizing, storage, shard and replica layout, TLS, users and roles, ingestion, snapshots, monitoring and upgrades.
- Product website: https://opensearch.org/
- Source review: 2026-11-18; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Sample deployments and demo security settings require production configuration. Official images distributed through Amazon ECR are not evidence of an AWS-specific deployment. The listing covers self-operated OpenSearch; Amazon OpenSearch Service and other managed services are separate delivery models. Embeddings and AI connectors can involve external models or services. OpenSearch 3.10.0 removes experimental Views and macOS x64 archives and fixes remote-store data-loss or stall paths, bulk-index corruption, heap leaks, snapshot queue stalls, remote-translog issues, and OOM behavior. Validate plugins, Dashboards, and storage recovery before upgrading.

The reviewed upstream project uses Apache License 2.0. This classification covers the upstream software; third-party components and separately operated services retain their own terms.

Official Docker images run OpenSearch nodes and Dashboards on compatible container hosts. Persistent index storage and host memory and kernel settings are operational requirements; distribution through a cloud registry does not establish a provider deployment badge.


### Category fit

- databases-vector: Indexes and searches vectors alongside metadata, with lexical, nearest-neighbor, semantic and hybrid retrieval. Embedding generation requires an appropriate configured model or externally generated vectors.

- data-analytics: Distributed search and aggregation engine with OpenSearch Dashboards for exploring and visualizing indexed data.

- observability: Search and analytics over ingested operational data, including log analysis and monitoring; collection, ingestion and dashboard configuration remain deployment work.

- ai-tools: Vector storage, semantic search and retrieval for AI applications and RAG. Embedding generation and model connectors have separately configured runtimes and data flows.

### Deployment boundaries


- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://railway.com/deploy/opensearch-analytics (checked 2026-11-12). 


### Cloud deployment evidence

- Self-operated OpenSearch and Dashboards on Railway (railway): https://railway.com/deploy/opensearch-analytics
  The community recipe deploys OpenSearch 3 and Dashboards as customer-project services, with the search API on private networking. Its wrappers derive from upstream OpenSearch images. Review node count, heap/storage sizing, security plugin configuration, TLS and backups; this is separate from Amazon OpenSearch Service and does not imply high availability.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

The OpenSearch Software Foundation is organized under the Linux Foundation. Official release records show OpenSearch 3.9.0 released on 29 September 2026 and continuing maintenance planning. Project case studies describe production adoption by Atlassian, LINE and other organizations; managed-service case studies demonstrate project adoption rather than proving self-hosted account boundaries.

Reviewed 2026-11-10.

- OpenSearch Software Foundation: https://opensearch.org/foundation/

- Current releases and maintenance policy: https://opensearch.org/releases/

- Current released artifacts: https://opensearch.org/downloads/

- Named production case studies: https://opensearch.org/case-studies/

### Sources

- OpenSearch Core capabilities and architecture: https://opensearch.org/platform/opensearch-core/

- Vector search documentation: https://docs.opensearch.org/latest/vector-search/

- Official Docker installation: https://docs.opensearch.org/latest/install-and-configure/install-opensearch/docker/

- Security demo configuration: https://docs.opensearch.org/latest/security/configuration/demo-configuration/

- Release downloads and Apache-2.0 licensing: https://opensearch.org/downloads/

- Upstream Apache-2.0 license: https://github.com/opensearch-project/OpenSearch/blob/main/LICENSE.txt

- OpenSearch 3.10.0 release: https://github.com/opensearch-project/OpenSearch/releases/tag/3.10.0

### Licensing sources

- https://github.com/opensearch-project/OpenSearch/blob/main/LICENSE.txt

### Infrastructure sources

- https://docs.opensearch.org/latest/install-and-configure/install-opensearch/docker/

- https://opensearch.org/platform/opensearch-core/


### 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: Documented. The Security plugin supports the SAML 2.0 browser SSO profile, primarily for OpenSearch Dashboards. This is not a general authentication method for every direct OpenSearch client/API call. Scope: OpenSearch Security plugin and Dashboards browser login. Source: https://docs.opensearch.org/latest/security/authentication-backends/saml/ (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The Docker installation guide provides official images and Compose examples. Configure the required administrator password, persistent data and security settings; demo certificates/settings are not a production security baseline. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://docs.opensearch.org/latest/install-and-configure/install-opensearch/docker/ (reviewed 2026-11-14).

- Minimum footprint / sizing: Sources checked — unresolved. The install guide sets a default 1-GB JVM heap and recommends allocating about half of system RAM to heap. It does not establish one complete production minimum: data/index size, roles, replicas, ingestion, Dashboards, vectors and storage performance must be sized separately. A JVM default is not HA capacity. Scope: Upstream JVM/install defaults; full production footprint unresolved. Source: https://docs.opensearch.org/latest/install-and-configure/install-opensearch/index/ (reviewed 2026-11-20).

- License pricing: Documented. The OpenSearch core is Apache-2.0 licensed. Plugins and bundled components require their own licence review; commercial support, managed Amazon OpenSearch Service, model services and infrastructure have separate prices. Scope: Upstream OpenSearch core licence; managed service pricing excluded. Source: https://raw.githubusercontent.com/opensearch-project/OpenSearch/main/LICENSE.txt (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. OpenSearch 3.10.0 was published November 18, 2026. It removes experimental Views and macOS x64 archives and contains material remote-store, indexing, heap, snapshot, translog, and OOM fixes; match OpenSearch Dashboards and plugins to 3.10. Scope: Upstream OpenSearch 3.10 release. Source: https://github.com/opensearch-project/OpenSearch/releases/tag/3.10.0 (reviewed 2026-11-18).







## 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).






