Secure systems governments run on.

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.

Deployment registerSelected systems in production, by country.
CountryClientSystemStatus
Saudi ArabiaTahakomPhone and seat‑belt violation detectionIn production, nationwide
PalestineLand and Tax Department, PalestineDigital transformation of the Land and Tax DepartmentDelivered and handed over
United Arab EmiratesGlobal & PartnersFreovia freight operations platformLive — freovia.tech
Saudi ArabiaTafawaqTafawaqLive — web, iOS, Android
8
years building software
40
engineers, designers and delivery staff
3
countries with production systems
8
systems in production today
4.6★
App Store rating, Percentage for Qudrat

Selected work

Government systems, enterprise platforms and consumer products in production.

United Arab EmiratesLogistics / freight forwarding2026

Freovia freight operations platform

Operations platform for a Dubai freight forwarder: sales, pricing, jobs, finance and back office in one bilingual system.

22-step
job lifecycle, every transition audited
15
sales KPIs with commission calculated from them

Read the case study

Saudi ArabiaEducation technology2024–present

Tafawaq

Preparation platform for the Saudi Qudrat and Tahsili exams, used by more than 16,000 students.

16,000+
registered students
3
platforms from one codebase of rules

Read the case study

United States / globalEducation technology2019–present

Quizplus

AI study platform used by more than 10 million students, covering 30+ fields with AI videos, quizzes, flashcards and textbook solutions.

10M+
students worldwide
30+
fields of study

Read the case study

All projects

Why public entities choose us

  1. Built for scrutiny

    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.

  2. Deployed where the data lives

    We deliver on-premise and in sovereign clouds. Nothing leaves the jurisdiction unless the contract says it can.

  3. Arabic is a first language

    Interfaces, documents and support are designed bilingually from day one, with right-to-left layout done properly rather than mirrored at the end.

  4. We hand over, fully

    Source code, infrastructure, documentation and trained staff. The Land and Tax Department runs its system without us.

What we do

Four disciplines, one team. Most engagements combine at least two.

  1. AI and computer vision

    Detection, classification and language systems that run in production, on your hardware if needed.

  2. Web platforms and digital transformation

    Case management, registries, portals and back-office systems that replace paper and spreadsheets.

  3. Mobile applications

    Native iOS and Android apps, published and maintained.

  4. Operations and support

    We keep running what we build, with response times written into the contract.

What clients say

  • “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.”

How an engagement runs

  1. Discovery

    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.

  2. Build in the open

    Working software every two weeks, on your infrastructure when required. Your stakeholders see progress rather than status reports.

  3. Verify

    Security review, load testing and user acceptance with your staff before anything is called done.

  4. Hand over and support

    Documentation, training and a support agreement with defined response times. You own the code.

Insights

What we have learned delivering for the public sector, written for the people who evaluate vendors.

  1. What data residency actually requires in a government AI project

    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.

  2. The handover checklist we sign before a system is called done

    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.

  3. Arabic-first interfaces are not mirrored English interfaces

    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.

All insights

Planning a digital transformation, an AI pilot or a citizen-facing service?

Send us the brief or the tender documents. You will hear back from an engineer, not a salesperson, within two working days.