WHY OMNIMEM

The boring details, which are the ones that matter when the data is sensitive

Most of what separates one AI supplier from another is not visible in a demo. It shows up later, in a data processing agreement, in an audit, or on the day somebody has to explain to a regulator where a number came from.

This page is written for whoever has to sign, and for the colleague who will be asked whether this is safe.

Everything below is a commitment rather than a capability. If it is on this page, it goes in the agreement, and you are entitled to hold us to it. Where something depends on how the work is set up, the page says so instead of rounding up.

Nothing here requires you to take our word for the technology. It requires you to check the paperwork, which is the point.

TRUST THE ANSWER

Every answer carries the source behind it

A citation on the bottom of a paragraph is a gesture. What makes an answer defensible is that each individual statement in it can be taken back to the exact text it rests on, and that the chain survives being turned into a summary, a letter or a comparison table.

Citations sit on statements, not on responses. Each one links to the document and the passage that supports it, so a reader who doubts the third sentence does not have to re-read the first two.

Provenance survives the whole journey. You can see which collection, which document and which version of it answered, from the first retrieval through to a table cell in a report months later.

It declines rather than improvises. Where the material does not cover a question, the answer says so. This can be set as a hard rule, and in the work where being wrong is expensive it always is.

The record is complete enough to audit. Conversations are logged with what was retrieved and what answered, turn by turn, so a decision made a year ago can still be reconstructed.

WHY OMNIMEM

Where your data sits, and where it does not go

Data residency here is a deployment choice, not a tier you have to buy up to. The three shapes below are the same system with the boundary drawn in a different place, and which one you need is usually decided by your legal team rather than by us.

European data residency
Hosted in Europe, in a region named in the agreement rather than described as a policy. Where you run it yourself, the question does not arise.
Your content is never used to train a model
Not by us, and not by anyone we work with. This is a contractual term, not a setting somebody could change later without telling you.
One tenant, not a shared pool
Your material and everything derived from it are isolated from every other customer. Nothing you load contributes to anybody else’s answers.
A data processing agreement you can hand to your DPO
Standard terms, GDPR aligned, with sub-processors listed. We would rather your data protection officer reads it early than finds it at the end of a procurement.
You can leave, and take everything with you
The material, the metadata and everything built from it are exportable in a non-proprietary format, with help migrating. An exit that works is part of the agreement rather than a favour at the end of one.

DOMAIN FIT

Tuned to your language, not the open web

A general assistant reads a clinical guideline the way it reads a blog post. Specialist material is not written that way. It carries defined terms, local abbreviations, tables that mean nothing without their footnotes, and conventions that a reader in the field absorbs over years.

Getting that right is most of the work on any engagement, and it is the part that does not transfer from one customer to the next.

Your vocabulary, including the parts that are only yours. Internal names, abbreviations and the terms your field uses differently from everyone else.
What is in scope is your decision, written down. The collection is defined deliberately at the start, and changing it is a decision somebody makes rather than something that drifts.
Measured against questions your own experts wrote. Not a public benchmark. Real questions from the people who will use it, with the answers they consider correct.
Adjusted while you use it. What it gets wrong in the first weeks is the most useful information available, and acting on it is part of the engagement rather than a change request.

WORKFLOW FIT

It goes where the work already happens

A system people have to remember to open is a system people stop opening. Four ways in, and most engagements use more than one.

The web app

Your branding, your single sign-on, your existing groups and permissions. Nobody has another password to keep.

Embedded

Inside the intranet, portal or record system people are already in, so the answer arrives where the question came up.

An API

Plain HTTP, so your own developers can build whatever the situation actually needs without waiting for us.

A sealed device

Where there is no connection to build on at all. This is FORTIAID, and it is the same commitments in a case.

PEOPLE

Built with you, and still here afterwards

We are a small team that works on a small number of engagements. That is a real limit on how many we can take, and it is also why the person who built your system is the person who answers when something is wrong with it.

The material keeps moving after go-live. Guidelines are revised, statistics are restated, regulations change. Ingestion, evaluation and adjustment continue as part of the engagement, because a knowledge base that is not maintained quietly becomes a confident source of last year’s answers.

Where the stakes require a person, we say so at the start rather than discovering it later. A named analyst accepting a model parameter, a clinician approving a patient letter, a defined set of cases routed to human judgement. Where that boundary sits is agreed in writing before anything is built.

FIVE QUESTIONS

What to ask any supplier, including us

These are the questions that separate suppliers quickly. Ask them of us and of whoever else is in the process.

Show me one answer, and take me from a single sentence in it back to the exact text it came from.
What happens when the material does not cover the question? Show me that, not a demo of a question it handles well.
Where does our content sit, who else’s data sits beside it, and is that a contract term or a configuration?
If we leave in two years, what do we walk out with, in what format, and who does the work?
Who maintains this once the guidelines change, and is that in the price or a separate conversation?

Bring the difficult question

The useful demo is not the one we prepared. Bring a question your own people argue about, and material you already have, and we will show you what it does with it, including where it stops.

Book a demo

What we do