Lexlegis.ai vs Manupatra: how they compare in 2026

Every product sold is model work and the company describes itself as AI-first. Legal AID is three generative capabilities: Ask answers legal questions in the IRAC format with sources returned and explained, Interact reads uploaded contracts, orders and notices and answers across them, and Draft produces contracts, submissions, written arguments, oral argument outlines and authority bundles. MIRA sits on the same foundation as a skill-configurable agent that reads a brief, selects from a library of 215 production skills, orders them into a plan, reasons through each step and checks its own reasoning against a verification layer before producing output. The agreement defines the Service as the platform including Ask, Interact, Draft and MIRA, so the model products are the contracted thing rather than a layer over something else. The vendor states it trained its own model on its corpus and positions that against fine-tuning and retrieval-augmented generation, and its published model layer describes signed checkpoints, per-tenant guardrails and an inference audit trail, which are the controls of an organization running its own inference rather than reselling someone else's. The non-model asset is real and is described honestly rather than credited: a curated closed corpus of Indian laws, circulars and judgments built over decades of legal documentation work. No separately purchasable non-AI product was located on any surface read, and the corpus is an input to the assistants rather than a search subscription sold on its own. Terms of service v2.0, trust page and product pages read 7 September 2026.

Artificial intelligence is a substantial, named, shipped layer on a research platform that existed for twenty-five years without it, which is the B band rather than the A. What ships is specific and dated. Manupatra AI Search launched in December 2025, is described by the vendor as powered by semantic AI and large language models, and retrieves judgments by legal concept rather than keyword; AI Summary generates judgment summaries; AI Compare sets judgments side by side. The separately branded ManuWorks toolkit adds OCR, summarization, translation, document question-answering, case timeline generation, document comparison and AI-assisted drafting, each with its own published credit rate. The product page carries the HTML title 'Powered by AI' and the headline 'India's trusted Legal Research partner, Powered by AI', and the features link states the platform uses NLP, AI and ML for information retrieval. What holds it off A is that the vendor itself positions the AI as one retrieval mode among several rather than as the product. Its own guidance directs users to MANU SEARCH, LEGAL SEARCH and CITATION SEARCH for precise, literal or Boolean queries and reserves AI Search for meaning-based ones, and the AI is metered separately from the content subscription through a credit wallet, so a subscriber can hold the platform without holding the AI. The underlying asset is the editorially enriched corpus and the citation and treatment apparatus, which predate the models and would survive their removal. Verified 13 September 2026.

Real architectural controls sit under an unqualified accuracy claim that is never measured, which is the shape this band's middle grade exists for. The controls are documented and specific. Output is returned in the IRAC format with a list of the sources relied on, each openable and downloadable, with a summary of the source and a statement of why it was pertinent. Retrieval is from a closed curated database of laws, circulars and judgments rather than the open web, and the vendor describes the order as retrieve from the corpus, then reason, then verify. The published model layer names output hallucination detection and a meta reasoning gate, per-tenant guardrails and signed model checkpoints. The reasoning chain is stated in absolute terms: every factual claim in every output is traced back to its source, and if the trace is broken the claim is flagged, with no exceptions. MIRA is described as checking its own reasoning against a layer built specifically to catch its mistakes. What is absent is any measurement of the claim. The vendor markets research without hallucination and grounded, hallucination-free legal intelligence, and publishes no accuracy figure, no error rate, no hallucination rate, no test set, no benchmark and no evaluation result for any of it. An absolute negative claim with no measurement behind it is weaker evidence than a modest measured one, and it is recorded here because a reader should be able to see the gap between the claim and what supports it. The trust center lists an item titled A note on Hallucinations and a report titled AI Flow for Ask; neither was opened on this channel and both are the named rebuttal route on this row. Trust page, product pages and terms read 7 September 2026.

Grounding is real, documented and architecturally specific, and no accuracy figure is published, which is the B band precisely. The grounding is described in the vendor's own AI brochure and is more than an assertion: AI Search runs against a proprietary, editorially enriched corpus rather than public web data, results are returned as the ten most relevant judgments organized into Facts, Issues, Arguments, Reasoning, Ratio and Summary, hovering Reference confirms the case source, clicking Citation opens the full judgment, and the vendor states that every insight is explainable and traceable to verified legal sources. The platform also surfaces judicial treatment directly, detecting overruled, distinguished and conflicting judgments and marking currency with blue, yellow and red flags, so the citation-status limb of the A band is satisfied even though the band overall is not. The index's rule governs the hallucination claim rather than the D limb: the brochure states that the editorial foundation ensures the AI operates strictly within the legal framework, significantly reducing inaccuracies and eliminating AI hallucinations, and that claim stands alongside real controls rather than in place of them, so 'bare' does not apply. The failure-modes limb of the A band is satisfied, and it is the most substantive thing this vendor publishes about the limits of its own AI. The brochure carries a section headed 'Guidance on Using AI Search' with an express 'When NOT to Use AI Search' list, telling users to avoid AI Search for precise or literal queries, party names, case citations, exact statutory phrases and verbatim quotations, stating that it does not follow Boolean logic, and routing those queries by name to MANU SEARCH, LEGAL SEARCH and CITATION SEARCH. A further page contrasts well-framed and poorly framed queries across nine worked examples. Very few records in this corpus publish where their own retrieval is weak, and this one does it in the vendor's own voice and in specific terms. What keeps the row at B is the limb the band leads on: no measured accuracy is published for AI Search, AI Summary or AI Compare, no test set is described, no error rate or evaluation exists, and nothing quantifies the elimination claim, which is an absolute assertion of the kind this axis exists to test. The remaining A limb also fails: nothing states that the system reports finding no support, and on a product that always returns a ranked ten, whether the tenth result is relevant or merely nearest is unanswered. The agreement pulls the other way and is recorded because it is the vendor's own instrument: clause 11.12 states that judgment text on the site is computer generated and that authenticity, correctness and preciseness must be verified from the certified copy, and clauses 15.1 to 15.3 disclaim any warranty of accuracy and place verification checkpoints on the user. Verified 13 September 2026.

