Data cannot leave
Contracts, regulation, or plain caution rule out sending records to a third-party model.
Private models and governance
We deploy open-weight models on your servers or in a region you approve, and put access policies, audit trails, and testing around every assistant and agent.
The problem
Contracts, regulation, or plain caution rule out sending records to a third-party model.
Without records, no one can answer what an assistant read or changed.
Access is granted ad hoc, and revoked late or never.
Our approach
Open-weight models deployed on your hardware or a cloud region you choose.
Who may connect which assistant, and what each may read or change.
A record of every action an assistant or agent took, kept as long as you need.
Agents are tested against misuse and bad inputs before they reach your staff or customers.
How Desk handles AI access
In Desk, organisations choose which assistants may connect, connections expire and can be revoked, and writes need approval unless policy says otherwise.
See DeskHow it works
We agree where data may go, who may use what, and what must be logged.
We stand up the models and connectors inside those rules.
We monitor, update models, and review access with you over time.
Privacy and control
Questions
For many document, drafting, and classification tasks, yes. We test against your own tasks before recommending one.
Yes. Sensitive work can stay on private models while other tasks use a hosted provider you approve.
Your team, us under a support agreement, or both. Everything is documented for handover.
Start a conversation
An engineer replies within 24 hours with how we would approach it.