Josef vs Legito: how they compare in 2026

Josef sells three products: Josef Q for AI question and answer, contract automation, and workflow automation. Only the first is driven by models. The contract and workflow modules are template and rules automation that predate the AI layer, and they are what the L’Oréal case study's 66% turnaround figure rests on. Josef Q is not peripheral: it has its own login at q.joseflegal.com, four dedicated product pages and its own named customers at adidas, Bupa and Cityblock Health. Remove it, though, and a working no code document and workflow platform remains. The models drive a core capability layered on a product that would still work without them.

The vendor's own headline settles this. The AI page is titled AI-powered Document Automation and CLM, and its subtitle says AI powered and rule based document automation complement each other. Kedy AI is a real, named, shipped layer with five distinct capabilities, but it sits on top of a platform that stands entirely without it. Remove the models and a buyer still has interactive template automation, lifecycle management with routing and approvals, a no code application builder, an audit trail and a free electronic signature product. That is the whole of the free plan and the whole of what the named customers are quoted describing. The company was founded in 2015, and its case studies, including the PwC deployment and the 450,000 hours figure, rest on rule based automation rather than on inference. AI accelerates authoring and extraction here; it is not the mechanism the buyer is paying for.

Grounding is real and specifically documented. The AI controls page says Josef Q is a closed domain system answering only from uploaded content, and the source list shows the exact page, paragraph and clause an answer drew on, so a user can open and check the support. A document processing engine is described as scanning and optimizing uploaded content before indexing. No measured accuracy figure or test set is published. Josef Q retrieves the customer's own policies rather than primary law, so grounding to primary authority and citation status checking are not capabilities it claims. Against that, the audit trail page carries an unqualified “No hallucinations!” claim, which is marketing running ahead of the mechanism, though it sits alongside a described architectural control and a published refusal path.

No accuracy content of any kind is published. There is no figure, test set, evaluation, third party validation or named failure mode on the AI page, the security page, the pricing page or the subscription agreement, and the agreement does not mention AI at all. The nearest thing to a control is a design constraint. AI drafting is described as inserting extracted data into automated templates while keeping the template fully intact, which bounds what the model can alter but says nothing about output accuracy. The nearest thing to a limitation disclosure is a blog article asking whether a reader can accept that AI returns different results in two identical situations. It acknowledges nondeterminism in the abstract without stating what the product does about it. Grounding to primary legal authority does not apply to a document automation and CLM product. The knowledge base article on AI document drafting was not opened and may say more.

The control structure is published in detail. The AI controls page documents human moderation of every answer, adding and removing sources in a Moderation tab, a Tuning Lab for tone, length and spelling, and Smart and Follow-up Suggestions that shape what end users ask. The stop rule is published and specific: outside the uploaded content, the tool answers “Sorry, I don’t know.” The audit trail page adds that all user questions and generated answers are tracked and stored. What is missing is a route back to human judgment. No escalation path from an unanswered question to a lawyer is published, and no thresholds or distinct autonomy modes are published. The review surfaces are the strongest part of the published material.

Autonomy is claimed and oversight is not described. The vendor states that AI agents will undertake regularly recurring tasks in the customer's workspace, which is unattended operation, and that Kedy AI navigates through workflows and controls lifecycle operations. Nothing published states what an agent may do without a human, at what point it stops, whether a confidence signal is shown to a reviewer, or what happens after an agent acts wrongly. No approval gate for AI output is described anywhere. The platform audit trail, described on the security page as timeline and versioning, is a general control that predates the AI and is not presented as a way to oversee it. The subscription agreement, where a supervision obligation would ordinarily sit, is silent on AI entirely.

