Read anything, with any engine.
No single model reads every document well. Flux picks per document, audits what comes back, and tells you how much of it to trust.
Reading engines, vision models and layout models each handle different documents better. Flux routes each document to the engine most likely to read it correctly, and new engines register without a code change.
On the settings that call for it, several engines read the same page at once. They do not see each other's output, so agreement between them means something.
The readings are scored against each other, text that repeats is penalised, and on the top setting a model that can see the page checks the winner against the original image.
The surviving text becomes the fields you defined, with a confidence signal on each one and an empty value where nothing could be read.
WHAT IT HANDLES
Handwriting
Filled forms, margin notes, endorsements on the back of a cheque, read and returned as fields, not as an image.
Tables
Dense, irregular, spanning pages, with merged cells and no ruling. Rows and relationships come back intact.
Signatures
Located, cropped and verified against an enrolled signer, with the score and the coordinates behind the verdict.
Scans that arrived badly
Rotation, skew and low contrast corrected before reading, and flagged when the scan is too poor to trust.
OUR VIEW
Document processing has been rebuilt twice. Neither rebuild solved the thing that actually blocks automation.
Templates broke first
OCR could only read what someone had already mapped. Every new document type was a project, and anything that arrived off template failed silently, or returned the wrong field with no sign anything was wrong.
Then models broke it differently
Language models read anything you give them. They also invent, fluently and without warning. Flexibility arrived, and with it a system that sounds equally certain whether it read the number or made it up.
What both left behind
Teams that can process any document but cannot prove any answer, so a person checks everything anyway, and the automation was never really automation.
CONFIDENCE
Every result carries the evidence behind it, so your workflow knows what to trust, and what to send to a person.
A number you cannot audit is not a result. It is a guess with formatting.
CAPABILITIES
Each one is a call, and each one leaves a record of how it decided.
THE API
Every call has a synchronous, asynchronous and batch form. Webhooks on completion. Schema and prompt registries, so extraction logic is versioned rather than pasted.
TRUST
Built for banks and insurers, without slowing down the teams that ship.
Four deployment modes
Global cloud, local cloud, on-premises or LLM as a Service. Same architecture, your choice.
Data stays where you say
Documents, conversations and logs live in your perimeter. Nothing leaves without a rule that says it can.
ISO 27001 · 42001
Information security and AI management: audited, not self-declared.
Your models, your keys
Bring your own model and keys, or run ours behind your firewall. Swap either without touching the pipeline.
APPLICATIONS
Start with one concrete workflow.
A document flow, a conversation line, an approval process. Live in weeks.