The oversight position is contractual and an automated checkpoint is described, with the threshold at which the agent acts alone left unstated. Clause 8 of the terms is headed AI outputs and professional responsibility and is unusually direct: outputs are tools to support legal or compliance work and not legal advice, the customer remains responsible for reviewing and validating all outputs before relying on them, filing them or acting upon them, no output creates a lawyer client relationship with the vendor, and the customer's professional judgment is not replaced by the Service. Clause 7 adds a conduct obligation most agreements omit, that the customer will not use outputs to falsely attribute authority or to deceive any court or tribunal. On the product side an automated gate is described rather than merely asserted: the model layer publishes a meta reasoning gate and output hallucination detection through which every input and output passes, with the vendor stating that failure of any layer opens a ticket rather than a breach, and MIRA is described as verifying its own reasoning before producing output. Marketing states the position plainly, that the routine work is taken and the judgment stays with the user, end to end under supervision. What is missing is the limb this band names as commonly absent. Nothing states what MIRA does without a person, at what point a skill chain completes unattended, whether any step requires human approval before the next runs, what a user sees when the meta reasoning gate rejects a claim, or whether autonomy is configurable. Terms of service and trust page read in full 7 September 2026.

Substantive published material on how the tool is meant to be used and where it should not be relied on, short of the A band's thresholds and review surfaces. The strongest item is unusual enough to name in full. The vendor's AI brochure carries a section headed 'Guidance on Using AI Search' with an express 'When NOT to Use AI Search' list, telling users to avoid AI Search for precise or literal queries, party names, case citations, exact statutory phrases and verbatim quotations, stating that AI Search does not follow Boolean logic, and routing those queries to the named non-AI modes MANU SEARCH, LEGAL SEARCH and CITATION SEARCH. That is a published negative boundary attaching to a named mode, and it is rarer in this corpus than a confidence score. Around it sit real verification affordances: Reference hover to confirm the source, Citation click to open the full judgment, and a follow-up chatbot for narrowing rather than for acting. The agreement reinforces it, clause 15.3 placing responsibility for sufficient procedures and checkpoints on the user and clause 11.12 requiring verification against the certified copy. What is absent is what A asks for. No confidence score, no threshold, no statement of what the system does with a query it cannot answer well, no review surface before output, and nothing at all on oversight of the ManuWorks AI Drafter, which generates legal drafts at 50 credits per query with no described review step. R124(2) is the reason this is B and not A: the constraint published here attaches to a named mode but describes which queries the mode suits rather than what its output may not be used for, which is the limb the Verbit tier constraint satisfied. Recorded against parking item 2 as the closest instance in this lane. Verified 13 September 2026.

A named customer roster with real institutional weight, and no outcome measured or attributed. The roster is published on the homepage and spans professional services, industry and government: KPMG, Dhruva Advisors, Greaves Cotton, Thermax, K Raheja Corp, Aurtus, MyGate, Artha Energy and the Government of India, with the vendor stating more than 100 enterprises. A government body and a Big Four firm as named users are meaningful signals in this market. Public milestones are dated and checkable: the platform was showcased at NVIDIA GTC 2026 in March 2026, where the company announced a preview beta launch in the United States, and the skill library is quantified at 215 production skills. What is absent is everything past the logo. No case study is published, no customer is quoted by name and role, no deployment is described, and no outcome is measured: no time saved, no volume processed, no adoption figure, no accuracy or quality result from any customer. The efficiency claims that do appear are unattributed and unquantified, being research memos in hours rather than days and authority bundles built automatically. A reader can establish who is said to use it and nothing about what it did for them. Homepage, about page, trust page and the March 2026 announcement read 7 September 2026.

