Aracor AI vs Luminance: how they compare in 2026

Every function Aracor describes is an inference over an uploaded document set: a fully cited term comparison produced without setup or prompting, structured due diligence workflows, one click summarization of entire folders, redlining against preset or custom criteria, citation of answers back to source text at sentence level, optical character recognition over scanned material, and signature verification. No document management system, data room or workflow product is sold underneath on its own; the deal environment exists to hold the documents the models read and the findings they produce. Article 4.5 of the agreement records that outputs are generated by third party large language models enhanced by Aracor's own Legal AI Engine.

Luminance uses models throughout contract interpretation, negotiation and portfolio analysis. Luna Crescent specializes in extraction, classification and other repetitive legal tasks, while additional models handle work that benefits from broader generative capabilities. A routing layer selects the model for each task, and separate validation models test important answers. The repository connects agreements and amendments into context for later questions, and negotiation uses prior concessions and approved positions to generate markups. Workflows turn those findings into contract actions across legal and business teams. The October 2026 release added External Sources, which brings cited research from legal sources, the open web and LexisNexis Protégé into answers, and a Template Agent, with New Lumi taking actions across connected workflows in beta. The central service depends on model generated understanding of contractual language and relationships, rather than a template library alone.

Outputs link to the exact source language and reasoning, answers carry citations at sentence level drawn from the material, and term comparisons are fully cited, so a reader can open the source and check. Article 4.4 of the agreement warns that outputs may contain material inaccuracies even where they look accurate because of their detail, and that the customer should not rely on any output without confirming it independently. Article 9.4 records that the models are probabilistic. No accuracy figure, evaluation, test set, error rate or benchmark appears anywhere, so the traceability design is documented but not measured.

Luna Crescent is tested against ContractIQ Bench, with 189,000 manually annotated data points covering provisions such as liability caps, termination rights and confidentiality. Testing includes unseen concepts and blind review by legal specialists. Luminance claims 5 percent higher accuracy in blind legal expert tests, without naming what that is measured against, and says Luna is four times faster than general purpose frontier models on contract intelligence tasks. Its test harness measures precision and recall, with no absolute result given. Separate validation checks important outputs against model agreement, source evidence and task requirements. A failed check can lead to a retry and a visible request for human review. The model is also trained to identify missing information rather than fill the gap. Public sample tasks, a reproducible evaluation set and detailed error rates are not available.

Article 9.3 requires that the customer will not rely on any output without seeking the advice of, or vetting the output through, a duly licensed and qualified lawyer in the applicable subject matter and jurisdiction, and article 9.4 adds that output should be evaluated for accuracy as appropriate to the use case, including by ensuring qualified lawyer review. That places a supervising lawyer between the model and the decision, and every output is tied to source language a reviewer can open. Nothing states what runs unattended, and the marketing sells a fully cited comparison in minutes with no setup and no prompting, which describes autonomous processing of an entire document set. No confidence signal, escalation path or route for handling errors is described, and nothing addresses what happens when a cited finding is wrong.

Business users can generate and progress routine agreements under legal approved templates and role permissions, with nonstandard terms routed to legal. Proposed negotiation language appears in Word. For important AI outputs, a separate model or panel checks agreement, supporting evidence and task requirements. Every required critic check must pass. A failed check prompts another attempt using the feedback, followed by a review flag if the problem persists, which sends a doubtful answer back to a person. Customer decisions and workflow actions retain an audit trail. The AI terms require automatic event logs kept for the life of the agreement, interfaces that support human oversight, and corrective action by Luminance when the system does not conform. The agreement requires manual interpretation of all results. An NDA Negotiation Agent that moves routine negotiations forward automatically is announced and not yet live.

Two testimonials give a full name, role and organization: Nader A. Mettawa, General Counsel at Dabico Group, and Richard F. Christesen, Senior Commercial and Corporate Counsel at Constructor Group. Christesen's account links to a case study titled with a claim of 85 percent of review time saved. Another customer story reports review time on large document sets cut by at least 40 percent. A logo strip names eight organizations, including Dabico Airport Solutions, Virtuozzo, Chainstack, Constructor Capital and Dutchess Management. Nothing is dated and neither percentage has a method. Fuel Venture Capital appears in the customer logo strip and is also the company's lead investor, which is not stated. The first quote in the user stories carousel is from Kevin J. Sullivan, Senior Advisor at Aracor, the vendor's own adviser shown alongside customers.

