gantt
title Aarokya Rollout
dateFormat YYYY-MM
axisFormat %b %Y
section Phase 1 — Foundation
Founding Hackathon :p1a, 2026-03, 10d
MVP Launch :p1b, 2026-03, 45d
Platform Integrations & SDK :p1c, 2026-05, 3M
Insurance Eligibility Engine :p1d, 2026-06, 3M
Phase 1 Maturity :milestone, 2026-09, 0d
section Phase 2 — Preventive Intelligence
AI Chat & Voice Interface :p2a, 2026-06, 3M
Nurse & Doctor Network :p2b, 2026-08, 3M
Screening & Risk Detection :p2c, 2026-09, 4M
Health Profiles & Nudges :p2d, 2026-11, 3M
Phase 2 Maturity :milestone, 2027-02, 0d
section Phase 3 — Hyperlocal Care
Pharmacy Network Onboarding :p3a, 2026-10, 4M
Local Lab Integration :p3b, 2027-01, 4M
Teleconsultation Nodes :p3c, 2027-03, 3M
Hyperlocal Network Live :milestone, 2027-06, 0d
13 Roadmap and Rollout
13.1 Phase 1 in 30–45 Days
The first version of Aarokya — the Health Savings Account, the contribution rails, the first platform integrations — launches in 30 to 45 days.
This is not a stretch goal born from pressure. It is a realistic timeline, because the core components already exist. Juspay — the organization building Aarokya — already operates wallet infrastructure, payment orchestration, UPI integration, and merchant settlement systems that processes millions of transactions daily. The HSA is, at its technical core, a purpose-constrained digital account with multi-source funding and restricted-use payments. These are problems Juspay has already solved — at scale, in production, under regulatory compliance.
What is new is the purpose. The money flows into a health account instead of a commerce account. The constraints are healthcare-specific. The integrations connect to gig platforms, employers, and insurance providers instead of merchants. But the underlying rails — identity, accounts, payments, SDKs — are proven infrastructure being repurposed for a mission that matters.
Need to make the right team meet the right problem, and reuse as many building blocks already in hand.
13.2 Open Source: Healthcare Infrastructure as a Public Good
Aarokya is open source from day one.
It is a philosophical decision. Healthcare infrastructure — the rails on which hundreds of millions of people’s health security will depend — should not be a black box. It should be transparent, auditable, improvable by anyone, and adaptable for any community or country that needs it, inviting review and collaboration.
Open source means:
- Transparency — every line of code is visible. Regulators, healthcare experts, security researchers, and citizens can inspect how the system works. Trust is not asked for; it is verifiable.
- Community ownership — Aarokya belongs to the ecosystem, not to a single entity. Contributors from across India and the world can improve it, extend it, and adapt it.
- Adaptability — the model that works for gig workers in Bengaluru can be forked and adapted for informal workers in Nairobi, domestic workers in Jakarta, or street vendors in São Paulo. Open source makes Aarokya a gift to the world, not just a product for India.
- Speed through collaboration — the best open source projects move fast because they harness the intelligence of thousands of contributors. Aarokya invites that energy.
This is not without precedent. Two of India’s most ambitious open source projects have already proven that critical infrastructure can be built this way — and both are part of Aarokya’s lineage.
Namma Yatri — an open source ride-hailing platform, built in Bengaluru, serving millions of auto and cab rides. It proved that consumer-facing apps with beautiful UI/UX and massive daily transaction volumes can be built and operated as open source.
HyperSwitch — an open source payments orchestration system, processing transactions at scale across multiple payment gateways and geographies. It proved that financial infrastructure demanding the highest standards of reliability, security, and compliance can be built in the open.
Aarokya inherits the DNA of both. The backend robustness of HyperSwitch. The consumer-grade experience of Namma Yatri. The open source ethos of both.
13.3 The Team: Juspay and the Builder Community
Aarokya is being built by Juspay — a 1,600-member engineering organization that processes over 50 million payment transactions daily for India’s largest banks, platforms, and enterprises.
Juspay is not a typical outsourced development vendor. It is the company that built HyperSwitch and Namma Yatri. It has deep expertise in payments infrastructure, platform architecture, open source engineering, and building systems that work at population scale with zero tolerance for failure.
For Aarokya, Juspay is deploying:
A dedicated Aarokya team — engineers, designers, product managers, and healthcare domain experts working full-time on the platform.
A 10-day founding hackathon with the HyperSwitch team — the engineers who built India’s open source payments switch are the ones kickstarting Aarokya’s backend. They know how to build production-grade, secure, auditable financial systems — the exact skills needed for Health Savings Accounts, contribution rails, and insurance integration. Ten days to go from zero to a working backend. This is how HyperSwitch itself was born.
Namma Yatri’s frontend and UX team — the designers and engineers who shipped an open source consumer app used by millions of riders and drivers daily. They bring deep expertise in building interfaces that work for India — multilingual, low-bandwidth-friendly, accessible to first-time smartphone users. They are bringing that same craft to Aarokya’s user experience.
Company-wide hackathons — Juspay is opening Aarokya to its entire 1,600-member organization through internal hackathons. Teams across payments, risk, AI, infrastructure, and design are invited to contribute features, solve problems, and bring their expertise to the mission. This isn’t just about building faster — it is about recruiting the best internal talent into the Aarokya effort and giving every engineer the chance to work on something that directly improves lives.
This is a mission-driven build. The people writing the code have already shipped open source products used by millions. They understand what it takes to build infrastructure that cannot fail — because in payments, as in healthcare, failure has real consequences for real people.
13.4 AI-Powered Development
Aarokya is being built with modern AI-driven development practices — and this matters not just for speed, but for what it represents.
AI pair programming, code generation, rapid prototyping, automated testing, and intelligent code review are accelerating every phase of development. Tasks that would have taken weeks take days. Explorations that would have required large teams can be done by small, focused groups augmented by AI.
This is itself a demonstration of the core thesis. Aarokya is a system built on the conviction that AI amplifies human capability. The development process proves it: a team of talented engineers, amplified by AI tools, building in weeks what would traditionally take months.
If AI can accelerate the building of healthcare infrastructure, imagine what it can do when that infrastructure is deployed — amplifying nurses, doctors, and community health workers at the point of care.
The tool and the mission are aligned. AI builds Aarokya. Aarokya delivers AI-powered healthcare. The future is not AI alone. It is AI + Empathy — all the way down.
13.5 The Three Phases — Compressed, Urgent, Real
The vision unfolds in three phases. But these are not the slow, sequential phases of a traditional enterprise roadmap. They overlap aggressively. Phase 2 begins before Phase 1 is complete. Phase 3 development starts while Phase 2 is still maturing.
When the need is this urgent and the team is this capable, you build in parallel.
Phase 1 — The Foundation (30–45 Days to MVP, 6 Months to Maturity)
The founding hackathon produces the core backend — Health Savings Account engine, contribution rails, payment integration. Within 30 to 45 days, the first version of Aarokya is live:
- HSA creation — linked to Aadhaar/ABHA, UPI-enabled, purpose-constrained for healthcare
- Multi-source contributions — employers, families, platforms, tips, CSR — all flowing into a single health account
- Progress tracking — visual dashboard showing savings, insurance eligibility progress, contribution history
- SDK for platform integration — so gig platforms can embed health contributions into their payment flows from day one
Over the next 3 to 6 months, the foundation matures:
- Deeper integrations with gig platforms (Swiggy, Namma Yatri, Urban Company, and others)
- Insurance eligibility engine connecting HSA balances to real insurance products
- Employer and CSR contribution management
- Onboarding optimized through real user feedback from pilots
| Dimension | Details |
|---|---|
| Timeline | MVP in 30–45 days; full maturity by Month 6 |
| Key Activities | Founding hackathon; MVP launch; HSA engine; contribution rails; platform SDK; insurance eligibility; pilot deployment |
| Target Users | Gig workers (delivery, ride-hailing, domestic work); urban families employing gig workers; early platform partners |
| Success Metrics | 100K+ HSAs created in 90 days; 10+ platform integrations; first insurance policies activated from HSA balances |
Phase 2 — Preventive Intelligence (Months 3–9)
Once the financial rails are live, the intelligence layer arrives. AI-powered preventive care — starting as a chat interface in the app, with voice support in Indian languages.
- AI health assistant — conversational, multilingual, voice-enabled. Collects symptoms, screens for risks, provides guidance, escalates to professionals.
- Nurse and doctor network — trained professionals connected through the platform, available for teleconsultation when AI triage indicates the need.
- Health profiles — every user builds a living health record through interactions, screenings, and shared data.
- Nudges and reminders — medication reminders, checkup schedules, vaccination tracking, risk-based alerts.
The goal: catch health problems before they become catastrophes. Reduce the ₹5,00,000 emergency surgery to a ₹500 early screening.
| Dimension | Details |
|---|---|
| Timeline | Begins Month 3; mature by Month 9 |
| Key Activities | AI chat and voice interface; nurse/doctor network; screening and risk detection; health profiles; multilingual NLP |
| Target Users | All HSA holders; high-risk populations; families; elderly users |
| Success Metrics | 500K+ AI health conversations/month; 50K+ screenings; 30%+ reduction in late-stage presentations among active users |
Phase 3 — Hyperlocal Care Network (Months 6–18)
The digital platform connects to the physical world. Local pharmacies, labs, testing centers, and clinics become nodes in the Aarokya network.
- Pharmacy nodes — equipped with basic diagnostic devices, connected to the platform, offering testing, sample collection, and teleconsultation-assisted care.
- Lab integration — seamless test ordering, sample tracking, and result delivery into the patient’s health profile.
- Teleconsultation spaces — private areas in pharmacies or community centers for video consultations with doctors.
- Sample collection networks — trained workers visiting homes for collection and delivery to partner labs.
Healthcare within walking distance. Not a bus ride to a district hospital.
| Dimension | Details |
|---|---|
| Timeline | Begins Month 6; network live by Month 18 |
| Key Activities | Pharmacy onboarding; diagnostic devices; lab integration; sample collection; teleconsultation infrastructure |
| Target Users | All Aarokya users needing physical care; elderly; chronic disease patients; rural/peri-urban populations |
| Success Metrics | 5,000+ pharmacy nodes; 200+ lab partners; average distance to care < 2km for active users |
13.6 Pilot Strategy: Fast, Focused, Learning
Aarokya launches where the conditions are right — and fast.
The first pilots happen within the first 30–45 days, alongside the MVP launch. Not after months of planning. In parallel with building. Real users, real feedback, real iteration.
First Pilot Cities
- Bengaluru — home base. High gig worker density, strong platform partnerships, Juspay and Narayana Health headquarters. The natural starting point.
- Pune — growing gig economy, strong community organizations, mix of urban and peri-urban populations.
- Jaipur — gateway to Rajasthan’s underserved populations, significant uninsured population.
- Specific communities within Mumbai — domestic worker networks, auto-rickshaw collectives, housing society clusters.
Each city teaches something different. Together, they prove the model across India’s diversity.
flowchart LR
A["Founding<br/>Hackathon<br/><i>10 days</i>"] --> B["MVP +<br/>Community Pilots<br/><i>30-45 days</i><br/><i>5,000 users</i>"]
B --> C["City<br/>Pilots<br/><i>3 months</i><br/><i>100K users</i>"]
C --> D["Regional<br/>Expansion<br/><i>6-9 months</i><br/><i>1M users</i>"]
D --> E["National<br/>Scale<br/><i>12-18 months</i><br/><i>10M+ users</i>"]
Each stage has clear graduation criteria:
- Hackathon → MVP: Working backend, core HSA flows functional, first users onboarded
- MVP → City Pilots: User retention >60%, contribution flows working across 3+ sources, positive user feedback
- City Pilots → Regional: Unit economics viable, platform integrations scalable, insurance pathways proven
- Regional → National: Repeatable playbook, self-sustaining growth, regulatory clarity
No stage waits longer than it needs to. Every stage earns the right to the next through demonstrated impact.
13.7 Building in Public
Aarokya is not just being built fast. It is being built in public.
The code is open. The progress is visible. The roadmap is shared. The problems encountered and solutions found are documented for the world to see.
This is deliberate. When you are building healthcare infrastructure that will affect hundreds of millions of lives, you want the brightest minds looking at your code. You want security researchers auditing your systems. You want healthcare experts reviewing your care pathways. You want regulators able to inspect the machinery. You want other countries able to study, adapt, and improve upon what you’ve built.
Open source is not just a development model. It is a trust model. In a domain where trust is everything — where people are entrusting you with their health data, their savings, their family’s wellbeing — radical transparency is not a nice-to-have. It is a requirement.
The invitation is open:
- Engineers — contribute code, review pull requests, build integrations
- Healthcare professionals — review care pathways, improve screening protocols, validate AI models
- Designers — improve accessibility, create better experiences for underserved users
- Security researchers — audit the platform, find vulnerabilities, make the system stronger
- Policy experts — help shape the regulatory framework, inform compliance
- Anyone who cares — file issues, suggest improvements, spread the word
Aarokya is being built by Juspay. But it belongs to everyone who needs it.
Healthcare infrastructure should be a public good. Open source makes that real — not as an aspiration, but as an architecture.
The speed is real. The urgency is real. The team is proven. The tools are ready.
Thirty to forty-five days from hackathon to first launch. Six months from launch to a mature foundation with insurance pathways. Twelve to eighteen months from foundation to a hyperlocal care network serving millions.
This is what happens when world-class engineering meets moral purpose. When open source meets empathy. When AI meets urgency.
Affordable Healthcare for EVERYONE — and we are building it now.