Juro vs Lexagle: how they compare in 2026
Juro suits an in house legal team that wants business colleagues to create and negotiate agreements under legal controlled templates and workflows. It combines browser contracting with Word based AI review, and its current plans include unlimited users, workflows and templates while contract volume and integrations shape the quote. Lexagle is more distinctive when the requirement is an AI decision gate bound to a particular version. Document Guard sends partial compliance to human review and forces reevaluation after an external change. The training terms require precision on both sides. Juro prohibits a customer model being used for another customer but permits training confined to that same customer; Lexagle allows defined aggregated or nonidentifying uses and broader service improvement. In those terms, AI Legal Index identifies different permitted uses, rather than a simple training versus no training split.
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.
Juro manages the complete contract lifecycle, from template creation and approval routing through negotiation, electronic signature, storage and tracking. AI Review redlines third party contracts, AI Extract captures data from signed agreements, and the AI Assistant supports drafting and summaries. Operator adds conversational access to the repository and can answer questions with source citations. The underlying contract platform also has a distinct function without those AI features. Legal teams control templates and approval processes while colleagues generate agreements within those controls. Native electronic signature and lifecycle tracking complete transactions independently of an AI response. The company began in 2016 and added AI to that established contracting workflow.
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.
Juro's AI terms warn that generated output may misstate people, facts or laws, including legal authorities. Operator connects repository answers to source citations, while AI playbooks constrain tasks with contract context and customer rules. Prompt shortcuts help users structure instructions consistently. These features provide context and a route back to source material, but no measured hallucination rate, legal accuracy benchmark or test set accompanies them. The retrieval mechanism behind Operator's citations is unspecified. Juro treats generative AI as fallible and places responsibility for identifying and correcting errors with the customer before reliance. A source citation therefore provides a review aid, without a separate guarantee that the answer is correct.
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.
Human review is required before customers use or rely on AI output. Juro also prohibits presenting generated output as human authored. Inside the product, legal teams establish approval routes and set playbook context and constraints at the template or individual contract level. AI Review explains which playbook rule supports a proposed edit, and reviewers can accept, edit or skip suggestions. The responsible AI guidance limits recommended use to tasks that the professional could perform and verify independently. These controls put the reviewer between a proposed redline and its acceptance. The circumstances that stop unattended agent activity and the escalation process after an erroneous result remain unspecified.
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.
Juro associates customer outcomes with named legal and business leaders. Talentful reports an 86 percent reduction in time to sign, Funnel an 88 percent reduction in manual contract reviews, and Luno a 91 percent time saving per contract. Paddle attributes three and a half hours saved per contract to the platform. Goldin's stated workload is 20,000 contracts annually, while Deliveroo describes eight years of use. These examples cover contract operations across multiple companies and roles. They do not establish the contribution of an individual AI feature, and the figures lack a measurement method or deployment period. Older lifecycle results cannot establish the performance of the current AI review and Operator features.
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.
Customer data cannot train an AI model serving another customer. Juro's AI terms permit a model used exclusively for the same customer, with deletion of that model within 60 days after termination. Generated output belongs to the customer and is treated as customer data. The responsible AI guidance identifies OpenAI's GPT family through Microsoft Azure and describes confidentiality obligations covering Juro and its technology providers. A data processing agreement and named subprocessors support that contractual framework. Repository separation and permission enforcement across legal, sales, HR and procurement are not explained in that material. Professional confidentiality is recognized, but attorney client privilege and work product receive no separate treatment.
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.
Juro requires human review of generated output and prohibits passing it off as human authored. Its responsible AI guidance recognizes lawyers' professional confidentiality duties and extends a related concern to HR teams handling employee information. The contracting workflow allows sales, procurement, HR and finance teams to act within legal team templates and approvals. These are operational controls around contract production, rather than a jurisdiction specific professional responsibility framework. The terms and guidance do not establish a no legal advice boundary, identify a governing bar opinion, or map product behavior to ABA Formal Opinion 512. Restrictions on which jurisdictions or categories of professional work the AI can support are also unspecified.
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.
Juro's responsible AI framework focuses on privacy, confidentiality and accuracy in contracting. Customers can obtain a data protection impact assessment template populated for AI Assistant, with separate data protection guides for AI Assistant and AI Extract. AI playbooks let legal teams specify context and constraints, while an EU AI Act guide addresses the regulatory setting. The framework acknowledges bias and intellectual property issues but treats them as less pertinent than its three principal concerns. It does not identify a person accountable for model behavior, a release testing regime or evaluation results. Those omissions leave the operational ownership of model risk and the testing of biased outputs unclear.
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.
Juro names infrastructure providers including Algolia, AWS and MongoDB, along with analytics, communications and payments providers. Salesforce, Slack and Google also appear as customer initiated integrations. A data processing agreement governs personal data, and customers have access, portability and erasure rights. Separate security and resilience guidance accompanies a status page and a 99.9 percent uptime commitment. The AI terms require deletion of customer specific models within 60 days of termination; that period is not a retention schedule for contract text, prompts or generated output. The broader content retention window and AI specific incident notification process remain unspecified in the material underlying this assessment.
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.
Juro separates its AI terms from the Master Services Agreements for customers in the United States and elsewhere. Under clause 3.2 of the AI terms, any MSA indemnity for infringement of intellectual property or other third party rights excludes generated AI output. Clause 3.1 assigns the customer the duty to identify and correct output errors before relying on a result. The March 2025 AI terms retain a link to their February predecessor, making the version boundary identifiable. This arrangement defines the treatment of AI output directly, but leaves customers without the MSA's infringement remedy for that output. Human review is the customer's contractual responsibility.
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.
Juro connects contract creation and management with business systems and Microsoft Word. Word synchronizes edits, comments, redlines and versions with the contract workspace. Slack, email, Google Drive and Word are available across plans. Growth adds HubSpot, Claude, Copilot, DocuSign, Greenhouse, Zapier and Ashby; Enterprise includes Salesforce, REST API access and webhooks. Claude uses MCP to work with the repository, while the ChatGPT connection remains a beta. Pricing depends partly on integration complexity, and the pricing FAQ identifies Salesforce, HubSpot and Workday as integrations carrying additional cost. No iManage or NetDocuments connection is identified. The integration set primarily follows in house contracting and business system workflows.
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.
AWS supplies part of Juro's infrastructure, and the responsible AI guidance places GPT processing on Microsoft Azure servers. Customers use the hosted contract workspace across more than 85 countries. An EU Data Act addendum addresses a separate contractual requirement around the service. That international reach does not itself establish where an individual customer's contract data resides. The deployment material underlying this assessment does not specify a choice of regions, a residency commitment, tenant architecture or a private installation. The distinction between platform infrastructure and the model processing route is identifiable, but the customer controlled boundary for hosting location remains unclear.
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.
Juro's trust center covers privacy regulations, application security, network infrastructure, resilience, electronic signatures and responsible AI. Its security claims include SOC 2 Type 2, supported by a corresponding trust center topic and a certification badge. The platform also has a status page and a stated 99.9 percent uptime. Access to the explanatory articles does not require a form, email address or confidentiality agreement. The trust center index does not identify the auditor, attestation period, report date or tested scope. A route to the underlying report and details of a penetration test are also unspecified there. The security claim is identifiable, while its independent verification details remain incomplete.
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.
Juro identifies OpenAI's GPT family as the model behind its AI tools, delivered through Microsoft on Azure servers. That establishes a provider, model family and delivery route for the arrangement described in its responsible AI guidance. The discussion also uses GPT 4 as an example of training scale, without confirming that version as the current production model. A precise version and a customer notice commitment for model changes are unspecified. The trust center's infrastructure subprocessor list names Algolia, AWS and MongoDB but omits OpenAI and Microsoft. The named model route therefore does not resolve the complete chain of processors or how customers learn of a change.
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.
Juro charges according to monthly contract volume and integration complexity, with unlimited users, workflows and templates across plans. Volume bands range from fewer than 20 contracts per month to more than 1,000. Slack, Google Drive and Companies House are included according to the pricing FAQ, while Salesforce, HubSpot and Workday incur additional cost. Quotes also reflect implementation complexity. Billing can use USD, GBP or EUR, and nonprofit discounts are available. No numeric subscription or implementation price is stated. The pricing page supplies the main drivers of a quote without a per seat rate or an independently calculable total. A previous demo month promotion is no longer part of the current pricing offer.
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.
Juro serves legal, HR, procurement, sales and finance teams. Legal establishes templates and workflow controls, allowing other departments to produce agreements within an approved process. Contract types include NDAs, employment agreements, master services agreements, statements of work, order forms, acquisition material and supplier agreements. The company describes customers in more than 85 countries and positions the platform for businesses completing roughly ten or more contracts each month. Its industry examples include software, food delivery and marketplaces. The central setting is an in house contract operation. A dedicated law firm, government or court workflow is not identified, and the product does not function as a primary legal research service.
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?
Juro's AI terms prohibit using customer data to train a model for anyone else. A model used only to provide services to that same customer is permitted, and Juro must erase it within 60 days after the agreement ends. The responsible AI guidance also rejects training foundational models with customer data. The contract's limited customer specific exception is therefore distinct from shared model training, and the deletion deadline applies to that derived model.
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?
Juro's AI terms require erasure of a customer specific model within 60 days after termination. That deadline governs the model rather than the contracts, prompts or generated output used in the service. Customers can exercise portability and erasure rights under the privacy framework. A content retention window and a customer controlled retention setting are unspecified in the material underlying this assessment, leaving the lifetime of operational AI content separate from the model deletion commitment.
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?
Legal, sales, HR, procurement and finance can work in Juro's contract workspace. The AI terms prevent a customer specific model from serving another customer and distinguish one user's output from similar output produced for others. Those contractual boundaries do not explain permission enforcement within the repository or retrieval across teams. A technical separation model and controls for ethical walls between matters are unspecified in the material underlying this assessment.
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?
Juro's data processing agreement requires notice to the customer of government access requests under Appendix 3, paragraph 4.4(k). The commitment operates through the Standard Contractual Clauses where the corresponding transfer law applies. Notification to individual data subjects remains the customer's responsibility. An equivalent commitment is not identified in the general terms or CCPA appendix. Requests from a third party claiming to control customer personal data are directed to the customer. No transparency report or request volume accompanies these provisions.
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?
Operator answers questions from the customer's contract repository and connects responses to its sources. AI Extract captures data from signed agreements in that same customer supplied collection. The underlying model route is separately identified as OpenAI's GPT family through Microsoft Azure. Juro is not a primary law research corpus. Rights to the foundation model's training material and an update schedule for that material are not established by the repository's customer supplied provenance.
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?
Juro works with a customer's contracts rather than a primary law collection. It has no identified citator, treatment signal or process for checking the subsequent history of a legal authority. Operator's citations connect repository answers to contract sources, which serves a different purpose from determining whether a case remains good law. The AI terms acknowledge that generated output can misstate laws and legal authorities and require human correction before reliance.
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?
Juro warns that generative AI can produce errors and requires a person to review results before reliance. Playbooks provide context and constraints for contract tasks, but no defined abstention path or confidence indicator explains how the system responds when an answer lacks support. The responsible AI guidance treats accuracy as an ongoing professional review responsibility. That establishes a warning and a human control, without specifying when the AI itself declines a request.
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?
No identified court decision or disciplinary record names Juro or Juro Online Limited in connection with fabricated citations. Damien Charlotin's AI Hallucination Cases database and the sanctions material underlying this assessment contain no attributable incident. That finding does not establish an error rate or demonstrate that generated authorities are reliable. Juro primarily supports commercial contracting inside companies, a setting in which output is less likely to become part of a court filing.
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?
Juro recognizes that lawyers must protect professional confidentiality when using AI. Its responsible AI guidance connects that duty to restrictions on training with customer data, while making a similar confidentiality point for HR teams. It does not connect these controls to a named ethics opinion or regulator's requirements. ABA Formal Opinion 512, state bar guidance, and Solicitors Regulation Authority or Law Society materials are not identified as the governing framework.
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?
Juro's customer examples describe reduced contract work, including faster signing, fewer manual reviews and time saved per agreement. The commercial focus is an in house operation where legal and business teams share the platform. Those efficiency claims do not establish how a law firm should bill a client for AI assisted work. No matter based fee record, disclosure procedure or guidance on passing time savings through to clients accompanies the contracting workflow.
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?
Juro identifies infrastructure, analytics, communications and payment subprocessors, including AWS, MongoDB, Algolia, Stripe and HubSpot. Customer initiated integrations include Salesforce, Slack and Google. The contractual package includes a data processing agreement, an EU Data Act addendum and separate AI terms, with an impact assessment template available for AI Assistant. The trust center list does not include the OpenAI and Microsoft route described in the responsible AI guidance. No client consent or notification pack accompanies this material.
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?
Juro manages commercial contracts rather than court filings. Operator provides source citations for repository answers, and the AI terms prohibit representing generated output as human authored. These features support a limited record of sources and a contractual disclosure boundary. They do not create a court certification, standing order workflow or export that records the model's role and a lawyer's verification. A dedicated litigation disclosure process is not identified.
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
Which one fits
Choose Juro if
- Business users need access without a per seat subscription constraint.
- Word review and browser negotiation both belong in the process.
- Repository questions should return source citations through Operator.
Choose Lexagle if
- An AI compliance state should determine the next approval action.
- A replacement draft must trigger mandatory reevaluation.
- A customized combination of contract and other business modules is useful.
In summary
Juro
Juro connects templates, approvals, negotiation, signatures and obligations in one contract workspace. AI Review works in Word as well as the platform, Operator returns repository answers with citations, and integrations vary with the chosen package.
Lexagle
Lexagle offers collaboration rooms, signing and agreement assistance with an additional policy enforcement layer. Document Guard classifies compliance, routes exceptions and protects the result against changes to the reviewed contract version.
Questions buyers ask
Must a Juro customer abandon Microsoft Word?
No. Current AI Review includes a Word workflow where reviewers accept, change or skip suggestions. Older comparisons portraying Juro as exclusively a replacement for Word do not capture that capability. From the AI Legal Index, based on each vendor's own published materials as of October 16, 2026. No vendor pays for placement.
Are Juro's unlimited users an unlimited contract allowance?
No. User access, workflows and templates are included without those limits, but contract volume, integrations and implementation still affect the quote. The relevant commercial unit is not simply seats. From the AI Legal Index, based on each vendor's own published materials as of October 16, 2026. No vendor pays for placement.
Does Lexagle promise not to reuse any customer information?
Its displayed terms permit some customer information and insights to improve services, including specified aggregated or nonidentifying machine learning uses. Those rights differ from a blanket prohibition. From the AI Legal Index, based on each vendor's own published materials as of October 16, 2026. No vendor pays for placement.
How does the Juro training boundary compare with Lexagle's?
The distinction concerns who may benefit from permitted model use and under what conditions. For this pairing, AI Legal Index identifies Juro's restriction to the same customer's model and Lexagle's broader stated improvement permissions.
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.
Juro's current Word capabilities are included despite outdated browser only descriptions elsewhere. Both vendors require a quote for the intended contract volume and integration scope.