They shipped an eval suite before they shipped the model. That's when I knew we hired the right team.
Webuildthe engineroom
for SaudiArabia'sAI.
Production AI, bilingual software, security hardening. No fluff, no slide-ware. You ship, we ship.
shipping in production for





signal > noise
What running in production actually looks like.
what-we-do.md
Three practices. One shared engineering bar.
pipeline
discover → model → ship → hand over.
Four stages. No theater. You always know exactly what's happening in the repo.
discover()
Read the code. Map constraints. Write honest scope.
model()
Threat-model first. Architecture doc gets signed.
ship()
Weekly demos against real users. Tight loops.
handover()
Runbooks, evals, on-call. You inherit a running system.
git log --oneline
Selected shipments.
Bilingual SME lending platform
Migrated a legacy SAMA-regulated flow. p95 −73%. Shipped in 9 weeks.
Arabic document intelligence
RAG over 2M docs/mo. On-prem, audited, human-in-the-loop.
cat ./wall-of-clients.md
What the people who've shipped with us say.
Bilingual from the first pixel. No retrofits, no awkward Arabic. Our users felt it on day one.
Small team, senior engineers, zero theatrics. We skipped three months of vendor dance and just built the thing.
They found two gaps in our threat model before we'd even signed. That set the tone for the whole engagement.
Runbooks, evals, on-call docs — we inherited a system we could actually operate without them.
They told us the cheaper path three times. I still don't know another agency that would have done that.
p95 latency cut 73% in nine weeks. We expected a slide deck, we got a shipped system.
Weekly demos against real users. No 12-month waterfall, no PowerPoint theater. Refreshing.
FAQ.md
Got any questions?
We've got answers. If you need more, just say so.
Still got questions? Talk to usDiscovery runs one week. Architecture takes 1–2 weeks. Build is usually 4–12 weeks depending on scope, with weekly demos against real users. Handover — runbooks, evals, on-call docs — takes another two weeks.
Yes — bilingual from day one. Every interface we design is RTL-native and respects Arabic typographic norms. We do not retrofit Arabic after the fact; it is part of the initial design pass.
Discovery is a fixed fee. The build phase runs milestone-based, tied to demos rather than hours. You always know the next payment and what it buys. No hidden T&M drift.
Yes. We routinely ship to SAMA-regulated and public-sector environments on-prem, with full audit trails and human-in-the-loop controls where required.
You do — completely. Full source transfer, full model weights where applicable, documentation, eval suites, and CI. No vendor lock-in, no seat licenses for the things we build for you.
The engineers. We intentionally keep teams small enough that the people writing the code are the people you meet on calls. No layers between you and the work.
Got a system that needs to actually work?
$ curl -X POST tuwaiqtech.ai/start