Skip to content

About

AI-powered legal document analysis and chat platform that helps users upload, process, and query legal documents with intelligent retrieval, summarization, and conversational assistance. The app combines a Node.js backend, a Next.js frontend, and a Python RAG service to enable secure document ingestion, vector-based search, and contextual legal Q&A

Topics

Resources

Stars

2 stars

Watchers

0 watching

Forks

Latest commit

 

History

54 Commits

Folders and files

Repository files navigation

# LiveLegalAI — Minimal Overview LiveLegalAI is a small multi-service project for document-grounded legal analysis. It consists of: - `frontend/` — Next.js (App Router, TypeScript) UI for upload, history, analysis, chat, and settings. Auth via NextAuth (credentials + Google OAuth), Tailwind CSS + shadcn/ui, feature-based folder structure. - `backend/api_express/` — Node/Express API with its own JWT auth (bcrypt-hashed passwords + Google ID token verification), that stores metadata, proxies to the RAG service, and handles uploads and reports. - `backend/rag-api_python/` — Python FastAPI service that ingests documents, creates per-document FAISS indexes, and runs retrieval + generation. Only PDF and DOCX are parsed. Quick start (development), in three separate terminals: 1. RAG service (Python): ```bash cd backend/rag-api_python python -m venv venv venv\Scripts\activate pip install -r requirements.txt copy .env.example .env python main.py ``` 2. Backend (Node): ```bash cd backend/api_express npm install copy .env.example .env # fill in JWT_SECRET, GOOGLE_CLIENT_ID, MONGODB_URI, etc. npm run dev ``` 3. Frontend (Next.js): ```bash cd frontend npm install copy .env.example .env.local # fill in NEXTAUTH_SECRET, GOOGLE_CLIENT_ID/SECRET, etc. npm run dev ``` Key notes: - Auth is JWT-only: the Express backend issues its own token on register/login/Google sign-in (`/api/auth/*`), and every protected API route (`requireAuth` middleware) verifies it via `Authorization: Bearer `. NextAuth on the frontend wraps that same backend token in its session — it never uses a Google-native token for API calls. - Google OAuth requires a Google Cloud OAuth Client ID/Secret (redirect URI `http://localhost:3000/api/auth/callback/google` in dev), shared between `frontend/.env.local` (`GOOGLE_CLIENT_ID`/`GOOGLE_CLIENT_SECRET`) and `backend/.env` (`GOOGLE_CLIENT_ID` only — used to verify token audience). - The RAG service performs text extraction, chunking, embeddings, and FAISS index management per `document_id`. It only supports PDF and DOCX uploads. - PDFs/DOCs uploaded via the frontend are ingested by the RAG service and then referenced by the backend. Where to look: - Frontend routes: `frontend/src/app/`; feature code: `frontend/src/features/` - Backend controllers: `backend/api_express/controllers/`; auth: `backend/api_express/controllers/authController.js`, `backend/api_express/middleware/authMiddleware.js` - RAG core pipeline: `backend/rag-api_python/core/` ## For deployment using a VPS: 1. git clone the repo, then edit root .env (real domain + email) and each service's .env 2. Point the domain's DNS A record at the VPS IP. 3. docker compose up -d --build For a backend-only Docker environment, run `docker compose up -d --build` from `backend/`. That starts Express and the RAG service without the frontend or Caddy.# idea_lab

About

AI-powered legal document analysis and chat platform that helps users upload, process, and query legal documents with intelligent retrieval, summarization, and conversational assistance. The app combines a Node.js backend, a Next.js frontend, and a Python RAG service to enable secure document ingestion, vector-based search, and contextual legal Q&A

Topics

Resources

Stars

2 stars

Watchers

0 watching

Forks

Releases

Contributors

Languages