netLex vs Oneflow: how they compare in 2026
netLex is a fit for organizations coordinating legal requests and contracts in a Brazilian business context, with Portuguese service and explicit CRM field mappings into templates. Oneflow is a fit for teams emphasizing an editable web agreement, Salesforce CPQ integration and review dashboards with highlighted findings. Both connect commercial data to contract creation, so the decision should include language, review behavior and data lifecycle. netLex's privacy policy prohibits training on AI inputs but retains platform backups for five years. Oneflow has an express contractual training prohibition, yet its generative AI history can follow provider terms and its appendix excludes confidentiality for that functionality. In that contrast between training promises and retained records, AI Legal Index identifies why deletion and AI processing must be specified separately. Oneflow publishes a starting package; netLex describes user based subscription units without an amount.
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.
netLex combines a contract lifecycle platform with AI for clause drafting, review, extraction and questions about agreements. Its OpenAI integration lets users simplify, translate or revise clauses with prepared or custom prompts. Review Agent compares incoming contracts with the customer's playbook, while Creation Agent turns an existing document into questionnaire fields and variables. Management Agent extracts dates, parties, amounts and obligations for portfolio monitoring. Those capabilities sit within a wider system of templates, approvals, negotiation, signatures and storage that can operate without generation. The June 2026 agent announcement also describes an early access program; creating templates from a description alone was still forthcoming.
AI supports several substantial contract tasks within Oneflow's wider platform. Write with AI drafts, edits and translates text inside an agreement; AI Extract imports participants, dates and duration into editable metadata. AI Review compares terms with a workspace playbook, and AI Insights aggregates the resulting risks across the portfolio. The premium package adds custom rules, dashboard widgets and a report for negotiation follow up. Electronic signatures, editable HTML agreements, permissions, approvals and renewal reminders continue to work without these models. Customers can disable AI, and several review capabilities remain in beta. AI therefore changes how users analyze contracts without replacing the underlying contract system.
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.
Review Agent compares clauses with a company playbook and explains departures from its standards. netLex also describes questions about contracts and attachments, including inconsistencies between the main agreement and a commercial appendix. These are useful sources of context, but the product materials do not demonstrate an openable citation for each answer or a method for validating cited legal authorities. No reproducible accuracy test, sample size or breakdown of missed risks is published. The terms explicitly warn that AI responses may be inaccurate, incomplete or unsuitable. A reviewer therefore has to compare proposed changes with the agreement and applicable law before relying on them.
Review findings connect to highlighted passages in the agreement, with controls for moving between them. Each finding carries the relevant playbook concept, configured feedback and example clause text. A separate view identifies required clauses that the review did not find, while portfolio charts open the corresponding contract list. This lets the reviewer compare a proposed concern with the actual wording and the organization's rule. Oneflow warns that generated text can misstate facts, numbers and law and recommends human correction. No reproducible accuracy study, error rate or jurisdiction specific evaluation accompanies these features. The contract highlighting supports source verification, not validation of legal authority.
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.
Administrators must enable the OpenAI functionality before users can access it, and customer policies govern its use. A reviewer can accept, edit or reject suggested wording, with the final contract remaining under human control. netLex describes additional approval steps for important negotiation changes and a Review Agent configured against the customer's clause rules and acceptable limits. Its July 2026 explanation distinguishes automated actions from human decisions in the history. The precise uncertainty level that stops an agent, mandatory escalation triggers and the procedure for undoing an erroneous downstream action are not published. The terms require users to assess AI results before adopting them.
Administrators enable AI Review for a workspace and configure its playbook, including which clauses matter, which findings count as risks or issues, and what feedback appears. Role permissions separately control access to individual reviews and the Insights dashboard. Sent contracts receive continuing analysis; draft contracts require a manual review action. A person can inspect highlighted text, edit the playbook and use example wording when revising an agreement. The AI appendix advises human review before relying on output. No confidence cutoff, mandatory lawyer approval after an AI finding, or correction route for an already approved mistake is specified. Risk colors classify findings rather than stop execution.
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.
Gupy provides a named example of deployment with operational figures. In netLex's September 2026 account, Gupy simplified its commercial amendment language, introduced defined approval responsibilities and connected Salesforce before measuring changes in the first months. Average amendment completion fell from 38 to 25 days, while legal response time fell from 1.58 to 0.31 day. Amendments signed without customer changes increased from 16% to 60%. The account attributes the improvements to a combined process and integration project, not an isolated AI intervention. Exact observation dates, document counts and an independently reviewed measurement protocol are absent, limiting comparisons with other organizations.
Puzzel's Sales Operations Manager, Anette Johnsen, describes generating offers and contracts from Salesforce opportunities with items from related CPQ quotes. She identifies a concrete benefit of the HTML format: participants revise one agreement instead of uploading successive files before signature. Other named users include Systembolaget's Head of Indirect Sourcing, Tor Myhrman, and Hedin Bil's HR Business Partner, Elin Skoglund, who describe handling agreements and maintaining oversight. These accounts establish operational use across sales, procurement and HR. They do not isolate AI review performance or supply a measured error reduction, evaluation period and sample for Oneflow's current AI packages.
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.
The privacy policy states that inputs supplied to netLex AI will not train the model, and the product description says drafting and review data are not retained by the AI service. Access controls use roles, corporate authentication and customer permissions. netLex describes agents as unable to reach information beyond the current user's access, with a separate customer environment. Contract storage nevertheless has its own lifecycle: deleted user records can leave name and email history, and backups remain for five years. The public terms do not directly promise preservation of attorney privilege or explain how model provider access affects work product protection.
The AI appendix expressly prohibits Oneflow from training any AI model on customer data and takes precedence over conflicting general terms for AI features. Ordinary service confidentiality continues while information remains confidential, with restrictions on compelled disclosure. There is a consequential exception: the generative AI section excludes Oneflow's contractual confidentiality obligations along with liability, indemnities and service levels. Review, Insights and Extract have a separate processing section tied to the DPA. Workspace permissions and optional provider controls support access management, but attorney client privilege and work product receive no specific undertaking. The contract therefore requires attention to the exact AI functionality being enabled.
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.
netLex is aimed at legal departments and the business teams working with them on company agreements. Its terms require users to assess the relevance, accuracy and suitability of AI results before adopting them for any purpose. They also state that AI cannot replace necessary human, legal, technical or professional analysis. The drafting interface supports this division by leaving acceptance or rejection of suggestions with the user. However, jurisdictional limits on automated legal opinions and a detailed account of lawyers' competence or supervision duties are not supplied. Corporate staff can initiate contracts and requests without being lawyers, making the configured approval route significant.
Oneflow's AI appendix says output is not legal advice, legal conclusions, recommendations about legal rights or an application of law to a customer's circumstances. It advises human review because generated content can misstate law as well as facts. A separate UK article maps solicitor responsibilities to SRA standards, confidentiality, client communication and supervision, and describes practical review and pilot controls. North American terms also prohibit treating the platform as a substitute for an attorney. The product nevertheless serves sales, HR and other users without legal qualifications. No comprehensive jurisdiction by jurisdiction set of product restrictions or lawyer competence program is supplied.
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.
netLex publishes principles for AI use in contracts: company playbooks, access permissions, traceable decisions and final human approval. It describes logs that distinguish automated decisions from human actions and presents these controls as part of its own design. That establishes an AI governance position, but not a full account of how the vendor tests its models. No named owner for model risk, release evaluation protocol, bias assessment across languages or results across contract types are supplied. The Information Security and Compliance Committee oversees security and privacy; its existence alone does not show accountability for uneven legal output or model behavior.
Oneflow promotes human accountability and warns against automation bias in its guidance for UK legal teams. It recommends evaluating missed issues, overrides and review quality rather than relying only on speed, and says its AI performs best in English and Swedish. These are useful limits and principles for customers designing a pilot. The public material does not identify an accountable AI governance owner, publish a model release evaluation, or report bias and performance differences across languages, contract types or populations. General ISO security controls and a list of security policies concern operational protection; they do not describe a separate AI testing and governance program.
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.
The privacy policy separates user data, customer agreements and AI inputs, and names the purposes for processing them. Users' personal data are deleted when their account or the customer contract ends, with limited identity history retained and backups kept for five years. Customers direct deletion of third party personal data in agreements. At termination, extraction is through REST APIs returning base64 content, so the customer needs its own conversion and storage capability. Published safeguards include encryption, role permissions, annual external penetration testing and an incident response team. A deadline for notifying customers of a breach and precise AI service retention exceptions are not supplied.
Contract data is encrypted with AES 256 at rest and TLS 1.2 in transit. Customers configure permissions and retention policies; administrators can disable optional providers or AI features. Global DPA terms require breach notification without undue delay, while the North American DPA specifies 48 hours. Daily database snapshots last seven days, and system and authentication logs last 90 days. The DPA permits limited residual backups after deletion without fixing that period. Generative AI history can follow provider terms, while the product page promises removal of temporary review and import data. That leaves no single, specific retention schedule for every prompt and output.
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 August 2025 terms place responsibility for AI results on the user and disclaim accuracy, completeness and suitability. They expressly exclude netLex's liability for decisions, actions and omissions arising from use of AI functionality. Separate provisions also disclaim losses from errors in generated agreements and third party service failures. If netLex is nevertheless held liable, the stated ceiling is the amount the customer paid for the platform during the preceding twelve months. No published AI output indemnity, professional liability insurance commitment or compensation mechanism for a harmful clause is provided. A negotiated software license may contain additional provisions unavailable in these public user terms.
Ordinary global service terms include an intellectual property defense obligation, a material performance warranty and a general cap based on 12 months of fees. Those protections do not carry through unchanged to AI. The appendix supplies AI output as is, disclaims warranties and excludes all liability and indemnification undertakings for generative AI functionality, together with confidentiality obligations and agreed service levels. It also permits specified AI suspensions or termination without reimbursing fees. North American terms contain the same generative AI exclusion. A wrong clause, inaccurate summary or reliance on generated advice has no specific affirmative AI remedy in these published terms.
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.
Salesforce and HubSpot integrations map CRM properties to variables in netLex contract templates. Customer identity, commercial amounts, payment terms, dates and opportunity stage can feed the agreement; the configured stage triggers generation. Contract creation history and the information used remain visible inside the CRM. Legal teams prepare the approved templates and the customer configures the field mapping and trigger. Gupy describes using this process for commercial amendments. netLex also supplies Slack notifications, directory authentication, signature connections and a REST API, with netLex Connect supporting custom input and output flows. Its announced MCP interface still lacks a separate public release confirmation.
The Salesforce integration creates interactive contracts from opportunities and transfers contact, company and opportunity data into them. Its configurable sync sends data from Salesforce objects into Oneflow and returns contract values to Salesforce. Product tables can reflect price books or CPQ quotes, while workflows map contract stages back to pipeline stages. Engagement events and status changes appear in the Salesforce timeline, and returned contract data supports dashboards. Oneflow identifies separate setup guidance for older and newer integration versions and compatibility with Professional edition upward. HubSpot, Dynamics 365 and other CRM connections complement this workflow; Salesforce and Dynamics can require premium integration charges.
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.
netLex runs on AWS and lets customers choose storage in the United States, Europe or South America. The privacy policy identifies the United States, Ireland and Brazil as contractual locations for storage or processing. It separately permits subcontracting and sharing with providers in other countries, including the United States. A selected repository region therefore does not establish that every AI request stays there. Backups are geographically distributed, without a separate public map of their locations. The native AI integration is with OpenAI, but its processing geography is not tied to each customer region. No customer hosted deployment option is described.
Production infrastructure uses AWS availability zones in Ireland, with document replication and backups in Sweden. Oneflow's AI FAQ broadly describes data as remaining in the EU, and Insights Premium is described as running within Oneflow's own EU infrastructure. The published subprocessor table gives a more varied picture: optional Legly review operates in Germany, optional OpenAI extraction in the United States, and Postmark email processing also in the United States. Administrators can disable optional services. The public descriptions do not fully reconcile these routes or map every AI function to a processing region. No on premises deployment is offered in the published package descriptions.
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.
netLex states that it holds ISO 27001:2022 certification and obtains SOC 2 Type I and Type II reports through recurring audits. The reports are available by request under a nondisclosure agreement. The public security description also specifies annual external penetration testing, static code analysis, component vulnerability analysis and separation of development, test and production environments. Production data are excluded from development and testing. These are more specific assurances than an infrastructure badge alone. However, the public text does not identify the SOC auditor, report observation period or exceptions. AWS's separate certifications should not be treated as independent coverage of every netLex AI function.
A public certificate issued by Qvalify covers Oneflow AB's digital solution for contract automation under ISO 9001:2015, ISO 14001:2015 and ISO 27001:2022. It was issued on June 28, 2024 and remains valid through June 30, 2027, identifying the Stockholm organization and its registration number. A June 2026 statement of applicability lists the security controls and their implementation status. The security center separately identifies SOC 1 Type 1 and SOC 2 Type 1 reports issued by Grant Thornton, available under NDA. Those reports concern control design; neither is identified as a Type II examination of operating effectiveness over a stated period.
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.
OpenAI is identified as the provider behind netLex's native AI drafting and revision features. The privacy policy explains that the integration uses the OpenAI API, and the published supplier list also names OpenAI API and ChatGPT alongside AWS and other service providers. It does not identify a current model version for each agent or specify how those agents route tasks among models. Nor does it map OpenAI processing to the customer's selected storage region. Customers receive notice of privacy policy changes, but a distinct commitment to advance notice of model substitutions is absent. Newer agent features therefore need more detailed supply chain terms.
The subprocessor list identifies Legly AB for contract review in Germany and OpenAI for extraction in the United States, alongside AWS infrastructure in Ireland and Sweden. Both AI suppliers are optional and controlled through account settings. The AI appendix directs customers to their Data Management page for the current generative model suppliers and their terms. It does not publish model versions or a complete function to model map. DPA provisions require reasonable advance notice of subprocessor changes to the customer's designated email address and allow a 14 day objection. That process concerns suppliers, without promising notice of every underlying model 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 monthly subscription normally depends on the number of users and their access profiles. It includes implementation and automation of an agreed number of documents; additional document automation is priced according to project complexity. Native integrations, including electronic signature connections, are included, while integrations needing special configuration receive a separate project price. This explains the charging structure without publishing a per user rate, minimum contract value or an AI consumption allowance. A quote must distinguish ordinary platform access from any agent entitlement or usage charge. Public materials do not settle renewal increases, termination charges or the total cost of a large migration.
Business starts at $292 a month, billed annually, including five users; Enterprise has ten users and a custom quote. Business includes writing, extraction and summary features. Standard AI Review and Insights have conflicting public treatment: the pricing page marks paid beta additions, while September help guidance says they are included in Enterprise during beta. Insights Premium is explicitly a paid addition for Business and Enterprise. SMS, identity verification, premium integrations and enhanced support can cost more. A 14 day trial needs no card. Implementation has no published amount, and global annual renewals can increase by the greater of 5 percent or Swedish CPI.
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.
netLex serves company legal, sales, procurement, finance and operations teams through contracts, powers of attorney, legal requests and related corporate records. Named customers include Ambev, Blip and Isaac, with Gupy illustrating commercial amendments generated from a CRM. Its templates and playbooks can cover supply agreements, employment contracts, confidentiality agreements and services contracts. The interface is offered in eleven languages and service is available in Portuguese, English and Spanish. Use in more than sixty countries describes geographic adoption, not verified legal coverage in each jurisdiction. The product does not publish an exhaustive set of supported laws, exclusions or a separate law firm matter management offering.
Legal, procurement, sales, finance and HR teams can create and manage agreements in Oneflow. Legal users configure review rules and approve terms; business teams use reusable templates and CRM data for offers, sales agreements and employment documents. Named customers span telecoms, retail, recruitment and public sector purchasing. UK guidance also addresses solicitors using AI for commercial contract review, bringing professional duties into the intended audience. AI is optimized for English and Swedish, with variable results in other languages. The product does not supply a jurisdiction specific research corpus, and its coverage statements do not define supported litigation work or every category of legal agreement.
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?
netLex's privacy policy expressly says that data supplied to its AI functionality will not train the model. It identifies the OpenAI API as the integration used for drafting and reviewing clauses. This is a published policy promise, rather than a separately supplied negotiated AI agreement. The prohibition concerns AI inputs; it does not erase ordinary contract storage, user history or the five year backup period. The policy does not provide model specific audit results or an enforcement mechanism against every underlying provider.
The AI appendix forbids Oneflow from using customer data to train any AI models and overrides conflicting general terms for AI issues. Inputs and attributable outputs fall within the customer data definition. The general service license permits improvement and anonymized analysis, and AI feedback may improve accuracy, but those clauses do not remove the express training ban. The product FAQ also says underlying models do not train on customer data.
Separate provider processing, retained history and the generative AI confidentiality exclusion remain relevant to handling client material.
Prompt and Output Retention
How long does the product keep what a lawyer typed, and can that be set to zero?
The AI product description says drafting and review data will not be stored, while the general privacy policy retains platform records under a separate schedule. User deletion or contract termination removes user personal data, subject to limited name and email history; backups persist for five years. Customers can request removal of third party personal data from agreements. These provisions distinguish transient AI processing from saved contract content, but do not enumerate provider abuse monitoring exceptions or a separate schedule for agent conversation histories.
Oneflow permits customers to set retention policies for stored contracts, and its AI page says temporary import, review and Insights data is removed after use. Generative AI has a different contractual provision: input questions and output responses may remain as history under the model supplier's current terms. No uniform period covers that history or every provider copy. Daily database snapshots last seven days, system logs last 90 days, and residual backups after termination have no precise DPA deadline. Contract deletion therefore cannot be treated as an immediate purge of all AI processing records.
Ethical Walls and Matter Segregation
Does retrieval respect the firm’s ethical walls, or can the model read across them?
netLex describes AI permissions tied to the current user's profile and says agents cannot access data beyond what that person can see. It also describes a separate customer environment, with role permissions and corporate authentication supporting access control. This is a product permission model for corporate contracts, rather than inheritance of a law firm's document management system permissions. The materials do not describe adverse party conflicts, lateral hire screening or an administratively tested ethical wall between separate legal client matters.
Workspace roles control access to contracts, and Oneflow provides distinct permissions for AI Review and the Insights dashboard. Administrators enable review for selected workspaces and can disable AI features or optional suppliers. These controls can support departmental separation and limit who sees review results. The descriptions do not specify how retrieval enforces every contract permission within a workspace, how restrictions propagate to generated summaries, or how a law firm's matter wall follows an AI request. Permission controls alone do not establish a complete ethical wall mechanism for confidential client 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 privacy policy permits disclosure in situations required by law or judicial decisions. It does not promise advance customer notification of a subpoena, an opportunity to contest the demand or a regular transparency report. A separate notification provision concerns a data subject asking netLex to delete information: the customer is notified so it can instruct the processor. That deletion procedure should not be read as notice of government access. The user terms also allow netLex to report suspected unlawful activity to authorities.
Global confidentiality terms require reasonable prior notice when disclosure is legally compelled, unless notice is prohibited, and reasonable assistance at the customer's expense in seeking protection. That gives the customer an opportunity to contest or narrow a request involving ordinary confidential service data. The AI appendix expressly removes contractual confidentiality obligations for generative AI functionality, so the same protection should not be assumed across every AI route.
No transparency report accompanies the commitment. North American and global agreements need to be matched to the contracting entity and enabled services.
Primary Law Corpus Provenance
Where does the law in this product come from, and does the vendor have the right to use it?
The AI features work with customer contracts, attachments, clause playbooks and internal policies. They are not accompanied by an identified collection of licensed case law, statutes or commentary. OpenAI is named as a model provider, but the provider name does not establish the legal sources or licenses behind any generated proposition. Questions about company policy and departures from approved contract wording can have a useful internal reference base. They do not carry a published promise of comprehensive, current legal authority for a jurisdiction.
Oneflow's review and portfolio analysis work with the customer's agreements and configured playbook concepts. Example clauses come from the organization's rule setup, and drafting can use selected text as input. No catalog of legislation, reported decisions or licensed legal commentary is supplied for these features. Naming a model provider does not identify the legal sources in its training data or their licensing terms.
The UK educational articles link professional guidance, but those links do not constitute a legal research corpus inside the product.
Good Law Verification
Does the product tell you when the authority it just cited has been overruled?
netLex's clause review compares agreements with customer standards and can suggest revised wording. No citator integration, case treatment service or automatic validation of whether a cited decision remains good law is described. Its requirement that users assess AI accuracy before adoption is a general review obligation, not a documented legal authority validation workflow. A team using generated legal opinions would still need an external research source to assess authority, subsequent treatment and relevance to the law governing the contract.
Highlighted review passages let a user inspect contract language, not whether a judicial decision remains authoritative. Oneflow has no published citator connection, treatment history service or automated check of legislation's current status. Teams maintain their own playbooks, including preferred and fallback clauses, so changing a rule after a legal development remains an organizational responsibility. The appendix warns that AI can generate incorrect law and recommends human review. A portfolio risk chart or missing clause flag does not establish that the underlying legal proposition remains valid.
Refusal and Uncertainty Behavior
What does the product do when the answer is not in the corpus?
Review Agent flags departures from a configured playbook and explains their severity, while Intake Agent is described as routing complex requests to appropriate people. Neither description specifies when a model declines to answer because support is missing, how uncertainty is communicated or what happens when contract clauses conflict with its assumptions. The terms warn that results can be inaccurate and require human assessment.
They do not supply an abstention policy, confidence calibration or examples of a refusal when legal context is insufficient.
The AI Review interface separates findings from a missing clauses view. That view identifies playbook concepts absent from the agreement, giving the reviewer an explicit negative result instead of merely omitting a match. Red and yellow labels distinguish issues from risks; they are not numerical confidence estimates. Oneflow warns that generated facts and law can be wrong, but does not publish a general abstention rule for drafting or summaries. Missing clause handling is described for review, without promising that every unsupported question will be refused.
Fabricated Citation Record
Does a public court record exist addressing fabricated or hallucinated legal citations in output from this product?
The Charlotin collection contained 2,191 cases at this review, with no whole word match for netLex in either the tool field or the full case material. That result is limited to reported incidents included in the collection and does not measure the product's error rate. netLex primarily supports company agreements and internal legal requests, and its terms explicitly acknowledge that AI results may be inaccurate. A lack of a named reported incident does not make a generated legal citation reliable.
Damien Charlotin's AI Hallucination Cases database contained no entry naming Oneflow as of October 16, 2026. The result covers the database's reported court incidents, not every private use of the product or every inaccurate contract response. Oneflow itself discusses court examples involving generic AI tools in educational material; those examples do not identify Oneflow as the tool involved. Contract drafting and risk analysis can still produce incorrect law, which the AI appendix expressly warns about. The absence of a named incident provides no accuracy guarantee.
Bar Guidance Alignment
Has the vendor engaged in public with the ethics opinions its buyers are bound by?
The terms require users to evaluate AI output and preserve necessary human legal analysis. netLex also discusses privacy, access permissions and final approval by a legal team. It does not map these arrangements to a named bar association opinion, professional conduct rule or jurisdiction specific guidance on legal AI. Compliance with the LGPD and GDPR concerns data protection and does not establish professional responsibility alignment.
Lawyers remain responsible for applying the conduct rules that govern their practice and the particular use of generated work.
Oneflow's UK contract review guidance maps SRA standards and conduct duties to human supervision, confidentiality, client transparency and practical controls. It also discusses insurance, data protection and the legal team's responsibility for final judgment. This is a jurisdiction specific mapping with suggested review steps, rather than a generic statement that lawyers remain responsible. It is vendor guidance, not regulator approval or an independent finding of compliance. The mapping does not establish equivalent coverage for every jurisdiction in which Oneflow sells its platform.
Billing and Fee Posture
Does the vendor address what happens to the bill when the work takes an hour instead of six?
netLex is sold for a company's own contracting and internal legal operations. The published savings concern productivity, amendment cycle time and business process costs, with subscription charges generally tied to users and their access profiles. Those claims do not describe lawyers charging external clients for time saved by AI. No legal fee allocation, client technology surcharge or invoice narrative is offered. Gupy's measured legal response time is an operational service level within a business, rather than a disclosure of billable legal time.
The vendor's UK AI review material addresses solicitors as well as internal legal departments and promotes faster review with retained professional judgment. Its product pages also describe reducing routine contract work and administrative effort. No accompanying procedure explains how a firm records AI time, adjusts a client invoice, discloses savings or passes through Oneflow charges. Subscription pricing is the buyer's software cost rather than a client billing policy.
Because the audience includes lawyers serving clients, the time savings claims cannot be treated solely as an organization's internal operating expense.
Outside Counsel Guideline Readiness
Can a firm get this vendor through a client’s AI clause without a bespoke negotiation?
A published supplier list identifies AWS, OpenAI, Microsoft, Google, Zendesk, signature services and other providers. The privacy policy explains AI input treatment, international transfers, deletion and the five year backup exception. Security reports can be requested under a nondisclosure agreement. These materials give a corporate team information to supply when a client asks about its technology, but do not constitute a named outside counsel approval workflow. The supplier list does not assign locations or detailed processing functions to every listed company.
Oneflow supplies a public DPA, global and North American service terms, an AI appendix and a subprocessor table with functions and processing locations. Optional AI suppliers include Legly and OpenAI, and administrators can control optional services. A public ISO certificate and statement of applicability support security diligence; SOC reports require an NDA. These materials help counsel explain data handling to a client.
They do not form a dedicated client AI disclosure package, and the generative AI confidentiality exclusion and conflicting regional descriptions require specific attention in any outside counsel approval process.
Court Disclosure Support
If a judge’s standing order requires an AI disclosure, can the product produce one?
netLex describes version history, approval tracking and AI interaction logs that distinguish automated actions from human decisions. Its privacy policy provides a REST API route for exporting stored agreements and data when a customer contract ends. The public description does not specify an export joining each prompt, model version, response and lawyer review into a court disclosure record. Contract negotiation history can support internal reconstruction of a drafting decision, but it is not a published filing certificate or a complete account of AI assistance for a court.
AI Insights supports an export of portfolio analysis, and reviewers can inspect the contract passages associated with a playbook finding. Insights Premium adds an action report for internal discussion and negotiation. Enterprise also includes an account audit log, while signing workflows maintain transaction records. The published export instructions do not establish a complete record of model identity, prompt, output and human edits for each AI action.
These are useful contract administration records, but no court disclosure template or complete model provenance export is described for a later filing.
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.
- Primary Law Corpus Provenance
- Good Law Verification
Which one fits
Choose netLex if
- Portuguese service and Brazilian legal operations are central to adoption.
- Contracts and internal legal requests should share an operating platform.
- Salesforce or HubSpot fields need explicit mappings to approved templates.
Choose Oneflow if
- The contract should remain editable as a shared web agreement.
- Reviewers need highlighted findings and a missing clauses view.
- A public Business starting price helps plan the first five users.
In summary
netLex
netLex supports contracts, powers of attorney and internal legal requests, with AI clause revision and playbook review. Salesforce or HubSpot data can populate template variables and drive approval workflows.
Oneflow
Oneflow supports collaborative web agreements with Salesforce quote items and stage synchronization. AI Review connects configured findings to highlighted language, and Insights presents portfolio risks in charts.
Questions buyers ask
How do the CRM creation workflows compare?
netLex describes mapping CRM fields to variables in contract templates and using stages to trigger work. Oneflow describes data from Salesforce objects and CPQ quotes flowing into interactive contracts and returning updated values and stages. From the AI Legal Index, based on each vendor's own published materials as of October 16, 2026. No vendor pays for placement.
Does netLex's AI nonretention promise remove old platform backups?
No. Its AI processing promise is separate from the privacy policy's five year backup retention. Contract records and transient model processing must be treated as different data stores. From the AI Legal Index, based on each vendor's own published materials as of October 16, 2026. No vendor pays for placement.
Are all announced netLex agents already available?
Its published agent material separates existing capabilities from previews and future releases. That distinction is important when comparing current review and extraction with Oneflow's beta features. From the AI Legal Index, based on each vendor's own published materials as of October 16, 2026. No vendor pays for placement.
Which retention issue most distinguishes the two offers?
For an organization requiring short deletion periods, AI Legal Index highlights netLex's explicit five year backup exception. Oneflow instead leaves parts of generative history and residual backup duration unspecified, despite its contractual training ban.
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.
netLex's future agent announcements and Oneflow's live beta features are not treated as equivalent release states.