The principles
Five principles we build by
Residency by architecture
Storage, processing, and AI inference are placed in your country at design time. A system that cannot leak data abroad is safer than a policy that says it should not.
No hidden dependencies
We document every external service a system touches. If a component would send data outside the country, it is replaced or removed before delivery.
The owner decides
Data moves only when the organization that owns it makes an explicit, recorded decision, and only where the data protection law in force in your country allows.
Auditable foundations
Our AI runs on open-weight models that clients and regulators can inspect. Our proprietary products sit on top, and you know exactly where the line is.
You can leave
Documentation, training, and agreed source access mean that you are never dependent on us either. Sovereignty that ends at your vendor is not sovereignty.
Deployment options
Where your systems can run
| Option | Where it runs | Best for |
|---|---|---|
| On-premises | Servers inside your own facility | Health data, financial records, and other data that must stay on-site |
| Hosted | Data centers of a hosting provider you choose, in your country if residency requires it | Personal data and business systems that need residency without on-site hardware |
| Hybrid | Sensitive workloads on-site, the rest with your hosting provider | Organizations with mixed data sensitivity |
Local AI in practice
Modern AI, inside your perimeter
- Models
- Open-weight language, vision, and speech models, selected and tuned for your domain and for content in Arabic, French, and English.
- Inference
- Runs on hardware that you or your hosting provider controls. No prompt, document, or record is sent to an outside AI service.
- Private RAG
- Your documents are indexed and queried inside your perimeter. The knowledge base is yours; the model only reads it under your access rules.
- Sizing
- We help you choose hardware that fits the workload, from a single server to a cluster, and we tell you what each option costs and delivers.
What we ask of clients
Sovereignty is shared work
We will need a clear owner for data decisions on your side, access to the environment where the system will live, and honesty about which data is sensitive.
In return, you get a system whose every data flow is on a diagram you can hand to a regulator.
Architecture review
See where every byte lives
Tell us about the system you run or plan to build, and we will map where its data is stored, processed, and sent.
Request an architecture review