Inhubber vs Lexagle: how they compare in 2026
Inhubber is better aligned with a team prioritizing encrypted contract storage, deadlines, signatures and a durable activity history. It describes encryption before upload, German hosting and a blockchain anchored audit trail, with AI summaries and risk indicators on higher plans. Lexagle puts the compliance decision itself at the front of the workflow: Document Guard can permit signing, divert review or block an agreement, and later changes invalidate the prior result. The disclosures differ as well. Inhubber names its hosts but does not publish complete customer terms or identify its AI models; Lexagle publishes service terms that expressly permit defined data uses. For this choice, AI Legal Index identifies a difference between absent contractual detail and a visible permission that requires acceptance. Neither encryption nor a green indicator establishes legal accuracy.
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.
Inhubber's AI sits in the Standard and Professional plans, and the Basic plan runs without it. On those plans it writes a summary of each contract covering partners, payment terms and key obligations, extracts start and end dates, milestones and payment schedules, and analyzes financial and legal risk. The risk analysis flags language such as unlimited or unusually broad liability, marks clauses red, yellow or green, and points out missing clauses and deviations from standard terms. It reads PDF, DOCX and XLSX files, with OCR for scans. The repository with encryption on the user's side, deadline reminders, approval workflows, the blockchain audit trail and electronic signatures make up the rest of the product and all work without the AI. Ansorge Logistik and 17er Oberlandenergie describe using the AI summaries day to day, while rebuy runs Inhubber without the AI features.
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.
Inhubber's AI document analysis page claims accuracy levels over 90 percent, rivaling human reviewers, and attributes results to pre trained legal models, continuous learning and human validation. No method, test set, contract types or date stands behind the figure, and it appears on no other page. Risks are marked directly in the contract with colored indicators, so a reader sees the flagged clause in place. Extracted dates and summary points are not linked back to the passages they came from on any product page. The results widgets on Inhubber's pages show 0 percent in every slot. A November 2025 blog post claims time savings of up to 60 to 70 percent and says more than 95 percent of obligations are completed before their due dates, with no source for either figure.
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.
Inhubber's AI page says material legal differences should still be reviewed by the responsible business or legal teams, and the German version leaves the final comparison with the responsible departments. The product assigns reviewer, editor, observer, approver and auditor roles, with configurable tasks, approvals and escalations, but these govern the contract workflow rather than the AI's output. A blog post says the machine learning learns from user corrections. Inhubber does not describe whether summaries, extracted dates or risk colors take effect without a person confirming them, how a user corrects an extracted deadline, or what the AI may not be used for. The AI page describes the AI as an assistant to legal expertise, not a replacement for it.
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.
Inhubber's case studies are dated and name their customers. Ansorge Logistik, a company of about 500 employees, uses the AI summaries daily, and Markus Sauter of its accounting and contract management team says a 40 page contract can be understood in a few sentences. Its cleanup found 5 to 10 outdated contracts still running (November 2025). At rebuy, Frank Kurzer, head of the legal department, credits deadline monitoring with avoiding unwanted extensions and saving thousands of euros, while the legal team still reviews contracts by hand (May 2025). 17er Oberlandenergie, a utility of 11 to 50 employees, uses AI summaries and overviews (September 2026), and TTI Group reported paper costs down 50 percent in 2021. Logos include EDEKA Baur, Ankerkraut, the OECD, Apetito, Kreis Paderborn and Stadtwerke Penzberg, and the site claims more than 10,000 users. The SAENTIS Family Office study shows only placeholder figures, though the legal page quotes it as saving around 80 percent of the time.
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.
Inhubber's security page, updated September 2026, says documents are encrypted just before upload and that only the machine on the user's side can read their contents. It adds that zero knowledge encryption and selective disclosure meet GDPR requirements. The AI page adds that even Inhubber cannot access the content, and the German privacy policy says Inhubber has no control over or access to it. Inhubber does not explain how server side AI analysis reads documents that are encrypted on the user's side. It does not say whether customer contracts are used to train or improve its models, and its data processing agreement is available only on request. Encryption is AES 256 in transit and at rest. Privilege and work product are not mentioned.
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.
Inhubber's AI page says the AI acts as an intelligent assistant rather than replacing legal expertise, and the German page says the software does not replace a legal assessment. It recommends that material legal differences be reviewed by the responsible business or legal teams. The product is sold to procurement, finance, HR, logistics and sales as well as legal teams, and its AI analysis of legal risks is available to all of them. The German legal page carries the heading contract management for law firms while its text addresses in house legal departments. With its customer terms private, Inhubber states no contractual disclaimer of legal advice, and nothing addresses the German Legal Services Act or the professional duties of lawyers who use it.
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.
Inhubber sets out no AI governance for the models behind its summaries and risk analysis. It names no responsible AI policy, EU AI Act position, owner for model behavior, model testing process, model card or AI management certification. The only statements about how the models behave are the claim of more than 90 percent accuracy and the reference to pre trained legal models, continuous learning and human validation. None of them comes with a method. The use case page promises human validation without saying who validates or when. Its ISO 27001 certificate covers information security for the platform's development, operation and support rather than model behavior. Nothing addresses whether risk flags differ across contract types or across languages, though Inhubber says the AI reads contracts in any language.
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.
Inhubber's security page describes AES 256 encryption in transit and at rest, encryption on the user's side before upload, and hosting on AWS and DigitalOcean in Frankfurt. It also describes automated unit and integration tests with manual regression testing. Its privacy policies, dated June 2022 in German and January 2023 in English, cover personal data in general and name co founder Andre Sokolov as the contact. They say personal data is kept no longer than necessary, that name, email, blockchain address and password hash remain after deactivation, and that users may ask for deletion at any time, without a timeline. Subprocessors are described only by category, such as IT, hosting, error logging, advisers and payment, with no named list and no AI provider. Breach handling is a promise to follow applicable law. Nothing states what happens to contracts, summaries or risk analysis results when a customer leaves. A trust center for key2contract GmbH sits on the SECJUR compliance platform.
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.
Inhubber's privacy policy includes conditions for its signing service. Customers take sole responsibility for the content, quality and format of agreements, and Inhubber disclaims warranties about the transactions those agreements implement. It also declines responsibility for deciding whether a particular document may legally be signed electronically. These are limited allocation and disclaimer provisions, without a published subscription liability cap or indemnity covering AI analysis. Full customer terms and the data processing agreement remain unavailable without contacting the company. The advertised accuracy percentage therefore does not come with an identifiable warranty or remedy for an erroneous summary, extracted deadline or risk assessment.
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.
Inhubber's integrations page lists Microsoft SharePoint, Microsoft single sign on, Nect for identity checks and QES signatures, Evaco, Outlook Calendar, Google Docs and Sheets, and migration from DocuSign and Adobe Sign. SAP is marked beta, and Microsoft Office 365, Salesforce and Shopify are marked upcoming. API integrations are part of the Professional plan, and a feature FAQ mentions automated SharePoint sync, but Inhubber offers no public API documentation or description of what any connector moves. A help center at help.inhubber.com sits alongside the main site. The signature module imports contracts signed elsewhere and exports signature reports as PDFs with timestamps and participant identities.
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.
Inhubber's security page says contract data is stored only in German data centers, on AWS and DigitalOcean in Frankfurt am Main. Inhubber does not say separately where the AI processing runs. The AI document analysis page offers cloud, hybrid or on premises deployment, while the product and feature pages describe a cloud service only. The privacy policies say Inhubber does its best to keep data within the EEA and treat use of the service as consent to transfers abroad under standard contractual clauses. Inhubber states no tenancy model, and the blockchain that anchors the audit trail is described both as a consortium and as a private Ethereum network.
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.
Inhubber's security page states that the company holds ISO/IEC 27001:2022 certification from Proks Certification GmbH, an auditor it describes as accredited by DAkkS. The certified scope covers the development, operation and support of the platform with its IT infrastructure, processes and personnel. Inhubber gives no certificate number, issue date or validity period, and offers no copy of the certificate. A case study by the compliance platform SECJUR describes taking key2contract from first inquiry to a passed ISO 27001 audit in two months, and a trust center for the company sits on SECJUR's platform. An older blog FAQ attributes ISO 27001 to the data centers instead. The signature FAQ says signature reports meet SOC 2 audit requirements, though no SOC 2 attestation is listed.
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.
Inhubber does not name the models behind its summaries and risk analysis, their provider, or where they run. Its pages refer to pre trained legal models, natural language processing and machine learning that learns from corrections, and its AI page mentions ChatGPT only as a point of comparison. The use case page says the models learn continuously, without saying from whose data. The privacy policies describe subprocessors by category without naming an AI provider, and Inhubber commits to no change notice for models or subprocessors. The security page names AWS and DigitalOcean as hosts, which covers storage rather than the models. Inhubber does not say whether the AI runs on its own servers in Frankfurt or with an outside provider.
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.
Inhubber's pricing page lists Basic, Standard and Professional plans without prices. Basic and Standard carry a request for a price and Professional a contact sales link. Basic allows 50 contract files per user and 1,000 documents and has no AI. Standard and Professional add AI summaries and financial and legal risk analysis, and Professional adds API integrations. The page mentions per contract pricing, a saving of up to 33 percent on annual billing and a free trial without stating its length. G2's listing, supplied by the vendor, shows Basic from $16.99 and Standard from $44.99 per seat a month, figures that do not appear on Inhubber's own site.
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.
Inhubber serves procurement, finance, legal, HR, logistics and sales teams across businesses and public bodies. Industries include retail, energy, manufacturing, healthcare, property and professional services. Its dedicated German law firm offering covers engagement and fee agreements, amendments and office contracts, with access rights assigned to partners, lawyers and administrative staff. AI summarizes agreements, extracts dates and flags contractual risks; it is not presented as a substitute for a lawyer's legal assessment. German, English and French are named examples within a broader multilingual claim. The vendor does not publish a tested coverage matrix for contract types, jurisdictions or language specific interpretation.
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?
Inhubber does not say whether customer contracts are used to train or improve the models behind its summaries and risk analysis. Its customer terms, subscription agreement and general terms are not public, and its data processing agreement is available only on request. The security page says documents are encrypted on the user's side and that zero knowledge encryption and selective disclosure meet GDPR requirements, and the AI page says even Inhubber cannot access the content.
A blog post says the machine learning learns from user corrections, without saying whose data that learning draws on or whether customers can turn it off. The privacy policies cover personal data rather than contract content.
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?
Inhubber's privacy policies say personal data is kept no longer than necessary and list the account details kept after deactivation (name, email, blockchain address and password hash). Users may ask for deletion at any time, without a timeline. Inhubber does not say how long contracts, AI summaries or risk analysis results are kept, whether they are deleted when a customer leaves, or what any AI provider retains. The security page describes hosting on AWS and DigitalOcean in Frankfurt with encryption at rest, without a deletion schedule. No public document sets a contractual retention period, and the data processing agreement is available only on request.
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?
Inhubber keeps its own permission model. Users take reviewer, editor, observer, approver and auditor roles, and tasks and approvals are assigned per contract. The security page describes documents encrypted on the user's side with selective disclosure, so only authorized parties can read them. Microsoft single sign on is listed among its integrations. Every action is recorded in an audit trail anchored to a private Ethereum blockchain, which stores cryptographic proofs rather than contents.
Groups with subsidiaries are a stated use case. Inhubber does not describe how AI analysis reaches documents that are encrypted for specific users, or how one customer's data is kept apart from another's in the Frankfurt hosting.
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?
Inhubber's privacy policies, the only legal documents on its site, do not address requests from authorities or other third parties for customer data. Its customer terms are not public, and its data processing agreement is available on request. The policies say Inhubber does its best to keep data within the EEA and treat use of the service as consent to transfers abroad under standard contractual clauses. The security page says documents are encrypted on the user's side and that Inhubber cannot read their contents. Inhubber issues no transparency report, and nothing says whether a customer would be told of a request.
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?
Inhubber's AI reads the customer's own contracts to summarize them, extract dates and flag risks, and does not retrieve case law or legislation. It handles PDF, DOCX and XLSX files with OCR for scans, and Inhubber says it reads contracts in any language, naming German, English and French. Its pages attribute results to pre trained legal models and continuous learning without naming the models, their provider or the data they were trained on.
The risk analysis compares clauses against standard terms and flags missing clauses without saying whose standard terms it uses or how customers set their own.
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?
Inhubber manages, signs and analyzes contracts and does not cite case law or legislation, so a citator sits outside the product. Its risk analysis flags missing clauses and deviations from standard terms, marking them red, yellow and green, and names unlimited or unusually broad liability as one pattern it catches. The CLM page says the AI suggests missing clauses after scanning each signed contract. Inhubber does not explain how those standards are kept current with changes in the law or in which jurisdictions they were drawn up.
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?
Inhubber does not describe what its AI does when it cannot find a date or classify a clause. Risk flags come as red, yellow and green markings in the contract, and no confidence measure is shown for summaries or extracted values. The AI document analysis page claims accuracy above 90 percent and recommends that the responsible business or legal teams review material legal differences. A blog post says the machine learning learns from user corrections, and the use case page mentions human validation without describing when it happens.
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 records court decisions worldwide that address hallucinated AI content and the tool involved where known, has no entry naming Inhubber or key2contract. Inhubber stores, signs and analyzes contracts for companies rather than producing court filings, so its output does not ordinarily reach a brief. Its AI summaries and risk flags stay inside the contract record.
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?
Inhubber's AI pages say the AI assists rather than replaces legal expertise and does not replace a legal assessment, and they recommend review of material legal differences by the responsible business or legal teams. The product is sold to procurement, HR, sales and other teams outside legal, which receive the same AI analysis of legal risks. No professional conduct guidance or ethics opinion is named, and with its customer terms private, no advice disclaimer can be read in a contract.
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?
Inhubber markets a dedicated law firm workspace for engagement agreements, fee arrangements and other contracts, alongside its corporate customer base. It promises less coordination work and more time for client matters, with AI helping lawyers identify important clauses and deadlines. Storing a fee agreement does not explain how AI assisted work should be charged to that client. No time adjustment guidance, client disclosure template or allocation of AI expenses accompanies the efficiency claims.
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?
Inhubber offers a data processing agreement on request and names no subprocessors, describing them in its privacy policies only by category, such as hosting, error logging and payment. A trust center for key2contract GmbH sits on the SECJUR compliance platform, and a SECJUR case study describes the company passing its ISO 27001 audit two months after first contact. The security page names AWS and DigitalOcean in Frankfurt as hosts and states the certification. No AI provider is named, so a customer has no model provider list to pass to its own stakeholders.
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?
Inhubber records every action, from edits to signatures, in an audit trail anchored to a private Ethereum blockchain, and signature reports export as PDFs with timestamps and participant identities. Only cryptographic proofs, not contents, are written to the blockchain. Signature options run from simple electronic signatures to QES through Nect, and the FAQ claims all three eIDAS levels while the product offers no separate advanced signature.
Inhubber does not say whether AI summaries or risk flags are marked as machine generated in that trail or which model produced them. Inhubber's output is a contract repository, signatures and reports rather than court filings, and it offers no disclosure template or guidance.
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.
- AI Governance and Bias Disclosure
- Good Law Verification
- Refusal and Uncertainty Behavior
Which one fits
Choose Inhubber if
- German contract hosting and encryption before upload are priorities.
- The main operational problem is deadlines and portfolio visibility.
- A blockchain anchored history and signature options fit audit needs.
Choose Lexagle if
- The organization wants an explicit AI gate controlling signing eligibility.
- Legal policy deviations need an automatic review or block route.
- External changes must trigger a new compliance evaluation.
In summary
Inhubber
Inhubber is a Berlin based contract platform with German hosting, user level encryption, deadline management and electronic signatures. Standard and Professional add AI summaries and risk analysis, and law firm materials cover engagement and fee agreements.
Lexagle
Lexagle's contracting platform combines Lexie assistance with Document Guard. The AI gate uses customer rules and version protection to control the path toward signing, with partial matches sent to a human rather than automatically accepted.
Questions buyers ask
Do both products use traffic light indicators in the same way?
Inhubber uses colors to flag contractual risk. Lexagle explicitly links its compliance states to workflow actions, including immediate progress to signing, human review or blocking and escalation. From the AI Legal Index, based on each vendor's own published materials as of October 16, 2026. No vendor pays for placement.
Does Inhubber explain how AI reads encrypted content?
It claims that only authorized users can read content and that even Inhubber cannot access it. The published explanation does not fully connect that architecture with the AI processing path or name the model provider. From the AI Legal Index, based on each vendor's own published materials as of October 16, 2026. No vendor pays for placement.
Are Inhubber's subscription terms as accessible as Lexagle's?
Full Inhubber customer terms are not publicly available, although its privacy policy contains limited signing disclaimers and a DPA is offered on request. Lexagle displays a service agreement with substantive data and liability provisions. From the AI Legal Index, based on each vendor's own published materials as of October 16, 2026. No vendor pays for placement.
How should a law firm interpret the savings claims?
Both products address law firm users without providing an AI client fee allocation method. In this comparison, AI Legal Index identifies efficiency claims that remain separate from guidance on what the lawyer should charge a client.
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.
Inhubber's hosting commitments do not separately establish model processing location. Lexagle's published terms and actual processing configuration also need to be considered together.