Digital Water Management for Urban Utilities
September 29, 2026
What AgriStack builds nationally, what states build on top, and where state agriculture departments keep the most control.
Ask five officials what AgriStack India is and you may get five answers: a farmer database, a national app, an ID card, a crop survey, a data-sharing platform. Each is partly right, which is exactly why the relationship between AgriStack and the agriculture platforms states are building confuses so many people. If AgriStack is national infrastructure, why does Andhra Pradesh need APAIMS or Kerala need KATHIR? And if states are building their own platforms, what is AgriStack for?
The short answer is that they are two layers of the same system, designed to do different jobs. AgriStack establishes who the farmer is, what land they cultivate, and what they grew. State platforms use that foundation to deliver services: advisories, input entitlements, insurance support, market access. Understanding where one ends and the other begins matters for anyone deciding what to build, fund or procure.
AgriStack is the core of the Digital Agriculture Mission approved by the Union Cabinet in September 2024. The Mission describes it as a farmer-centric digital public infrastructure built in a federated structure, with three foundational registries: the Farmers’ Registry, geo-referenced village maps, and the Crop Sown Registry. Crucially, all three are created and maintained by state governments and union territories, not by a central office.
Each farmer receives a Farmer ID, linked to the state’s land records, and crops sown are recorded each season through the mobile-based Digital Crop Survey. The scale is now substantial. The government told the Rajya Sabha that more than 10.31 crore Farmer IDs had been created as of 3 August 2026, and that the Digital Crop Survey covered over 31.3 crore plots across 648 districts in Rabi 2025-26, as reported by ChiniMandi.
Around the registries sits the connective tissue: the Unified Farmer Service Interface, an open API gateway with a consent manager and sandbox that lets authorised public and private applications query registry data.
A registry tells you a farmer exists and what they planted. It does not tell a field officer which plots are showing crop stress this week, send a pest warning in Telugu, calculate how much urea a farmer is entitled to, or route a complaint about a delayed payment. Those are service-layer jobs, and they are shaped by state priorities, crops, languages, schemes and administrative structures.
That is the space a state agriculture DPI fills. It consumes AgriStack’s verified identity and crop data and combines it with the state’s own datasets and systems: scheme databases, soil health records, input dealer networks, weather feeds, satellite imagery and extension workflows.
| Question | AgriStack (national foundation) | State agri-DPI (service layer) |
|---|---|---|
|
Core job |
Establish verified farmer, land and crop records |
Deliver services and decisions using those records |
|
Who maintains it |
States maintain registries; the Centre sets standards and provides shared components |
The state agriculture department, often with a technology partner |
|
Typical contents |
Farmer ID, land parcel links, seasonal crop sown data |
Advisories, crop monitoring, pest surveillance, input entitlements, scheme tracking, grievances |
|
Design goal |
Uniformity and interoperability across states |
Fit to state crops, schemes, languages and workflows |
|
Main users |
Government agencies and authorised service providers via APIs
|
Farmers, field officers, department officials, local service providers |
The interface between the layers is where most of the practical design work happens. Three touchpoints matter most.
Identity and eligibility. When a state scheme needs to confirm that an applicant is a cultivator with a given extent of land, the Farmer ID and linked land records are the obvious source. The PIB has cited Maharashtra’s use of AgriStack to transfer over ₹14,000 crore to 89 lakh farmers for Kharif 2025 crop losses within five days, and Chhattisgarh’s use of Farmer ID and crop survey data for MSP paddy procurement covering over 32 lakh farmers.
Crop data. The Crop Sown Registry gives state platforms ground-verified crop and area data each season. Satellite analytics can then extend and cross-check it between survey rounds, which is how plot-level crop health monitoring becomes possible.
Advisory channels. Nationally, the Union Budget 2026-27 introduced Bharat-VISTAAR, a multilingual AI tool integrating AgriStack portals with ICAR’s package of practices. State platforms can feed it state-specific context or connect their own advisory engines to it.
The federated design is not a formality. Because registries are built and maintained by states, states control the quality and completeness of their own data, including decisions such as whether tenant farmers are included, which the Mission leaves to state policy. States also decide:
The government has also said AgriStack follows the Digital Personal Data Protection Act, 2023 and its 2025 Rules, with consent-based collection and access limited to authorised purposes. That sets the floor; a state’s own governance model sets how it operates in practice.
“AgriStack replaces state platforms.” It does not provide state-specific services and was not designed to. It gives every state the same verified base to build on.
“A state platform can ignore AgriStack.” It can, but it will end up maintaining a parallel farmer database that disagrees with the national one, which is the fragmentation DPI was meant to end.
“Registering on one means registering on both.” Farmer ID creation happens through state Farmer Registry portals. Whether a state platform reuses that record or asks farmers to register again depends on how well the two are integrated, which is precisely the design choice worth getting right.
AgriStack gives every state the same verified base of farmer, land and crop records. What each state builds on top of that base differs, because it follows the state’s own crops, schemes and priorities. Three fieldWISE-based platforms (APAIMS in Andhra Pradesh, KATHIR in Kerala and MahaAgriNEX in Maharashtra) show how the service layer takes different forms on the same foundation.
The problem: India’s fertilizer subsidy regime has historically rewarded volume over precision. Over-application carries well-documented ecological costs, including soil acidification and nitrate leaching into groundwater. Fixing this meant knowing what each farmer actually grows and on how much land, at the point where fertilizer is sold.
The solution: APAIMS uses verified crop and extent data to set fertilizer entitlements for each farmer. Doses are customised by location, crop and extent, and sales cannot exceed what is dispensed against that entitlement. The same verified base also drives crop health monitoring and pest alerts for field officers.
The problem: Festival seasons bring peak demand and sharp price swings, leaving farmers exposed to volatility and dependent on intermediaries. Kerala also needed one platform that connects national schemes with state-specific services.
The solution: KATHIR aligns with PM-KISAN, PMFBY and the AgriStack Digital Crop Survey, and adds services specific to Kerala. For Onam, it powers a dedicated e-market module that gives farmers direct, fair-price access to buyers, handling operations digitally across cash and UPI.
The problem: A state as large as Maharashtra needs plot-level visibility into its farmland. Without farm boundaries, advisories and monitoring fall back on district averages. Maharashtra is also one of the states PIB cites for using AgriStack to move relief and procurement payments quickly, which makes a strong geospatial service layer on top of it all the more relevant.
The solution: MahaAgriNEX applies AI and satellite data to build that plot-level base statewide, running on the same data backbone as the other two platforms.
The registries are created and maintained by state governments and union territories within a federated architecture, with access governed by consent and authorised purpose.
Not primarily. It is infrastructure: registries plus APIs. Farmers typically experience it through state portals, scheme applications and advisory services built on top.
Every state needs a service layer. Whether it is built in-house, with a partner or by reusing shared components is a state decision.
PIB: Cabinet approves the Digital Agriculture Mission
PIB: AgriStack’s Farmers Registry crosses 9.20 crore Farmer IDs
Related on this blog:What Is the Digital Crop Survey? · How Andhra Pradesh Built APAIMS
