Architecture

How Assitio is built

From the outside, Assitio is one thing: an assistant you can ask. Inside, we think of it in three layers.

Three layers — each with its one noun

Control, reasoning and content. Three words that together describe everything Assitio does — and make it easy to talk precisely about the system.

Control

Assitio Platform

People and their data: access, roles, assistant configuration — and consent, all the way.

Reasoning

Assitio Engine

The path from question to answer: understand, retrieve, formulate — and never claim anything without evidence.

Content

Assitio Knowledge

What the system knows, made findable: your material and shared sources — strictly separated per organisation.

The interplay

How the layers talk to each other when a question becomes an answer.

Content · shelves

Assitio Knowledge

Ingest agentsVector database Hybrid search & rankingRelevance gate Customer corpora — separated per organisationShared corpora + subscriptions
evidence back — passages with sources, only above the relevance gate
retrieval call — rewritten question and chosen source categories, scoped to organisation and subscriptions

Reasoning · voice

Assitio Engine

Question understandingSource routing Assistant → sub-agentsAnswer generation & model choice Grounding gateBackground agents (conclusions)
answer, ready to display — from your material, general knowledge or the web; source-shaped claims always require evidence
context — who is asking, which assistant, which scope, which organisation

Control

Assitio Platform

Users, roles & expert relationsAssistant configuration & scope Document metadata & pseudonymisationMemory: storage, consent, deletion Feedback & conversation views

What the boundaries mean in practice

Each boundary in the map corresponds to a rule in the system. Here are the most important ones.

Organisations are kept separate

Your material is kept strictly separate from others' — the separation is enforced in all three layers, as a basic condition, not a setting.

Source-shaped claims require evidence

The grounding gate does not allow an answer to sound source-backed without being so. The source comes along, so the claim can be verified.

Only relevant evidence gets through

The relevance gate sets a floor: if sufficiently relevant material isn't found, it isn't used as support.

Memory is governed by consent

What the assistant remembers about people and departments is owned by the control layer: consent before use, deletion on request — and memory never becomes shared reference knowledge on its own.

Questions and answers

Are the three layers three systems?

No. The layers are a conceptual map — not three separate installations.

Can answers come from the internet?

Yes, if the assistant is set up for it. An answer can draw on your own material, the model's general knowledge and relevant sources on the web. Whatever the source, the same rule applies: what sounds like a source-backed claim must have evidence behind it, and the source is shown.

Who builds and runs it?

Assitio is built and developed by the team behind it. Operations are flexible: the control layer — users, access and configuration — can live with you, in your own operations, while we run the machinery behind it. And the content is a collaboration: you contribute domain knowledge, material and experts; we make it findable and build the answers on it.