Mobile apps
Native apps for iOS, Android and Huawei, where a web app on the home screen is not enough.
Web app or nativeEverything below is ours and on our servers. Nothing follows you to another site.
Who
How we work
Rebuild
CUSTOM WEB AND SOFTWARE DEVELOPMENT · DUBAI
Both ends of that range, same team and same standards. We build without page builders, without plugin stacks and without anything on the page we did not write. Whatever the size, you own the code, the servers and the data.
Company sites, microsites, campaign pages and portfolios. Fast and built to be found.
CRMs, SaaS products, internal systems, booking engines and property or logistics platforms.
Many sellers, many buyers, money moving between them. The hardest thing on this page to get right.
Websites have a range, platforms a starting price, and marketplaces are priced per project, because scope is what moves the number. We also publish the method: we scope in writing before anything is agreed, and we remove whatever will not earn its cost. Third-party services are billed at cost — we do not mark up other people's software.
THE FULL LIST
Each one has its own page with process, examples and what it costs. If something you need is not here, ask — we are a single point of contact by design.
05 SERVICES
From
Product launches, events, pavilions. Built fast, taken down cleanly, measured properly.
Two to five days. For a campaign that needs somewhere to send traffic tomorrow.
Arabic right-to-left built into the system, not translated over a left-to-right design.
Everything installs to a home screen by default. Native where the device features genuinely require it.
04 SERVICES
Custom checkout on Stripe, real stock control, no app subscriptions eating your margin.
Clinics, classes, rentals, tours. Availability, deposits, no-shows and reminders.
Gateways, subscriptions, split payments, multi-currency and reconciliation that balances.
Many sellers, escrow, split payments, disputes and payouts. Built in, not bolted on.
05 SERVICES
Software or data sold by subscription. Single tenant for isolation, multi-tenant for scale.
CRM, listings, marketplaces, tenancies and rent collection. We run two of these ourselves.
Load boards, dispatch, hours-of-service compliance, device integration and carrier reporting.
Making systems that were never designed to talk to each other work together reliably.
Hardened servers, atomic releases, one-command rollback, backups tested by restoring them.
05 SERVICES
Days, not weeks. Enquiry handling, catalogue, booking and routing on the channel people actually use.
Workflow and approvals, data sync between systems, and reporting that arrives without being asked.
WhatsApp, Telegram, email, SMS and web chat in one inbox with the full history.
Calls and recordings inside your own system rather than a third-party tool you also pay for.
Several sites or systems on one screen: uptime, traffic, errors, cost and security.
04 SERVICES
Under strict protocols. Our own AI on our servers, or a model reached through an API.
A full app that opens inside Telegram. Nothing to install, no app store.
A tool in your team’s browser, working on the pages they already use.
For work that needs the whole computer: files, long sessions, several screens.
APPS ON EVERY SCREEN
Four kinds of app, built to the same standards and ownership terms as everything else on this page. You own the code of each one.
Native apps for iOS, Android and Huawei, where a web app on the home screen is not enough.
Web app or nativeA full app that opens inside Telegram, where your customers already write to you. Nothing to install.
A tool that sits in your team’s browser and works on the pages and systems they already use.
For work that needs the whole computer: local files, long sessions and several screens at once.
All four kinds, and which one fits.
AI UNDER STRICT PROTOCOLS
Zero trust, a person in the loop, and an answer only when it is verified. The client decides where AI works and can turn it off.
Our own AI runs on servers we operate, under the same rules as the rest of the system. A model built for a client belongs to that client alone.
Where an outside model fits the job, it is connected through an API on the same protocols. We do not train AI on client data, whichever model it is.
The protocols, and where each part stands today.
TEZZ, our own AIIn training. API access only.
INCLUDED REGARDLESS OF BUDGET
These are defaults, not upgrades, and they are not negotiable downward. They cost us nothing extra because they are how we build anyway.
Code in your repository, servers in your name, domain under your control, data exportable at any moment. No licence, no lock-in, nothing that makes leaving expensive.
Security headers configured, encryption in transit and at rest, and no third-party script on the render path.
Schema markup, clean heading hierarchy, proper metadata and an llms.txt file, so both search engines and AI assistants describe you accurately rather than guessing.
An untested backup is a hope, not a control. Restores are rehearsed on a schedule and every deploy can be reversed with one command.
Measures we publish, not guarantees we cannot make.
BEFORE WE QUOTE
A bad doctor prescribes expensive medicine nobody needs. Scope is where that happens in our industry.
Not everything you might eventually want. The smallest version that solves the actual problem, because that version can launch, earn and then tell you what to build next.
If we cannot answer that for a feature, it comes out of scope before you pay for it. Scope we talk you out of is scope we do not bill for, which is a rule rather than a gesture.
Sometimes a template genuinely fits, or a three-day fix beats a rebuild. We say so and point you somewhere sensible, including when that somewhere is not us.
Six published rules, dated and not open to negotiation.
WHAT WE BUILD WITH
Chosen for maintainability over fashion. Every one of these is something another competent developer can pick up if you ever move on from us.
| Layer | What we use | Why |
|---|---|---|
| Websites | Astro, TypeScript | Ships almost no JavaScript by default, which is why our pages load in under a second rather than four. |
| Applications | React, Svelte | Where a screen genuinely needs to be interactive. Not used for pages that only need to be read. |
| Backend | Node.js, Go | Node where the team velocity matters, Go where the throughput does. Both boring, both fast, both hireable. |
| Database | PostgreSQL | Relational, proven, and it does not surprise you at scale. Nothing exotic that only we can operate. |
| Payments | Stripe | Handles card, currency and regional edge cases in milliseconds. Multi-vendor settlement done properly. |
| Search | Elasticsearch | When a platform has enough data that ordinary queries stop being fast enough. |
| Messaging | WhatsApp API | Official channels, not scraped integrations that break when a policy changes. |
| Infrastructure | Hardened Linux at DigitalOcean, Frankfurt | Atomic releases, one-command rollback, and monitoring that pages a human only for real incidents. |
BY INDUSTRY
A property portal fails differently from a clinic booking page. Each page below covers the specific problems of that sector rather than repeating the same copy.
If yours is not listed, the process is identical. Ask.
STRAIGHT ANSWERS
Cost and timeline first, because those are what everyone actually wants to know.
A custom website costs between
No. Both carry a plugin ecosystem that is the single largest source of security incidents and performance loss on the web. We build custom, which means no plugin conflicts, no forced updates, no monthly platform fee and nothing on the page we did not write. For a simple brochure site a template may genuinely be cheaper, and we will tell you so.
Yes: mobile apps, Telegram mini apps, browser extensions and native desktop apps. Everything we build is mobile-first and installs to a phone home screen without an app store, which covers most requirements at a fraction of native cost. Where a project needs device features such as offline use, background location or push at scale, we build native for iOS, Android and Huawei.
Yes, under strict protocols: zero trust, a person in the loop, and an answer only when it is verified. The AI is our own, running on our servers, or a model reached through an API. The client decides where AI works in the project and can turn it off. We do not train AI on client data.
Full ownership of code, servers, domains and data. Security headers, encryption in transit and at rest, and no third-party scripts on the render path. Structured data so search engines and AI assistants read the site correctly. Automatic backups with tested restores. These are defaults, not upgrades, and a
A working MVP takes 2 to 6 weeks for most platforms and 1 to 2 months for a marketplace, with 3 months to a version ready for real commercial testing. Websites are much faster: 7 days, 10 days with an integration. Enterprise and complex multi-site builds are scoped after review.
Yes, and it often works well. We can take a defined component, an integration or the infrastructure layer while your team handles the rest. What we will not do is take responsibility for code we did not write, so the boundary gets agreed in writing at the start.
No discovery call required to start. Tell us what you need and we send back a scope and a number, or an honest reason why we are not the right people for it.
One tap, then your app opens with it written.