Scale is claimed at length and no customer is named and no outcome is measured, which is the C band. What is published is substantial as usage evidence: more than 150,000 active users, more than 10 million legal documents and judgments indexed, twenty-five years of operation, a team of more than 175, and offices across India and Bangladesh. The About page's 'Who We Serve' section enumerates five clientele categories, being legal professionals and law firms, in-house legal departments in corporations and banks, academic institutions, government bodies and regulatory agencies, and law students and researchers across Asia. Categories are not customers. Not one law firm, company, court, tribunal or university is named anywhere on the surfaces read, there is no client wall, no case study, no testimonial and no logo strip, which is a marked contrast with the penetration disclosure typical of vendors at this scale in the corpus. Nor is any outcome quantified: nothing states time saved, research hours displaced, accuracy improved or matters affected, and the AI brochure's benefit claims are functional descriptions rather than measurements. The 150,000 figure is itself unattributed and undated, appearing as a counter on the product page and in the About page metadata. The seed recorded 100,000 users, which the vendor's own current pages contradict; the figure written here is the vendor's. Verified 13 September 2026.

Substantive published commitments across every limb this axis tests except the one that decides the top grade. What is published, and most of it contractually: clause 10 of the terms binds each party to hold the other's confidential information in confidence and use it only for the purposes of the agreement, names Customer Content as the Customer's confidential information, and survives termination for five years or in perpetuity for trade secrets. Clause 5 leaves all rights in customer content with the customer and grants the vendor a license to process it solely to provide the Service. The privacy policy states that content data is governed by strict access controls and is accessible only to the account it belongs to. The trust page publishes matter level isolation on multi-tenant software as a service, which is a direct answer to the question this axis asks and one most records cannot give, alongside role based access control with custom roles, single sign-on required on all enterprise deployments, least privilege, access log management, and session recording and replay on enterprise. Customer managed keys with hardware security module storage are available on the non-SaaS modes, and retention is configurable to zero on enterprise and on the on-premises and air-gapped modes. What is absent is express privilege and work product treatment. The words privilege and work product appear nowhere on any surface read; clause 8's statement that no lawyer client relationship arises with the vendor addresses the vendor's own position, not the protection of the customer's privilege. That limb is required, so the record holds below the top grade. Terms, privacy policy and trust page read in full 7 September 2026.

Substantive published commitments across every limb this axis tests except the one the index's rule makes decisive, which is what holds an otherwise exceptional record at B. The commitments sit in the published customer agreement rather than a policy page, and they are unusually precise. Clause 4.1 defines Confidential Information to include documents, data, personal data, case files, names, facts, legal strategies and client information uploaded through the website, the AI tools or any related service. Clause 4.2 requires that it be treated as strictly confidential, used solely for the limited purpose of providing the specific service requested, and not copied, stored, retained, archived, analyzed, mined, disclosed or shared for any other purpose, with access restricted to need-to-know personnel under equivalent confidentiality obligations. Clause 4.3 bars disclosure to any third party including affiliates, subcontractors, AI engines and cloud providers without prior express written consent. Clause 4.7 requires permanent deletion of all Confidential Information and any copies, backups, AI memory, logs, caches or traces immediately after the request is fulfilled and in no event later than 24 hours, with written certification of deletion available on request. Clause 5.8 bars employee viewing of Subscriber Content or AI outputs except to resolve a specific technical issue the Subscriber has raised, with such access logged and minimized. Clause 4.8 makes these obligations survive termination indefinitely. Training is consent-gated and graded separately. The limb that fails is privilege and work product, and it fails as a matter of language rather than of substance: neither privilege, professional secrecy, work product nor any equivalent is named anywhere, and nothing addresses what happens to privileged material if disclosure is compelled. Clause 4.1's enumeration of case files and legal strategies is the closest the corpus has come outside Verbit's express work-product clause, and it is not the same thing. Verified 13 September 2026.

The boundary is drawn in the agreement, backed by an access gate, and no governing professional instrument is named. What is published: clause 8 states that outputs are tools to support legal or compliance work and not legal advice, that the customer remains responsible for reviewing and validating outputs before relying on, filing or acting on them, that no output constitutes a lawyer client relationship with the vendor, and that professional judgment is not replaced. Clause 7 carries a prohibition rarely seen in a legal AI agreement and directly on this axis: the customer will not use outputs to falsely attribute authority or to deceive any court or tribunal. Clause 2 gates the product itself, restricting paid plan eligibility to legal or compliance professionals or those employed in a role requiring legal research and drafting tools, which is an access control rather than a disclaimer and is a real answer to the unauthorised practice question. The vendor also states that every skill is designed, tested and validated by senior lawyers. What is absent is any named authority. No rule of the Bar Council of India, no provision of the Advocates Act, no state bar council guidance and no court practice direction is cited anywhere, in a jurisdiction where the Supreme Court has publicly taken up the consequences of AI-generated authority in filings. Terms of service and about page read in full 7 September 2026.

