AI over your own records.
The AI tier is a set of services inside the estate: a search index built from your own records, web search the estate runs itself, and the connection to an AI model. The keys for AI models are held on the server, never in a browser. The model itself is a provider’s, called from the server.
What it holds
| Meilisearch | the search index built from your own records |
|---|---|
| SearXNG | web search, run as a service of the estate |
| Application backend | holds the model key and makes the calls |
| Model provider | outside the estate, called only from the server |
What it promises
Search over your own records
A Meilisearch index is built from your own records, so search and assistants start from what your organisation holds, not only from the open web.
Keys stay on the server
The keys for AI models are held on the server, never in a browser. People use the assistant without ever handling a key.
Web search the estate runs
When an answer needs the web, the search goes through SearXNG, a metasearch engine the estate runs itself, with no address of its own on the internet.
Behind the same door
The assistant lives inside the apps, so it sits behind the same sign-in and the same proxy as everything else.
What people ask
Does our data leave the estate when someone asks the AI?
What a question sends to a model goes to that model’s provider, from the server. So we do not claim your data never leaves. The search index over your records runs inside the estate.
Can anyone copy the model key from the app?
No. The key is held on the server and calls to the model are made from there. The browser never receives it.
Is the search index another outside service?
No. Meilisearch runs as one of the estate’s own services, beside the apps it serves, and has no address outside the estate.