Gaius-Lex vs Omnilex: how they compare in 2026

The terms of service define the paid services as putting questions to a language model and issuing instructions to it, and the metered unit of charge, called a Lex, is consumed per AI action. A classic text search sits alongside it as a separate service in the terms, and every function the product is sold on runs through the model.

The models drive what people use, on top of a large content collection. The site counts 1,057,541 sources, mostly 797,321 Swiss court decisions and 22,181 laws and articles, and that collection would still work as a Swiss law database without any model. The AI adds a reasoning layer over it and one thing that exists only because of the models: the Omnilex Commentary, 222,525 annotations the company writes article by article. Agents built without code from a firm's own playbooks sit on top. The pricing page sells sources, models and agents together as one license.

Every thesis carries a footnote and a link to the regulation or ruling, case signatures are checked for existence against the database, and the vendor says that where confirmation is missing the system flags it rather than asserting. No accuracy rate, hallucination rate or published evaluation exists. The marketing sites claim the product never guesses and produces no hallucinations. The terms of service say the AI does not always answer in line with reality, name the problem as hallucinating, and warn that it may materially affect the result.

Grounding is documented and clearly labeled. Omnilex says every claim is cited and ready for the file, and its home page example shows an annotation to article 336c of the Code of Obligations footnoted to its authorities. Users choose whether research draws on court rulings, commentary or internal data. The commentary Omnilex generates is labeled as AI drafted, so a lawyer can tell machine written analysis from published doctrine. No accuracy figure, evaluation, benchmark or test set is published, and clause 6 of the terms says the provider accepts no liability for the accuracy or legal usability of generated content.

The product is marketed as an autonomous trainee that plans its own research and delivers drafts. The terms say generated content is never self standing, is to be treated only as a suggested formulation, and requires the user's own work at the concept, creation and review stages. That statement is general and is not attached to a named plan or mode stating what its output may not be used for.

Review is a contract duty, and agents run when a user starts them. Clause 6 of the terms says the user remains responsible for reviewing, adapting and using all content, which puts the check on the lawyer in the binding document rather than in marketing. The product description matches: clause 2 speaks of AI assisted suggestions, and the product page describes a system that analyzes documents, laws and judgments, structures arguments and highlights relevant content. Agents are built from a firm's own playbooks and review steps and run on demand, so they start only when a person starts them, and the worked example shows its four steps. The boundary is not published. Nothing says what an agent completes without a human once started, what happens when a step fails or returns nothing, or what separates a suggestion from an action. The firm writes the workflow, so the limits are set by the customer and not described.

The vendor publishes no named customer, case study or production figure. Polish trade press covers the product, and a blog post by its investor, Digital Ocean Ventures, refers to dozens of early clients. The product runs with a live checkout, an application and four jurisdictions.

Ten customers are named by logo: the Swiss Confederation, Bayer, the legal protection insurer Dextra, the pension fund Asga, the disability charity Pro Infirmis, and the firms SwissLegal, Ruoss Voegele, Neuwerk, Domenig and Seeger Frick. Two have case pages with named people on video: Florian Probala, Chief Claims Officer at Dextra, and Dr. iur. Marco S. Marty, Founding Partner at MV Legal Partners. One figure is published: over 6,000 lawyers use the platform. That counts adoption, not outcomes; no figure is tied to a named customer, and nothing is dated.

Encryption in transit and at rest is published, along with automatic or manual anonymization for each document. A contractual term bars users from submitting third party personal data at all unless a data processing agreement has been signed, and requires every document to be anonymized until then. Privilege, work product and professional secrecy are not treated anywhere as duties the vendor owes, and no segregation by matter is described. The terms reserve a right to use query history to develop the vendor's AI algorithms, while the English site says client files, cases and analyses are never used to train any model by the vendor or any third party.

Omnilex addresses professional secrecy in Swiss terms but says nothing about training. Its home page says models are processed on Swiss infrastructure so attorney client privilege stays intact, and that the platform was built for professional secrecy from day one. The license agreement and data processing agreement are described as drafted to respect professional secrecy and auxiliary person liability, the Swiss doctrine on a lawyer's responsibility for third parties they engage. Clause 7 of the terms covers deletion after the contract ends, subject to statutory retention. Two gaps remain. Nothing describes separation between customers, users or matters, although work is organized into named projects and mandates. And nothing says whether customer content is used for training.

