Most of what gets called Indian legaltech today is features on top of features. Drafting tools, research tools, chatbots, case management apps, due diligence dashboards. They all share a common dependency they rarely talk about: a single source of truth for what is happening inside Indian courts. That source of truth is the operating system for Indian law. This post defines the category, explains why it has three layers, and lays out what it takes to actually build one.
What an operating system actually is
In software, an operating system is the layer between raw hardware and application code. It abstracts the messy, heterogeneous reality of the underlying machine into a small set of clean, dependable interfaces. Applications do not have to know which specific disk controller is present. They call a file API and trust the OS to translate. That abstraction is what makes a thousand applications possible.
An operating system for Indian law is the same idea applied to court data. The raw hardware, in this analogy, is the Indian judicial system: the Supreme Court, 36 High Courts, 3,705 district and taluka court complexes, and their respective portals. These are public rails operated by the Indian state. They produce enormous amounts of legally significant data every day. But they expose that data in thirty different formats, across twenty-five different sites, with no consistent schema, no unified identifiers, and no common API. An application developer who wants to build on top of this reality needs something in between: an operating system.
Layer 1: the data infrastructure
The foundation is the data layer. It does seven things. It ingests from public upstream sources (ecourts.gov.in, NJDG, individual High Court sites, the Supreme Court portal). It cleans inconsistent formats. It de-duplicates records that appear in multiple places. It entity-resolves parties, advocates, and judges so that one lawyer with five spellings of their name becomes one record. It enriches the raw data with AI summaries, tags, and linkages. It indexes everything for sub-second search. And it serves all of it through a consistent, well-documented API.
This is the hardest layer to build. It is also the most valuable, precisely because it is the one that makes everything else possible. A legaltech startup without a real data layer is fundamentally renting one from someone else.
Layer 2: the consumer portal
The middle layer is the consumer and professional portal. This is where working lawyers, litigants, researchers, journalists, and compliance teams actually interact with the data. Unified case search across all court levels. Cause list lookup for a particular courtroom on a particular day. Advocate profiles with case history. Judge profiles with disposition patterns. Litigant search across parties. Order and judgment downloads. Notifications for hearings, filings, and order uploads.
The consumer portal is the distribution engine. It is how millions of users discover the operating system in the first place, and how they build the daily habits that eventually convert into paying usage in the third layer.
Layer 3: applications and AI
The top layer is where the visible products live. AI drafting tools, legal due diligence APIs, litigation risk scorers, compliance dashboards, litigation analytics for corporates, AI clerks for solo practitioners, summarisation agents for researchers, and vertical offerings for banks, PE firms, insurers, and regulators. Hundreds of companies will eventually build at this layer.
An individual application is easier to build than the layer below it, but also less defensible. Applications with exclusive access to a strong data layer inherit that defensibility. Applications without it do not.
Why this framing matters
| Question | Feature mindset | Operating system mindset |
|---|---|---|
| What is the product? | A drafting tool | A data and interface layer that enables many products |
| What is the moat? | Better prompts, better UI | A multi-year data pipeline that compounds |
| Who is the customer? | Individual lawyers | Lawyers, enterprises, and other legaltech builders |
| What is the failure mode? | A bigger competitor copies the feature | The upstream public data changes format |
The difference is not cosmetic. A feature is priced by the capacity of the user to pay for that one task. An operating system is priced by the value of every application built on top of it. One of these ceilings is small. The other is very large.
The public layer underneath the OS
It is important to say this clearly. The upstream public rails, ecourts.gov.in, the NJDG, and individual court portals, are and should remain government-operated. They are the foundation without which none of this is possible. The eCourts Mission Mode Project has invested INR 935 Cr in Phase I, INR 1,670 Cr in Phase II, and INR 7,210 Cr in Phase III precisely to produce this public data at scale. A private operating system sits on top of these rails the way PhonePe and Google Pay sit on top of UPI and NPCI. The private layer adds experience, reliability, speed, and integration. The public layer provides the data and the legal legitimacy.
What this means for eCourtsIndia
We are building all three layers. The data infrastructure covers 26.8 crore records across 29,600+ courts. The consumer portal serves lawyers, litigants, and researchers every day with unified search, cause lists, profiles, and AI-assisted case reading. The enterprise API and MCP services expose the operating system to other legaltech builders, fintech risk teams, lenders, PE and M&A due diligence teams, and AI agent developers. The goal is not to win any one application. The goal is to make the whole ecosystem possible.
Explore the platform: eCourtsIndia.com • API documentation • MCP services.
Related reading
- From PDFs to APIs: The Evolution of Indian Court Data
- The AI Agent Layer for Indian Law
- Public Data, Private Experience: A Manifesto
- eCourts Phase III: What INR 7,210 Crore Will Build
Sources
- National Judicial Data Grid (njdg.ecourts.gov.in), accessed April 2026
- eCourts Mission Mode Project Phase I, II and III outlays, Department of Justice
- e-Committee, Supreme Court of India, reports on court digitisation
- eCourtsIndia.com platform and API documentation, April 2026