Five ways in. No wrong door.
Start wherever you are, and stop wherever it stops being useful.
Not sure which door? Answer two questions.
{{ fwTitle }}
{{ fwBody }}
Licences, free or near-free
Any product in our portfolio, clinical records, judicial workflow, road and asset intelligence, media accessibility, at zero or cost-recovery pricing for verified nonprofits, onboarding included.
Weeks, not quartersAI & data training for your staff
A practical curriculum for programme teams, not engineers: what these tools can and cannot do, data hygiene, consent, and governance you can defend to a donor or a district officer.
Cohorts of 20 · Hindi & EnglishThe open challenge
Send us the problem, not the solution. Twice a year we take the submissions with the widest reach, build the thing properly, and release it so every organisation facing the same wall can use it.
Two intakes a yearThe Anvaya fellowship
Our engineers, designers and data scientists spend a funded stint inside your organisation, in your field offices, not on a call, learning the work well enough to build for it.
3–6 months · salaried by usA pro-bono engineering pod
A standing squad, product, engineering, data, design, assigned to one organisation for a year.
4–6 people · 12 monthsNo one gets to the last mile alone.
A nonprofit knows the household. A university knows whether it worked.
Anvaya is one point on this map, not the centre of it
Nonprofits & community organisations
The household, and what happens after the form is filled.
Software, engineers, training, and the IP.
Academic institutions
Proof, and the willingness to publish a negative result.
Live deployments to study, and student placements.
Think tanks & policy researchers
Framing that turns one district into a state decision.
Deployments instrumented for evidence, not anecdote.
Government departments & missions
Mandate, and the only route to the other forty districts.
A working district first, handed over entirely.
Funders & CSR teams
The one line we cannot cover: devices, data, people.
A deployment rather than a pilot, and an asset at the end.
Technology partners
Compute, model access, shared infrastructure kept alive.
A hard testbed: offline, multilingual, on old devices.
Individuals belong on this map too: an engineer with evenings free, a doctor on sabbatical, a translator who can give a weekend.
Four things, none of them money.
One named owner
A person inside your organisation who will own the system after we leave. Not necessarily technical, but accountable.
Access to the field
Two days with your team where the work happens. Every deployment we got right began with a visit; every one we got wrong did not.
A decision on data
Who may see what, and what must never leave a device. We will not make that call on your behalf.
Honesty about failure
If it is not being used, we need to hear it in month two rather than month eleven.
A sector page traces what the six weeks after this actually look like.
Tell us what is stuck.
One paragraph is enough. You do not need a technology plan, a budget or the right vocabulary, only the problem you keep running into.
Thank you, it's with us.
A person, not an autoresponder, will read this and come back to you within a week.