The terms say the provider does not supply legal assistance, that an answer is not legal assistance, and that a user taking any legal step should consult someone professionally qualified to give it. Eligibility is limited to entrepreneurs contracting directly in connection with their business or profession. Consumers are routed to a separate, individually negotiated arrangement through a dedicated address. A separate student agreement grants an educational license that expressly bars commercial, paid or professional use, including during a law firm internship. No bar or ethics guidance is named, and the terms address Polish law while the product is marketed across four jurisdictions, with no jurisdictional limits stated.

The terms take a position on tool versus advice. Clause 2 describes the service as software that supports users on legal questions with AI assisted suggestions. Clause 6 says the provider accepts no liability for the accuracy or legal usability of generated content and that the user is responsible for reviewing, adapting and using all of it. The product covers Swiss law throughout, and the terms are governed by Swiss law with jurisdiction in Zurich. Professional secrecy and auxiliary person liability are named. No statement says output is not legal advice, and nothing covers the professional relationship. No bar or professional body guidance is named, neither the BGFA nor Swiss Bar Association material.

No governance owner, testing before release, evaluation practice or statement about output variation across matter types, jurisdictions or parties is published. The terms disclose that the model is developed on limited data sets whose content the provider does not answer for.

Omnilex's SafeBase trust center lists AI Security, AI Governance and AI Monitoring as published items, which shows a governance position exists, but the items themselves do not display on the public portal. Nothing addresses bias or uneven output, such as whether results differ across cantons, languages, court levels or party types, which matters in a federal system with three official languages.

The privacy policy names the providers whose engines power the AI (OpenAI, OctoML, Gladia, Anthropic and RunPod) and says each processes under a data processing agreement using European Commission standard contractual clauses. An earlier published version named two of the five. Encryption at rest and in transit, anonymization for each document, account deletion within 24 hours of a request, and an export of stored query history when an account is blocked are all published. No retention period is stated for documents or prompts, and no incident response practice is described.

Most of the ground is covered, with two gaps. Access controls are stated: SAML single sign on, audit logs, IP allowlisting and data lifecycle management, plus credential management, brute force protection, account hardening, endpoint detection and response and disk encryption in the trust center. Data is encrypted at rest and in transit. Amazon Web Services and Microsoft Azure are named as subprocessors. A dedicated incident response team is stated, and backups, business continuity, disaster recovery and DDoS protection appear as trust center items. The gaps: retention is given only as deletion after the contract ends unless the law requires otherwise, with no period during the term, and there is no deadline for telling customers about an incident, with the trust center saying more detail is available on request.

The terms exclude the provider's liability for the quality of AI output and give six reasons, including that the system depends on third party providers running the AI engine, that the model is built on limited data sets, and that it may hallucinate. No indemnity, liability cap, carve out or insurance position is published. The terms also say an individually negotiated agreement takes precedence where it conflicts.

Clause 6 of the terms says use is at the user's own risk, the provider accepts no liability for the accuracy or legal usability of generated content, the user is responsible for reviewing and using all content, and liability is limited to gross negligence and intent. That is the widest exclusion Swiss law permits, so nothing is recoverable for ordinary negligence, and no monetary cap is set. Cyber insurance is listed as a trust center document. No indemnity runs either way, and clause 6 disclaims any warranty on output. Clause 5 targets at least 90 percent availability outside maintenance windows and says this is not guaranteed. Clause 9 says use rests on a separate license agreement, which is not published and sits behind the trust center access flow, so its terms are not public.

No document management integration is published, and iManage, NetDocuments, SharePoint and OneDrive appear nowhere. There is no Word or Outlook add-in. The product is a browser application, defined in the terms as software run in a web browser, into which a user uploads files in listed formats. Documents live in the vendor's own store rather than the firm's.

Integration is claimed but not specified. The product page says a firm can connect its document management and legal tools without media breaks and keep its workflows. None of those systems is named: no document management, practice management or electronic filing product, no connector list and no integrations page. Enterprise plans include custom integrations and APIs, but no API or developer documentation is published. What is concrete is SAML single sign on across plans and company SSO at enterprise level.

SaaS, hybrid and on premise are all published as buyer choices, and running locally is the core pitch. The English site says every uploaded document is processed only on servers in the European Economic Area and never routed outside it. The privacy policy names US incorporated providers among those receiving user queries, and an earlier version of the same policy expressly contemplated transfers outside the European Economic Area under standard contractual clauses. On premise deployment keeps data on the customer's systems, and no page says the residency claim applies to one deployment shape only.

