How mintplex-labs/vector-admin works
Main components
• Frontend (React/Vite UI)
• Backend API (Node.js + Express + Prisma)
• Relational metadata store (Postgres/MySQL via Prisma)
• Vector database connectors (Pinecone, Chroma, Qdrant, Weaviate)
• Document-processor service (Python/Flask)
• Background workers (InngestJS functions)
• Telemetry (PostHog)
• Docker orchestration (docker-compose)
Relationships and data–flow
a. User → Frontend: browser requests UI (login, dashboards, CRUD on documents, connectors, RAG tests).
b. Frontend → Backend API: HTTP REST calls (auth, system settings, organizations, workspaces, documents, embeddings, jobs, RAG tests).
c. Backend → Relational DB: Prisma client for all metadata and user/organization/workspace/join tables.
d. Backend → Vector DBs: through “utils/vectordatabases/providers/*” modules to perform search, insert, delete, copy, migrate embeddings.
e. Backend ↔ Document-processor: HTTP to Flask on port 8888 for text extraction, parsing, initial embedding.
f. Backend → Inngest: publish job events (addDocumentsJob, syncJobs, ragTestJobRun, etc.).
g. Workers (Inngest functions) → Vector DBs: perform long-running tasks asynchronously (add, update, delete embeddings; clone, migrate, sync).
h. Backend & Workers → Telemetry: calls to PostHog to record usage events.
Architectural patterns
• Monorepo with four services and shared config (env, .nvmrc, linting).
• Microservices for specialized tasks: Flask for doc processing, InngestJS for background jobs.
• Layered backend: endpoints → models → utils → vectordb providers.
• Plugin-style vector DB connectors for extensibility.
• API-driven UI with React Context for auth and state.
• Docker Compose for full-stack local deployment.
Relevant technologies
• Frontend: React, Vite, TypeScript, Tailwind CSS
• Backend: Node.js, Express, Prisma ORM, JWT auth, Multer for file uploads
• Doc-processor: Python 3.9+, Flask, various parser scripts
• Workers: InngestJS, Node.js functions
• Databases: Postgres (or MySQL) via Prisma; Pinecone, ChromaDB, Qdrant, Weaviate
• Telemetry: PostHog API
Don’t forget these details
• Meta-data store: Prisma schema.prisma with migrations folder.
• Env management: .env.example files in each service.
• Authentication flows: auth endpoint issuing JWT, React AuthContext.
• File upload path: Multer → storage/settings.json.
• Background job examples: “createRagTestJobRun” → runs RAG test and writes results back to relational DB.
• Vector DB providers folder, demonstrating plugin approach.