Icertis vs Lexagle: how they compare in 2026
Icertis is a stronger candidate for a large organization treating contracts as connected enterprise data across procurement, sales, finance and compliance. Its Azure based platform connects with systems such as SAP, Microsoft, Salesforce and Workday, with Copilots and the Vera agent layer spanning contract work. Lexagle offers a more focused approval proposition through Document Guard: plain English rules classify an agreement and tie the result to a protected version. Both need careful reading of data improvement rights. Icertis permits subscriber information to support service development and improvement under stated confidentiality limits, while Lexagle expressly includes certain aggregated or nonidentifying data in machine learning uses. In this respect, AI Legal Index identifies permission boundaries rather than a categorical no training distinction. The choice turns more on enterprise integration breadth versus the specificity of Lexagle's review gate.
At a glance
All 15 axes, side by side
The same grid applied to every vendor in the index, graded from public sources. Hover a grade to see what the letter means on that axis.
AI Centrality
How much of the product is actually AI. Whether the machine learning is the mechanism the buyer is paying for or a feature layered onto conventional software, and whether the vendor is specific about which is which.
Icertis offers Icertis Copilots, a contract intelligence engine that extracts clauses, obligations and risk, and Vera, an agent layer released across Engage, Operate and Analyze in 2026. The vendor says Vera acts autonomously within boundaries the customer sets. These sit on a contract platform for authoring, negotiation, approval, execution, obligation management and analytics, which runs without the models and was sold as Icertis Contract Management before the AI positioning. The rename to Contract Intelligence added an AI layer to that platform rather than rebuilding it.
Lexagle combines a conventional contract workspace with Lexie and Document Guard. Lexie drafts from approved templates, proposes clauses, extracts metadata and answers questions about agreements. Document Guard inspects clauses against a company's playbook and uses the result to permit signing, route a partial match to a person or block an unacceptable contract. It also requires another review when a protected version changes. These functions make AI part of the contract approval process, beyond a separate writing assistant. Templates, collaboration rooms, signatures and the repository still have value without those models, so the wider platform does not depend entirely on AI.
Citation Accuracy and Hallucination Disclosure
Whether the vendor publishes measured accuracy on citations and assertions, grounds output to primary sources, and says plainly what its system does when it does not know. Legal has a documented public record of fabricated citations reaching filed briefs, so an untested claim of accuracy is not evidence.
Icertis describes a contract intelligence engine that extracts clauses, obligations and risk and turns them into queryable data, and an intelligence layer across the enterprise that it says understands business and industry context. It publishes no accuracy figure, hallucination rate, test set or evaluation, and does not describe how an output links back to a source the user can open. One Gartner Peer Insights reviewer says their organization has not been impressed with the Discovery tool AI.
Document Guard compares agreement language with customer rules, highlights risky provisions and explains why a clause was flagged. The user can inspect the contract and the applicable playbook. Lexie also answers questions using the organization's contracts and institutional information. Lexagle promises consistent assessments through low temperature settings and fixed response parameters, but does not provide a reproducible accuracy test, error breakdown or hallucination rate. A claim of complete playbook alignment is not accompanied by test conditions. The material does not establish that every generated answer carries a link to its supporting passage or that suggested legal language has been independently validated.
Autonomy and Oversight Model
What the system decides on its own, what a lawyer must approve, and whether the vendor documents where the review point sits. A tool that drafts under review and a tool that files without one are different products and different risks.
Vera Composer gathers NDA or statement of work details through conversation, converts them into structured context, and assembles a draft using approved templates, clauses, and business rules. Vera Redline compares uploaded contracts with playbooks, exposes clause references and explanations, and proposes targeted changes for review. Exceptions escalate, while humans retain final legal judgment on complex or nuanced issues. Edits, clause selections, and reviewer actions are logged. The broader platform lets customers set boundaries for autonomous agents. Exact stop thresholds, configuration permissions, and correction procedures after an accepted error remain unspecified, although the review surface and human role are now explicit.
Document Guard has an explicit three state control scheme. A compliant agreement can proceed directly to signing, a partially compliant agreement is diverted for human review, and a noncompliant agreement is blocked or escalated. Legal teams define the rules in plain English, including payment, liability and jurisdiction requirements. Routing is driven by AI extracted information rather than a person selecting every action. A digital seal ties the compliance result to a particular version; external edits or a replacement upload trigger lockdown and another AI evaluation. This explains both the permitted unattended action and the circumstances requiring intervention, although it does not establish error rates.
Operational and Outcome Evidence
Named, dated evidence that the product works in production at real firms or legal departments. Case studies with figures and identified customers count. Unattributed testimonials and launch announcements do not.
Icertis publishes customer quotes that identify the customer by industry and revenue band rather than by name. Among them are an IT services company with more than $30 billion in annual revenue and a healthcare and biotech company with more than $1 billion. It says 30 percent of the Fortune 100 are customers, across more than 90 countries and millions of contracts. Gartner named Icertis a Customers' Choice in the 2025 Peer Insights Voice of the Customer report for CLM, with 93 percent of customers recommending the platform across 84 ratings. No published case study pairs a named customer with measured results.
Yamaha Motor Philippines is a named customer describing improved contract visibility, approvals and signing. Lexagle also describes deployments for a global financial institution, a property developer and a state lottery, but those organizations are unnamed. Its promotional results include shorter contract cycles, reduced administrative work and a high satisfaction percentage. Those figures do not share a published sampling method or an independently reproducible baseline. The Document Guard testimonials identify job titles and sectors without customer names. There is therefore support for operational use of the broader platform, while the measured accuracy and incremental benefit of its current AI gatekeeper remain uncertain.
Privilege and Confidentiality Posture
How client confidences are handled: attorney client privilege and work product treatment, segregation of one client matter from another, whether client data trains any model, and what the vendor commits to in writing rather than in marketing.
The SaaS Subscription and Services Agreement sets out role based access control, identity provider authentication, audit logs of every user action, encryption at rest and in transit, and a single tenant option. Section 4.5 returns Subscriber Data on request and permits destruction if it is not requested within five days of termination. Section 5.2 lets Icertis use Subscriber Data, including output, to maintain, develop and improve the service, provided the data is not shared with third parties and the Subscriber stays anonymous. The agreement does not address attorney client privilege or work product, or say how the Vera agents respect user permissions. A 2017 company news item describes storage on GDPR compliant cloud infrastructure with encryption at rest and in transit. Icertis also links a Trust Center from its site.
Lexagle describes separate customer datastores, application controls that prevent access across customers and tests that block a release if separation fails. Administrators can assign permissions for individual platform components, and internal collaboration rooms separate private discussion from counterparty work. Its displayed service terms also impose confidentiality obligations, but permit analysis of customer information to improve services and expressly allow certain aggregated or nonidentifying data to train machine learning. That permission matters for confidential contracts even when natural persons cannot be identified. No attorney client privilege preservation undertaking or detailed explanation of how legal matter restrictions apply to AI answers is provided.
UPL and Professional Responsibility Posture
Whether the vendor is clear that it supplies a tool rather than legal advice, who its audience is, and how it addresses unauthorized practice of law, competence and supervision duties, and jurisdiction limits. ABA Formal Opinion 512 is the reference point. Where the advice line is not the duty a product raises, the axis is read through the nearest professional duty it does raise: judicial conduct rules and the reviewing duty for products sold only to courts, and the duty to bill for time actually spent for products that draft time entries.
Icertis sells the platform across legal, procurement, sales, finance and HR, where it handles NDAs, service agreements and HR paperwork alongside commercial contracts. Its AI drafts, redlines and negotiates for all of those users. The product pages, company section and research library take no position on where a tool ends and legal advice begins, and say nothing about competence or supervision duties. They set no jurisdiction limits, although Icertis operates in more than 90 countries. The human first framing describes how the product is designed rather than a position on professional responsibility.
The service terms expressly state that Lexagle is not a law firm, does not provide legal advice and does not create a lawyer client relationship. They also state that it carries no professional indemnity insurance and leave legal suitability and conclusions with the customer. Document Guard can apply a legal team's playbook, but passing its rules does not establish the legal effect of an agreement. The product is promoted to law firm partners and associates as well as corporate teams, while the displayed terms restrict third party service provision. That unresolved scope difference matters before using it for external client work.
AI Governance and Bias Disclosure
Published governance over model behavior: who owns it inside the vendor, what is tested before release, and what is disclosed about disparate output across matter types, parties, or populations.
Icertis calls itself AI native and human first, says its agents operate within boundaries the customer sets, and publishes annual research on buyer concerns about AI. That research reports that 55 percent of contracting leaders cite data output quality as a significant concern and 44 percent lack sufficient trust in autonomous AI. The product pages and research library describe no AI governance framework, no AI management certification such as ISO 42001, no named owner of model governance and no testing before release. They say nothing about uneven output across matter types, parties or populations.
Lexagle describes client defined rules, low temperature model settings and automated checks on software access controls. These explain parts of application behavior, but not a company program for governing AI development and release. There is no named AI risk owner, published bias evaluation, testing across languages or report of recurring model failures and corrective action. The platform's regional compliance claims and security certifications address other responsibilities. Legal teams can control the standards used to approve their own contracts, yet the vendor does not explain how it assesses systematic errors in the underlying models or decides when a changed model is ready for use.
AI Safety and Data Stewardship
Retention, deletion, access control, and what happens to prompts and documents after they are processed. Whether the vendor states its subprocessors and its incident practice, or leaves the buyer to assume.
Section 4.5 of the agreement returns Subscriber Data on request at no fee and permits destruction if it is not requested within five days of termination. Exhibit B sets out strict role based access, identity provider authentication with multifactor support, audit logs of all user actions, encryption at rest and in transit, Azure network security groups and threat monitoring. It also commits Icertis to notify the Subscriber of any breach resulting in loss or unauthorized disclosure of Subscriber Data, under a documented incident process. Section 6.1 bars sale of personal data and its combination with other sources, while section 5.2 permits use of Subscriber Data to develop and improve the SaaS. A List of Standard Sub-Processors, in a version dated June 2023, is published on the foundation page.
The security policy describes encryption in storage and transit, isolated customer datastores, component permissions and an incident process with prompt written notice once a breach affecting customer data is verified. The privacy notice names several service providers and describes retention for account operation, legal requirements and other stated purposes. It promises deletion or anonymization once information is no longer needed, without a complete schedule for contract content, AI prompts, outputs and backups. The service terms separately permit some improvement and machine learning uses after the subscription ends. This provides several concrete controls, while leaving the full AI data lifecycle and model processor arrangements incomplete.
AI Liability and Recourse
What the vendor stands behind contractually when its output is wrong. Indemnities, caps, carve outs, insurance, and whether any of it is published or only reachable through a negotiated agreement.
Section 9.1 of the agreement gives a defense and indemnity for third party intellectual property claims, for claims by Icertis subcontractors or personnel, and for gross negligence causing injury or property damage. It states an exclusion for Subscriber Data. Section 10.1 excludes consequential loss, and section 10.2 caps each party at the amounts Icertis received in the preceding twelve months. Section 8.2 warrants noninfringement, professional performance and material conformity to the documentation, with a correction remedy and a termination right. Section 10.4 commits Icertis to carry commercial general liability cover of $1 million per occurrence and $2 million in aggregate. It adds technology errors and omissions cover including cyber liability of $5 million, umbrella cover of $5 million and employer's liability. The cover comes from a carrier rated A minus, runs for the term and one year after, and a certificate is available on request. The agreement gives AI output no separate warranty. An AI Acceptable Use Policy sits on the foundation page as an addendum to the agreement.
Lexagle undertakes to defend customers against specified infringement claims concerning the service, including Singapore patent, copyright, trademark, database and confidentiality rights. That is an ordinary service indemnity, with procedural conditions and an exclusive remedy provision; it does not expressly cover fabricated legal analysis or defective AI drafting. The displayed terms disclaim legal suitability and accuracy, assign responsibility for conclusions to the customer and exclude consequential losses. They also state that Lexagle has no professional indemnity insurance. The combination provides some recourse for a defined class of service claims, without an affirmative warranty or specific remedy for an AI generated clause that causes loss.
Practice Systems Integration Depth
How deeply the product reaches into the systems legal work already lives in: document management such as iManage and NetDocuments, Word and Outlook, contract lifecycle management, matter management, e-billing, and court filing systems.
Icertis publishes a Native Integrations page with prebuilt adapters for SAP, Microsoft, Salesforce, Workday, Adobe Sign and DocuSign, each described by what it moves. The SAP Ariba adapter syncs procurement contracts, line items and suppliers, and the SAP S/4HANA adapter brings buy side supplier master data into the platform. For ERP and finance, adapters for Microsoft Dynamics 365 Finance and Operations and for Workday Financials sync procurement contracts, suppliers and financial data. The Salesforce CRM and CPQ adapter creates contracts from accounts, opportunities and quotes, with two way sync of deal and pricing data, and a Dynamics 365 Sales adapter keeps contract and sales data in step. The Adobe Sign and DocuSign adapters return signed agreements and audit trails to the platform. Microsoft Teams, Microsoft 365 for the web and Outlook connections cover collaboration, and SAM.gov and federal clause adapters serve public sector work. Licensed public APIs and connections to OpenAI, Claude, Microsoft Copilot and SAP Joule agents round out the list. The page does not describe setup or what an administrator configures, and it names no document management or identity connector. The platform runs on Microsoft Azure, with Microsoft as a strategic partner, and its named competitors include SAP Ariba and DocuSign CLM.
Lexagle supports single sign on through Microsoft Azure and offers APIs for connecting contract information with existing business systems. Its service terms describe optional transfers of completed contracts to Google Drive and individual PDF downloads. Collaboration rooms keep internal discussion separate from external negotiation, while the repository supplies contract data for reminders and other workflows. The vendor also describes Oracle connectivity and transfers to ERP systems. These are identifiable connection and transfer functions, although the published material does not provide a complete implementation account covering field mappings, permission inheritance, synchronization failures and conflict handling across those systems. Custom integration scope is settled during the commercial discussion.
Deployment Model and Data Residency
Where the software runs and where the data sits. Multi tenant cloud, single tenant, private deployment, on premises, and whether region of residence is a published option or an enterprise conversation.
Exhibit B of the SaaS Subscription and Services Agreement states that the platform is hosted on Microsoft Azure and that the Subscriber may select the Azure data center at the outset of the subscription. Production backups sit on geo replicated Azure storage. Exhibit A-2 distinguishes single tenant subscribers, who schedule their own upgrades and receive wider version support, from multitenant subscribers on the automatic upgrade calendar, so both tenancy models are offered. A FedRAMP government community cloud is listed separately. The agreement does not say where model inference runs.
Lexagle's security policy places its hosted service and customer data on AWS in Singapore. The displayed service terms nevertheless allow personal data to be transferred or stored outside Singapore, and the privacy notice also contemplates processing at partner facilities. A newer product article describes Lexie processing as resident with the client, with no client data sent to Lexagle servers or third parties. It does not explain how that arrangement relates to the hosted platform or which product configurations receive it. Customers therefore have several location statements, but no single published architecture that resolves storage, inference, remote access and the available deployment choices.
Security Certifications and Trust Center
Independent attestation a buyer can pull without a sales call: SOC 2, ISO 27001, penetration test summaries, a trust center with current reports and named scope rather than a badge image.
Exhibit B of the SaaS Subscription and Services Agreement states that Icertis is ISO 27001, ISO 27017 and ISO 27018 certified, holds SOC 2 Type 1 and Type 2 certifications and complies with ITAR. It manages risk under the ISO 27001 framework, commissions regular third party vulnerability assessments and penetration testing, encrypts data at rest with AES-256 and supports customer managed keys in Azure Key Vault. The agreement names no auditor, coverage period or self serve route to the reports. Icertis links a Trust Center from its site.
Lexagle names ISO 27001:2022, SOC 2 Type I and Type II, and CSA STAR Level 2 among its security credentials. Its security policy adds details about encryption, deployment tests, access controls, incident response and AWS hosting. Those statements are more specific than a generic promise of secure contracts. The public materials do not supply the audit period, named assessor or complete reports establishing which services and AI components were covered. Separate claims of alignment with other industry and regulatory frameworks should not be treated as additional certifications. The credentials concern information security controls rather than the legal accuracy of generated contract language.
Model Supply Chain Disclosure
Which models sit underneath, whose they are, where they run, and whether the vendor commits to telling customers when that changes. A legal buyer inherits every dependency it cannot see.
Icertis names Microsoft as a strategic partner and Azure as its platform, and a Microsoft published customer story records Icertis monitoring Azure OpenAI deployments, which places Azure OpenAI in the stack. Its integrations page lists interoperability with OpenAI, Claude (Anthropic), Microsoft Copilot and SAP Joule agents. Neither source says which models power the Copilots, the contract intelligence engine or Vera, or which model serves which task. The agreement and product pages do not say where models run or commit to notifying customers when the model supply chain changes. A List of Standard Sub-Processors, dated June 2023, sits on the foundation page.
Lexie is described as Lexagle's proprietary legal AI engine, trained on client specific contracts, approval knowledge and other institutional information. Document Guard adds low temperature settings, fixed response parameters and customer playbook context. These details identify the intended behavior and some training inputs, but not a foundation model family, inference provider or complete chain of model subprocessors. AWS hosting alone does not establish which model performs a review. There is also no published procedure for notifying customers before a model supplier or model version changes. The branded engine name consequently offers limited visibility into the technology handling confidential legal content.
Commercial Transparency
Whether a buyer can learn what this costs without entering a sales process: published rates, the unit being charged, what sits behind an enterprise tier, and what implementation adds.
Icertis publishes no pricing page, rate, unit of charge or tier structure. Every commercial path on its site ends in a demo or contact request, and there is no free trial or self serve entry point. No third party pricing figure is published either.
Lexagle prices a selected combination of modules after a discussion of business workflows, localization needs and implementation scale. Its menu includes contract management, signing, document management, vendor management and intellectual property management. The resulting package is customized, with no published entry amount, standard user allowance, contract volume unit or AI consumption rate. The acceptable use policy allows extra charges or restricted capacity for excessive usage, but supplies no numerical boundary. Implementation fees and a separate price for Document Guard are also unspecified. A proposal must therefore establish both the functional scope and the cost of growth before a buyer can estimate ongoing spend.
Firm and Practice Coverage
Who the product is actually built for. AmLaw, midlaw, small firm and solo, in house departments, government and courts, and which practice areas are supported rather than merely claimed.
Icertis sells to large enterprises, says 30 percent of the Fortune 100 are customers across more than 90 countries and multiple languages, and covers buy side and sell side agreements rather than one direction. The vendor's own research publishes industry breakouts for public sector, healthcare and life sciences, and banking and insurance, among others. Functional coverage spans legal, procurement, sales, finance and HR. Icertis does not say which organization sizes, contract types or practice areas the platform is not built for. Third party reviews say small and most mid market businesses will find it more platform than they need.
Lexagle serves legal, sales, procurement and HR teams, with industry examples in banking, telecommunications, manufacturing, property and other sectors. Its headquarters and regional focus are in Singapore, and it describes customers across Asia Pacific and other markets. Document Guard is also promoted to law firm partners, associates, legal operations and compliance professionals. Malaysian contract and digital signature laws receive explicit attention in the product explanation. Broader claims of multilingual and jurisdictional adaptability do not include a tested coverage matrix or exclusions for particular legal tasks. The displayed restriction on providing services to third parties also needs reconciliation with the law firm audience.
The 12 legal signals, side by side
Recorded rather than graded. These are the questions a practitioner has to answer before a tool touches a client matter, and the answers are taken from public material only.
Client Data in Training
Can material a lawyer puts into this product be used to train a model?
Section 5.2 of the SaaS Subscription and Services Agreement licenses Icertis to use Subscriber Data to provide the SaaS. It also lets Icertis use Subscriber Data to maintain, develop and improve the SaaS, including creating industry relevant analysis, provided the data is not shared with third parties and the Subscriber stays anonymous. Subscriber Data is defined to include the output of processing. The clause does not name model training. An Artificial Intelligence Acceptable Use Policy is listed on the foundation page as an addendum to the agreement.
The displayed service terms permit analysis of customer information to improve Lexagle offerings during and after the subscription. They expressly allow use or disclosure in aggregate form, or another form that does not identify a natural person, including training machine learning algorithms. A separate confidentiality clause permits customer insights to improve services for other customers. This is a contractual permission with stated limits, rather than an assurance that confidential agreement content is excluded from all model development.
Prompt and Output Retention
How long does the product keep what a lawyer typed, and can that be set to zero?
Under section 4.5 of the agreement, Icertis returns Subscriber Data on written request in its then current format at no fee. It may destroy the data if no request arrives within five days of termination. Subscriber Data includes the output of processing. The agreement sets no shorter or configurable window for AI prompts and outputs during the term.
Lexagle retains personal information for the account relationship and other stated legal or operational needs, then deletes or anonymizes it when no longer required. The service terms preserve some analysis and improvement rights after termination. Neither statement supplies a complete retention timetable for prompts, generated clauses, model logs or backup copies. The separate claim of client resident AI processing does not establish a default zero retention setting for the hosted contract repository or its supporting systems.
Ethical Walls and Matter Segregation
Does retrieval respect the firm’s ethical walls, or can the model read across them?
Exhibit B of the agreement describes the product's own permission model. It sets out strict role based access control, with authorization implemented through the platform's own features, identity provider authentication, and audit logs capturing every user action with date and time. Section 2.4 makes the Subscriber responsible for determining access privileges, and single tenant deployment is available. The agreement does not describe how the Vera agents respect those permissions across a contract portfolio.
Customer information sits in separate datastores, with application controls intended to prevent one customer accessing another's data. Lexagle describes tests of that separation that run on each code update and prevent release on failure. Administrators can set permissions for individual components, and internal rooms separate private collaboration from counterparties. These are described tenant and workspace controls.
They do not establish a complete ethical wall model within a law firm or prove that every AI response inherits exclusions for a particular client matter.
Third Party Request and Subpoena Notice
If someone subpoenas the vendor for a firm’s data, does the firm hear about it first?
Section 7.2 of the agreement permits disclosure of confidential information as required by law, regulation or court order. Unless legally prohibited, the receiving party must give the disclosing party prompt written notice before the disclosure and reasonable assistance in limiting it or obtaining a protective order. Confidential information is defined broadly, and Exhibit B states that Subscriber data is treated as confidential. Icertis publishes no transparency report.
The privacy notice permits disclosure to courts, regulators and other authorities where required, and the displayed confidentiality terms make an exception for legally required disclosure. Neither gives the affected customer a specific advance notification commitment or a process for contesting a demand. Security breach notices concern a different event and cannot substitute for notice of compelled access. There is also no recurring report of government requests that would explain how such demands have been handled.
Primary Law Corpus Provenance
Where does the law in this product come from, and does the vendor have the right to use it?
Icertis identifies no primary law corpus, and the product does not appear to hold one. Retrieval runs against the customer's own contract repository, templates and clause library, so the source material is the customer's own agreements and its provenance is theirs. The product pages and research library name no vendor supplied legal corpus, license basis or update cadence, which reflects a product built on the customer's own contracts.
Document Guard describes training on principles of the Malaysian Contracts Act 1950 and refers to Malaysian digital signature requirements. Lexie also uses customer contracts and institutional approval knowledge. The product does not enumerate a licensed collection of statutes, cases or commentary behind its legal suggestions, nor explain how external legal material is updated. Naming a jurisdiction and selected legislation gives some geographic context without establishing the provenance or usage rights for the full legal knowledge used by the models.
Good Law Verification
Does the product tell you when the authority it just cited has been overruled?
Icertis is a contract lifecycle platform grounded in the customer's own agreements, with no case law research feature, so a citator falls outside its design. Its product pages and research library say nothing about whether authority carries a treatment signal or whether the product tracks subsequent history, and they name no commercial citator license.
Lexagle's review process measures contract language against organizational rules and highlights deviations. It does not identify a licensed citator, a judicial treatment database or an equivalent mechanism for determining whether a cited legal authority remains reliable. The reference to Malaysian contract law is not a treatment history service. A green compliance result therefore concerns the supplied playbook and workflow, while the continuing validity of the legal assumptions behind that playbook remains a separate responsibility.
Refusal and Uncertainty Behavior
What does the product do when the answer is not in the corpus?
The product pages and research library do not describe what Icertis does when it cannot ground an answer, and mention no explicit no answer path or confidence signal shown to the user. The boundaries the vendor describes are limits a customer sets on what an agent may do. They are a permission concept, not a statement of what the system does when it does not know.
Amber and red outcomes divert or block agreements that fail customer rules. They are defined compliance states, rather than an explanation of how Lexie responds when it lacks enough information to answer a legal question. No refusal policy describes unsupported jurisdictions, conflicting authorities or uncertain interpretation, and no published confidence measure supplies a defined response to those problems. Low temperature settings may limit variation in responses, but they do not by themselves show when the system will decline to answer.
Fabricated Citation Record
Does a public court record exist addressing fabricated or hallucinated legal citations in output from this product?
The AI Hallucination Cases database maintained by Damien Charlotin, which tracks court decisions worldwide involving AI generated hallucinated content and records the AI tool implicated where it is known, records no court order, opinion or disciplinary record naming Icertis. Published 2026 sanctions summaries and secondary sanctions trackers do not name it either. Icertis is a contract lifecycle platform with no case law research feature, so its output is very unlikely to reach a court filing as cited authority.
The October 16, 2026 review of the Charlotin database found no Lexagle entry in the AI tool field or elsewhere in the case information. Lexagle's primary workflow concerns private contract review and approval rather than generation of court submissions, which may affect the visibility of an incident in a litigation database. This absence does not establish a hallucination rate or rule out unsupported legal assertions in suggested clauses, explanations or answers about agreements.
Bar Guidance Alignment
Has the vendor engaged in public with the ethics opinions its buyers are bound by?
Icertis publishes substantial annual research on AI adoption and trust in contracting, including the State of Contracting reports, and that research surveys practitioner sentiment. Neither the research library nor the blog, the news index or the product pages engages with a named ethics opinion or bar guidance, including ABA Formal Opinion 512 and state bar guidance. None of it addresses the professional responsibility rules that bind the vendor's legal buyers.
Lexagle expressly distinguishes its software from legal advice and assigns responsibility for conclusions to customers. Its regional materials discuss contract, signature and data protection requirements, but do not map AI features to a named bar opinion or professional conduct framework. Approval routing and private collaboration rooms may assist a lawyer's working practices. The vendor does not explain how those controls satisfy jurisdiction specific duties of competence, client communication, confidentiality and supervision when using generative AI.
Billing and Fee Posture
Does the vendor address what happens to the bill when the work takes an hour instead of six?
Icertis frames its material around business outcomes rather than hours, such as growing revenue, controlling costs, reducing risk and ensuring compliance, and it claims faster drafting and more precise execution. Its product pages and research library describe no per matter record of work done with AI for fee purposes and give no guidance on billing, fees or client disclosure. The buyer is a corporate legal, procurement or finance function rather than a firm billing a client by the hour, so the savings are enterprise cost rather than billable time.
Document Guard is promoted to law firm partners and associates for faster due diligence and routine review. Lexagle also advertises reduced administrative work and shorter contract cycles across its wider customer base. It does not provide a client fee allocation method, a billing disclosure template or a record of how time saved by AI changes the charge to a legal client. Those efficiency claims therefore remain separate from the lawyer's professional responsibility for the fee ultimately billed.
Outside Counsel Guideline Readiness
Can a firm get this vendor through a client’s AI clause without a bespoke negotiation?
Icertis publishes a subprocessor list on its foundation page alongside the agreement, a Data Protection Addendum with standard contractual clauses, EU Data Act terms and an AI Acceptable Use Policy. The list on that page is dated June 2023.
The privacy notice names several service providers, including Heap, FullStory, Google analytics services, Intercom and SendGrid, and the security policy identifies AWS hosting. That gives part of the supplier information needed for a client approval discussion. It does not identify the complete model supply chain or provide a prepared outside counsel AI disclosure package. A legal team would still need the applicable contract, processing configuration and client specific restrictions to assess whether a proposed matter can use the service.
Court Disclosure Support
If a judge’s standing order requires an AI disclosure, can the product produce one?
Vera Composer records template usage, clause selection, and edits, while Vera Redline logs reviewer actions and supplies clause references with explanations. These records preserve parts of contract drafting and human review. A combined export identifying the specific model, all retrieved sources, and human verification of each generated passage is not described. The audit workflow serves commercial contracting and does not establish a court filing certification process.
Lexagle records contract changes, approval activity and signing events. Document Guard binds its compliance result to a version and requires renewed evaluation after an external change, helping distinguish an approved draft from a later upload. These controls can support an account of the agreement's history. They do not supply a complete export of model identity, prompts, generated text and counsel's verification, or a prepared court declaration explaining AI use in a filed document.
The questions both sides leave open
Derived from the records above rather than written, so it cannot favor either vendor. Take these into both conversations and ask each side the same question.
- Good Law Verification
- Refusal and Uncertainty Behavior
- Bar Guidance Alignment
Which one fits
Choose Icertis if
- Contracts must connect to SAP, Microsoft, Salesforce or Workday processes.
- Obligations and commercial performance need enterprise wide analysis.
- A broad contract intelligence rollout has dedicated implementation resources.
Choose Lexagle if
- The key requirement is rule based approval before signature.
- Legal teams need a clear partial compliance route to a person.
- Protecting the reviewed version is a priority in external negotiations.
In summary
Icertis
Icertis Contract Intelligence structures contract obligations, risks and commercial information across an enterprise lifecycle. Its Copilots and Vera agents sit alongside adapters for major ERP, CRM, collaboration and signature systems on Microsoft Azure.
Lexagle
Lexagle combines contract drafting and negotiation with Document Guard's approval controls. It emphasizes regional contract operations and a digital seal that requires reevaluation if the version underlying a compliance result changes.
Questions buyers ask
Are Icertis agents interchangeable with Document Guard?
Icertis describes agents across engagement, operations and analysis within customer set boundaries. Document Guard describes a narrower traffic light compliance gate tied to the contract version. The intended task and permitted actions need to match. From the AI Legal Index, based on each vendor's own published materials as of October 16, 2026. No vendor pays for placement.
Can Lexagle's Singapore hosting statement settle all processing questions?
No. Its security policy names Singapore AWS hosting, while contractual transfers and a newer client resident AI statement create an incomplete picture of where each processing step occurs. From the AI Legal Index, based on each vendor's own published materials as of October 16, 2026. No vendor pays for placement.
Does Icertis prohibit every improvement use of subscriber data?
No. Its SaaS agreement permits data to maintain, develop and improve the service under restrictions on disclosure and identification. That is different from an express blanket model training exclusion. From the AI Legal Index, based on each vendor's own published materials as of October 16, 2026. No vendor pays for placement.
Which option has the more developed enterprise integration proposition?
The deciding factor is whether contracts must exchange information with existing operational systems. In this pairing, AI Legal Index identifies Icertis's named enterprise adapters as a stronger integration proposition than Lexagle's less detailed connection descriptions.
Neither vendor paid for inclusion, placement or a grade, and neither reviewed this page before it published. Everything on it comes from public material on the dates shown. How the index grades.
Vera capabilities, integrations and deployment scope depend on the Icertis implementation. Lexagle's processing arrangements require reconciliation of its different public statements.