Public Data, Private Experience: A Manifesto for the Indian Court Data Layer

India has a long tradition of public infrastructure being the foundation on which a rich private ecosystem grows. Indian Railways carries 2.4 crore passengers a day; IRCTC and a thousand private booking agents sit on top. UPI processes 1,300 crore transactions a month; PhonePe, Google Pay, and Paytm sit on top. The National Payments Corporation runs the rails; the private sector runs the experience. This model, which India now exports, is the right way to think about court data too.

This post is a manifesto for that view. The eCourts Mission Mode Project is the rail. Private companies, including eCourtsIndia.com, are the experience layer. The public side is not the enemy of the private side. They need each other. Here is how we think about the responsibilities of each layer, and what we commit to as a private operator.

The three responsibilities of the public layer

Run the rails. The Supreme Court eCommittee and the Department of Justice are responsible for the underlying infrastructure: Case Information System, National Judicial Data Grid, public portals, and the physical and digital plumbing that connects 29,600+ courts.
Guarantee citizen access. Every citizen of India should be able to search for their own case, get a hearing date, and download an order, free of charge. That is a non-negotiable public good.
Maintain authority. The canonical version of any Indian court record is the official record. Private aggregators reflect it. They do not replace it.

We respect each of these. Our product at eCourtsIndia.com is designed to sit above the public infrastructure, not alongside it or instead of it. Every case record we serve is sourced from the official stack. Every link we present leads back to the authoritative source when the user wants to verify. We do not attempt to be the system of record for Indian litigation. We do not need to be.

The three responsibilities of the private layer

Productise the experience. Translate the public record into workflows, integrations, and interfaces that professional users and enterprises actually need, at the speed and scale they need them.
Invest in depth and completeness. Entity resolution, freshness, reliability, and developer-grade access are expensive to maintain. The private layer earns its place by funding these investments.
Extend, do not enclose. A private layer should make it easier, not harder, for the next private builder to innovate on top. Open APIs, predictable pricing, and documented data shapes are baseline.

Our commitments

Drawing from the above, these are the commitments we live by at eCourtsIndia.com. We name them here so users and partners can hold us to them.

We will always credit the source. Every record traces back to its originating court. We do not claim ownership of the underlying data, only of the structure and interface we add.
We will not lock the ecosystem. Our API is documented publicly. Pricing is visible. We do not use exclusive deals to block other aggregators.
We will build for the developer. Clear docs, SDKs, and an MCP for AI-native buyers. Infrastructure is only as good as the people building on it.
We will be honest about coverage and freshness. We do not oversell. If a state’s feed is lagging, we say so. If a court is missing from the index, we flag it.
We will respect confidentiality. We follow the redaction and sensitivity norms established by the courts. We do not surface material that the court system has chosen not to publish.
We will stay complementary. The public system is the foundation. We are on top. If ever our positioning drifts toward replacement, we will correct it.

Why this matters for the market

A healthy public-private legal data ecosystem is a competitive advantage for India. Developers and founders can build on top of a stable public foundation without worrying that the foundation will compete them out of existence. Regulators and courts benefit because the private layer pushes data accuracy, completeness, and accessibility forward. Enterprises and citizens benefit because the product experience keeps improving.

This is already the model for payments (UPI), identity (Aadhaar and DigiLocker), and increasingly for agriculture (Agristack) and logistics (ULIP). There is no reason the same pattern cannot work for legal data. In many ways, it already is. The private aggregation layer has grown because the public foundation has been stable and growing.

A note on the tone of the conversation

There is sometimes a temptation in private-sector writing to frame the public sector as slow, bureaucratic, or behind. That framing is unfair to the teams at the Supreme Court eCommittee, the Department of Justice, and the High Courts who have, over two decades, built the largest judicial technology system in the world. We commit, in our content and in our positioning, to treat the public system with the respect it has earned.

We also commit to treating peer private-sector players with the same respect. Indian Kanoon, Manupatra, SCC Online, LegitQuest, Casemine, Spotdraft, and others have each contributed materially to the ecosystem. Competition is healthy. Disrespect is not useful.

What this means for eCourtsIndia

This manifesto is our public accountability statement. Every product decision, every pricing choice, every communication should be readable against these commitments. If we ever write a blog post or ship a feature that reads inconsistently with this manifesto, a reader should be able to flag it, and we should respond.

See the live product at eCourtsIndia.com, or explore how we make data available through our REST API and MCP.

Sources

Supreme Court eCommittee Publications
Department of Justice eCourts project documentation
National Payments Corporation of India’s UPI documentation (as ecosystem analogy)