01 / AI research / Full-stack system
AI Research Copilot
Research. Retrieve. Reason. Remember.
A full-stack AI research workspace designed to help users explore the web, analyze documents, retrieve relevant knowledge, and build contextual answers with citations.
Contextual answer with citations and retrieved evidence.
The problem
Research is fragmented.
Answering a meaningful research question often means moving between web sources, documents, notes, previous conversations, and reports. This project brings those workflows together in one AI-powered workspace.
Capabilities
One workspace, several research paths.
Research mode
Routes current research questions through Exa and brings returned sources into the response.
Document mode
Retrieves relevant document chunks instead of sending an uploaded file in full to the model.
Memory
Useful context can be embedded, stored, and retrieved across sessions when it is relevant.
Report generation
Turns research and conversation outputs into structured PDF or DOCX exports.
Core architecture
Separate paths, shared intelligence.
Research mode
Exa Web Search↓Cited SourcesDocument mode
Document Processing↓Chunks + EmbeddingsSupabase PostgreSQL + pgvector · Supabase Storage · Persistent Sessions / Memory
Document retrieval
RAG makes documents queryable.
The system retrieves relevant document chunks for a question instead of sending the entire uploaded document to the model.
Upload document
Extract content
Split into chunks
Generate embeddings
Store vectors
Semantic search
Retrieve relevant chunks
Contextual answer
Grounded research
From a question to evidence-backed answers.
When Research Mode is enabled, the application routes the request to Exa and returns available sources to the interface.
Conversational memory
Context that can carry forward.
Useful personal facts and conversation context can be embedded and stored for later semantic retrieval. It is a retrieval feature, not human-like memory.
User shares useful context
Embedded and stored
Relevant context can be retrieved
The user experience
A research conversation with a clear path.
Start a conversation
Choose research or documents
Ask a question
Retrieve evidence
Generate a contextual answer
Continue the conversation
Export the result
Technical contribution
Building the system behind the interface.
Frontend
Next.js · React · TypeScriptResponsive workspace, conversation history, controls, uploads, sources, and streaming interaction.
Backend
Python · FastAPIAPI routes, AI orchestration, research routing, document processing, memory, and reports.
AI layer
Gemini · ExaLLM responses combined with web research and source retrieval.
Retrieval
Supabase PostgreSQL · pgvectorPersistent data and semantic retrieval for documents, memory, and research context.
Storage
Supabase StorageUploaded documents and generated reports.
Engineering decisions
Each tool supports a deliberate boundary.
Why RAG?To ground document-based answers in retrieved content.
Why Exa?A dedicated web-research path with source retrieval and citations.
Why FastAPI?To separate AI orchestration and backend services from the frontend.
Why PostgreSQL + pgvector?To combine persistent application data with semantic vector retrieval.
Why Supabase?Database, vector storage, and file storage infrastructure in one system.
Deployment
A live, connected production architecture.
See it in action
See the Copilot in action.
From research questions to document analysis, retrieval, sources, and contextual answers.
Technical ecosystem
AIGemini · RAG · Exa
BackendPython · FastAPI
FrontendNext.js · React · TypeScript
DataPostgreSQL · pgvector · Supabase
InfrastructureDocker · Vercel · Render
Project scope
Research should not mean switching between ten different tools.
One workspace. Multiple sources. Contextual answers.
Next project: Text-to-SQL Data Assistant