BYOAIK (Bring Your Own AI Key) is a directory of AI tools that run on your own API key.

RAGFlow

Open-source RAG engine with deep document understanding for grounded, cited document Q&A.

Website Source code

Category:
Document Analysis
Maintenance:
Actively developed (last commit today)
Pricing:
Open Source
Open source:
Yes (Apache-2.0)
Self-hostable:
Yes
Local-first:
Yes
Platforms:
Web, Self-hosted, Docker
AI providers (bring your own key):
OpenAI, Anthropic, Azure OpenAI, Google Gemini, DeepSeek, Groq, Mistral, Cohere, Perplexity, xAI Grok, Together AI, Ollama, Hugging Face, Custom / OpenAI-compatible
API key storage:
User controls deployment
Key risk level:
LOW
Trust score:
91/100

RAGFlow is a leading open-source Retrieval-Augmented Generation engine built on deep document understanding (OCR, layout and table parsing) that delivers grounded, citation-backed question answering over your documents, fused with agent capabilities. Users self-host via Docker and configure AI providers through an in-app Model providers page (avatar > Model providers), pasting their own API key and optional base URL. It supports 60+ model vendors, so end users bring their own keys for OpenAI, Anthropic, Azure OpenAI, DeepSeek, Groq, Mistral, Gemini, Cohere, Together, xAI, Perplexity, local Ollama/Xinference/LocalAI, and any OpenAI-compatible endpoint. A managed cloud tier (cloud.ragflow.io) also exists, but the self-hosted open-source build is fully BYOK.

Why this trust score (91/100)

Trust measures how the tool treats your API key and how much of that has been verified. It contains no popularity signal.

  • Key Safety 23/25: The key lives in a deployment you run yourself. Observed using the operating system keychain rather than a file.
  • Request Routing 17/20: Requests go straight from you to the AI provider.
  • Transparency 20/20: Source is public under Apache-2.0, so anyone can check how the key is handled.
  • Privacy 14/15: Local-first: it works without sending your data anywhere. Can be self-hosted, so the data path stays inside infrastructure you control.
  • Maintenance 10/10: Actively developed: commits within the last three months.
  • Verification Confidence 7/10: Key handling was found in the published source by BYOAIK's scanner.

What was checked

Verification tier SOURCE_VERIFIED, derived from the evidence below and not set by hand.

  • [REPORTED · RESEARCH] This listing was compiled by an AI-assisted research pass over the tool's public website, README and documentation. No person independently confirmed it.
  • [STRONG · SOURCE_SCAN] Uses the operating system keychain / credential store to hold the key. source
  • [CONFIRMED · SOURCE_SCAN] Ships a container definition, so it can be self-hosted on your own infrastructure. source
  • [STRONG · SOURCE_SCAN] Supports a local model backend, so it can run with no cloud provider key at all. source
  • [CONFIRMED · SOURCE_SCAN] Most recent commit 2026-08-14, about 0 month(s) ago. source

How your API key is handled

You self-host the app, so your API key lives in your own deployment. Requests are sent directly to the AI provider. Because it can be self-hosted, your key never has to touch a third-party backend.

Setup

Deploy it (Docker/compose), add your provider API key in the admin or environment config, then select models.