Attribution and figures are both present. The L’Oréal case study names Candy Welsh, Legal Counsel, and reports a 66% drop in contract turnaround, one contract moving from over an hour to 20 minutes, more than 100 such contracts a year, and roughly two weeks of work saved annually. Other named deployments carry named officers. Katherine Roseveare, General Counsel at adidas, is named for a deployment across more than 65,000 people, and Claire Nuske, Head of Legal Operations at Bupa, for more than 40 self service tools. Wendy Chow, General Counsel at Cityblock Health, and Sheila Dusseau, Head of Global Legal Operations at Ferring Pharmaceuticals, are also named. No case study carries a date, and the 66% figure comes with no statement of how it was measured or over what period, so neither the method nor the currency can be assessed.

Deployment evidence is broad and well attributed. Named customers appear with logos, including PwC, Deloitte Legal, LexisNexis, Holland & Knight, Santander, Société Générale, UniCredit, Telia, Škoda, Vialto, U.S. VETS and the Bronx and New York County District Attorneys' offices, against a stated base of over 400,000 users. Testimonials carry full names and roles. Tomas Fiala, Director at PwC, describes a Center of Excellence running since 2018 across the PwC global network. Others include Paul V. Saunders, Chief Innovation Officer and Partner at Stewart McKelvey, and Sony Varughese, Chief Technology Officer. Nel Pelle, Sales Manager at BAM, Galya Oster at Atrafin, Eli Cohen, Chief Operating Officer at RBI, and Jeremy Aber, a software attorney, are also quoted. Figures include contract checking falling from 20 to 50 minutes down to 5 minutes, 450,000 hours saved at a Big Four firm, and a deployment for 10,000 users built by two specialists working part time. The figures sit inside testimonials and case study titles with no method, baseline, sample or date. None of the outcome evidence is attributed to Kedy AI; every quoted result describes rule based document automation.

No customer agreement is published. The only published documents are website terms and a privacy policy dated 15 February 2024, which applies to Josef as a controller rather than to customer content held as a processor. What is published is real but general. Josef's FAQ says customers keep full ownership of their data and Josef acts as custodian, and the security page states AES-256 at rest and TLS 1.3 in transit with server side keys held by Josef. Nothing addresses training on customer content, tenant separation, or privilege and work product. For an in house buyer the key need is separation between tenants, and no separation of any kind is documented. The ownership and encryption commitments can be read before signing, but the commitments that matter most cannot.

Substantive published commitments, short of the full picture. The subscription agreement makes all data, files, documents and templates uploaded or created by the customer the customer's property. It grants Legito the right to use customer data solely to perform under the agreement, a purpose limitation rather than a broad license. Section 5 makes customer data the customer's confidential information and binds Legito to reasonable care, purpose limitation and access on a need to know basis under signed confidentiality agreements. The AI page adds that no third party service processes customer data in AI and that data is never used for AI training. Retention is bounded: the customer may export for 30 days after termination, after which Legito may destroy the data. The customer chooses a named storage region, and the processing agreement bars transfer outside it without express written consent. Encryption is applied in transit and at rest with keys held away from the hosting provider, and a self anonymization feature covers data in documents. Privilege and work product are not mentioned anywhere in the agreement or on any published surface. The product holds contract and back office documents rather than matter files.

The only published disclaimer covers the wrong thing. The website terms say content on the Josef website is for information purposes only, which addresses the marketing site rather than the output of a tool answering policy questions for employees. The product, meanwhile, is described in advice terms. The Josef Q demo panel offers scalable guidance and advice, and the FAQ describes legal aid organizations and boutique firms using Josef to deliver onboarding, wills and guidance tools to members of the public. No jurisdiction limit, statement of who may rely on an answer, or disclosure requirement for consumers is published, and ABA Formal Opinion 512 is not mentioned. The disclaimer exists but does not reach the product, and the uses the vendor advertises to the public are where the advice line matters most.

Nothing addressing unauthorized practice, professional responsibility or the boundary between the software and legal advice is published on any Workspace surface. The subscription agreement, which is the customer agreement for this product, contains no such provision, and neither the AI page, the legal department page nor the law firms page carries a disclaimer. One instrument on the same domain does address it. The Legito Marketplace terms of service require a user to tick a box agreeing that the application is not a legal service or its substitute. The Marketplace is a separate product with its own purchase path, its own terms and its own single use conditions for consumers, so that acknowledgment governs a different transaction and does not apply to the Workspace product.

