A Saudi engineering house with a bias for shipping.
We are engineers who would rather be judged on what is running than on what was presented.
Why we exist
Duloq was founded in Jeddah on a simple frustration: plenty of AI advice, very few systems in production. The market had no shortage of strategy decks and pilots that impressed a steering committee and then quietly stopped being mentioned.
We are engineers first — architects, data scientists and designers who stay on a project until it carries real load, and who would rather be judged on what is running than on what was presented.
How we are built
We are deliberately small and senior. Teams are four to eight people with an architect who stays for the whole engagement rather than appearing at kickoff and at handover. There is no layer of account management between you and the people writing the code.
Roughly half the team works in Arabic as a first language, which matters more than it sounds: the products we build are read by Arabic speakers, and a team that cannot read its own output is guessing.
Where we fit
We are not the largest integrator in the market and we are not trying to be. We take on work where the technical risk is real — where the answer is not known at the start — and we are a poor fit for pure staff augmentation or for programmes that need forty people on site by Sunday.
When a request is better served by a product you can buy, or by a larger firm, we will say so. We lose some work that way and keep the clients who come back.
0+
Systems delivered0
Years average team experience0/7
Operations coverage0%
Code ownership transferredWhat we put in writing
These four appear in every contract we sign. They are the terms we would want if we were the client.
You own everything
Source code, models, infrastructure definitions and documentation are yours from the first commit, in your repository and your cloud account. There is no runtime licence and no component that only we can maintain.
Fixed price after discovery
We will not quote a number before we understand the problem, and we will not move the number afterwards because the problem turned out to be what we should have asked about.
Data stays in the Kingdom
Residency is designed in — including backups, logs and inference calls, which is where most architectures leak. We will show you the full data path before you sign anything.
An exit plan from month one
Every support contract includes a written, current exit plan. A supplier you cannot leave has no incentive to stay good, and we would rather earn the renewal.
Built for the Kingdom’s requirements, not adapted to them
Residency is an architecture constraint here, not a deployment setting — it changes which managed services are available to you, which is expensive to reverse late.
- Personal Data Protection Law (PDPL) aligned processing and retention
- In-Kingdom data residency across storage, backup, logging and inference
- Alignment with SDAIA guidance on responsible and explainable AI
- Role-based access with quarterly reviews and full audit trails
- Vision 2030 digital transformation and localisation objectives
Tell us what you are trying to build.
Send a short note and one of our engineers — not a salesperson — will reply within one business day.