Substantive published commitments short of alignment with any conduct rule, which is the B band. The agreement addresses the question head on rather than by implication. Clause 16.1, headed 'No Legal Advice', states that material contained on or made available through the site is not intended to and does not constitute legal advice and does not in any manner establish a client-advocate relationship. The disclaimer published on the legal page repeats that the company does not warrant any form it provides and is not creating a lawyer-client relationship by providing forms, and adds that forms should be used as a guide and modified to suit requirements and laws, at the user's own risk. Clause 15.3 places on the user the responsibility for implementing sufficient procedures and checkpoints to satisfy accuracy requirements for input and output. Clause 11.12 goes further than most records in this corpus by requiring that the authenticity, correctness and preciseness of judgment text be verified from the certified copy of the judgment, which is a verification duty rather than a disclaimer. Taken together that is a real posture on who is answerable for the output. What is absent is any engagement with the professional rules themselves. No conduct rule of any jurisdiction is named, the Bar Council of India is not mentioned, and no clause requires the subscriber to use the product consistently with professional obligations. The gap is sharper than usual on this record and is named rather than passed over: the Supreme Court of India held in July 2026 that citing unverified AI-generated precedent is professional misconduct and directed the Bar Council of India to frame norms, and this vendor publishes that ruling as editorial content on its own updates service while publishing nothing about what its own AI features mean for that duty. Verified 13 September 2026.

Technical controls over the model are published in detail and no governance apparatus is described. What is genuinely governance-adjacent and credited here rather than on the security row: per-tenant custom guardrails, which put configuration of model behavior in the customer's hands, and the vendor's statement that every skill in the library is designed, tested and validated by senior lawyers before it ships, which is a human review gate on the product's content. The trust center also lists a code of ethics, anti-bribery and anti-modern-slavery items, and a product security entry titled A note on Hallucinations. What is missing is everything that would make this governance of the AI rather than security around it. No AI governance framework or standard is published or claimed and no ISO/IEC 42001 or equivalent is asserted, in contrast to the five security and privacy frameworks that are asserted with precision. Nobody is named as accountable for model behavior. No pre-release evaluation protocol, benchmark, red-team exercise or published result exists for any model or skill. And no bias, fairness or representativeness disclosure appears at any level, which is worth naming for a product whose corpus is Indian judicial and tax material and whose outputs are used in a jurisdiction where courts have begun scrutinizing AI-derived authority. Trust page, about page and trust center index read 7 September 2026.

Something is published and it is a paragraph, which is the C band rather than the D. The legal page carries a section headed 'Use of AI' reading, in full, that the vendor is committed to using artificial intelligence responsibly and prioritizes data privacy, bias mitigation, transparency, human oversight, accountability, user consent, and collaboration with regulations, with the stated aim of maximizing AI's benefits while ensuring ethical practices and minimizing potential risks. That is a list of the right words and it is the whole of it. Nothing behind any of the seven named priorities is published: no framework is adopted or certified, no accountable owner or committee is named, no governance process is described, no bias testing is described and no results of any kind are disclosed, and nothing states how human oversight is exercised in a product where the oversight the vendor actually documents is guidance to the user rather than a control in the system. Bias in particular is asserted as a priority and never returned to, on a product whose AI ranks and summarizes judicial authority and surfaces judicial treatment, where a systematic tilt in which precedents surface would be invisible to the researcher. Recorded and not credited as governance, because they are commercial or contractual rather than governance instruments: the agreement's AI section is a strong commitment and is graded on the confidentiality and training rows, and the responsible-AI paragraph is not tied to it. The Grievance Redressal Officer named on the same page is a statutory Indian IT Act appointment for complaints handling, not an AI accountability owner, and is recorded as such. Verified 13 September 2026.

Published policy across every limb this axis asks about, in the agreement and in a structured trust architecture, with one gap named. Certifications are asserted with precision: ISO/IEC 27001 certification stated as the 2022 revision, SOC 2 Type 2, ISO/IEC 20000-1:2018, plus GDPR, CCPA and India's DPDP alignment, with CERT-In empanelled audits and annual audit stated where applicable. Encryption is specified as TLS 1.3 in transit and AES 256 at rest, with customer managed keys and hardware security module key storage available on the non-SaaS modes. Access control is detailed: SAML 2.0, OIDC and SCIM 2.0 provisioning, single sign-on required on enterprise, role based access control with custom roles, multi-factor enforced through the customer's identity provider, least privilege and access log management. Network controls include virtual private cloud isolation, private link, web application firewall, denial of service protection, IP allow listing and geographic restriction, with no inbound traffic at all on the on-premises and air-gapped modes. On the model itself, prompt injection detection and sanitization and model poisoning defense via signed checkpoints. Training, retention and deletion are all committed: no customer content in shared training corpora, retention configurable and reducible to zero on enterprise and the isolated modes, data erasure documented, and data exportable at any time with return or destruction at customer election on termination, with attestation. Incident practice exists on both sides, a data breach notification item in the trust center and a coordinated disclosure program committing acknowledgment within 24 hours, triage within 72 and remediation to severity-based service levels, with safe harbor for good faith researchers. The gap, named because every partial names its limitation: the privacy policy states that a current sub-processor list is published at the trust center, and no such list appears on that page. Privacy policy, terms, trust page and trust center read 7 September 2026.

