Who is behind Facticy

Why it exists

Business documents carry numbers that almost nobody checks. Not out of carelessness — checking one deck properly costs an analyst a day, so it is not done, and a figure that entered a slide as an estimate leaves it as a fact.

Facticy does the mechanical part of that day: find the claims, find the sources, judge each claim against the evidence, and show the working. The judgement stays with the reader; what changes is that the evidence is on the table when they make it.

Cristóbal

Founder. Builds and runs the product.

How it is built

• Verdicts come from sources, not from a model's memory. Every checked claim links to what was retrieved, so a verdict you disagree with can be inspected rather than argued with.
• Deterministic checks run before any model is asked. Arithmetic that does not add up, a total that is not the sum of its parts, a chart contradicting its own caption — those are found without an LLM and cost nothing.
• Disagreement between models is shown, not averaged away. When the panel does not converge, the claim is marked disputed and each model's reasoning is on screen.
• What we cannot do is written down. The methodology page has a limitations section, and it is not fine print — a fact-checker presenting itself as infallible is exactly the kind of claim this product exists to flag.

Where it runs

Built in Abu Dhabi, UAE. Hosted in the EU, with compute in Germany; documents are encrypted at rest and no model in the roster is permitted to train on your data. Data residency is configurable for enterprise customers.

Where a product is built and where its data lives are different questions, and this page keeps them apart on purpose.