WeKnora vs Supabase

Accepts heterogeneous document types (PDF, Word, images, structured data) and processes them through a document upload pipeline that extracts content, applies intelligent chunking strategies, and preserves semantic boundaries. Uses event-driven architecture with async task processing via Asynq to handle large-scale document ingestion without blocking the main service, storing chunks in a vector-indexed database with metadata tags for retrieval.

Unique: Combines event-driven async task processing (Asynq) with semantic-aware chunking and multi-tenant isolation, allowing organizations to ingest heterogeneous documents at scale without blocking chat interactions. The architecture separates document processing from retrieval, enabling independent scaling of ingestion pipelines.

vs alternatives: Outperforms single-threaded document processors by using async task queues and event-driven architecture, enabling concurrent ingestion of multiple documents while maintaining semantic chunk boundaries across diverse formats.

Implements a hybrid retrieval strategy combining vector similarity search (semantic) with keyword-based matching, using a configurable reranking engine to fuse results from both approaches. The retrieval pipeline queries the vector database for semantic matches and applies optional reranking (e.g., BM25, cross-encoder models) to surface the most relevant chunks before passing them to the LLM context window.

Unique: Decouples semantic and keyword retrieval into independent pipelines with pluggable reranking, allowing fine-grained control over fusion strategy per knowledge base. Supports multiple reranking backends (BM25, cross-encoder models) without requiring model retraining.

vs alternatives: More flexible than pure semantic search (handles domain jargon better) and more intelligent than keyword-only search (understands intent), with configurable reranking that adapts to domain-specific precision/recall tradeoffs.

Uses Asynq (Redis-backed task queue) to handle long-running operations asynchronously, including document processing, embedding generation, and knowledge graph construction. Tasks are enqueued with configurable retry policies, priority levels, and deadlines. The system provides task status tracking and allows users to monitor progress without blocking the API.

Unique: Decouples long-running operations from API request/response cycles using Asynq, enabling responsive user experience during heavy processing. Tasks support priority levels and configurable retry policies.

