Solutions · SaaS
A product for many customers, built so one never sees another.
Launching software for a whole industry is a different job from building it for one company. We engineer the parts that are expensive to add later: isolation, permissions, billing, onboarding and the admin you will run it from.

What it covers
The foundations a SaaS cannot add later
Isolation in the database
Each customer’s rows are separated by the database itself (row-level security), not only by application code.
Roles and visibility
Permissions per role and per record, so a trainee sees but cannot approve, and a colleague’s files stay private.
Billing and invoices
Money stored as exact integers, numbered invoices, payments and statements.
Imports and onboarding
New customers bring their spreadsheets; nothing is written until a person has seen the preview.
Customer portals
A separate, deny-by-default space for your customers’ own clients.
Admin and audit
Health checks after every deploy, scheduled alerts and an audit trail per customer.
Arabic-first is engineering, not translation
For products aimed at the Gulf, Arabic is where the hard problems are: search that understands spelling variants, Hijri dates converted correctly, PDFs that shape Arabic text, and right-to-left layouts that do not break. We design for that from the first table.
- Arabic full-text search with normalised spellings
- Hijri ↔ Gregorian with the Umm al-Qura calendar
- Arabic PDF invoices and documents

Built by us
Questions we are often asked
Can you build the MVP and then keep going with us?
Yes. We plan the first release around what you can sell, then keep developing in milestones as customers arrive.
Where is it hosted?
Where your customers need it: a major cloud, a regional data centre or your own servers. We set up deployment, backups and monitoring.
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.



