Skip to content

Glossary

What is inference?

Inference is running a trained model on an input to produce an output, whether that output is a prediction, an extracted value or generated text.

Updated 21 Aug 2026

01

Where this one gets misread

Where inference runs decides what leaves your network, and it is a separate question from where the documents are stored. A system can hold every file on your own hardware and still send the passages to an external model to get an answer.

02

Questions to ask

Ask for a worked example on your own material, and the evidence needed to reproduce it.

  • Where does inference run for each step in the chain?
  • Which providers see the passages?
  • What are the retention terms for what is sent?
  • Can it be moved elsewhere without a rebuild?
03

How Marella uses the term

We use “Inference” only where a product mechanism or an evaluation method backs it up, and we say when the behaviour depends on how a deployment is configured.

  • Backed by a product mechanism or an evaluation method
  • Deployment differences flagged

What this page does not prove

  1. B1A definition is not a claim about how the product performs.
  2. B2Vendor implementations vary.
  3. B3Test the term against a representative workflow.

Test the claim on your documents

Pick a real piece of work, agree what a good answer looks like, then go through the results together.