Compare

Luminance puts a model in charge of applying your standards. Lexnus puts a rule in charge, and records which one decided.

Luminance reads contracts against your standards, marks up non-standard clauses to your preferred positions, and can negotiate routine paper on its own. Lexnus uses a model to read, then hands the decision to a rule in a policy you have published.

The difference in one line

Luminance: Model-ledAn AI layer across the contract's life: analyse, mark up non-standard clauses to your preferred positions, and negotiate routine paper end to end.
vs
Lexnus: Policy-firstStarts from the standard: your published playbook holds the rules, returns a verdict on each of them, and reaches Slack and AI agents over MCP as well as the application.

Why the starting point decides everything

Reading contracts at scale is a hard problem, and AI is genuinely good at it. Extracting the cap, finding the missing indemnity, spotting the clause that does not look like the others: that is real work being done well.

Luminance goes further than reading. Auto Mark-Up redrafts non-standard clauses to your preferred positions in a click, and Autopilot negotiates routine contracts without a reviewer in the loop.

The difference is how the standard is applied. Luminance uses AI to analyse contract language against configured standards. Lexnus uses AI to read the contract, then evaluates the extracted values against versioned, deterministic policy rules.

Lexnus moves that knowledge into the product. Your standard is a published, versioned playbook: aggregate liability must not exceed 1.5x annual contract value. The AI still reads the contract and extracts the value. That part is the same hard problem. What is different is what happens next. The rule evaluates the value. The answer is the verdict the rule defines, not the model’s opinion.

That is what lets the decision travel. You cannot hand a risk report to someone in sales and expect a good decision. You can hand them a verdict, because the judgement already happened when a lawyer published the rule.

Side by side

 AI contract automationLexnus
Where the product startsThe modelThe published policy
What comes backAnalysis, risk flags, automatic mark-up to your positions, and negotiated outcomesA verdict on every rule in the playbook
Where your standard livesConfigured standards and playbooksIn a versioned playbook the product serves out, rule by rule
What decides the outcomeThe model, applying your positionsA rule comparing an extracted value
What the model is allowed to doRead, mark up, and negotiateRead and extract, nothing more
What the audit trail provesWhat the analysis foundWhich policy version judged it, and what it said

This page describes an architectural difference, not a feature scorecard, and it was checked against Luminance's own published documentation in September 2026. Products change; for what any vendor ships today, read their documentation rather than ours.

When Luminance is the right answer

Your problem is comprehension at volume: due diligence across a large back catalogue, or open questions about contracts you did not write. Or you want a model to negotiate your routine paper, and you are comfortable with it deciding.

We would rather tell you that than sell you the wrong layer. Every CLM started with the document. Lexnus started with the policy. If the policy is not what is failing you, this is not the product to buy.

Questions

Is Lexnus not also an analysis tool?

It analyses, but that is the input rather than the output. The analysis extracts the Smart Fields your rules reference; the playbook then evaluates them and returns a verdict. The distinction is whether the product ends with a finding or with a decision.

Where does the AI stop and the policy start?

The model reads and extracts. The playbook judges. That boundary is deliberate: a probabilistic reader is the right tool for messy contract language, and the wrong tool for deciding whether your company accepts a term.

It also means the model layer is replaceable without your compliance changing. The encoded policy is the asset.

Can we use both?

Yes. Reading contracts at volume and holding a policy line on new paper are different jobs. Lexnus governs what leaves, and records the rule that let it leave; a review tool tells you what your contracts say.

See it on your own contract

Upload one contract you have already signed. Lexnus drafts a playbook from it, and you can watch your own standard get enforced. Free trial, no card.