Prototype · v1.0

e-Shram registration, inside your app

Your workers get a UAN in minutes. You get Rule 48(2) compliance without building any of it.

The e-Shram portal was built for desktops and paperwork. Most gig workers won't finish it alone. This is that journey rebuilt for a driver on an entry-level phone, parked between trips — and it lives inside your app, not somewhere else.

• • Never leaves your app. Starts on your splash, ends on your profile screen with the UAN in place. Your brand throughout, driven by a single config file.
• • Three ways to verify identity. Aadhaar app, DigiLocker, or OTP — so a worker whose phone isn't Aadhaar-linked still gets through instead of hitting a wall.
• • Built for interruptions. Saves at every step. A trip request mid-registration doesn't cost the worker anything.
• • Knows who they are already. Occupation and aggregator details arrive pre-filled. Fewer fields, higher completion.
• • You never touch Aadhaar data. You receive the UAN, a status and a timestamp. Nothing else crosses into your systems.
• • Compliance you can't break. Consent and declaration screens are locked and unthemeable by design.