MahaSevak
AI-Powered Platform for Citizen-Centric Maharashtra Governance
Created on 13th April 2025
•
MahaSevak
AI-Powered Platform for Citizen-Centric Maharashtra Governance
The problem MahaSevak solves
Maharashtra's public service delivery faces significant challenges: delays in permits/benefits due to manual processes; lack of transparency leaving citizens unsure of request statuses; inefficient grievance redressal systems; and fragmented information across departmental silos. This negatively impacts citizens through frustration and delays in accessing essential services, while increasing government costs and eroding public trust. Key portals like Aaple Sarkar, MahaDBT, and MahaBhulekh are particularly affected. MahaSuvidha tackles these issues head-on by proposing a suite of integrated AI-driven solutions designed to enhance efficiency, promote transparency, automate processes, and ultimately improve the citizen experience when interacting with Maharashtra's government services.
Challenges we ran into
Building the MahaSuvidha platform involved several technical hurdles:
Integrating Diverse Technologies: Combining the frontend (Next.js for the UI/dashboard), backend (FastAPI for APIs), browser extension components (background scripts, content scripts, popup UI), Python AI libraries (scikit-learn, Transformers, etc.), and external APIs (Firecrawl, LLMs, Bhashini) presented significant integration challenges.
Solution: We adopted a modular, microservices-inspired architecture for the backend features (MahaVerify, MahaSecure, etc.) exposed via FastAPI. Clear API contracts were defined using OpenAPI/Swagger. For the extension, we used standard browser extension messaging protocols (chrome.runtime.sendMessage, etc.) to ensure reliable communication between the content script, background script, popup UI, and the backend. We tested communication pathways incrementally.
Secure API Key Management: Handling API keys for multiple external services (Firecrawl, Gemini, Sarvam, Bhashini) securely was critical.
Solution: We enforced a strict policy where all external API calls requiring keys are made exclusively from our secure backend (FastAPI/Next.js API routes). The browser extension never handles or stores these keys directly; it only communicat