The dabb is our neighbor in this desert. It belongs to our environment: we understand it, and it understands us. Here are some important facts about it.
The facts
01/07, Toughness
Fig. 01·Toughness
Tough enough for the harshest weather
When a dabb is cold its color darkens almost to black; when it warms up it turns pale yellow. Its ground swings just as much: to know how strong and tough the dabb is, it is enough that the soil at the door of one of its homes was recorded at 66 °C in summer!
Raise the temperature. The skin turns from almost black to pale yellow.
ColdWarm
Fig. 01
At DABB
We build your product to hold on its hardest day
Peak days, heavy traffic, unstable networks: your product is tested automatically before every release, rolled out in stages with real-user monitoring, and tuned for performance after launch.
Fig. 02·Ground
Choosing the right site
The dabb mostly prefers to build its home in coarse sand. It avoids loose, deep sand, and digs only in firm ground or ground above the flood channel, so that its home stays solid and does not collapse.
Fig. 02
At DABB
We help you choose the ground your product will live on
Before anything is built, we choose with you the technology and the platform that fit your sector, your capabilities and your situation: the game engine, the app’s language, the hosting. Every project starts with a short discovery; after it you receive a scope, a milestone plan and a budget range.
Fig. 03·Home
A unique spiral design
In a study of 199 homes, not one had a second door. The opening is about 22 cm wide; the passage runs straight, then usually turns at a right angle, then winds down in a spiral: 3 to 5.3 m in all. The home has a unique cooling system: inside, the temperature of a summer day moves only 3 °C; outside, 26.
Fig. 03
At DABB
Steady inside, whatever happens outside
We design your product’s infrastructure around your capabilities, your situation and the sector you work in, for your next three years and not for launch day alone. Its core is built from modules we have already tested: sign-in, payments, analytics, admin.
Fig. 04·Armor
The line of defense is at the back
The dabb’s tail carries 20 to 23 rings of spines. They are its first line of defense.
Fig. 04
At DABB
Security is built in, not added
Security starts in the first sprint: threat modeling, code scanning, dependency checks and least-privilege access. Every change is peer-reviewed and tested automatically before a staged release. Standard on every project, not an extra.
Fig. 05·Patience
It lives on what plants hold
Water is mostly not available, so the dabb lives almost wholly on plants and wastes hardly any of what it eats. In one study it digested 69% of the tough plant cell wall, mostly through microbes in its gut.
Fig. 05
At DABB
Systems that live on little
We design your software to live the way the dabb does: it consumes little and gives a lot. On AI work we estimate the running cost before production, keep token use and hosting costs low, and reuse our own tested modules so you do not pay to build them twice.
Fig. 06·Watch
A pause of alertness and caution
We see the dabb being careful when it wants to leave home: first only its head comes out, or its head and forelimbs, and it waits at the door for about half an hour early on a spring morning. Then it comes out into the sun beside its door.
Fig. 06
At DABB
Look first. Then move
Nothing reaches every user at once. Releases roll out in stages, with real-user monitoring. You see a working build every two weeks and a report against the plan every week. We raise a risk the day we see it.
Fig. 07·Coexistence
At home with everything around it
The dabb is a generous host. Its home shelters even troublesome creatures, especially in summer, such as ground beetles and lizards, which take refuge there from the heat. An animal that builds shelter for others and lives alongside those around it is what ecologists call an “ecosystem engineer”.
Fig. 07
At DABB
A product that gets along with everything around it
We build your product to live with its environment: it integrates with your existing systems and your partners’ systems, with contract tests and monitoring, and it is prepared for the uninvited guests: viruses, attacks and failures. After launch we stay with you for fixes, OS and store updates, and new features.
The dabb is protected by law in Saudi Arabia. We celebrate the living animal, in its own desert.
Tuwaiq: the escarpment that runs through the heart of Najd
How we work
One trail. Five stops.
Every project takes the same route, from your first message to the months after launch. At every stop you receive something you can open, read or test.
The stops
Track of a walking dabb: hand ahead of foot, the tail’s line between.
01
First message
You write to us. A senior engineer, not a salesperson, reads your message.
You receiveA reply within one business day: next steps and first questions.
02
Discovery
A 30–45 minute call on goals, constraints and what success means, under a mutual NDA if you want one.
You receiveA scoped proposal within a week: timeline, team, budget options.
03
Prototype
Before heavy engineering, the idea becomes something to try: a playable build, a clickable flow or a proof of concept.
You receiveA prototype in your hands, and a milestone plan with dates.
04
Build
Two-week sprints, each ending in a build you can open. Every change is peer-reviewed, tested and security-scanned.
You receiveA working build every two weeks; a report every week.
05
Launch and after
A staged release with real-user monitoring. Then fixes, OS and store updates, performance tuning and new features under a support plan.
You receiveA live product, yours on full payment, and a support plan.
Working commitments
01
A senior engineer leads
Every project is led by a senior engineer, from the first reply to the release.
02
A build every two weeks
Progress is something you open, not a slide. A written report against the plan follows every week.
03
Security from the first sprint
Threat modeling, code scanning and least-privilege access are standard, not extras.
04
Risks raised early
We raise a risk with you the day we see it.
05
What we build is yours
Ownership of the final deliverables transfers to you on full payment. An NDA is available on request.
06
From idea to launch
Strategy, design, engineering and QA under one roof, so nothing is lost between vendors.
Numbers you can check
As of October 2026
Products live on the App Store and Google Play
5
Four games and one app.
Downloads of SANAM on Google Play
50,000+
Built for Rai Alnadhar.
App Store ratings for SANAM in the Saudi store
25,000+
Average 4.37 out of 5.
Offices: Riyadh · Garner, North Carolina · Karachi