Substantive published policy covering most of the ground, missing the named subprocessor list, which is the B band and the single limb it names. What is published is contractual rather than promotional and it is specific. Clause 4.4 requires industry-standard technical and organisational security measures. Clause 4.5 commits to notifying the Subscriber in writing within 24 hours of becoming aware of any actual or suspected unauthorised access, disclosure, loss, corruption or breach, to providing full details and impact, to containing, investigating and remediating at its own cost, and to cooperating in legal, regulatory or remedial action. A named notification window with a stated content requirement is the limb most records in this corpus lack entirely. Clause 4.6 accepts the role of data processor with the Subscriber as data fiduciary under the Digital Personal Data Protection Act 2023 and commits to the Information Technology Act 2000. Clause 4.7 requires deletion within 24 hours with written certification. Clause 5.3 requires that any storage be temporary, encrypted and automatically deleted after use. The privacy policy adds encryption technologies, secure servers and firewalls, access control mechanisms, employee confidentiality agreements and training, and states these are regularly reviewed, and records compliance with the SPDI Rules 2011. What is missing is the subprocessor limb and it is missing in an interesting way. No processor is named anywhere, and clause 4.3 explains why the vendor might think none needs naming, since it bars disclosure to any third party including subcontractors, AI engines and cloud providers without express written consent. The privacy policy nonetheless discloses that third parties perform payment processing, email delivery and hosting, and that the products may integrate cloud storage services including Dropbox and Google Drive, so processors exist and none is identified. No certification supports any of it. Verified 13 September 2026.

More of what this axis asks for than most records carry, with one absence that keeps it off the top. What is published: an affirmative warranty, clause 11 warranting that the Service will be provided with reasonable care and skill, which is a positive obligation rather than the pure as-is disclaimer that is the norm in this corpus. A service level with a number, clause 9 carrying a 99.5 percent monthly uptime target on the SaaS mode and bespoke service levels on enterprise and non-SaaS modes set out in the order form, with a named customer success manager for enterprise. Insurance disclosed rather than absent, the trust center listing both cyber insurance and professional indemnity insurance in its legal section. A liability cap at clause 12 set at fees paid in the twelve months preceding the claim, mutual exclusion of indirect, incidental, consequential and punitive damages, and express carve-outs preserving liability for gross negligence, wilful misconduct and anything that cannot be limited by law. Termination at clause 13 on 30 days uncured material breach, with customer content returned or destroyed at the customer's election and, per the trust page, with attestation. What is absent is indemnity. No indemnity of any kind runs to the customer: no intellectual property indemnity, no defense obligation, no remedy ladder, nothing. And the warranty that does exist covers the manner of provision rather than the product's output, clause 11 stating expressly that outputs are not warranted to be accurate, complete, error free or fit for purpose, so on the question this axis exists to ask the customer still bears the loss when an output is wrong. Terms of service and trust center read in full 7 September 2026.

A published agreement addresses three of the four limbs with real specificity and the overall allocation is heavily one-sided, which is B rather than A. Warranty is addressed by exclusion: clauses 25.1 and 25.2 provide the information on an 'As Is' basis and disclaim all warranties including merchantability, fitness for purpose and non-infringement, and clauses 15.1 and 15.2 disclaim any representation that the service will be correct, accurate, reliable, uninterrupted or timely. Liability is addressed and largely excluded: clauses 25.3 and 25.4 exclude liability in contract or tort for any loss howsoever arising in connection with the service, expressly including where caused by the vendor's own negligence, and clause 25.5(i) is the provision that matters most on this axis, excluding liability for any claim relating to the subscriber's inability or failure to perform legal research work properly or completely, or to any decision made or action taken in reliance on the Data. A cap exists at clause 26.1, limited to the aggregate charges paid during the subscription period, though it is drafted as applying to claims relating to copyright in the data rather than as a general cap, which is a real gap named here rather than smoothed over. What lifts this above the floor is that the agreement also runs the other way, which is uncommon in this corpus. Clauses 21.2 and 26.3 require the vendor to indemnify, defend and hold harmless the Subscriber, its clients, employees and affiliates against claims, losses, damages, liabilities, penalties and legal costs arising from any breach of confidentiality or misuse of Subscriber Content, any unauthorised access or data breach, any negligence, wilful misconduct or violation of law by the vendor or its personnel, and any infringement of intellectual property rights. Clause 5.9 adds immediate termination, indemnification and injunctive relief without proof of special damages for misuse of Subscriber Content, and clause 12.1 a prorated refund. Insurance is not addressed anywhere. Verified 13 September 2026.

