EN
Idioma · Language · Lingua
Your data, where your case requires.
A ladder of control.
Each rung trades capability and cost for control. The four levels are architecture alternatives subject to technical and contractual evaluation in each case.
- Level 1 · AI provider's cloud
- Data goes out to third-party interfaces (models, voice). Maximum capability and minimum cost; suitable only for non-sensitive data.
- Level 2 · Dedicated cloud with residency
- Isolated infrastructure in the region or country the client requires, with models through private endpoints. Data does not leave the region.
- Level 3 · Client's private cloud
- Everything inside the client's perimeter, with open models. Nothing goes out to third parties.
- Level 4 · 100% on premises
- Full on-site processing, only with open models and tools. Viable when the technology allows it, the cost supports it and someone operates it.
Universal availability of any level is not claimed.
Five questions to choose the rung.
We answer them together in process consulting. They are used to choose the level and design the solution.
-
Question
In which jurisdiction must the data reside?
The country or region where regulation or the contract requires it to live.
-
Question
Which data classes cannot leave which perimeter?
For example, health data, payment data or identity data.
-
Question
How long is it retained?
Retention periods by data type and by process.
-
Question
Who audits?
Which department or third party reviews access, decisions and records.
-
Question
How is the right to erasure exercised?
Who requests it, who carries it out and what evidence remains.
The resulting design is validated in a technical and contractual evaluation before it is implemented.
When level 4 makes sense.
The 100% on-premises deployment is offered when the case requires it and it is viable, and it has its own billing scheme.
-
Condition
The technology allows it
Only with open models and tools that reach the quality the task requires.
-
Condition
The cost supports it
License, implementation, support and hardware, which is billed separately or provided by the client.
See the billing scheme → -
Condition
Someone operates it
Controlled versions that are installed and validated at your site, with defined roles.
The same rules for your data.
Minimization, encryption, configurable retention and deletion, separation per client and data that doesn't train models for anyone else: at any level. The details are under Security.
-
AI strategy
The why comes first
The belief, the six hows with their proof, what we sell and how to start with a first flow.
See the strategy → -
Security
Bounded, traceable mandate
«Actions» with limits no one expands, conversation locks, data isolated per client and change control.
See security → -
Regulation and compliance
Built for those who are held accountable
The standards we follow from the design stage, those of each industry and the decisions that always belong to your institution.
See the standards →
Where should your data live?
Tell us what your regulator and your operations require.
Let's talk about your operations →or write to us at hola@abbiamo.ai