No governance position is published. There is no responsible AI page, no named internal owner, no testing regime before release, and no ISO 42001 or equivalent. Nothing addresses whether answer quality varies across topics, document types or populations. The moderation and review controls are real, but they are an oversight mechanism rather than governance, and security controls are a separate subject. The chief executive's published article on context engineering is a design argument, not a governance disclosure.

No governance disclosure is published. There is no AI policy, no acceptable use policy for AI, no responsible AI or ethics statement, no bias or fairness discussion, no ISO 42001 or NIST AI RMF alignment claim, and no named internal owner for AI decisions. No model evaluation or testing is described, and neither the subscription agreement nor the data processing agreement has a section on AI. Two blog articles discuss AI in document processes and where AI brings value and where its limits lie, but both are market commentary rather than statements of how the vendor governs its own models. The ISO 27001 certification covers information security, and its quoted scope names document automation and CLM software development and hosting, not AI governance. Surfaces read: the AI page, the security page, the subscription agreement and its data processing exhibit, the pricing page and the site footer inventory.

Access control is documented and the rest is not. The security page states AES-256 encryption at rest, TLS 1.3 in transit, encryption keys held by Josef on the server side and regular access audits, alongside OWASP and ASD secure coding frameworks, automated vulnerability scanning and annual third party penetration testing. What happens to uploaded documents and prompts afterwards is not addressed. The privacy policy keeps service data for the business relationship and an unstated period after, and describes deletion only as securely deleting or anonymizing once no legitimate business need remains. No incident practice is published. The subprocessor list is not published; the privacy policy says it can be provided on request, and no self service portal or download route is published.

Three express commitments sit together on the AI page. Kedy AI is hosted entirely on Legito servers, no third party services process customer data in AI, and customer data is never used for AI training. The subscription agreement is consistent with them: it grants Legito the right to use customer data solely to perform under the agreement and reserves no training or improvement right anywhere. The closest clause, on statistical information, permits Legito to compile and publish performance statistics about the service if they neither identify customer data or the customer nor permit reidentification. That is a right to performance metrics, not to machine learning. The processing agreement bars transfer outside the chosen region, sets an eight hour breach notification undertaking, and requires subprocessors to be bound to confidentiality. The limit is placement. Every AI commitment lives on a marketing page, and the customer agreement, last modified in September 2023, does not mention AI at all, so a buyer has the vendor's word rather than a term to enforce.

Nothing is published on who bears the loss when an answer is wrong. The only published liability clause sits in the website terms and excludes liability arising from use of the Josef website, limited, where it cannot be excluded, to resupplying the relevant services or information. That is a website clause, not a position on product output. No master subscription agreement, customer agreement, service level agreement, warranty or indemnity is published, and the site footer offers only the website terms, the privacy policy and a cookie notice.

A published agreement gives real general recourse and none specific to AI. A tiered availability warranty credits 10, 25 or 50 percent of the monthly fee by uptime level. If availability falls below 98 percent for two months in a row or any three in six, the customer may terminate and recover prepaid fees. Legito warrants that security and functionality will not materially decrease and that the service will perform in accordance with its documentation. There is a 30 day cure period for material breach, an intellectual property indemnity covering defense costs, negotiated settlements and damages awarded by a court, and an eight hour breach notification undertaking in the processing exhibit. Against that, liability is capped at fees paid in the preceding twelve months, and all indirect damages are excluded, including loss of or unauthorized access to data. Nothing in the agreement addresses AI output. There is no warranty, allocation of responsibility or remedy where Kedy AI extracts a term wrongly, drafts from the wrong source, or an agent acts on a bad inference. The processing exhibit also disclaims liability for customer data disclosed through a cyber attack despite reasonable efforts.