vs alternatives: More reliable than naive async (Asynq provides persistence and retry), more scalable than synchronous processing (operations don't block API), and more observable than fire-and-forget (task status is trackable).

Implements an event-driven architecture for chat interactions where user messages trigger events that flow through handlers (retrieval, reasoning, response generation). The pipeline supports streaming responses, allowing partial results to be sent to the client as they become available. Events are processed sequentially within a session to maintain conversation order.

Unique: Decouples chat processing into event-driven stages with streaming support, allowing partial results to be sent to clients immediately. Events flow through handlers sequentially per session, maintaining conversation order.

vs alternatives: More responsive than batch processing (streaming provides real-time feedback), more reliable than naive event handling (sequential processing per session), and more flexible than monolithic chat handlers (stages are composable).

Allows organizations to select and configure embedding models from multiple providers (OpenAI, Ollama, local models) at the knowledge base level. Embeddings are generated during document indexing and stored in the vector database. The system supports model switching with re-embedding of existing documents, and provides fallback mechanisms if the primary provider is unavailable.

Unique: Decouples embedding model selection from core RAG logic, allowing per-knowledge-base model configuration. Supports model switching with re-embedding, enabling experimentation without data loss.

vs alternatives: More flexible than fixed embedding models (supports multiple providers), more cost-efficient than always using premium models (can use cheaper alternatives), and more privacy-preserving than cloud-only embeddings (supports local models).

Allows documents and chunks to be tagged with custom labels, enabling hierarchical organization and filtering during retrieval. Tags are stored in the database and indexed for fast filtering. Queries can be scoped to specific tags, and retrieval results can be filtered by tag combinations. Tags support hierarchical relationships (parent-child).

Unique: Integrates tagging as a first-class feature in the indexing and retrieval pipeline, supporting both flat and hierarchical tag structures. Tags enable content organization without requiring separate document collections.

vs alternatives: More flexible than fixed document categories (tags are user-defined), more efficient than separate knowledge bases (single index with filtering), and more maintainable than prompt-based filtering (tags are explicit metadata).

Provides tools to evaluate RAG pipeline quality by measuring retrieval precision/recall, answer relevance, and end-to-end QA accuracy. Supports benchmark datasets and allows comparing performance across different retrieval strategies, embedding models, and LLM configurations. Evaluation results are stored and can be tracked over time.

Unique: Integrates evaluation as a built-in capability, allowing RAG quality to be measured and tracked over time. Supports comparing multiple configurations and storing historical results.

vs alternatives: More systematic than manual testing (automated metrics), more comprehensive than single-metric evaluation (multiple metrics), and more actionable than offline metrics (enables configuration comparison).

Implements a ReAct (Reasoning + Acting) agent engine that decomposes user queries into reasoning steps, selects appropriate tools (web search, knowledge base retrieval, MCP-integrated functions), executes them, and iterates until reaching a conclusion. The agent maintains conversation context across multiple turns, uses dependency injection to wire tools dynamically, and supports both synchronous and streaming responses.

Unique: Combines ReAct reasoning with dependency-injected tool orchestration and multi-turn session management, allowing agents to reason across heterogeneous data sources (KB, web, MCP tools) while maintaining conversation context. Supports both streaming and batch reasoning modes.

vs alternatives: More transparent and debuggable than black-box agent frameworks (reasoning steps are visible), more flexible than fixed RAG pipelines (can adapt strategy per query), and more cost-efficient than multi-turn LLM calls by batching reasoning and retrieval.

Executes SQL queries against Supabase PostgreSQL instances through the Model Context Protocol, translating natural language or structured query requests into parameterized SQL statements. Uses MCP's tool-calling interface to expose database operations as callable functions with schema validation, enabling LLM agents to perform CRUD operations, joins, and aggregations with automatic connection pooling and credential management through Supabase client SDK.

Unique: Exposes Supabase PostgreSQL as MCP tools with automatic credential injection from Supabase client SDK, eliminating manual connection string management and enabling seamless LLM-to-database queries within Claude or compatible agents

vs alternatives: Tighter integration than generic SQL MCP servers because it leverages Supabase's built-in authentication and connection pooling rather than requiring separate database credential configuration

Exposes Supabase Auth session state and user metadata through MCP tools, allowing agents to inspect current authentication context, retrieve user profiles, and trigger auth-related operations. Integrates with Supabase's JWT-based auth system to validate sessions and access user claims without re-authenticating, using the Supabase client's built-in session management.

Unique: Integrates Supabase's JWT-based auth system directly into MCP tool interface, allowing agents to inspect and act on auth state without managing separate credential stores or re-authentication flows

vs alternatives: More seamless than generic auth MCP servers because it leverages Supabase's built-in session management and avoids redundant credential passing between agent and auth system

Invokes Supabase Edge Functions (serverless TypeScript/JavaScript functions) through MCP tools, passing parameters and receiving results with optional streaming support. Uses Supabase's edge function HTTP API to trigger functions with automatic authentication headers and response parsing, enabling agents to execute custom business logic without embedding it in the agent itself.

Unique: Exposes Supabase Edge Functions as MCP tools with automatic authentication and response parsing, allowing agents to invoke custom serverless logic without managing HTTP clients or credential injection

vs alternatives: More integrated than generic HTTP MCP tools because it handles Supabase-specific authentication, error handling, and response formatting automatically

Subscribes to real-time changes on Supabase tables through MCP's event streaming interface, using Supabase's PostgreSQL LISTEN/NOTIFY mechanism to push INSERT, UPDATE, and DELETE events to agents. Maintains persistent WebSocket connections and filters events by table and row-level policies, enabling agents to react to database changes without polling.

Unique: Bridges Supabase's PostgreSQL LISTEN/NOTIFY real-time system with MCP's tool interface, enabling agents to subscribe to database changes without managing WebSocket connections or event serialization

vs alternatives: More efficient than polling-based approaches because it uses Supabase's native real-time infrastructure rather than repeated database queries

Manages files in Supabase Storage buckets through MCP tools, supporting upload, download, list, and delete operations with automatic authentication and path-based access control. Uses Supabase's S3-compatible storage API with built-in support for public/private buckets and signed URLs for temporary access, enabling agents to handle file I/O without managing cloud storage credentials.

Unique: Exposes Supabase Storage's S3-compatible API as MCP tools with automatic authentication and signed URL generation, eliminating the need for agents to manage cloud storage credentials or generate temporary access tokens

vs alternatives: More integrated than generic S3 MCP tools because it leverages Supabase's built-in bucket policies and authentication rather than requiring separate AWS credentials

Performs semantic similarity searches on vector embeddings stored in Supabase PostgreSQL using pgvector extension, translating natural language queries into embedding vectors and executing cosine/L2 distance searches. Integrates with embedding providers (OpenAI, Cohere) or uses pre-computed embeddings, enabling agents to retrieve semantically similar documents or records without full-text search limitations.

Unique: Integrates pgvector directly into MCP tools with automatic embedding generation and distance calculation, enabling agents to perform semantic search without managing separate vector database infrastructure

vs alternatives: More efficient than external vector databases (Pinecone, Weaviate) for Supabase users because it colocates embeddings with relational data, reducing network latency and simplifying data synchronization

Exposes Supabase database schema information through MCP tools, allowing agents to discover table structures, column types, constraints, and relationships without manual schema documentation. Queries PostgreSQL information_schema and Supabase metadata tables to dynamically generate schema descriptions, enabling agents to construct valid queries and understand data relationships.

Unique: Queries Supabase's PostgreSQL information_schema directly through MCP tools, enabling agents to dynamically discover and adapt to database schemas without pre-configured schema definitions

vs alternatives: More flexible than static schema definitions because it reflects live database state, including recent migrations or schema changes

Enforces Supabase Row-Level Security policies within agent queries, ensuring that agents can only access rows permitted by RLS rules defined in the database. Evaluates policies based on authenticated user context (JWT claims, user ID) and applies WHERE clause filters automatically, preventing unauthorized data access at the database layer rather than application layer.

Unique: Delegates authorization enforcement to PostgreSQL RLS policies rather than implementing authorization in agent code, ensuring that data access rules are centralized and cannot be bypassed by agent logic

vs alternatives: More secure than application-level authorization because RLS is enforced at the database layer, preventing accidental data leaks even if agent code has bugs