Abu Dhabi · served remotely
Software development company for Abu Dhabi
We build enterprise software, AI and cloud systems for Abu Dhabi organisations, delivered remotely by a senior UK team. Built for the scrutiny that government, energy and institutional work actually attracts.
§ 01
The market
Building software for Abu Dhabi
Abu Dhabi is a different market from its neighbour, and software built for it has to reflect that. Where Dubai runs on commerce and speed, Abu Dhabi runs on institutions: government, energy, sovereign investment, healthcare and the growing ADGM financial centre. The work is larger, slower to sign, and held to a higher standard of governance, documentation and durability.
Yarqat is a UK-registered company and we serve Abu Dhabi remotely. We say that plainly because institutional buyers value a partner who does not oversell, and a fictional local office is exactly the kind of small dishonesty that erodes trust before a contract is signed. What we bring instead is senior engineering, a working-hours overlap with the Gulf, and delivery practices that survive an audit.
The kind of software Abu Dhabi buys is the kind that has to still be running, and still be understood, in ten years. That favours our approach: architecture decided deliberately, systems built to be operated by the client, and nothing shipped that the receiving team cannot maintain. Enterprise standards are not a tier we upsell here, they are the baseline the market requires.
§ 02
What is specific
What building for Abu Dhabi actually requires
Governance is designed in
Government and institutional work carries change control, audit trails and documentation requirements that most software teams treat as an afterthought. We build them in from the start, with architecture decision records and a definition of done that includes the things auditors actually ask for.
Built to outlast the vendor
Institutional systems are expected to run for a decade and to be maintainable by whoever holds them next. We design for that: clean boundaries, real documentation, and observability, so the software does not depend on the people who wrote it.
Data residency taken as a constraint
Where data must stay in a jurisdiction or within specific controls, that shapes the architecture from the first decision rather than being negotiated near launch. It is the kind of requirement that is cheap to honour early and ruinous to retrofit.
§ 03
Working together
How working with us goes from Abu Dhabi
- 01
Scoping that respects procurement
A free consultation with the engineer who would run delivery, followed by written scope, risk and effort that stands up to the review an institutional purchase involves.
- 02
Architecture before build
Significant decisions recorded with their alternatives, so the reasoning survives handovers, audits and the years between them.
- 03
Delivery with a paper trail
Working increments, reviewable throughout, with the governance and documentation the sector expects produced as we go rather than assembled at the end.
- 04
A genuine handover
The system, its documentation and its runbooks, transferred so your team or your operator can run it without us. Handover is a deliverable, not a favour.
§ 04
Services
What we build for Abu Dhabi clients
Project delivery, owned end to end. We take on the outcome rather than supplying engineering hours.
Working with Yarqat in Abu Dhabi
Do you have an office in Abu Dhabi?
No. Yarqat is UK-registered and serves Abu Dhabi clients remotely. For institutional buyers we think that honesty matters more than a local address would: you deal directly with senior engineers, and we do not pad our rate with the cost of a presence you would not use.
Can you meet the governance requirements of government or institutional work?
Yes. Change control, audit trails, architecture decision records and documentation are built into how we deliver rather than added at the end. If your procurement or compliance process has specific requirements, we would rather hear them at the first conversation and design around them.
How do you handle data residency and jurisdiction requirements?
As an architecture constraint decided at the start. Where data must remain in a specific jurisdiction or under specific controls, that shapes the design from the first decision. Retrofitting it later means rebuilding, which is why we ask about it early.
Will the system be maintainable after you hand it over?
That is a design goal, not an afterthought. We build with clean boundaries, real documentation and observability specifically so the software can be operated and changed by your team or a successor, without depending on the people who originally wrote it.
What size of project do you take on?
From a focused build to a substantial enterprise system. What we do not do is supply loose engineering capacity by the hour; we take on defined outcomes and own the delivery, which suits the accountability institutional work requires.
Have a project in Abu Dhabi?
A technical conversation with the engineers who would do the work. If we are not the right fit, we will say so on the call.