Current customer examples tie specific organizations to contracting work. AMD reports finding precedent language in under two minutes, Emma Sleep reports twice as many contracts reviewed per quarter, and Avianca claims 90 percent less document review time. Repository examples include Yokogawa's 99 percent faster response to business questions and IDEXX finding sanctions ties in 20 minutes. Trench Group ran a tariff analysis in two hours, compared with two weeks and about €11,000. Workflow examples include ProSapient cutting its process from eight steps to three, Fluence reporting 50 percent fewer contract turns and Hitachi moving from NDA generation to signature in under five minutes. The homepage claims more than 1.3 million questions answered and 75 percent less repetitive review work, and adds Staples, Imerys and Cryptomathic to the customer logos. These are vendor presented customer results, without a common study protocol or dated measurement period. The current customer base exceeds 1,000 enterprises.

Zero data retention is the default: documents are processed only during a session and never stored or reused, in isolated environments with isolation for every session. Data is encrypted with TLS 1.2 or higher in transit and AES 256 at rest, with optional customer managed keys, role based access control, multifactor authentication and audit logging. Downstream model providers must support zero data retention, and article 4.6 commits that neither third party models nor Aracor's own engine will train on customer content without explicit consent. Article VI makes customer content the customer's proprietary information, and the deployment options let a customer keep processing entirely in its own environment. No privilege or work product treatment appears, although privilege often attaches to transaction documents. Article 6.2 also allows use of proprietary information as needed to provide, improve and enhance the services, and the confidentiality duty ends five years after disclosure.

Each customer has an isolated environment with separate workloads, data and layered access controls. The agreement treats private learning and outputs as customer property and confidential information, and limits support access to service delivery. It also licenses customer data for product improvements, private learning and usage insights; there is no general prohibition on learning from customer content. Private learning stays with that customer, while nonidentifying usage insights can be retained for improvement. Inputs sent to external models are permitted disclosures directed by the customer. No specific clause protects attorney client privilege or work product, and the model list gives no provider retention limits.

Article 9.3 says output may concern legal services or documents but is not formal legal advice, and that Aracor's services and output are for general information only. It says the customer will not rely on output without the advice of, or review by, a licensed and qualified lawyer in the relevant subject and jurisdiction. Article 9.4 makes the customer responsible for all decisions based on output and requires review by a qualified lawyer. No bar association, rule of professional conduct or ethics opinion is named, and nothing addresses the supervision or competence duties of a firm putting a machine produced diligence finding in front of a client.

The master agreement prohibits treating the product as legal advice or a substitute for relevant independent or internal legal advice. All results require manual interpretation, and customers must tell third party users about those limits. AI Systems Terms add human oversight duties and describe the intended use as legal document analysis, research, contract analytics and legal workflows. The product also serves procurement, finance, sales and other business functions, with exceptions routed to legal. Luminance sets out no lawyer competence procedures and no boundaries for supported jurisdictions. The license permits professional services firms to use the software when serving their own clients.

No governance position is published. The security page has a section titled Continuous Security and Responsible AI Development, but everything under it is security engineering: independent penetration testing, continuous vulnerability scanning, security reviews of new features, a controlled bug bounty, threat modeling, secure coding, peer reviews, red and blue team exercises and incident response procedures. Nothing names a person or function accountable for model behavior, describes evaluation of outputs before release, sets out AI principles, or addresses uneven performance across document types, deal sizes or the non English material the platform supports. No ISO 42001 or equivalent is claimed. The published policies are the terms of service, the privacy policy and a data processing addendum.

AI Systems Terms, version 3.0 of 1 October 2026, require ongoing risk management, records of risks and tests, and data governance that considers bias, representativeness and missing data. Model selection ranks candidates on accuracy, speed, reliability and cost, in that order. Luminance says it has tested more than 30 models through a test harness measuring precision and recall, blind comparisons in Luminance Arena and five validation stages. The evaluation process also includes complete workflow testing through ALumNI, blind expert review and a human sign off before a reversible production rollout. Luna Crescent releases must clear ContractIQ Bench and expert review before replacing a current version. Luminance names no individually accountable AI governance owner and gives no results on uneven performance across matter types, parties or populations.

Zero data retention is the default design: data is processed only during a session in isolated environments and never stored, logged or reused, and downstream providers are contractually required to do the same. Article 8.3 lets the customer delete its content at any time in the product. Access controls are listed: TLS 1.2 or higher in transit, AES 256 at rest, optional customer managed encryption keys, isolation for every session, role based access control, multifactor authentication and audit logging. Testing is continuous, with independent penetration testing, ongoing vulnerability scanning, security review of each new feature and a controlled bug bounty, plus formal incident response procedures. No subprocessor register is published beyond the model providers and the two named payment processors. No hosting provider is named for the Aracor managed option, and no breach notification commitment or timeline is published.

