Project Showdown: Archive Korexbase
Korexbase Leads is a comprehensive, full-stack AI-powered lead generation platform designed to help businesses automatically discover, extract, and manage potential customer leads from various online sources. The platform combines advanced web scraping capabilities, AI-driven data extraction, and a robust job queue system to efficiently process large volumes of lead generation requests.
Status: Archived on 14 June 2026 Duration: May 2026 - June 2026 Built by: Harsh Verma Reason: Strategic shift toward Korexbase AI Infrastructure
- π― AI-Powered Lead Extraction: Intelligent data extraction and filtering
- β‘ High-Performance Processing: Async job processing with BullMQ and Redis
- π User Dashboard: Comprehensive dashboard for lead management
- π§ Multi-Channel Integration: Email campaigns via Mailjet and Zepto Mail
- π³ Payment Processing: Subscription management with Lemon Squeezy
- π Advanced Web Scraping: Browser automation with Playwright and HTML parsing
- π Secure Authentication: JWT-based auth with role-based access control
- π Real-Time Job Tracking: Monitor lead generation jobs in real-time
- π Excel Exports: Export leads in multiple formats
- π₯ Health Monitoring: System health checks and performance metrics
- π Comprehensive Logging: Structured logging with Winston
This is a full-stack application with clearly separated frontend and backend:
- Framework: React 18 + Vite
- Location:
/frontend - Purpose: User dashboard for lead management, subscription plans, and job tracking
- Features: Real-time updates, responsive design, integrated payment checkout
- Framework: Node.js + Express.js
- Location:
/backend - Purpose: API server, lead generation engine, job queue management
- Features: RESTful API, WebSocket support, background workers, payment webhooks
The comprehensive dashboard allows users to:
- View and manage extracted leads
- Track job status in real-time
- Filter and search leads
- Export data to Excel
- Monitor subscription usage
Flexible subscription plans for different business needs:
- Starter Plan
- Professional Plan
- Enterprise Plan
For detailed information about each component:
-
Backend README - Complete backend documentation including:
- Tech stack and dependencies
- Project structure and architecture
- API endpoints reference
- Installation and setup guide
- Docker deployment instructions
- Background job processing
- Security and performance optimization
-
Frontend README - Frontend documentation including:
- Development setup
- Running locally
- Production build process
- Environment configuration
- React 18
- Vite
- TypeScript
- Tailwind CSS
- Axios
- Zustand (State Management)
- Node.js (ES Modules)
- Express.js v5.2.1
- MongoDB v9.6.2
- Redis v5.12.1
- BullMQ v5.76.10
- Playwright v1.60.0
- Cheerio v1.2.0
- JWT Authentication
- Winston Logging
- Docker & Docker Compose
- MongoDB Container
- Redis Container
- Ngrok (Development tunneling)
- Node.js v18 or higher
- npm or yarn
- MongoDB instance
- Redis instance
- Docker & Docker Compose (optional)
Easy-to-use form to submit lead generation parameters with advanced filtering options.
# Navigate to backend
cd backend
# Install dependencies
npm install
# Configure environment
cp env.example .env
# Edit .env with your credentials
# Start development server
npm run dev
# Start background worker (in another terminal)
npm run worker:leads# Navigate to frontend
cd frontend
# Install dependencies
npm install
# Configure environment
cp .env.example .env.local
# Edit .env.local with your API key
# Start development server
npm run dev# From project root, start all services
docker-compose up -d
# Services will be available at:
# Frontend: http://localhost:3000
# Backend API: http://localhost:2000
# MongoDB: localhost:27017
# Redis: localhost:6379POST /app/v1/auth/register- Register new userPOST /app/v1/auth/login- User loginPOST /app/v1/auth/refresh-token- Refresh JWT tokenPOST /app/v1/auth/logout- User logout
POST /app/v1/generate-leads- Create lead generation jobGET /app/v1/jobs/:jobId- Get job statusGET /app/v1/jobs- Get running jobs
GET /app/v1/dashboard/leads- Get extracted leadsGET /app/v1/dashboard/leads/:jobId- Get leads by jobGET /app/v1/dashboard/jobs- Get job historyGET /app/v1/dashboard/stats- Get dashboard statistics
GET /app/v1/payment/plans- Get available plansPOST /app/v1/payment/checkout- Create payment sessionGET /app/v1/payment/subscription- Get user subscription
GET /admin/settings- Get system settingsPUT /admin/settings- Update system settingsGET /admin/users- Get all users
GET /health- System health checkPOST /webhooks/lemon-squeezy- Payment webhook handler
Korexbase_Leads_GEN/
βββ frontend/ # React + Vite application
β βββ src/
β β βββ components/ # React components
β β βββ pages/ # Page components
β β βββ services/ # API services
β β βββ store/ # State management
β β βββ styles/ # CSS and styling
β βββ index.html
β βββ vite.config.ts
β βββ tsconfig.json
β βββ package.json
β
βββ backend/ # Node.js + Express application
β βββ src/
β β βββ app.js # Express app
β β βββ server.js # Server entry point
β β βββ config/ # Configuration
β β βββ controllers/ # Route controllers
β β βββ models/ # Mongoose schemas
β β βββ routes/ # API routes
β β βββ middlewares/ # Express middlewares
β β βββ services/ # Business logic
β β βββ jobs/ # Background jobs
β β βββ webhooks/ # Webhook handlers
β β βββ utils/ # Utility functions
β βββ test/ # Test files
β βββ Dockerfile
β βββ docker-compose.yml
β βββ package.json
β βββ env.example
β
βββ assests/ # Project assets
βββ Results Demo/ # Demo results
βββ ARCHIVE.md # Archive information
- Request Submission - User submits lead generation parameters
- Job Queuing - Request queued in BullMQ
- Web Scraping - Playwright and Cheerio extract data from web
- AI Processing - Intelligent data extraction and cleaning
- Data Storage - Results saved to MongoDB
- Notifications - User notified via email upon completion
- Dashboard Access - Leads available in user dashboard
View, manage, and export all extracted leads with detailed information and filtering options.
- JWT Authentication - Secure token-based authentication
- Role-Based Access Control - Different permission levels for users
- CORS Protection - Configured CORS headers
- Input Validation - Request validation on all endpoints
- Environment Secrets - Sensitive data stored in
.env - Raw Body Verification - Webhook signature verification
- Password Security - Bcrypt hashing for passwords
Key Mongoose schemas in MongoDB:
- User - User accounts and authentication data
- Lead - Extracted lead information
- Job - Lead generation job records
- Subscription - User subscription details
- AdminSettings - System configuration
- Health Endpoint -
GET /healthreturns system status - System Metrics - CPU, memory, disk usage tracking
- Request Logging - Morgan HTTP request logging
- Error Tracking - Winston error logs
- Job Monitoring - BullMQ queue dashboard
- Redis Caching - Cache frequently accessed data
- Async Job Queue - BullMQ for background processing
- Connection Pooling - MongoDB connection optimization
- Concurrency Control - p-limit for parallel operations
- Response Compression - Gzip compression enabled
- Check
MONGO_URI_PRIMARYin.env - Ensure MongoDB server is running
- Verify network connectivity
- Check
REDIS_HOSTandREDIS_PORT - Ensure Redis server is running
- Check firewall rules
- Verify Mailjet/Zepto Mail credentials
- Check email templates
- Review email service logs
- Verify worker process is running:
npm run worker:leads - Check BullMQ queue dashboard
- Review Redis for stuck jobs
Both frontend and backend require environment files. See:
backend/env.example- Backend environment templatefrontend/.env.example- Frontend environment template
Export your extracted leads directly to Excel format for further analysis and integration with other tools.
- Create a feature branch
- Make your changes
- Commit with descriptive messages
- Push to the branch
- Create a Pull Request
ISC License - see LICENSE file for details
Harsh Verma
For issues, feature requests, and documentation, please refer to:
- Backend README for API and backend-specific issues
- Frontend README for UI and frontend-specific issues
- ARCHIVE.md for project archival information
- Started: May 2026
- Completed: June 2026
- Archived: 14 June 2026
- Backend README - Comprehensive backend documentation
- Frontend README - Frontend setup and development guide
- ARCHIVE.md - Project archival information
- Results Demo - Demo results and screenshots
Last Updated: June 2026
For more detailed information about specific components, see the individual README files in the backend and frontend directories.






