Implemented
Private plot records, evidence timelines, offline queues, crop-photo handling, source-aware signals and consent-based pilot infrastructure.
THE IDEA BEHIND KRISHYAK
Better questions start with a clearer picture.
Krishyak started with farm-decision simulations. It is growing into a connected record of a field: what changed, what the farmer saw, and what happened next.
Explore the demo
Keep the question close to the field.
The first Krishyak tools explored how changing rainfall, inputs and market assumptions could change a farm’s simulated outcome. Those tools remain available under Planning, with their assumptions visible.
The field workspace connects that thinking to a record farmers can maintain: a named field, a crop season, an observation, an inspection and an outcome. The aim is understandable context, with clear limits on what a model or data source can establish.
THE DEVELOPER BEHIND THE PROJECT
Yashvardhan Thanvi
Yashvardhan maintains the Krishyak repository. His public profile describes his work with C, Python, interactive learning, cloud and AI. The project’s source and engineering reports are available for review.
This is a developer-led product under validation. There is no invented team, farmer testimonial, institutional endorsement or measured impact.
View the public developer profileWhat we can show, and what still needs proof.
Under validation
Farmer usability, local agronomic relevance, field-image performance and real-device operation.
Not claimed
Guaranteed yield, higher income, confirmed disease diagnoses, automatic scheme eligibility or government approval.
Your next step starts with a clearer picture.
Take a look around a demonstration farm, or start keeping your own field records when farm accounts are available.