1947
Independence
A promise of dignity for every citizen.
A design concept for Viksit Bharat @2047·विकसित भारत @2047 के लिए एक डिज़ाइन परिकल्पना
Designed for Viksit Bharat @2047
हर सरकारी सेवा का एक द्वार।
Saathi is a citizen app that starts from your life, not from a department. Ask in your own language — it finds what you're entitled to, fills in the forms and keeps the receipts.
Switch the whole site
This phone is the live prototype. Tap around.
Today, a citizen has to find the right app among hundreds.
Different logins, different languages, different forms — and a fake portal one search result away.
Saathi is one door.
Every service, organised around what's happening in your life: a birth, a harvest, a first job, a pension.
Keep scrolling
India already runs the largest digital public infrastructure in the world.
Yet a citizen still has to know which app, which portal and which form. Saathi is the front door those rails were waiting for — built on them, not beside them.
How Saathi would connect
Conceptual integrations. Saathi is not affiliated with these platforms.
Saathi AI is an assistant that acts — but only after it shows you the plan and you say yes.
In your own language, by voice or by typing. No department names, no form numbers.
Saathi lays out every step, which official service it will use, and why.
You see exactly what is shared, with whom, and for how long. Change it or cancel it.
Every action ends with a reference number, a named officer and a date — and anything else you're owed.
Saathi
Nagar Nigam · e-District · DigiLocker
Guardrails, built in
Official sources only
Every answer names the department or portal it came from.
Asks before it acts
It never submits, pays or shares without your approval.
Explains itself
“Why you qualify” is shown for every scheme it suggests.
A person is always close
One tap reaches a Common Service Centre or a helpline.
Development measured by the lives it changes — Garib, Yuva, Annadata and Nari.
गरीब
Garib
The poor
Entitlements find people, not the other way round.
Ramesh, 67, has his pension life certificate submitted by his son from Saathi — no queue, no agent.
See the pension flowयुवा
Yuva
The young
Scholarships, skills and a first job in one place.
Ananya renews her driving licence on a twenty-minute train ride.
See the licence renewalअन्नदाता
Annadata
Farmers
Land records and PM-KISAN, by voice.
Sunita, who reads slowly, asks out loud and hears her instalment status read back.
See PM-KISANनारी
Nari
Women
Maternity benefits, a daughter's savings and her certificate — as one checklist.
After Aanya is born, the birth certificate, JSY and Sukanya Samriddhi arrive together.
See the new-baby checklistEvery screen and form in 23 languages — English and all 22 of the Eighth Schedule, in twelve scripts, left to right and right to left. Hindi, Bengali and Tamil are fully authored alongside English; the other 19 are machine-assisted and awaiting native-speaker review.
मैं कैसे मदद करूँ?
Coming soon
Try the settings
These are the same controls every Saathi user gets.
Birth certificate
Collect it from Nagar Nigam, Kanpur, or download it to your DigiLocker.
Speak an answer instead of typing it.
Hear any screen in your language.
More time and fewer steps.
Act for a parent or child, clearly marked.
Designed to work offline and on 2G.
Status is always said in words too.
Property tax paid
₹2,450
Verify on the official portal
Sample
People told us they double-check every government website. Saathi is designed so they can.
Consent before data moves
Every share names who asks, what they get, why, and until when — shaped by the Digital Personal Data Protection Act, 2023.
A record of every access
See which officer opened your documents, when, and for what purpose. Revoke access with one switch.
Proof you can verify
Every action ends with a reference you can check on the official portal.
No ads. No selling data. No dark patterns.
A public service should never compete for your attention.
Designed to WCAG 2.1 AA, GIGW 3.0 and UX4G guidelines.
Saathi for Departments
Every service in the app has a desk on the other side. Fifteen department consoles review applications, check e-KYC with a stated purpose, issue signed records and run challans, exams and benefit transfers — and every decision reaches the citizen in their language.
A design concept with sample data — not a Government of India system.
Personal data is masked
Purpose of access
Verify identity for this application
Privacy & consent
Who accessed it
Every view is recorded with a reason.
System architecture
A scholarship deadline night, a PM-KISAN instalment day, an exam result at 10 AM — public services get their worst traffic all at once. Saathi is designed so that peak lands on a cache and a queue, not on a single server or a department's old database.
30,00,000per hour
Lakhs of people at once
30,00,000 · on phones, at CSCs and helplines
A copy kept nearby
Screens and scheme pages are already on the phone and in centres across India, so most taps are answered on the spot.
A fair entry gate
Everyone gets a fair turn. Pressing Submit 50 times can't push anyone else out.
Counters that open themselves
Like a station opening more ticket windows when the crowd grows — and closing them when it's quiet.
Token line
You get your token number in a second. Your application is handled in turn — never lost, even on the busiest day.
Government offices
Aadhaar, DigiLocker, UPI and departments get work at a pace they can handle.
Model: the busiest minute runs at 4× the hour's average; 85% of requests (app screens, scripts, images, scheme pages) are served by the CDN or the phone's offline cache; one service instance handles 250 requests a second at 60% load; at least 3 instances run in each of 2 regions; 12% of server requests write data; one PostgreSQL primary takes 3,000 writes a second. Design targets, to be proven with load tests — not measured on this prototype.
Not every request is the same. Opening a screen, checking a status, filing an application and paying a fee each take a different path — pick one and watch where it goes, how long each stop takes, and what happens if that stop has a problem.
Rakesh applies for the birth certificate at 11 PM on a busy night. He gets his token number in about a second; the office does the work in turn.
Step 1 of 6 · while typing
The form is saved on the phone as he types
Every answer is kept on the phone. Hospital records come from DigiLocker, so most of the form fills itself.
If something goes wrong: Battery dies or the app closes? He reopens it and the form is exactly where he left it.
Most traffic never reaches a server
About 85% of requests are answered by the CDN or the phone's own cache. At 30 lakh requests an hour, only ~500 a second reach Saathi's servers at the peak.
Servers multiply before the queue builds
Autoscaling adds instances when CPU passes 60% and keeps a minimum running in both regions, even at night. Capacity follows demand instead of being guessed in advance.
A burst becomes a line, not a crash
If departments can't keep up, applications wait safely in the queue. Nothing is lost, the citizen already has their reference number, and Track shows where they are.
A virtual waiting room above capacity
If demand ever passes what's provisioned, new sessions get a fair place in line with an honest wait time — people already in the middle of a form are never cut off.
Graceful degradation
If Aadhaar or a department system is slow, Saathi saves the form as a draft and messages the citizen when it's through. If AI is overloaded, it falls back to the scripted, reviewed answers.
Two regions, no single point of failure
Each state's data is replicated to a second region. If a whole region goes down, traffic moves over in minutes, with no loss of submitted applications.
Proven before launch
Load tests at 2× the target peak, chaos tests that switch off servers mid-test, and live dashboards with alerts on latency and error rate — before any real citizen depends on it.
Honest note: the site you're using is a static prototype with no servers behind it. This page is the production design and its capacity targets — the numbers will be proven with load tests in the pilot, not claimed in advance.
Citizens, CSCs and helplines
The installable app works offline and on 2G. It keeps screens and forms on the phone, so most taps never need the network at all.
Edge: CDN, firewall, DDoS shield
Screens, scripts and scheme pages are cached in data centres across India. Bots and floods are filtered here, before they reach anything that costs money.
API gateway
Checks the session, limits each person and each device to a fair rate, and routes the request. A citizen can't knock the system over by tapping Submit fifty times.
Stateless services that scale themselves
Small services on Kubernetes in two Indian cloud regions (MeghRaj / NIC). When load rises, more copies start in under a minute; when it falls, they stop.
Event queue
Submissions, payments and notifications go into a durable queue (Kafka). The citizen gets a reference number instantly; workers process in order, at the pace each department can take.
Data, split by state
PostgreSQL sharded by state, with read replicas, plus a Redis cache for hot data. Documents stay in DigiLocker — Saathi stores the reference, not a second copy.
Government rails
Aadhaar e-KYC, DigiLocker, UPI, PFMS and department systems are called through circuit breakers with retries and timeouts, so one slow system can't slow down the rest.
System & data architecture
Citizens see one Saathi app. Behind it, every service runs on its own group of servers with its own data. When 30 lakh people are online at once, the crowd is split by what they opened — so an exam-result rush grows the Exams room alone, and a birth certificate is never slowed down by it.
30,00,000
people using Saathi at the same moment
1,50,000
requests a second — each active person taps about once every 20 seconds
22,500
a second reach the servers — the rest are answered on the phone or nearby
One Saathi app
the same front door for every service, in every language
Smart router
reads which service you opened and sends you to its room
Certificates · Nagar Nigam1,350/s
Land & farming · PM-KISAN1,350/s
Taxes & bills1,350/s
Transport · RTO1,350/s
Exams & results15,750/s
Health · Ayushman1,350/s
↓ Each department's own system
Result day: the Exams & results room grows to 64 servers on its own. The other rooms don't feel it — they keep their own servers and their own data, so a birth certificate or a challan payment is as fast as on any other day. And if one room ever fails, only that service pauses; everything else keeps working.
A few things every service needs are built once and kept very light, so they never become the bottleneck.
Login with Aadhaar OTP
You sign in once. Every room trusts the same pass, so you never log in again for each service.
Consent & privacy
One record of what you allowed, to whom and until when — every room must check it before using your data.
Notifications
One SMS and app-message service for every department, so updates reach you the same way.
Your profile & documents
Kept once, and documents stay in DigiLocker — rooms receive a reference, never a copy to store.
Splitting the servers only works if the data is split the same way. Four rules:
Each room owns its own data
The Exams room has its own database; it can't slow down or break the Certificates database, and no room reaches into another's.
Inside a room, data is split by state
Uttar Pradesh's certificates live apart from Kerala's. A rush in one state never touches another, and each state's data stays in India.
Rooms talk through one message line
When a birth certificate is issued, the Certificates room posts “certificate issued”. The Health room hears it and starts Janani Suraksha — without the two databases being tied together.
Two copies, two regions
Every room's data is written to a second region as it happens. If a data centre goes down, that room carries on from the copy, with nothing lost.
Model: 30 lakh people online at once, each making a request about every 20 seconds (1,50,000 a second); 85% answered on the phone or from the nearby copy; one server handles 250 requests a second; every room keeps at least 4 servers (2 in each region). Shares per service are illustrative. Design targets, to be proven with load tests in the pilot — not measured on this prototype.
Scroll through a hundred years of the idea that government should serve every citizen.
1947
Independence
A promise of dignity for every citizen.
1950
The Constitution
Rights that public services exist to deliver.
2010
Aadhaar
The first number is issued — a verifiable identity for all.
2015
Digital India
DigiLocker puts official documents on the phone.
2016
UPI
Instant payments anyone can make.
2022
Bhashini
Language technology for India's languages.
2026
Saathi, designed
One door to every service, as a working prototype.
2030
Pilot in three states
Tested with the people it is for, in their languages.
Design target2040
Every district
All 22 scheduled languages, online and offline.
Design target2047
Viksit Bharat
A government that feels like a companion.
Design targetOnboard in your language, ask Saathi for a birth certificate, pay a bill, revoke a consent. Everything in the prototype works.
Explore the design system