Property decisions in Indian metros run on broker word-of-mouth and listing portals, both of which have an incentive to tell you what sells. Meanwhile the ground truth sits in public records: every project registration, every builder's track record, every government infrastructure announcement leaves a paper trail. It's just scattered across portals nobody can realistically search, in formats nobody can compare.
And different people need entirely different cuts of the same truth. A first-time buyer wants to know which builders actually deliver. A lender wants execution track records and adverse events. A materials supplier wants to know which sites hit the finishing stage next quarter. One dashboard can't serve them all.
A live tool that turns India's scattered public property records into one clear, honest picture. When you buy a home or invest in property here, you're trusting brokers and listing sites that get paid to sell you something. The facts that actually matter (has this builder delivered on time before, is that promised metro line real and funded) sit buried in government records no normal person can dig through. This pulls all of them into one place, so a buyer, lender, or investor can decide on facts instead of a sales pitch. I built the whole thing alone: collecting the government data, cleaning it, the maps, the logins, and six different views for six kinds of users. It runs live at tn-property-intelligence.akaashnidhiss.com behind real authentication.
Ingest the public record
A Python pipeline pulls project registrations, builder filings, and agent records from public government sources, plus a hand-curated, source-cited catalog of 110+ infrastructure catalysts (metro lines, expressways, airports, industrial corridors), each with timeline status.
Enrich into signals
Raw filings become decision signals: builder trust and risk scores from delivery track records, district-level supply velocity and momentum, project-phase classification, and catalyst proximity for every project.
Split public from gated
Aggregates and the catalyst catalog are public; project-, builder-, and agent-level records sit behind authentication and a server-side allow-list, served by serverless functions from pre-compressed payloads.
Serve six terminals
Each role gets its own workview over interactive maps: clustered project markers, momentum-colored district bubbles, and pulsing under-construction catalysts, with split-pane lists on desktop and tabbed sheets on mobile.
Public data, cited everywhere
Every claim traces to a government source. That's the product's moat and its ethics: it doesn't scrape private listings. It makes the public record legible.
No database in the hot path
Data refreshes monthly, not by the tick, so the pipeline pre-computes compressed JSON payloads and the app filters in memory. Near-zero hosting cost, no migration risk, instant queries.
Roles before features
The information architecture starts from who is asking, not what data exists. Six narrow terminals beat one configurable dashboard. Each view earns its place by answering one persona's next decision.
Boring auth, done properly
Hosted identity with encrypted server-side sessions and an allow-list gate on every data route. Solo projects die from clever auth; this one borrowed proven parts.