Ironclad vs Juro: how they compare in 2026
Ironclad and Juro are both contract lifecycle platforms for in house teams, so the decision turns on scale and on how each contract treats AI risk. Ironclad runs intake, no code workflows, approvals, negotiation, signature and analytics for high volume contracting. Ironclad Agent routes requests to specialized agents, and Contract Review Agent redlines third party paper against playbooks in Ironclad or Word. Juro lets legal own the templates and approvals while sales, HR, procurement and finance create agreements themselves. Its AI Review redlines in Word, AI Extract captures data from signed contracts, and Operator answers repository questions with source citations. The sharpest difference sits in the terms. Ironclad indemnifies customers against intellectual property claims on the platform and allows termination with a refund when a defect stays unfixed for 30 days. Juro's AI terms exclude generated output from its infringement indemnity. Juro answers with unlimited users on every plan and pricing driven by contract volume, while Ironclad bills extra AI use at $1 a unit beyond a shared credit pool.
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.
Intake, the no code Workflow Designer, approvals, signature, the repository and analytics run without AI, and Ironclad sells that system of record as the base of the platform. Ironclad AI sits on top of it. Ironclad Agent takes a plain language request and returns the answer, the contract or the workflow, or hands the task to a specialized agent. Contract Review Agent redlines third party paper against playbooks and, in early access, precedent, Intake Agent pulls terms into launch forms, Renewal Agent briefs upcoming renewals, and Analytics Agent charts contracting data. The agents act on live workflow state, such as where a contract sits in approval, as well as on documents. The contract platform predates generative AI and would still work without the models.
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.
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.
Extraction uses two passes to connect values to source text. The model returns each value with a description of where it sits in the contract. A second pass ties that value to the exact OCR tokens, so the interface highlights the passage with its page and position. If the model returns no match, the system tries the raw text and then the normalized value before giving up on a location. Contract Review Agent bases redlines on the customer's playbooks and templates, with precedent based redlining in early access, and redlines can show their rationale. Answers through the MCP connectors link back to the contract in Ironclad. No accuracy figure, error rate or test set is available, and the AI Addendum says output may be incorrect or inaccurate.
Generated output may misstate people, facts or laws, including legal authorities, Juro's AI terms warn. 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. Juro does not explain the retrieval mechanism behind Operator's citations. 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.
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.
Ironclad Agent routes each request to the right agent or workflow, and the agents work inside existing contracting workflows under the user's permissions. Contract Review Agent proposes redlines, flags risk and applies positions in Ironclad or directly in Microsoft Word, with the final decision left to the reviewer. Playbooks set preferred positions and fallbacks, and answers through the MCP connectors are limited to contracts the user can already open. The AI Addendum makes the customer responsible for reviewing and validating output before using it, and says the AI products are no substitute for human oversight. Agent stop conditions, handback routes and limits on work completed without a person are not specified.
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. Juro does not say what stops unattended agent activity or how an erroneous result is escalated.
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.
Named customers report figures. NEXT Insurance says Contract Review Agent gave legal operations half its time back, and AES reports first pass redlines that took 30 minutes to two hours now reach a first draft in minutes. Signifyd puts an MNDA review or custom order form clause at minutes rather than an hour to a day, and Hormel's senior counsel reports turnaround cut from 12 weeks to 3. A Forrester study drawn from five customer organizations puts the three year return at 314 percent. Apart from that study, the figures come from the customers themselves, undated and with no method stated.
Customer outcomes come attached to 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. None isolates 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.
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.
Training of Ironclad's own models on customer data, input and output starts only after a customer enables AI Training Settings in the admin console, under the AI Addendum. An opt out stops new training from that date. That data is first de identified, anonymized and aggregated, and output for other customers may not contain it. Whether or not a customer opts in, Ironclad may use input and output to evaluate the performance and accuracy of the service. External model providers may not train on customer data and run under zero data retention where available. The Enterprise Services Agreement treats customer data as confidential information, and SOC 2 covers the privacy category. The terms say nothing about attorney client privilege or work product, and access follows roles without specified matter boundaries.
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.
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.
Ironclad markets its AI to legal teams and to sales, procurement and operations users, and describes the platform as built for everyone, lawyers or not. Its AI Addendum states that Ironclad is not the customer's legal advisor, that using the AI products creates no attorney client relationship, and that the customer should consult its own counsel. A separate AI Disclaimer says output is not legal advice and should be verified with a licensed professional before anyone acts on it. Neither document addresses competence or supervision duties, or which jurisdictions the product suits.
A person must review generated output under Juro's rules, which prohibit 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 contain no statement that the product does not give legal advice, identify no governing bar opinion and do not map product behavior to ABA Formal Opinion 512. Nor do they restrict which jurisdictions or categories of professional work the AI can support.
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.
Every AI feature, Ironclad says, passes through its Evaluation Framework, which measures accuracy, consistency and reliability against curated benchmarks and real contract data. Subject matter experts validate model output during development and after release, with feedback loops meant to catch bias early, and training data is chosen to cover varied contract types and jurisdictions. Dimitry Dukhovny, the chief information security officer, leads security, compliance and AI governance. Customers can review, override and keep governing agent behavior across teams and contract types. Evaluation results and performance differences by contract type, jurisdiction or party are not available.
Privacy, confidentiality and accuracy in contracting are the focus of Juro's responsible AI framework. 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.
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.
Storage of customer personal data is limited to what the services need under Ironclad's Data Processing Addendum, version 3.10 from 5 March 2026. It destroys all copies, archives included, within 90 days of the agreement ending, returns data within 30 days on request and issues a deletion certificate within 30 days. A security incident is reported to the customer within 48 hours of Ironclad becoming aware of it. The subprocessor list names each provider, its activity and its location for the United States platform, the EU datacenter and Clickwrap. A new subprocessor comes with 30 days' email notice and a right to object. External model providers run under zero data retention and may not train on customer data. Data is encrypted with TLS 1.2 or higher in transit and AES 256 at rest, with per tenant keys and bring or hold your own key options, and access follows administrator set roles.
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. Juro gives no broader content retention window and no AI specific incident notification process.
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.
The Enterprise Services Agreement, version 2.2 effective July 2026, governs warranties and financial remedies. Ironclad defends and indemnifies customers against third party claims that the platform infringes intellectual property, and against claims from unauthorized disclosure of customer data caused by its breach of the data and security terms. It warrants that the services materially conform to the agreement and comply with applicable law; if a nonconformity is not fixed within 30 days, the customer may terminate for a pro rata refund. Liability is capped at the fees paid in the prior twelve months, rising to three times that amount for data and confidentiality breaches and the data indemnity. Gross negligence, intentional misconduct and the intellectual property indemnity sit outside the cap, and consequential loss is excluded. The service level schedule targets 99.7 percent uptime, with service credits as the remedy. The customer bears sole responsibility for results from AI output, which Ironclad does not warrant as accurate, and the agreement carries no insurance commitment.
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.
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.
Three routes connect Ironclad to other systems: native integrations, iPaaS connections to more than 8,000 applications, and an API, with Tray, Zapier and MuleSoft in its directory. The directory names Salesforce, which is AppExchange approved, Coupa, SAP, NetSuite, Zip and Ramp, Microsoft Word and Teams, Slack, DocuSign and Adobe Acrobat Sign, and Box, Google Drive, OneDrive, Dropbox and Egnyte. MCP connectors answer questions about contracts and workflow status in Claude, ChatGPT and Slackbot, scoped to the user's permissions and linked back to Ironclad. No iManage or NetDocuments connector is identified, and the directory does not specify individual field mappings or sync directions.
Contract creation and management connect to 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.
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.
Hosting is on Google Cloud Platform, across multiple zones in the United States, with a separate EU datacenter. For EU hosted customers the subprocessor list places Anthropic and OpenAI, along with Elastic Cloud, Datadog and the product database, in the EU, so AI processing stays in that region too. Clickwrap runs separately on Amazon Web Services in the United States. Customers can bring or hold their own encryption keys. Ironclad does not describe a tenancy model or what changes between plans.
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.
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.
Ironclad holds SOC 1 and SOC 2 Type II reports from routine third party audits covering security, availability, confidentiality and privacy, along with ISO 27001, 27701, 27017 and 27018. It runs a GDPR program with standard contractual clauses, complies with HIPAA and holds Cloud Security Alliance Trusted Cloud Provider status, with a public CAIQ on the alliance's site. Penetration tests run each year and vulnerability tests each quarter, and disaster recovery is tested twice a year. Certification documents are requested through a security portal, and the website gives no auditor, audit period or report date.
Privacy regulations, application security, network infrastructure, resilience, electronic signatures and responsible AI each get a section in Juro's trust center. 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. Nor does it give a route to the underlying report or details of a penetration test. The security claim is identifiable, while its independent verification details remain incomplete.
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.
Contract Review Agent uses models from Google Gemini, OpenAI and Anthropic, chosen for quality, latency and performance, and Ironclad says it evaluates and swaps in models as they change. Its own models, which learn from aggregated, anonymized data of customers who opt in, sit alongside them. The subprocessor list names Anthropic, OpenAI and Extend for AI and Google Cloud Platform for cloud and AI infrastructure, each in the United States or the EU. A new subprocessor brings 30 days' email notice and a right to object, and AI subprocessors run under zero data retention where available and may not train on customer data. Ironclad does not say which model serves which agent, and a change of model within an existing provider triggers no notice.
Behind the AI tools sits OpenAI's GPT family, delivered through Microsoft on Azure servers. The responsible AI guidance therefore names a provider, a model family and a delivery route. The discussion also uses GPT 4 as an example of training scale, without confirming that version as the current production model. Juro gives no precise version and no commitment to notify customers of model changes. 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.
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.
The base CLM, AI assistant and eSignature products use a custom quote, with deployment led by the customer, Ironclad's legal engineers or a partner. API connections, integrations, extra instances and support plans can add charges. Eligible agents consume a shared pool of AI Credits, with additional use billed at $1 per unit unless administrators enable a cap or buy prepaid packs. Not every AI feature uses those credits, and existing Contract Review Agent seat arrangements continue through the current contract term. Playbook creation and optimization require Professional Services; precedent redlining and Playbook Agent are in early access. A starting platform rate and fixed implementation fee are not specified.
Monthly contract volume and integration complexity set the price, 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.
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.
Enterprise and growing companies are Ironclad's buyers, with dedicated pages for general counsel, legal operations, procurement, sales and IT. It describes the platform as handling every contract type, from legal and sales to finance, HR, marketing and procurement, from intake through renewal. Named customers include Mastercard, L'Oreal, Cisco, Docker, Gusto and Rippling. The platform centers on contracting, while Contract Review Agent also supports legal questions with embedded citations. Ironclad does not say which organization sizes or contract types it does not serve.
Buyers span 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.
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 1.1 of the AI Addendum, version 2.1 from 20 April 2026, lets Ironclad train its own models on customer data, input and output once the customer turns on AI Training Settings. The data is de identified, anonymized and aggregated first, an opt out stops new training but not training already under way, and external model providers may never train on it. Ironclad's product FAQ says the default setting depends on the customer's agreement and data location.
Customer data may not train a model for anyone else under Juro's AI terms. 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.
Prompt and Output Retention
How long does the product keep what a lawyer typed, and can that be set to zero?
During the term, the Data Processing Addendum keeps customer personal data only as long as the services need it, and the AI Addendum sets no separate period for prompts and output. All copies are destroyed within 90 days after the agreement ends, with a 28 day window to export the repository. External model providers run under zero data retention.
A customer specific model must be erased within 60 days after termination under Juro's AI terms. 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. Juro gives no content retention window and no customer controlled retention setting, so the lifetime of operational AI content sits apart from the model deletion commitment.
Ethical Walls and Matter Segregation
Does retrieval respect the firm’s ethical walls, or can the model read across them?
Role based permissions set by administrators are Ironclad's own, rather than inherited from a document system. Agents and MCP answers respect the same permissions, so a user sees only the contracts already open to them. Nothing describes walls between matters, since the product is built for in house teams rather than firms.
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. Juro describes no technical separation model and no controls for ethical walls between matters.
Third Party Request and Subpoena Notice
If someone subpoenas the vendor for a firm’s data, does the firm hear about it first?
The Data Processing Addendum commits Ironclad to tell the customer promptly of any government or law enforcement request for its personal data, unless the law forbids it, and to help the customer contest it. The Enterprise Services Agreement allows disclosure of confidential information under a court or government order after reasonable notice where the law permits. No transparency report is available.
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.
Primary Law Corpus Provenance
Where does the law in this product come from, and does the vendor have the right to use it?
Ironclad's AI works over the customer's own contracts, playbooks and workflow data rather than a body of law. Its own models learn from aggregated, anonymized patterns across customers who opt in, and Ironclad cites more than 2 billion contracts processed. No source, scale, license or refresh cycle is given for that training data.
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.
Good Law Verification
Does the product tell you when the authority it just cited has been overruled?
Contracts sit at the center, while Contract Review Agent can also answer legal questions with embedded citations. No citator, treatment signal or check of later history is described.
Contracts belonging to the customer, rather than a primary law collection, are what Juro works with. 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.
Refusal and Uncertainty Behavior
What does the product do when the answer is not in the corpus?
Contract Review Agent flags missing clauses and departures from a company's standards, and extraction highlights the passage each value came from. When the model cannot place a value, the grounding system retries on the raw and normalized text rather than returning nothing. No path for declining to answer, and no confidence signal for the user, is described.
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. Juro thus pairs a warning with a human control, but does not say when the AI itself declines a request.
Fabricated Citation Record
Does a public court record exist addressing fabricated or hallucinated legal citations in output from this product?
No entry for Ironclad appears in the AI Hallucination Cases database, Damien Charlotin's record of court decisions involving hallucinated AI content. Ironclad is a contracting platform, and its output is seldom filed with a court as cited authority.
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. The absence of an incident gives no error rate and says nothing about whether 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.
Bar Guidance Alignment
Has the vendor engaged in public with the ethics opinions its buyers are bound by?
Ironclad's AI Addendum and AI Disclaimer say output is not legal advice and should be verified with a licensed professional. No ethics opinion or bar guidance is named, ABA Formal Opinion 512 included.
Lawyers must protect professional confidentiality when using AI, Juro recognizes. 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.
Billing and Fee Posture
Does the vendor address what happens to the bill when the work takes an hour instead of six?
Named corporate customers describe shorter contract reviews and less legal operations work. NEXT Insurance reports recovering half of its legal operations time, while AES and Signifyd describe first redlines and NDA reviews in minutes. The platform serves internal legal, procurement, sales and operations teams handling their organization's agreements. It does not provide a law firm billing workflow or a client fee disclosure process for the time saved.
Reduced contract work, including faster signing, fewer manual reviews and time saved per agreement, runs through the customer examples. The commercial focus is an in house operation where legal and business teams share the platform. Those efficiency claims say nothing about 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.
Outside Counsel Guideline Readiness
Can a firm get this vendor through a client’s AI clause without a bespoke negotiation?
Ironclad's subprocessor list names Anthropic, OpenAI and Extend for AI and Google Cloud Platform for cloud and AI infrastructure, with locations for the United States platform and the EU datacenter. The Enterprise Services Agreement, Data Processing Addendum and AI Addendum are public in its legal center. A new subprocessor brings 30 days' email notice and a right to object. No notice pack for a client's outside counsel guidelines is available.
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.
Court Disclosure Support
If a judge’s standing order requires an AI disclosure, can the product produce one?
Routing, assignment and approvals for each contract are recorded in Ironclad's workflows, and AI review is described as auditable, with humans able to review and override it. Extracted values highlight their source passage and redlines can show their rationale. No export records which model produced an output or who verified it. Ironclad's output is contract work rather than court filings.
Commercial contracts, not court filings, are what Juro manages. 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.
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 Ironclad if
- You need AI processing to stay in Europe. For customers hosted in Ironclad's EU datacenter, Anthropic and OpenAI processing runs in the EU too, and customers can bring or hold their own encryption keys.
- You want contractual remedies when the platform fails. Ironclad's agreement indemnifies against intellectual property and data disclosure claims, triples the liability cap for data breaches and allows termination with a refund after 30 days of an unfixed defect.
- You want contract answers inside the tools teams already use. MCP connectors bring repository answers into Claude, ChatGPT and Slackbot, limited to contracts each user can already open.
Choose Juro if
- You want every colleague on the platform without seat costs. Every Juro plan includes unlimited users, workflows and templates, and the quote follows monthly contract volume and integrations.
- You want a firm promise that your contracts will not train a shared model. Juro's AI terms bar training any model for another customer, and a model built only for you is erased within 60 days of the agreement ending.
- Reviewers should see why each edit is proposed. AI Review shows which playbook rule supports a suggested redline, and reviewers accept, change or skip each one in Word.
In summary
Ironclad
Ironclad is a contract lifecycle management platform for in house legal, procurement, sales, finance and IT teams. It covers intake, drafting, no code workflows, approvals, negotiation, eSignature, the repository and analytics. Ironclad Agent answers questions about the portfolio and hands work to specialized agents for intake, review, renewals and analytics, and Contract Review Agent redlines against playbooks in Ironclad or Microsoft Word. The agents use models from Google Gemini, OpenAI and Anthropic, which may not train on customer data, and Ironclad trains its own models only for customers who opt in. According to the AI Legal Index, Ironclad's extraction ties every value to the exact passage it came from, highlighting its page and position in the contract. Founded in San Francisco in 2014, it reports more than 2,000 customers.
Juro
Juro is a contract lifecycle platform for in house teams, where legal controls the templates and approval routes that sales, HR, procurement and finance use to create, negotiate, sign and track agreements. AI Review proposes redlines against a team's playbook, including inside Microsoft Word. AI Extract captures data from signed contracts, and Operator answers questions about the repository with source citations. Claude connects through MCP. Every plan includes unlimited users, workflows and templates, with the price set by contract volume and integrations. The AI Legal Index notes that Juro's AI Review explains which playbook rule supports each proposed edit, so a reviewer can accept, change or skip it with the reason in view. Juro was founded in London in 2016 and serves customers in more than 85 countries.
Questions buyers ask
Ironclad vs Juro: which is better for a mid sized in house team?
Juro suits teams that want legal to set templates and approvals while the rest of the business creates contracts, with unlimited users on every plan. Ironclad suits larger contracting operations that need no code workflows, a specialized agent layer, an EU datacenter and stronger contractual remedies. Juro's pricing follows contract volume from under 20 to over 1,000 a month, while Ironclad quotes the platform and meters extra AI use. From the AI Legal Index, based on each vendor's own published materials as of October 17, 2026. No vendor pays for placement.
Does Ironclad or Juro train AI on our contracts?
Ironclad trains its own models on customer data only after an administrator turns on AI Training Settings, and the data is anonymized and aggregated first. Outside model providers never train on it. Juro's AI terms bar using customer data to train any model for another customer, allow a model used only for that customer, and require that model to be erased within 60 days after termination. From the AI Legal Index, based on each vendor's own published materials as of October 17, 2026. No vendor pays for placement.
Which one works better inside Microsoft Word?
Both redline in Word. Ironclad's Contract Review Agent applies playbook positions, flags risk and drafts there, with precedent based redlining in early access. Juro's AI Review proposes redlines against a playbook in Word and shows the rule behind each edit, and its Word integration syncs edits, comments and versions back to the contract workspace. From the AI Legal Index, based on each vendor's own published materials as of October 17, 2026. No vendor pays for placement.
How are Ironclad and Juro priced?
Neither has a public base price. Ironclad quotes the platform, draws eligible agent work from a shared pool of AI Credits and bills extra use at $1 per unit unless an administrator sets a cap. Juro includes unlimited users, workflows and templates on every plan and prices by monthly contract volume and integration complexity, with Salesforce, HubSpot and Workday costing extra. From the AI Legal Index, based on each vendor's own published materials as of October 17, 2026. No vendor pays for placement.
What gaps do Ironclad and Juro share?
Neither gives an accuracy rate or test set for its AI redlines and extractions, so a buyer cannot compare how often either gets a clause wrong. Neither has a stated fallback for when it is unsure of an answer, and neither ties its controls to a named bar opinion such as ABA Formal Opinion 512. In the AI Legal Index's reading, both place the duty to check AI output on the customer.
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 excludes AI output from its infringement indemnity in its AI terms, which is a term a buyer can see and weigh before signing rather than a gap. Ironclad's remedies sit in its Enterprise Services Agreement and AI Addendum, and both agreements leave review of AI output to the customer before reliance. Neither product gives an accuracy figure or test set for its AI redlines, and neither shows the user a confidence signal when the model is unsure. Both are built for in house teams rather than law firms. Ironclad is based in San Francisco and Juro in London. Neither vendor reviewed this page.