PLATFORM · FOR TECHNICAL TEAMS

How it works inside.

From a PDF to an answer with its source: what happens to each document, where each fact lives and what your team controls.

  • Every answer links to its document
  • One isolated space per client
  • Local or cloud models
01 · A DOCUMENT’S JOURNEY

From the Document Hub to a verifiable answer.

A sales quote, from upload to answering a question. Every step leaves a trace.

JOURNEY · FICTITIOUS DATA
DOCUMENT HUB Entry contract v3 · published
Catalogue · Sales quotes
oferta_OF-0412.pdf2.4 MB · 6 pages
Uploaded · awaiting validation

Each catalogue has its contract: what a document must contain to get in.

02 · ARCHITECTURE

Five parts, each with a single responsibility.

Applications never touch the data directly: they ask the knowledge engine for evidence, and every AI model call goes through a single point.

Knowledge and evidence

OntoEngine

Ingestion, ontologies, dated and sourced assertions, contradictions and evidence receipts. The only part that reads and writes knowledge.

Pick a part to see what it does.
03 · CONTROLS

What your team controls.

What exists today and what’s coming, kept apart.

  • AVAILABLEIsolated space per clientEach client gets its own database schema.
  • AVAILABLEUntouched, versioned originalsEvery version is immutable; reprocessing creates a new one.
  • AVAILABLEEntry rules per document typeVersioned contracts: only what meets them gets in.
  • AVAILABLETraceability for every answerDocument, section and chunk for every fact used.
  • AVAILABLEExportable, no lock-inWhat we build can be exported and taken with you.
  • AVAILABLECost recorded per callEvery model call is logged with its cost.
  • IN VALIDATIONPrivate modelsA local-model profile that sends no data to third parties. We validate it with you in the pilot.
  • IN VALIDATIONReview with real sourcesAnswer evaluation with the pilot’s real documentation.
  • ROADMAPPer-user and per-role permissionsWho can see what, within each space.
  • ROADMAPERP, CRM and email connectorsToday: PDF and Markdown. Spreadsheets and email are in preparation.
  • ROADMAPActions with approvalApplications that act, always with a person approving.
  • ROADMAPStable context API (MCP)So your own applications and agents use the same base.

Shall we review it with your technical team?

In 45 minutes we go through architecture, data flow and controls with your specific case.