OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
RAG & Knowledge Systems

Docsflow

Docsflow is a multi-tenant document intelligence application and RAG reference architecture. It gives each team a separate workspace for uploading files, searching them, and asking questions answered with source citations and confidence scores. Its documented stack includes Next.js, TypeScript, Supabase, Pinecone and Clerk, and its repository describes hybrid retrieval, model failover and a public hallucination bench

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

Docsflow — OpenViST project profile in RAG & Knowledge Systems.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use Docsflow when a team needs document-grounded question answering with inspectable citations, or when evaluating a documented multi-tenant RAG implementation.

Who it is for

  • Teams that need to search shared documents and trace generated answers to source passages.
  • Developers exploring a multi-tenant RAG application architecture or its hallucination benchmark.

Documented uses

  • Upload common office, PDF, image and text files into a team workspace.
  • Ask natural-language questions across uploaded documents and inspect cited passages.
  • Separate team workspaces and assign workspace roles and access levels.
  • Study hybrid retrieval, multi-layer tenant isolation and model failover in a RAG reference architecture.
Before you choose

Requirements & limits

The README links a live demo and documents a local setup route. Local setup requires API keys for Clerk, Supabase, Pinecone, OpenRouter and Stripe. The repository is MIT-licensed.

  • Hybrid retrieval combines vector similarity and BM25 keyword matching using Reciprocal Rank Fusion.
  • The documented design uses row-level security, tenant-specific Pinecone namespaces, Clerk session context and subdomain routing for isolation.
  • The README describes four-model LLM failover and confidence-based abstention; these are project-described design features, not independent performance findings.
  • The application stack has several external service dependencies, including authentication, database, vector storage, model access, file storage and billing.
  • The repository is useful both as an application reference and as a documented RAG architecture; its benchmark is described as public.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Prepare a local Docsflow development environment

Set up the repository and configure its documented environment variables before opening the local development server.

Before you start

  • Git, Node.js/npm, and the Docsflow repository
  • API keys for Clerk, Supabase, Pinecone, OpenRouter and Stripe

Steps

  1. Clone the repository and change into its directory.

  2. Run npm install.

  3. Copy .env.example to .env.local and fill in the required API keys.

  4. Run npm run dev and open http://localhost:3000.

Expected outcome

The README’s documented local setup sequence reaches a development server at localhost:3000.

Guide limitations

  • This guide covers setup only; it does not verify deployment or successful document ingestion and question answering.
  • The README lists external service keys as prerequisites but does not provide their costs or account terms.
Documentation 1 ↗
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
14 October 2026
Original website title
nicuk/docsflow · Official homepage title · retained in its source language
How we review sourcesSuggest a correction