Enterprise identity integration is specified in unusual detail and no legal practice system is named. What is established: the agreement defines the Service as including web, API and on-premise components made available under an order form, so a programmatic surface is contracted for rather than merely advertised; and the identity layer is published with named standards, being SAML 2.0, OIDC and SCIM 2.0 provisioning, with single sign-on required on all enterprise deployments and multi-factor enforced through the customer's own identity provider policies. On the isolated modes the platform runs inside the customer's own cloud estate using the customer's identity and access management and keys. Those are real integrations and they are integrations with the customer's security stack, not with the systems a legal team works in. What is absent is the substance of this axis. No document management system, case or matter management platform, word processor, email client or e-signature product is named on any surface read. No integrations page, connector directory or partner list was located in the site navigation. No API or developer documentation was located, so the API's existence is established from the agreement and its scope and depth are not. Nothing describes what data moves in which direction between the platform and any system a firm already runs. Terms of service, trust page, privacy policy and site navigation checked 7 September 2026.

Integrations are claimed and some host applications are named, with no documented catalog and no configuration detail, which is the C band. What is named is thin and scattered rather than gathered on an integrations page, and no integrations page exists in the navigation, which is itself a page-inventory finding. The research platform publishes a 'Plug In' item in both the Subscription and Research menus, resolving to ManupatraAlert, an alerting plug-in on the manupatrafast.com property. The privacy policy discloses that the products may integrate or offer third-party services including data visualization services and cloud storage solutions, naming Dropbox and Google Drive, for uploading, storing or sharing documents. The wider suite implies internal connection between the research platform and the Mykase practice and case management product, Manucomply and Manucontract, but each sells on its own domain with its own login and nothing published describes data moving between them. What is absent is everything the higher bands ask for. No practice management system, document management system or CRM used by Indian firms is named as supported, so a buyer cannot establish whether its own system connects. No public API reference, developer documentation, connector register or authentication model was located. No direction of flow, prerequisite or configuration step is described for any connection, including the plug-in. Nothing states whether AI Search or the ManuWorks toolkit can be reached from inside another application or only from the vendor's own interface. Verified 13 September 2026.

Both limbs are published in full, per mode, and the record states what changes between tiers, which is the question this axis asks and which most records cannot answer. Five deployment modes are named and described. Mode A is multi-tenant software as a service hosted in India on ISO 27001 certified infrastructure, with matter level isolation stated for the multi-tenant case. Mode B is single tenant on the L&T Vyoma sovereign Indian cloud, with virtual private cloud isolation. Mode C runs inside the customer's own AWS, Azure or Google Cloud estate in a region of the customer's choosing, with the customer's own identity and access management and keys, virtual private cloud isolation and private link or private service connect. Mode D is on premises, including an NVIDIA DGX Spark unit on a desk or a full deployment in the customer's data center. Mode E is air gapped, with the vendor stating there is no inbound traffic at all on modes D and E. Residency is addressed as architecture rather than a setting: data location is stated per mode in the privacy policy, and residency can be locked to a chosen region on modes B, C, D and E. Customer managed keys with hardware security module storage are available on modes C, D and E. Cross-border transfers for customers outside India are stated to be governed by standard contractual clauses and equivalent mechanisms. What a buyer cannot establish is a residency choice on the entry SaaS mode, which is fixed in India, and no sub-processor list was located to test the mode statements against. Privacy policy, trust page and homepage read in full 7 September 2026.

Cloud delivery with a published residency commitment and no tenancy model stated, which is B because tenancy and region are co-equal limbs and publishing either clears C. Residency is answered in unusually committal terms for this corpus. The privacy policy carries a section headed 'Data Localization' stating that all personal information is stored and processed on servers located within the user's country of residence, that for users in jurisdictions requiring data localization the vendor ensures personal data is stored and processed on servers physically within that country's territorial boundaries, and that it does not transfer such data outside the country unless in accordance with applicable law and with appropriate safeguards. The About page describes the company as a cloud-first platform, and the AI brochure states that the models are trained on Indian data and built in India, which speaks to where the processing sits even though it is written as a provenance claim. The limits are real and are named rather than left to inference. The localization commitment is written about personal information, and the material this axis most concerns on an AI product is Subscriber Content uploaded to the AI tools, which the agreement governs on confidentiality terms without stating where it is processed; the two are not the same category and nothing joins them. No tenancy model is described anywhere, so a buyer cannot establish whether a firm's uploaded documents sit in a shared or isolated environment. No data center, region, availability zone or cloud provider is named, no on-premises or private deployment is offered or refused, and nothing distinguishes storage from processing for the AI features specifically. Verified 13 September 2026.

A real trust center with a named artifact inventory, and the reports behind a request whose terms the portal does not state. What is ungated: six compliance positions in the trust center, being ISO/IEC 27001, ISO/IEC 20000-1:2018, SOC 2 Type 2, SOC 2, GDPR and CCPA, with the vendor's own trust page adding DPDP and stating the ISO certification as the 2022 revision; CERT-In empanelled audits, which is the Indian government-recognised assessor regime and a meaningful local signal; a risk profile giving data access level, impact level and a four hour recovery time objective; a control inventory spanning product security, data security, data privacy, access control and environmental, social and governance items; and a coordinated disclosure program with published response times of 24 hours to acknowledge and 72 to triage. What sits behind the access flow: the ISO/IEC 27001 certificate, the SOC 2 Type 2 report, a vulnerability assessment report, a penetration test report, a security compliance and deployment FAQ, and a document titled AI Flow for Ask. The portal offers to start a security review, to view and download sensitive information and to request access, and does not state whether access is instant on an email address, a self-service non-disclosure click-through, or approval after a sales conversation, so the lower tier is taken under the standing rule and that is why this is not the top grade, alongside the absence of any named auditor, audit period or scope statement. One discrepancy is recorded: the on-site trust page lists five frameworks including DPDP and omitting ISO 20000-1, while the trust center lists six including ISO 20000-1 and omitting DPDP. No request was submitted. Trust page and trust center read 7 September 2026.

