For IT teams
Start with the questions your security team will ask.
Architecture, access, change control and evidence. CLUSA runs on a machine in your building, on your network, and there is no route from it to us.
Not technical? The Products page explains CLUSA in plain words.
Your users need AI. Your data cannot go to public AI services.
Sign-in, the AI system and your files all stay on your network.
Without CLUSA
Outside
Frontier LLMs, cloud AI services
Policy says no.
It happens anyway.
Your environment
Your users need intelligence. The only source is outside, so it gets used, with or without permission.
With CLUSA
Outside
Frontier LLMs, cloud AI services
Blocked.
No longer needed.
Your environment
Models, retrieval, loggingCLUSA supplies the intelligence inside your company. No prompt and no data leaves.
Architecture and data flow
On a machine in your building, on your network. One machine per customer. No shared infrastructure and no other organisation's data on it.
Your users and your own management access, over HTTPS on your internal network. The document stores and systems you nominate. Nothing else.
Nothing. CLUSA makes no outbound connection: no telemetry, no licence check, no model download in the background.
Traffic between your users and CLUSA is encrypted with TLS.
The machine sits on your LAN like any other server, and your LAN reaches the internet. CLUSA does not use it to.
In CLUSA's own configuration. You can enforce it again at your firewall, and nothing changes.
Every function, including inference, operates with the network disconnected. Available for demonstration.
Identity and access
Security is a shared responsibility, as it is with any cloud provider.
Through the directory you already run. CLUSA does not keep a separate user directory.
Existing access rights carry through. Nobody sees a document through CLUSA that they could not open directly.
No remote access of any kind. No support tunnel and no vendor account reachable from outside your network. Our engineers work on CLUSA physically, on your site, when you ask.
The support app connects your team to ours at any time. It carries the conversation, not a route into CLUSA.
Your building and your control, on the same terms as any other server in your building.
Data
Indexed on CLUSA. The index is built there and stays there.
Stay on CLUSA. They are not sent anywhere for processing.
Your material never trains a model, ours or anyone else's.
Your data, your index and your log are yours.
Change control
Signed by us and applied on your side, under your own change process. CLUSA never fetches anything from the internet, and we never reach it.
Packaged by us for an isolated network and applied under your own change process.
Applied by CLUSA on site. Models are not changed remotely and are never downloaded by CLUSA.
A written list of the software and models installed, with versions, so your security team can review it, scan it and re-check it later.
Evidence
Which user asked what, which documents were used, and which model answered.
On CLUSA, on your side. We never see it.
Exportable as a file, for your own retention and review.
Where an answer came from your documents, CLUSA names them, so a reviewer can check it against the source.
Private development environments
If your teams also need AI for software development, ask any supplier the five questions below. CLUSA's answers follow each question.
The AI models and the control plane run on your premises. CLUSA Private AI serves the models. CLUSA Code and CLUSA Deploy run on CLUSA hardware or your own servers. CLUSA has no remote access.
CLUSA Code and CLUSA Deploy are designed to work without internet access. CLUSA Private AI runs with no outbound connection at all. For CLUSA Code and CLUSA Deploy, we confirm the offline set-up with your team during the first phase.
Through an approved internal process: signed updates delivered offline, approved package sources and model files, applied under your change process.
Code changes, releases and model changes. Your team approves every code change, release and model change through your existing code review, CI/CD and change process.
Local logs of users, models, changes and releases. Recovery tested with your team. Representative applications delivered by your first team before wider roll-out.
Send us your security questionnaire. We answer in writing.
Tell us the environment, the identity system you run and the constraint you are under.