Thirteen integrations are named and grouped by function, and the direction of data flow is described. Policies sync in from SharePoint and Confluence, data is pulled from Airtable and Google Sheets, and captured information is pushed out to Slack, Teams, SharePoint and Salesforce. The legal systems are present: HighQ, Xakia, Dazychain and Actionstep are all named. The Xakia entry goes furthest, describing Josef bots launched from Xakia's internal client portal so that requests stay managed within Xakia. Two integrations, Actionstep and Xakia, have linked walkthroughs. No documentation an implementer could use is published: no developer index, no field mapping, and no statement of what a firm must configure. The integrations page answers any unlisted case by inviting a conversation with the team.

Integration is documented rather than asserted, and the documentation is public. A REST API is published with a Swagger specification, alongside webhooks described as a push API, programmable tags, a developers hub, and self service creation, deactivation and deletion of API keys. Named ready made integrations include Salesforce, Microsoft SharePoint and Zapier. The subscription agreement itself names DocuSign, Salesforce and HubSpot as third party services the platform works with, which puts the integration surface in the contract rather than only on a product page. A Model Context Protocol server is published so that other AI applications can reach Legito features. Legal practice systems are absent. No document management system such as iManage or NetDocuments, no practice or matter management system, no time and billing system and no court or filing system appears in the integration inventory. The depth is real, and the direction is general enterprise back office rather than the legal stack.

The security page and the FAQ both state data residency options in the US, Europe, the UK and Australia, a commitment to four regions stated consistently in two places. The tenancy model is never stated: nothing says whether customers sit in shared or separate instances. Processing location is not addressed separately from storage, and two documents pull in different directions. The security page offers regional residency, but the privacy policy says personal information may be transferred and processed outside the user's country, including in the United States, relying on standard data protection clauses for EEA and UK transfers. The two are not necessarily inconsistent, since the privacy policy governs Josef as controller rather than the platform tenancy, but no published document reconciles them.

Residency is published, specific and contractually locked. The security page states that each customer may choose its data storage location and names three: Vint Hill, Virginia in the United States; Limburg, Germany in the European Union; and Melbourne, Victoria in Australia. Hosting is with OVH, named openly. The data processing exhibit provides that Legito may not transfer customer data to a third country outside the chosen server location without the customer's express written consent, which makes the choice an enforceable term. Two gaps remain. Tenancy is nowhere stated, so a buyer cannot tell whether the service is single tenant, pooled or configurable, and no self hosted, private cloud or on premises option is published. There is also an inconsistency between the vendor's own pages. The account creation form on the AI page offers a server choice of Australia, Canada, Germany and the United States, adding Canada to the three locations the security page lists.

SOC 2 Type II is stated on the security page, the FAQ and the home page, and the privacy policy states SOC 2 Type I and II. Annual third party penetration testing is stated, as are GDPR compliance and ISO certification of the underlying server infrastructure. Nothing that would let a reader check any of it is published. No auditor, scope or coverage period is named, no report or summary is offered by any route, and no trust center exists. No Vanta, SafeBase or equivalent portal is linked from the footer or navigation. The standard is named in prose rather than only as a badge image, but there is no route to the evidence at all, not even a gated one.

The certification body is named, and the evidence is dated. The security page states approval by Lloyd's Register to ISO/IEC 27001 and quotes the certified scope: the development and hosting of Legito document automation and contract lifecycle management software, and the provision of document automation and software configuration services. The certification is cited as ISO/IEC 27001:2013, a revision superseded by the 2022 edition. The page states that the latest ISO 27001 audit was conducted in July 2021, on a page last modified in September 2024. No certificate document is published, no certificate number or validity window is given, there is no SOC 2 report, and there is no trust center or document request portal. The OVH certifications listed on the same page, ISO 27001, SOC 1 Type II, SOC 2 Type II, PCI DSS and a Cloud Security Alliance STAR self assessment, belong to the hosting provider, not to Legito. The penetration testing described is the customers' own: the page states that large customers engage third party auditors and that Big Four firms regularly test the application. That describes customer diligence, not a program Legito commissions.

