Is Legora Just a Wrapper? What It's Actually Built On

Is Legora just a wrapper? The short answer: it started as one, it's spending heavily to stop being one, and the label now obscures more than it reveals. The longer answer is worth five minutes, because it explains how most of the legal AI market actually works.

First, the jargon, because it does nobody any favours. A “wrapper” is a product that doesn't build its own artificial intelligence. It takes an underlying model built by someone else, Claude from Anthropic or the GPT models from OpenAI, and wraps a product around it: an interface lawyers recognise, security controls, document handling, legal workflows.

Legora began exactly that way. It launched in Stockholm in 2023 as Leya, and the early product was a secure legal layer over OpenAI's GPT-3.5: a way for lawyers to use a large language model without pasting client documents into a public chatbot. That was the pitch, and it was a wrapper in the plainest sense of the word.

So what is Legora's underlying model today? There isn't one; there are several. The product is deliberately model-agnostic, routing work across Claude, GPT and other frontier models depending on the task, with Anthropic's Claude doing much of the heavy lifting on the agentic work: the multi-step tasks where the system opens documents, follows a sequence and finishes a job rather than answering a single prompt. If your search was “is Legora built on Claude”, the accurate answer is: substantially, but not exclusively, and by design.

The product layer on top is where the last two years have gone: tabular review that reads hundreds of documents into a structured grid, drafting inside Microsoft Word, integrations with document management systems like iManage, and workflows tuned to how legal teams actually pass work around.

None of that settles the wrapper question, because the model makers can build all of it too. This is the precarious position I described in AI won't differentiate your law firm: AI is sold by the unit, the model makers own the units, and they can sell them cheaply enough to make a reseller's economics impossible. Harvey, Legora's biggest rival, now runs substantially inside Claude itself. A product that only rents and resells someone else's intelligence has no floor beneath it.

Legora has read that danger more clearly than most, and its answer has been to buy things the model makers can't simply replicate. Its acquisition of Qura, a Stockholm company that spent years building AI-native legal research databases, gives it structured legal sources a model can reason over rather than a search index bolted on the side. It has picked up the Canadian research startup Walter for similar reasons. Proprietary legal data, wired into the product, is the classic escape route from wrapper status. Whether Legora has taken it in time is the open question.

So, is Legora a wrapper? By origin, yes. By trajectory, it's becoming something harder to dislodge: a legal layer that sits across several models rather than on top of one, with research assets of its own underneath. If you're assessing it as an investment or a competitor, the wrapper label tells you where the supplier risk lives, and Qura is the hedge against exactly that risk.

If you're a law firm deciding whether to buy it, though, I'd steer you to a different question altogether. Whatever Legora is built on, every firm that licenses it gets the same thing, and a shared tool cannot be an edge. At best it's the cost of staying level. I've written a practical guide to how UK firms should evaluate legal AI that starts from that premise.

The wrapper debate is good sport for legal tech commentary. Inside a firm, three sharper questions do more work: what does the tool do that the raw model doesn't, what does it cost against using Claude or ChatGPT directly, and what will you build around it that your competitors won't? Legora will answer the first two in a demo. Only you can answer the third.