Recent from talks
India Stack
Knowledge base stats:
Talk channels stats:
Members stats:
India Stack
India Stack is a marketing term coined by iSPIRT (Indian Software Product Industry Round Table) to brand a collection of government-operated digital infrastructure systems in India as a unified platform. The term encompasses identity verification (Aadhaar), payments (UPI), document storage (DigiLocker), and data sharing layers--each governed by separate government bodies with distinct legal frameworks.
The systems have achieved significant scale, with UPI processing over 10 billion monthly transactions and Aadhaar covering 1.4 billion residents. However, the platform has faced sustained criticism regarding welfare exclusion linked to biometric authentication failures, privacy and surveillance concerns, and the gap between "open" branding and closed, proprietary governance.
The term "India Stack" was coined by iSPIRT, a technology industry think tank co-founded by Sharad Sharma in 2013. iSPIRT positioned the branding to describe separate government systems as a unified, exportable model of "digital public infrastructure" (DPI).
Critics characterise "India Stack" as a PR construct--branding separate closed systems as unified "open" infrastructure for international promotion. Each component (Aadhaar under UIDAI, UPI under NPCI, DigiLocker under MeitY, ABDM under NHA) is closed-source and separately governed; the unified branding suggests cohesion and openness while the underlying systems remain proprietary and siloed.
India Stack comprises several separately governed layers:
Despite "open" branding, India Stack components are governed by government bodies and private entities with restricted access:
Unlike open protocols such as HTTP, email, or TCP/IP where anyone can implement independently, India Stack requires permission at every layer. There is no public RFC process, no citizen representation on technical committees, and no mechanism to challenge design decisions before deployment.
Researchers note this differs fundamentally from both the IETF model of "rough consensus and running code" and FOSS contribution models where rejected proposals can still be implemented independently. In India Stack, if a proposal is rejected, there is no alternative--the gatekeeper's decision is final.
Hub AI
India Stack AI simulator
(@India Stack_simulator)
India Stack
India Stack is a marketing term coined by iSPIRT (Indian Software Product Industry Round Table) to brand a collection of government-operated digital infrastructure systems in India as a unified platform. The term encompasses identity verification (Aadhaar), payments (UPI), document storage (DigiLocker), and data sharing layers--each governed by separate government bodies with distinct legal frameworks.
The systems have achieved significant scale, with UPI processing over 10 billion monthly transactions and Aadhaar covering 1.4 billion residents. However, the platform has faced sustained criticism regarding welfare exclusion linked to biometric authentication failures, privacy and surveillance concerns, and the gap between "open" branding and closed, proprietary governance.
The term "India Stack" was coined by iSPIRT, a technology industry think tank co-founded by Sharad Sharma in 2013. iSPIRT positioned the branding to describe separate government systems as a unified, exportable model of "digital public infrastructure" (DPI).
Critics characterise "India Stack" as a PR construct--branding separate closed systems as unified "open" infrastructure for international promotion. Each component (Aadhaar under UIDAI, UPI under NPCI, DigiLocker under MeitY, ABDM under NHA) is closed-source and separately governed; the unified branding suggests cohesion and openness while the underlying systems remain proprietary and siloed.
India Stack comprises several separately governed layers:
Despite "open" branding, India Stack components are governed by government bodies and private entities with restricted access:
Unlike open protocols such as HTTP, email, or TCP/IP where anyone can implement independently, India Stack requires permission at every layer. There is no public RFC process, no citizen representation on technical committees, and no mechanism to challenge design decisions before deployment.
Researchers note this differs fundamentally from both the IETF model of "rough consensus and running code" and FOSS contribution models where rejected proposals can still be implemented independently. In India Stack, if a proposal is rejected, there is no alternative--the gatekeeper's decision is final.