Healthcare · Yemen
Tabibi
Patients in Yemen needed one place to find a clinic, compare it, and book. Clinics needed to run the day from that same system. Tabibi is that platform.
Pages
AL STACK
Software your business can run.
Unreliable tools and manual handoffs cost time, money, and the next customer. We build the system the business actually operates.
Badsoftwareisnotadesignproblem.Itislosttime,abrokenhandoff,andasystemnobodytrustsonabusyday.Webuildsoftwarethatholdsindailyuse,stayssecure,andcangrowwhenthebusinessdoes.
What changes
Systems you can operate. Cloud you own. Arabic that was designed, not pasted on.
01
Enterprise applications
When records, staff, and customers live in different tools, the business slows down. We build the system of record, the internal portals, and the services behind the public site.
You hold: A system your team can run and change, not a project that only the vendor understands.
02
Cloud applications
A launch that only works on our accounts is not yours. We put the software in your cloud, with a deployment path your team can see.
You hold: Your accounts, a running service, and no surprise on the day it goes live.
03
Yemen, the Gulf, Arabic
An Arabic audience should not meet a translated afterthought. We design the product for how people in Yemen and the Gulf actually work, including right-to-left use.
You hold: A product that feels native in Arabic, and still works for a team that also uses another language.
Why it holds
Engineering only matters if the business can depend on it.
Reliability you can plan around
A sound structure and tests mean the system behaves on a normal Tuesday, not only in a demo. Fewer avoidable failures, and a clearer place to look when something does break.
People who have run production
The engineers on your work spent 15 years inside Mercedes-Benz, IBM, and SAP, on systems used by millions of people. That is operating experience, not a slide about architecture.
Security and a clean handover
Access, encryption, and isolation are part of the design, because a leak or a locked-in codebase both stop the business. You receive the repository, the accounts, and the people who can explain them.
Proof
Live products, not case-study theatre.
A clinic platform in Yemen, a school system for families, a restaurant platform still in development, and a mission that reported a rise in donations.
Schools
Veda
Madrasati
Schools, students, and parents needed one place instead of paper and chat. Veda digitizes the school: admissions, the day, and what the family sees.
Pages
RestaurantsStill in development
Platto
Sufra
Platto is still being built. It will bring the dining room, the kitchen, and the guest’s order onto one platform, instead of three separate conversations.
Humanitarian
Yemen
A children's mission in Yemen needed a public voice that could take support. The organisation reported donations up 40% in the first month.
Pages
How you receive it
You know what you hold at the end of each stage.
- 01
Discovery
We write down the constraint, the users, and what “done” means, before anyone builds the wrong thing.
Asset: A written scope you can accept or refuse.
- 02
Design
Screens and the shape of the system come first, so the business can react before the expensive work.
Asset: Interfaces you can click through.
- 03
Build
The software lands in your repository and your cloud, in steps you can see, not in a folder we keep.
Asset: Working software you already host.
- 04
Launch
It goes to production with the keys, the accounts, and time from the engineers who built it.
Asset: A system your team can operate.
Insan e.V.
“Our mission is to change children's lives — and AL STACK gave that mission a voice online. Donations increased by 40% within the first month. They didn't just build us a website, they understood our cause and created something that truly moves people to act.”
The guarantee
If the engineering is not what we agreed, the fee comes back.
The written agreement names the engineering. If what we deliver is not the quality that agreement describes, we refund the fee for that work in full.
Before you write
Straight answers.
Next step
Tell us what is getting in the way.
Describe the workflow, the system, or the market. We reply with a proposed scope, how it would run, and what you would own at the end. Write to [email protected] or use the form. This starts a conversation. It is not a free build.