Josef acknowledges a large language model underneath and never says whose. The chief executive's published position is that an LLM alone cannot be trusted and needs context engineering, and the audit trail page refers to GenAI engineering. No model, model provider or inference location is named. Hosting region and ISO certified infrastructure are published, but a hosting location shows where the software runs rather than whose model sees client content. There is no commitment to notify customers if the underlying model changes. The only route to the supply chain is the subprocessor list the privacy policy says is available on request.

Nothing about the model itself is disclosed. No model, provider, model family or version is named, and the vendor does not say whether Kedy AI is built in house, fine tuned from open weights, or licensed and run on Legito infrastructure. What is published is architectural and useful to a buyer: Kedy AI is hosted entirely on Legito servers, and no third party service processes customer data in AI. That tells a firm that no external model provider sees client content, and it is covered under Deployment Model and Data Residency and under AI Safety and Data Stewardship. Where the models run is not what the models are. Legito does name three AI services, OpenAI, Anthropic Claude and Google Gemini, but offers them expressly as optional alternatives for customers who prefer them. The page states that Kedy AI does not require any integration, so these are a substitute the customer elects rather than Kedy's supply chain. An assurance that no third party processes data in AI is difficult to reconcile with an undisclosed model of unstated provenance, and only the vendor can close that gap.

No pricing information is published at any level. There is no pricing page, and the navigation and footer of the home page, the Josef Q and integrations pages, the security page, the AI controls page and the FAQ carry no pricing entry. Every commercial path is a demo booking or a contact form. No tier names, packaging structure, unit of charge or figure is published, so nothing shows what is charged for, let alone how much.

Real pricing information is published, but no rate is. A permanently free plan exists and its scope is named: document lifecycle management, the custom application builder and Legito Sign, as a lite version of the enterprise workspace described as free of charge forever. The electronic signature product is offered at no fee, and a 30 day trial opens all features with no credit card required. Pricing pages are maintained in six languages. No paid figure, volume band, unit of charge, minimum term or seat minimum is published on any vendor page, and the pricing page carries no plan table in its rendered body. The Complete Features List section of the pricing page is a heading with no content in the extracted body; the page's structure indicates something belongs there, so it may say more. A third party site publishes monthly rates per user and a minimum user count, but it is not the vendor's own publication.

Coverage is set out by segment, with named customers in each. The FAQ and customer navigation name five segments: in house legal, global law firms, boutique and NewLaw firms, legal aid organizations and community legal centers, and law schools. Each has its own page and named users. In house users include L’Oréal and Bumble, and firms include Orrick and Herbert Smith Freehills. NewLaw users include Hive Legal and Polaris Lawyers, legal aid users include Housing Court Answers and Everyday Justice, and education users include Cornell, NYU and the University of Pennsylvania. Document types are named too, including NDAs, MSAs, employment agreements, powers of attorney and client onboarding forms, with question and answer uses grouped under commercial, privacy and data, legal operations and HR. The limits are not stated: Josef's FAQ says anything repeatable can be automated, government use is not addressed, and no page says where the product stops.

The legal surface is real and named but sits inside a wider back office platform. A dedicated Legal department page addresses legal operations directly, framed as no code automation for legal ops to apply expertise at scale with controls, automation and oversight. A Law Firms industry page addresses knowledge transfer and repeat drafting, and a Professional Associations page addresses member document portals. Legal adoption is evidenced by name: Holland & Knight, Stewart McKelvey with a published automation journey, Deloitte Legal, LexisNexis, and the Bronx and New York County District Attorneys' offices, the last with its own prosecution automation case study. The interface and pricing pages are maintained in English, German, Spanish, French, Czech and Slovak, and three hosting regions serve the Americas, Europe and Asia-Pacific. Legal is one of seven departments and one of eight industries. There is no breakdown by practice area, no legal content for particular jurisdictions and no statement of which matter types are covered. A buyer can see that legal teams use it; they cannot see which legal work it is built for.