Skip to content

Glossary

What is a transformer?

A transformer is a neural-network architecture built around attention, and it is the design underneath most current language and multimodal models.

Updated 21 Aug 2026

01

Where this one gets misread

The architecture is rarely what decides whether a system works for you. Retrieval quality, document handling and permissions almost always matter more, and architecture talk tends to arrive when those are the weaker story.

02

Questions to ask

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

  • What does this change for your task, specifically?
  • What was measured to show that?
  • Where does the architecture constrain how you can deploy?
  • What would change if it were swapped?
03

How Marella uses the term

We use “Transformer” 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.