Every urban local body was solving the same problem separately: its own vendor-built site, its own logins, its own forms, its own dead ends. The cost gets paid three times over — by the citizen in travel and time, by the ULB in duplicated vendor spend, and by the state in having no view of its own service delivery.
eNagarSeba is one platform, built once and deployed everywhere.
Five things a citizen can do
Apply for any of 76 services on a form the ULB configured, never one an engineer hard-coded. Pay by UPI, card, net-banking or wallet, with fee slabs, late fees and deposits computed server-side. Track with a docket number and a live SLA timer from submission to certificate. Complain with photo, GPS and category, auto-routed to the right department. Ask Sahayak, which answers in the citizen's own language, grounded in their ULB's actual rules and their own history.
The core bet
A new municipality is data, never new code. An admin defines a service in the portal — form fields, workflow stages, fee rule, documents, SLA, revenue head — the platform validates the schema, workflow graph, fee expression and even the WCAG contrast of the chosen brand colour, and publishing is an explicit, audited action. The same schema then drives the PWA, the mobile app and server-side validation. No redeploy, no migration.
Six workflow patterns cover all 76 services. Per-service deviations are overrides on a pattern, never a new state machine.
Accessibility and language
English, Bengali and Hindi at full parity — every screen signed off in all three locales before it ships, with WCAG 2.1 AA on every public screen. Built to work on Android 9+ at 2 GB RAM, 360 px wide, on a poor network.