Customers can delete data during use, with removal from active stores within 30 days and backups within a further 30 days; faster deletion can be requested. Routine backups occur every 24 hours, remain within the hosting region and are kept for 14 to 28 days under the master agreement. Access follows least privilege, with multifactor authentication, optional single sign on and isolated customer workloads. The subprocessor list of 1 October 2026 names hosting, model, support and operations services, including Intercom and ClickUp. New providers require 30 days notice and allow 15 days to object. The data agreement requires notice of a personal data breach within 24 hours, mitigation and information about the affected records and likely consequences.

Article 10.1 caps Aracor's total liability for all damages, losses and claims, in contract or tort including negligence, at one dollar, on a product sold for merger and acquisition diligence, where a missed obligation is the loss in question. Article 9.1 provides the services as is with all warranties disclaimed. Article 9.2 specifically disclaims that the services will produce accurate or relevant content or satisfactory output, and any control over the operation or availability of the AI models. Article 10.3 has the customer indemnify Aracor for its use of the services, breach and customer content, and there is no indemnity from the vendor of any kind, including for intellectual property. The only published recourse is commercial: a fourteen day refund window under article 7.4.

Version 3.1 of the master agreement, dated 6 October 2026, provides an IP indemnity for the product, with exclusions for unauthorized combinations, continued infringing use and unsupported versions. A performance warranty allows correction, replacement or a refund of unused prepaid fees. General liability is capped at the previous 12 months' fees, rising to three times that amount for specified data obligations. Confidentiality and IP ownership breaches are outside those caps, and certain legally nonexcludable losses remain protected. Claims require notice within nine months. The agreement separately disclaims losses caused by output errors or omissions and treats customer directed model transmissions as permitted disclosures. No insurance commitment is specified.

Contract review can run in Word or in the Aracor platform, so Microsoft Word is a named integration described at workflow level, and Aracor has a listing in Microsoft's marketplace. No document management system is named, so nothing addresses iManage or NetDocuments. No virtual data room is named, though a diligence product's input is a data room, and no matter management, CLM or electronic signature system appears. No API, developer documentation or field mapping is published. Article 5.1 reserves rights in technology developed for the services, including integrations, without specifying any, while article 3.1(v) bars running automated tasks against the service. Nothing published says what moves between Aracor and a customer's existing systems or what a customer must configure.

Negotiation generates context based markups directly in Microsoft Word using approved language, earlier concessions and comparable agreements. The workflow product connects contract actions, tasks and approvals across business teams and lets other assistants access contract capabilities through MCP. Lumi MCP, in beta since October 2026, brings Luminance into Slack, ChatGPT and Outlook, and External Sources, live since the same release, brings cited research from LexisNexis Protégé and the open web into answers. The platform also names DocuSign connections. Its technical terms allow uploads from document management systems and virtual data rooms. Connector specific configuration, permission inheritance and the exact fields moving in each direction are not explained. These connections bring AI contract work into existing applications while retaining the central agreement record.

Three deployment options are published and specified. The first uses cloud models managed by Aracor, with data processed in Aracor's isolated environment under zero data retention. The second routes requests through the customer's own API keys, so the customer keeps its own contract and terms with the model provider and Aracor acts only as a secure interface. The third deploys a private model for one organization, either in the customer's own environment, on premise or in its private cloud, or in a fully isolated deployment managed by Aracor, with all computation and data kept inside. No region is named for storage or processing, no cloud provider is identified for the Aracor managed options, and no residency commitment appears in the terms or on the security page, for a product sold into European transactions.

The standard hosted product runs in an isolated customer environment on AWS. Customers choose an available AWS data center through the order form, with backups in the same region and recovery objectives of 24 hours for a complete primary data center failure. Additional inference can run on AWS, Azure or Google infrastructure. Azure and Google processing follows an EU or UK hosting choice; for other hosting choices the processing sits in an international location that Luminance does not name. Direct OpenAI API processing takes place in the United States, and a second OpenAI entry, for agentic workflows using Codex, is processed in the EU. Luminance publishes neither the full list of available hosting regions nor the routing of each model task, and a storage choice alone does not fix every processing location.

