Why does this question come up?
Shipping documents contain trade secrets and often carry personal data. Sending these documents to a shared, general AI service is unacceptable for some companies. The answer is to run the model on a server that belongs to the company or is reserved for it. There are two ways to do that.
Option A: on-prem
The server sits in the company’s own room. Data does not leave the company’s own network.
- Pro: data stays physically with the company; network and access are under its control.
- Con: hardware purchase, power, cooling, backup and fault response fall to the company or to whoever sets it up.
- Fits: companies with strict internal requirements and their own IT team.
Option B: hosted, dedicated to the company
The provider hosts the server, but it is not shared with another company. The model and the data run only in the environment reserved for that company.
- Pro: no hardware or operations burden; faster to set up.
- Con: the data is not physically in the company’s room; trust in the provider and the contract is needed.
- Fits: companies that do not want to run their own server room.
What criteria to look at
- Data classification: which documents fall in which category? How much is personal data and how much trade secret?
- Legal requirement: what do contracts and GDPR or KVKK obligations say about where data sits?
- Operating capacity: who will monitor, back up and update the server?
- Load: how many documents a day? Real-time voice and translation, or batch documents?
- Flexibility: is it possible to move later from B to A or the other way?
Security principles common to both
Whichever option is chosen: companies are isolated from each other and one cannot see another’s records; every AI tool call is checked for company and role; AI does not write to pricing or customer master data. These are architectural principles that do not depend on where the server sits. For detail see the data security guide.
Common mistakes
- Ignoring the operating load of the on-prem option: backup, updates and fault response are continuous work.
- Not asking, in the hosted option, whether it is reserved for the company alone; a shared environment is something else.
- Deciding before classifying which data will be processed.
- Treating the choice as irreversible; it can change if the architecture is designed for it.