unify intelligence for learning.
A student in India today touches half a dozen disconnected tools: a school portal for marks, a coaching app for practice, a video site for explanations, a group chat for doubts, a shelf of photocopied papers. None of them know what the others know, so none of them can adapt.
We think the useful thing to build is not another app in that pile, but the layer underneath it — one place where a learner’s history lives, so every product on top of it can act on the same picture. Vidyapeeth and Pustakalaya are the first two things standing on that layer.
Not values on a wall. These decide what we build and what we turn down.
The system suggests; the teacher
decides. We don’t ship features
that route around the person
responsible for the classroom.
If it only works on campus wifi, it
doesn’t work. Offline is a
requirement, not a later release.
A model that states a result
without a path to it is no use to
someone learning. Every
explanation is traceable to a
source.
Records stay in India, institutions
own them, and we don’t sell or
share them. Exit is always possible
with everything intact.
Started with a syllabus graph and a question: what would a learning system look like if it
were built around the learner’s record instead of the institution’s timetable?
First adaptive courses shipped with pilot schools and coaching institutes. The
recommendation engine moved from a prototype to something teachers used every day.
Semantic search across e-books, journals and past papers, running on the same
intelligence layer as the LMS — so a search result can become an assignment.
Both products in production across schools, coaching institutes and universities. Pariksha,
our assessment product, enters pilot.
in Gurugram.
If you’ve taught, and then wished
the software were better, we’d like
to hear from you.
No formal openings list — tell us what you’d want to work on and we’ll tell you honestly whether it’s something we need right now.