No certification and no trust center were located on any surface, which is the D band, and the absence is the vendor's rather than this index's. The page inventory was taken from the navigation and footer under R20 and there is no security page, no trust page, no compliance page and no certification badge anywhere on the estate: the footer's Company column runs About, Contact, Careers and Legal, and the Legal page's six tabs are Corporate, Copyright, Privacy Policy, Disclaimer, IT Compliance and Public Record. No ISO 27001, ISO 27701, SOC 2, StarAudit, CERT-In empanelment, PCI DSS or any other standard is claimed, no auditor is named, no report period is given, and no certificate, attestation or penetration test summary is offered for download or on request. A targeted search for certification claims returned nothing attributable to the vendor. What exists instead is a description of controls without external validation, and it is recorded so the grade is read as a disclosure finding rather than as a claim about the vendor's actual security: the privacy policy lists encryption technologies, secure servers and firewalls, access control mechanisms, and employee confidentiality agreements and training, stated to be regularly reviewed and updated, and the agreement commits at clause 4.4 to industry-standard technical and organisational measures. The statutory position is disclosed, being compliance with the Information Technology Act 2000, the SPDI Rules 2011 and the Digital Personal Data Protection Act 2023, with a named Grievance Redressal Officer, but a statutory compliance assertion is not an independent attestation and is not credited here. Verified 13 September 2026.

The architecture is described and nothing in it is named, and the one list the vendor says it publishes could not be found where it says it is. What is disclosed: the vendor states it built and trained its own model on its legal corpus and positions that against fine-tuning and retrieval-augmented generation, and its published model layer describes signed model checkpoints, per-tenant guardrails, prompt injection sanitization and an inference audit trail, all of which are the controls of an operator running its own inference. So a reader learns that the model is claimed to be the vendor's own, which is a real answer to part of the question. What is not disclosed is any name or any boundary. No model or model family is named. No third-party model, API or inference provider is named, and nothing states whether any is used at all, so a reader cannot tell whether customer content reaches an outside model on any mode. The infrastructure that is named is either the vendor's own hosting in India, the L&T Vyoma sovereign cloud, or the customer's own AWS, Azure or Google estate, and a customer's own cloud is not a supply chain disclosure by the vendor. Change notification is committed and is the strongest element here: the privacy policy states that customers are notified of material changes to the sub-processor list, with a right to object for enterprise customers. But the list itself is stated to be published at the trust center and does not appear on that page, so the commitment attaches to a document that could not be located. Privacy policy, terms, trust page and trust center read 7 September 2026.

The supply chain is partly disclosed, which is the B band's territory on partiality but falls to C because what is disclosed is the technology class and the build location rather than anything about the models themselves. What the vendor does say is more than silence and is recorded precisely. The AI brochure and the December 2025 launch material both state that Manupatra AI Search is powered by semantic AI and large language models. The brochure states that the system is trained on Indian data and built in India, and that it runs on a proprietary, editorially enriched legal knowledge ecosystem developed over decades rather than on generic AI systems trained on public or non-curated data. That answers what the models were pointed at and where the work was done. It does not answer the questions this axis asks. No model is named, no version is given, and no provider is identified, so a buyer cannot establish whether the large language models are the vendor's own, licensed, or accessed as a third-party service, and the phrase 'built in India' describes the product rather than the model. Nothing states where inference runs. No commitment to notify subscribers of a model change was located. There is no subprocessor list that would answer the question by another route. One provision cuts against the silence and is noted because a careful reader will find it: clause 5.5 of the agreement bars the vendor from making Subscriber Content available to third parties including, expressly, AI vendors and cloud providers without prior express written consent, which contemplates that such vendors exist in the stack while naming none of them. Verified 13 September 2026.