Residency is stated with a named city and cloud, and tenancy is not addressed. Omnilex says it is hosted on Microsoft Azure in Zurich, that data is encrypted at rest and in transit and hosted entirely on its Swiss Azure cloud, and that models run on Swiss infrastructure. The pricing FAQ says data is processed in Switzerland and in selected EU countries that the Swiss Federal Data Protection and Information Commissioner recognizes as adequate. Two gaps remain. Nothing says whether the platform is multitenant or single tenant, or how one firm's data is kept apart from another's. And hosting described as entirely Swiss sits beside processing that extends to EU countries, with no explanation. No on premises or customer cloud option is offered.

No SOC 2, ISO 27001, penetration test summary, trust portal or attestation of any kind is claimed or published, and there is no self service request route. The European Union funding badge in the footer is a grant mark, not a certification.

Omnilex runs a SafeBase trust center at trust.omnilex.ai that shows ISO/IEC 27001:2022 and lists documents including a penetration test report dated 5 September 2025, the Omnilex License Agreement with a DPA template, technical documentation, cyber insurance, a data security policy and a network diagram. Omnilex's home page says the certification is audited across the whole organization. The portal splits public and private documents behind a request flow and does not say whether access is instant on an email or NDA click, or only after review. No auditor, certificate number, issue date or validity period is published.

The privacy policy names five providers supplying the engines behind the AI (OpenAI, OctoML, Gladia, Anthropic and RunPod), with standard contractual clauses as the transfer basis, and earlier published versions show the list changing with the stack. No specific model or version is named, only providers. The marketing presents the product as running locally deployed small language models without connecting to public cloud AI services, while the privacy policy names OpenAI and Anthropic as recipients of user queries. No commitment to notify customers when the list changes is published.

Five models are named, with versions, as selectable on Omnilex's home page: GPT-5.6, Claude Opus 5, Mistral Large 3, Kimi K2.6 and Grok 4.6, with the user choosing which answers. Omnilex says every frontier model is processed on Swiss infrastructure so attorney client privilege stays intact, and hosting is on Microsoft Azure in Zurich. Omnilex's trust center names Amazon Web Services and Microsoft Azure as subprocessors. No model provider is named as a legal entity or listed as a subprocessor, so it is not clear who contracts for each model or what it may keep, and it is not stated whether the models run inside the Swiss setup or through the providers' own APIs. There is no commitment to notify customers when the model set changes.

Two plans are published with rates in Polish zloty on the Polish pricing page: Lite at 93.43 PLN net a month and Standard at 282 PLN net a month when paid yearly, with Standard at 329 PLN net on monthly billing, each with a live checkout, and a seven day full trial requires no card. Pro, the team plan with shared files and API access, is priced individually. The terms define the unit of charge at length: a Lex is an internal accounting unit consumed per action, plans carry a stated Lex allowance, 300 a month on Lite and 3,500 on Standard, a consumption table sets the cost of each action, and the rules on top ups, carry over, freezing on non renewal and expiry after 90 days are all written down. Billing runs by the month, the half year or the year, the subscription renews until canceled, and price changes require 14 days notice with a right to cancel. An education plan is also listed. The English site carries no pricing page.

Rates are published with unit and term: CHF 2,000 per user billed annually for a single user, CHF 1,600 per user billed annually for teams from two users, and a custom agreement for enterprise from twenty users, all excluding VAT. Omnilex says the price scales only with the number of people who use it. Onboarding, setup, training and support are included in every plan, and Omnilex's FAQ says nothing essential is held back for a higher tier. Team adds collaboration and integration of a firm's own knowledge, and Enterprise adds SSO, custom integrations and APIs. A fourteen day free trial needs no card or commitment. Usage limits are published at up to 1,000 pages and 500MB per document. Only the enterprise price is withheld, which the page explains as a scoping conversation about integrations and support.

Eight buyer segments are named, each with a stated use: law firms, solo practitioners, tax advisers, courts, public administration, financial institutions, corporations, and small and medium businesses, with a student plan alongside. Jurisdictional coverage is specific, naming the primary sources for Poland, the Czech Republic, Germany and Austria. Firm size is addressed only through the two plan tiers and a team seat model, and there is no breakdown by practice area beyond tax being called out separately.

Four buyer groups each have a page described by the work: law firms doing research, drafting and review; in house teams, from contract review to regulatory questions; public administrations applying federal and cantonal sources; and insurers assessing claims against statute and precedent. Named references include the Swiss Confederation and a legal protection insurer. Swiss coverage is shown by the counted federal and cantonal sources. No practice areas are listed; home page examples cover employment, tenancy and accident insurance law, but only as illustrations. No firm size band is given beyond the seat thresholds in pricing, nothing says whether any jurisdiction besides Switzerland is served, and nothing says what is not supported.