Four badges appear on Aracor's home page and twice on the security page: an AICPA SOC mark, an ISO mark, a zero data retention mark and a GDPR mark. The accompanying sentence says processing happens in secure, isolated environments aligned with ISO 27001, SOC 2 and GDPR, and a later line says Aracor aligns with recognized standards. Aligned with is not certified. No certification body, certificate number, examination period, scope or report is published. A Security Whitepaper is listed in the resources, and its link leads nowhere. A trust center sits at a published subdomain, linked from the home page and twice from the security page.

ISO 27001 covers the information security management system for development, sales, support and operation, including the Cambridge technical headquarters, remote workers and cloud processing. Regular SOC 2 Type II examinations sit alongside independent penetration tests. A trust center on Vanta offers the ISO certificates and the SOC 2 report. Contractual measures, in the technical and organizational measures of 1 October 2026, include encrypted storage and transport, nightly operating system updates, daily backups, least privilege access and a dedicated data protection officer. Senior leaders review the security program quarterly, and a security advisory board supports it. Audit information and certificates are also available through the contractual review process. The assurance statements leave out the auditor names, report dates and examination periods.

Article 4.5 identifies the third party large language models as OpenAI's GPT models, Google Gemini and Anthropic Claude, with Aracor's own Legal AI Engine as the layer that enhances them, so the contract names which companies process a customer's documents. The security page lists the supported zero retention models as ChatGPT, GPT-OSS, Claude and Gemini. Hosting is described through the three deployment options, and article 4.7 records business licenses with those providers that exempt uploaded data from training. No version is given for any model, so naming stops at the product family, and no commitment to notify customers when the models or a provider change is published.

Luna Crescent is a family of proprietary legal models built from a general purpose base model that Luminance does not name, with specialist contract training. It works alongside other models selected by task through benchmarks and expert review, from more than 30 tested. The subprocessor register of 1 October 2026 identifies AWS, Microsoft Azure and Google Cloud for inference inside cloud environments, direct OpenAI API processing in the United States, and a second OpenAI entry for agentic workflows using Codex, processed in the EU. The AI terms distinguish models hosted within infrastructure from requests sent to an external model provider. New subprocessors require advance notice, but Luminance does not name the individual foundation models, their versions or the task routing. No equivalent notice commitment covers every model substitution within an existing provider.

No pricing is published at any level, including the unit of charge. There is no pricing page in the navigation or footer, and every commercial route leads to talk to sales. Nothing says whether the service is charged per user, deal, document, page or organization, and no rate, band, minimum, tier or term length is given, although the three deployment options plainly cost different amounts. The payment article covers mechanics rather than price. Fees are paid in advance and are nonrefundable, a fourteen day refund window applies to a new subscription, named third parties process payments, and purchases may also go through a distributor. Article 7.1 obliges the customer to pay the published prices in effect at the time, yet no prices are published anywhere.

Subscription allowances measure the number of files held in the product, and each version counts as a separate document. Annual uploads are subject to a fair use ceiling of twice the contracted document allowance, regardless of later deletion. Fees, payment timing and the initial term are set in the order form rather than a public rate table. Luminance Corporate is also sold through AWS Marketplace as a private offer on a 36 month term, priced by document count. Renewal ordinarily repeats the initial term unless either party gives 90 days notice. The standard increase ceiling is the annual change in the UK Consumer Prices Index, compounded, plus three percentage points, unless the order form says otherwise. Luminance gives no prices for assisted implementation or extra modules.

Three buyer segments each have their own page and stated goals. Investment funds, including private equity, venture capital, growth and family offices, buy to evaluate deals faster and spot issues early. In house legal and corporate development teams buy to keep deal terms aligned and maintain defensible records. Law firms in private equity, venture capital, mergers and acquisitions and corporate advisory practice buy to speed up reviews and keep work defensible. Coverage is transactional throughout, covering diligence, term comparison, negotiation, closing and obligations after closing, and support for documents in several languages is claimed. Nothing says which transaction types or sizes the product does not suit, no jurisdiction is named for the diligence workflows, no firm or fund size is addressed, and the supported languages are never listed.

Legal, procurement, finance, sales, executive and HR teams use negotiation, repository analysis and workflows across commercial agreements. The license also permits professional services organizations to use the product for their clients and includes terms for United States government customers. The legal suite defines Corporate, Diligence and Discovery applications, while the AI terms describe legal document analysis, research, analytics and related legal workflows. Examples span NDA creation, supplier review, liability positions, tariffs and renewal obligations. Luminance does not set out firm size segments, supported research jurisdictions, language limits or excluded practice areas. Current product positioning extends across an enterprise's contract work.