Published figures with a stated unit, a genuine free trial, and the commercial mechanics in the agreement rather than withheld. Two paid tiers carry figures on the vendor's own site: Professional from 9,000 rupees per user per month and Enterprise from 17,250. A seven day free trial of Legal AID is published on the site and confirmed at clause 4 of the terms, expressly requiring no payment instrument to start, with the vendor reserving the right to limit trial features and usage caps. Eligibility is stated rather than left implicit, clause 2 restricting paid plans to legal or compliance professionals or those in a role requiring legal research and drafting tools. The mechanics sit in the agreement: subscription basis, fees and billing frequency and currency set out in an order form or product plan, all fees exclusive of GST, VAT and equivalent taxes added at prevailing rates, and late payment attracting interest at 1.5 percent per month or the statutory rate if lower. Clause 9 publishes a service level with a figure, a 99.5 percent monthly uptime target on the SaaS mode. Clause 13 states the termination position and what happens to customer content on exit. Three gaps are named rather than smoothed: the four non-SaaS deployment modes and MIRA carry no published price and route to an order form; no usage quota, seat minimum or overage term is published for either paid tier; and trial usage caps are expressly discretionary. Homepage, pricing statements and terms of service read 7 September 2026.

Figures, units, structure and the governing commercial terms are all published and a buyer can plan against them without a sales conversation, which is the A band. The AI Solutions page publishes an ungated price table. Unlimited AI Summary access is 5,000 rupees a year for Supreme Court judgments, 5,000 rupees a year for High Court judgments and 10,000 rupees a year for both, all stated exclusive of GST. AI wallet plans covering AI Search, AI Compare and AI Summary are published at 1,000 credits for 6,000 rupees, 1,500 credits for 9,000 rupees and 2,000 credits for 12,000 rupees. The unit of charge is not only stated but decomposed: the ManuWorks toolkit publishes per-feature consumption at 15 credits per page for OCR, 3 per page for summarization, 20 per page for translation, 5 per query for question-answering, 8 per page for timeline generation, 15 per document for comparison and 50 per query for AI drafting, with credit value fixed at 1 credit to 1.25 rupees, a 10,000 rupee minimum first purchase and a 5,000 rupee minimum top-up. Activation is stated to be pro-rated and a credit dashboard showing top-ups, usage and balance is described. So a buyer can model the cost of a specific workload in advance, which almost nothing else in this corpus permits. The commercial terms behind the price are published too, in the agreement: advance payment, non-refundability, renewal and deactivation mechanics, the vendor's right to modify charges with effect from the next renewal term, a seven-day window to dispute transactional charges, and taxes payable in addition. Two limits are named rather than glossed. The content subscription itself, as opposed to the AI add-ons, routes to a subscription plans page and the agreement states that the product price card is available on request, so the platform's own base price is less exposed than its AI pricing. And clause 3.9's transactional pricing statement implies a usage-metered tier whose rate card is not published. Verified 13 September 2026.

Practice scope is named with specificity and the corpus behind it is not inventoried. What is published: four practice domains addressed by name, being direct tax, indirect tax, corporate law and general laws, over a corpus described as a closed database of laws, circulars and judgments and characterized as India's largest repository of legal documents. Buyer types are named across the range this index cares about: general counsel, law firms and government bodies in the vendor's launch material, litigators and transactional and advisory counsel on the practitioner pages, and compliance professionals through the eligibility clause. Depth of capability is quantified where the vendor can quantify it, at 215 production skills composable into workflows. Currency of Indian law is addressed at least once in substance, the vendor distinguishing the Bharatiya Nyaya Sanhita from the Indian Penal Code as a failure mode of general-purpose assistants, which is a real coverage claim in a jurisdiction that has recently recodified its criminal law. What is absent is any inventory or boundary. No court or tribunal is named, no date range or historical start point is given, no depth statement distinguishes full text from headnote, and nothing states which parts of Indian law are thinly covered or out of scope. The United States is entered as a preview beta announced in March 2026 with no coverage description at all, so a reader cannot establish what the American corpus contains. Product pages, homepage, launch material and terms read 7 September 2026.

Coverage is documented with real substance across jurisdiction, content type and buyer role, short of the stated limits the A band requires. Jurisdictional coverage is the strongest part and is specific: Indian case law from the Supreme Court, all High Courts and all tribunals, together with legislative, regulatory and procedural material, notifications, reports, commentaries and secondary sources across all Indian jurisdictions and Commonwealth countries, with a dedicated content coverage page, more than 10 million indexed documents, and daily addition of new laws, notifications and judgments. A separate Bangladesh database, BDlex, is sold alongside. Buyer roles are addressed explicitly and across the range: the AI pricing page names students, lawyers, law firms and corporate legal teams as the audiences for the credit model, and the About page enumerates legal professionals and individual practitioners, in-house legal departments in corporations and banks, academic and educational institutions, government bodies, regulatory agencies and policy makers, and law students, researchers and educators across Asia. Practice coverage is addressed through the content rather than through practice-area packaging, which suits a general research database, and the index's rule governs that limb: a horizontal case-law platform does not vary by practice area and is neither credited nor penalized for the absence of practice-specific editions. What holds it off A is that no limit is stated anywhere. Nothing identifies a jurisdiction, court level, tribunal or content type that is out of scope, nothing states the earliest coverage date or any gap in the historical record, nothing says which Commonwealth jurisdictions are included and which are not, and nothing states whether the AI features cover the whole corpus or only parts of it, which matters because AI Search is described in terms of judgments while the database also holds statutes, rules and commentary. Verified 13 September 2026.