O xland started with a frustration a lot of people in Indian infrastructure share but rarely say out loud. Every serious land project — corridor, transmission line, industrial park, renewable farm — runs on a stack that looks basically the same everywhere: four spreadsheets, a legacy GIS install, two case-tracking tools, a WhatsApp group and a folder of scanned PDFs.
Then someone at the top asks "what's the status of parcel 128/2?" and it takes three days and four calls to find out.
The problem we saw
The invisible tax on every land project isn't the price of the platform — it's the hours spent reconciling three sources of truth. The GIS says one thing, the case tracker says another, the field team's WhatsApp update contradicts both. Someone in the middle spends a week aligning them, and the answer they land on is already stale.
We wanted to remove that tax. Not with a prettier spreadsheet. With a workspace where the parcel is the object, and everything else — the litigation case, the drone survey, the compensation ledger, the owner's KYC — attaches to it.
"One parcel record is the source of truth. No parallel spreadsheets, no side-of-desk trackers, no 'let me check with the field team'."
What we built
Oxland is twelve modules stitched together around a single parcel-first data model. But the philosophy underneath is what we care about — these four things are non-negotiable in every release:
One parcel record, every workflow attached
GIS, ownership, litigation, R&R, drone captures — all stitched to the same object. No reconciliation, no orphaned data.
Cadastre-first, not spreadsheet-first
We start with the map and the RoR, then layer everything else on top. It's the only sane way to build for Indian land.
Field ops is a first-class citizen
Offline Android app, DGPS uploads, drone integration, IoT for stockpile and encroachment. The people on the ground are our primary user.
Compliance out of the box
DPDP Act, SOC 2, ISO 27001, MeitY empanelment, GeM-ready. So legal and procurement don't have to slow down evaluation.
Where we're going
In the next twelve months, we're doubling down on three things: deeper GIS integrations with state revenue portals, an AI layer that reads court orders and auto-links them to the right parcels, and a proper mobile-first R&R workflow that field officers can run without training.
We're also hiring — engineers, GIS specialists, land-ops leads and a founding designer. If any of this reads like the thing you'd want to work on, our contact page goes straight to a human.
And if you're running a land project right now and any of this rings true, the best way to see what we're building is to book a walkthrough on your data. Forty-five minutes, no slides.
Thanks for reading — and for whatever's on the other side of your screen, we hope this made it a little clearer why we started this thing.