← Back to the caseThe Rishi Gurung Times · Case FilesFiled from Delhi
Case File · Exhibit A · NAVFarm

One roof, many farms

A farm ERP where one customer is a company — or several — running piggery, hatchery and shrimp at once. The subject co-develops the platform in a team of two, and the structure underneath it is what this file is about.

By The Investigation Desk · 2026 — ongoing

Exhibit AFig. 1 — withheld: client software with customer data in it.

NAVFarm is an ERP and operations platform for farm businesses. A single customer is not a single farm: it is a company, or several, running different kinds of operation — piggery, hatchery, shrimp — each with its own way of recording what happened today. The job is a redevelopment rather than a greenfield build: a system already in use, with data in it and people depending on it.

The structural decision the platform rests on is that a tenant is provisioned, not filtered. Each one gets its own isolated data instead of sharing tables behind a tenant_id column. Beneath it sit companies and operational areas, and beneath those the lines of business. Almost every question the product answers — who may see this record, which company owns this animal, what “this month” means for a hatchery versus a shrimp pond — is answered by walking that hierarchy.

Isolation is not free, and the file records where the bill lands. Provisioning becomes a first-class operation that has to succeed or roll back cleanly. Migrations fan out across every tenant and can partially fail. Anything platform-wide needs a deliberate answer rather than a GROUP BY. For a product whose customers are separate businesses, the desk regards it as the right trade.

“A tenant is not a row.”

Piggery, hatchery and shrimp are not three copies of one module with different labels. The working answer is a shared spine — tenancy, companies, operational areas, identity, reporting — with the domain-specific parts kept genuinely separate. An Nx monorepo keeps those boundaries visible in the dependency graph instead of in someone’s head.

Day to day the subject owns major frontend and product workflows — master data, inventory, sales, batch creation, daily feed and activity entry, multi-tenant access, user and role management — across NestJS services, Next.js interfaces and the MySQL schema underneath, through to deployment on Windows and IIS. A change rarely stays in one of those layers, and following it all the way to the server it runs on is where most of the lessons came from.

No screenshots are entered in evidence. NAVFarm is client software and its interface shows customer data; the structure is the subject’s to explain, the screens are not.