Phone and seat‑belt violation detection
Computer vision that flags phone use and unbuckled belts from roadside cameras, in production across Saudi Arabia since 2018.
- Nationwide
- production deployment
- 24/7
- continuous inference
AI, web platforms and mobile apps for the public sector, built to pass security review and stay inside your jurisdiction. In production for Saudi traffic enforcement since 2018 and for land and tax administration in Palestine. You own the code, the data and the infrastructure at handover.
| Country | Client | System | Status |
|---|---|---|---|
| Saudi Arabia | Tahakom | Phone and seat‑belt violation detection | In production, nationwide |
| Palestine | Land and Tax Department, Palestine | Digital transformation of the Land and Tax Department | Delivered and handed over |
| United Arab Emirates | Global & Partners | Freovia freight operations platform | Live — freovia.tech |
| Saudi Arabia | Tafawaq | Tafawaq | Live — web, iOS, Android |
Government systems, enterprise platforms and consumer products in production.
Computer vision that flags phone use and unbuckled belts from roadside cameras, in production across Saudi Arabia since 2018.
Paper land and tax records moved into a single secure system with citizen-facing services.
Operations platform for a Dubai freight forwarder: sales, pricing, jobs, finance and back office in one bilingual system.
Preparation platform for the Saudi Qudrat and Tahsili exams, used by more than 16,000 students.
AI study platform used by more than 10 million students, covering 30+ fields with AI videos, quizzes, flashcards and textbook solutions.
Auditable decisions, role-based access and complete logs are the default, not a change request. Our traffic-enforcement models attach the frame, model version and confidence to every detection.
We deliver on-premise and in sovereign clouds. Nothing leaves the jurisdiction unless the contract says it can.
Interfaces, documents and support are designed bilingually from day one, with right-to-left layout done properly rather than mirrored at the end.
Source code, infrastructure, documentation and trained staff. The Land and Tax Department runs its system without us.
Four disciplines, one team. Most engagements combine at least two.
Detection, classification and language systems that run in production, on your hardware if needed.
Case management, registries, portals and back-office systems that replace paper and spreadsheets.
Native iOS and Android apps, published and maintained.
We keep running what we build, with response times written into the contract.
“It has cut down significantly on our time spent managing cancellation requests. With the reporting functionality we can quickly identify customers that we may want to follow up with. The addition of A/B testing has been extremely helpful as well.”
Two to four weeks with your team to map processes, data and constraints. You receive a written scope, architecture and estimate you can attach to a tender.
Working software every two weeks, on your infrastructure when required. Your stakeholders see progress rather than status reports.
Security review, load testing and user acceptance with your staff before anything is called done.
Documentation, training and a support agreement with defined response times. You own the code.
What we have learned delivering for the public sector, written for the people who evaluate vendors.
Almost every proposal promises that data stays inside the country. Few describe the architecture that makes the promise true. This is the sequence we walk through before build starts, the trade-offs it forces, and the tests an evaluation committee can run before acceptance.
A government system should outlive its vendor. Here is the checklist we work through item by item, how each one is tested rather than asserted, what it costs both sides, and the cases where a strict handover is the wrong thing to demand.
Flipping a layout at the end of a project produces software citizens tolerate. Designing for Arabic from the first screen produces software they use. Here is what actually changes in the type, the data model and the test plan, and what it costs to do it properly.
Send us the brief or the tender documents. You will hear back from an engineer, not a salesperson, within two working days.