Engineering
The parts you don’t see are the parts you rely on.
These are the standards we hold ourselves to on every system, written down so you can hold us to them too.
Security and data
Built to be trusted with your data
Isolation by design
In multi-company systems, separation is enforced by the database (row-level security), not only by screens.
Access that fits roles
Every permission has a matching query scope, so lists and search never leak what a page would hide.
Every action on record
Audit trails, append-only ledgers for money, and a record of what any automation proposed and who approved it.
Tested and recoverable
Automated tests for each business rule, scheduled backups and written recovery steps.
Money done exactly
Amounts stored as integers in the smallest unit; no floating-point arithmetic anywhere near money.
Nothing trusted from the browser
Payments confirmed with the provider, webhooks verified, links re-checked on download.
Arabic-first engineering
Where most software quietly breaks
Right-to-left that holds
Layouts, numbers, phone numbers and mixed-direction text that stay readable.
Hijri dates
Converted with the Umm al-Qura calendar, and every conversion announced to the user.
Search that knows Arabic
Spelling variants folded, prefixes handled, and matches found inside words.
Arabic documents
PDFs and invoices with correctly shaped Arabic text and right-to-left tables.
Hosting and delivery
Deployed where your rules require
We deploy to a major cloud, a regional data centre, your own servers or, when the budget calls for it, carefully configured shared hosting. Each deployment comes with health checks, monitoring and a written runbook.
Every repository runs with fake providers by default, so it can be built and tested without keys or network — and nobody needs production data to work on it.
Have a system like this in mind?
Tell us how your team works today. We will tell you honestly what we would build, or whether an existing product is enough.