CUSTOM SAAS DEVELOPMENT

UAE SaaS founders building a product for the Gulf market need Arabic-English bilingual UI, AED billing, GCC data residency, and UAE Pass authentication as architectural decisions from day one — adding them after launch doubles the rebuild cost

Build your UAE SaaS product with bilingual UI, AED billing with UAE VAT, GCC-compliant infrastructure, and UAE Pass authentication designed into the architecture before the first sprint.

Request a SaaS Scoping Session → View the evidence →
This is for you if

Who This Is For

Dubai's real estate market generates high transaction volume with complex documentation, multi-party workflows, and regulatory requirements under the Dubai Land Department. A proptech SaaS for this market needs to support Arabic and English in the same interface, integrate with DLD's REST API for transaction registration, handle AED billing, and be hosted in the UAE for data residency compliance. Founders building in this vertical without these architectural requirements in place will not win deals from established Dubai real estate agencies.

Healthcare SaaS in the UAE must align with HAAD licensing requirements in Abu Dhabi and DHA requirements in Dubai. Products handling patient health data must integrate with NABIDH (Abu Dhabi's health data exchange) or Malaffi (Dubai's HIE platform) depending on the emirate of operation. The bilingual requirement is particularly acute in healthcare: Arabic is the primary language for a significant proportion of UAE patients, and clinical staff in UAE hospitals work in both Arabic and English. A clinic management SaaS that does not support Arabic is not a viable product for the UAE healthcare market.

The UAE's legal and corporate services market is multilingual by nature. Law firms operating in the DIFC work in English; mainland UAE law firms and corporate secretarial firms work in Arabic and English simultaneously. A matter management or document automation SaaS for this market must support RTL Arabic in document generation, handle AED billing, and be hosted in the UAE to meet the data residency expectations of legal clients with confidentiality requirements. The corporate services sector — company formation, visa processing, trade licence management — is a high-volume SaaS opportunity in a market with significant manual process still in place.

The Wage Protection System (WPS) is a UAE Central Bank mandate requiring employers to pay salaries through approved financial institutions with an electronic salary transfer record submitted to the Ministry of Human Resources. A UAE payroll SaaS that does not generate WPS-compliant salary transfer files is not a complete product for the UAE market. HR and payroll SaaS for the UAE also needs to handle free zone versus mainland employment rules, which differ in visa requirements, leave entitlements, and end-of-service gratuity calculation. These are compliance requirements that must be built into the product's data model, not handled as manual workarounds by the customer.

What's broken

What Is Broken

Arabic RTL UI not designed into the product from the start

UAE SaaS products built with English-only UI that add Arabic as a translation layer after the fact discover that Arabic is not a translation problem — it is a layout problem. Arabic is written right-to-left. Every UI component that was designed left-to-right must be mirrored: navigation menus, form field labels, table headers, modal dialogs, and data visualisations. The CSS must support bidirectional text handling for mixed Arabic-English content in the same field. The component library must have RTL variants for every component. Chart rendering libraries must support RTL axis orientation. Attempting to apply RTL after building an LTR-only product is the equivalent of mirroring the entire frontend codebase. It is a significant engineering effort that costs far more than designing for RTL from the start. This is an architectural decision at the component library level, not a translation pass.

AED billing and UAE VAT not configured

UAE SaaS products billing in USD and converting informally to AED are creating friction for UAE-market customers whose finance teams process invoices in AED and whose accounting software reconciles in AED. UAE VAT at 5% applies to SaaS services supplied in the UAE under the Federal Tax Authority guidelines. Stripe UAE supports AED billing and can be configured with the UAE 5% VAT rule in Stripe Tax. PayTabs and Telr are alternative payment gateways with strong UAE market presence for products requiring local acquirer relationships. The billing architecture decision — which currency, which gateway, how VAT is calculated and displayed — is made at the MVP stage. Changing from USD to AED billing after launch requires a migration of all existing subscription records, a re-issuance of invoices, and a reconfiguration of the billing platform. It is not a setting change.

GCC data residency not planned for

UAE SaaS products deployed on AWS US-East-1 or AWS EU-West-1 as the default deployment target will fail the IT due diligence of UAE government agencies, semi-government entities, and regulated industries including banking, insurance, and healthcare. These customers require that their data be stored within the UAE or, at minimum, within the GCC. Microsoft Azure UAE North (Abu Dhabi) and AWS Middle East (Bahrain) are the two primary GCC-compliant hosting options. Azure UAE North is the preferred option for products targeting UAE government and semi-government customers given Microsoft's UAE cloud sovereign commitments. Deploying in GCC regions requires a production infrastructure design that explicitly selects UAE/GCC availability zones and does not use global CDN or logging services that route data through non-GCC regions without configuration. This is an infrastructure architecture decision that must be made at the start of the project.

UAE Pass authentication integration not scoped

UAE Pass is the UAE government's national digital identity platform, managed by the Telecommunications and Digital Government Regulatory Authority. For SaaS products targeting government-adjacent use cases — public sector procurement tools, regulatory compliance platforms, citizen service applications, or products marketed to UAE government employees — UAE Pass integration is the expected authentication method. Integrating UAE Pass after the authentication system has been built requires significant rework of the auth layer: the existing authentication model must be extended to support UAE Pass as a federated identity provider, the user profile model must accommodate UAE Pass identity attributes, and the login flow must handle the UAE Pass mobile app confirmation step. Building UAE Pass as a supported authentication method from the start adds a small amount of complexity to the initial auth design and removes a major rebuild risk if the product needs government market access.

What we engineer

What We Do

Arabic-English bilingual UI with RTL architecture

Ignited Nepal designs the component library and frontend architecture for Arabic-English bilingual support from the first sprint. This includes RTL CSS configuration, a bidirectional component library with Arabic and English variants, a language switching mechanism at the application level, and text rendering validation for Arabic script in all form fields, labels, and data display components. The bilingual architecture supports content that is created in either language and displayed in the correct direction without manual handling by the user.

AED billing, UAE VAT, and Stripe UAE or PayTabs integration

Billing is configured for AED as the primary billing currency with UAE 5% VAT applied via Stripe Tax or the equivalent configuration in PayTabs. Invoices are generated in AED with the correct VAT line item and FTA-compliant invoice format. Subscription plan management, trial periods, and proration are configured in the billing platform before the first customer is asked to pay. For products requiring a UAE local acquirer, PayTabs or Telr integration is built and tested with UAE card types.

GCC data residency on Azure UAE North or AWS Middle East Bahrain

Production deployment is configured on Azure UAE North or AWS Middle East (Bahrain) depending on the product's data residency requirements and the customer segments being targeted. Azure UAE North is recommended for products targeting UAE government or regulated industry customers. The CI/CD pipeline, CDN, logging, and monitoring stack are all configured to operate within GCC regions. No customer data transits non-GCC infrastructure without explicit customer consent and documented data transfer controls.

UAE Pass authentication and enterprise SSO

UAE Pass integration is built as a supported authentication method for products where government-adjacent market access is required. For enterprise SaaS products targeting corporate customers in the DIFC or free zones, Microsoft Azure AD and Google Workspace SSO are implemented as enterprise authentication options alongside email/password.

Multi-tenant architecture with Arabic data model support

The data model is designed for multi-tenancy from the first migration, with Arabic text fields using the correct Unicode encoding and collation settings in PostgreSQL. Full-text search for Arabic content requires Arabic-aware tokenisation, which is configured at the database level. The permission model and tenant isolation strategy are defined in the scoping phase and enforced at the API layer.

Admin panel and post-launch iteration

The admin panel covers user and organisation management, subscription and billing management, language and region configuration per tenant, and support-facing data access. Post-launch iteration support is provided on a sprint basis covering bug fixes, performance work, and feature additions from the post-MVP backlog.

Request a SaaS Scoping Session →
What changes

What Changes

Before
After
Before UAE SaaS products built with English-only UI that add Arabic as a translation layer after the fact discover that Arabic is not a translation problem — it is a layout problem. Arabic is written right-to-left. Every UI component that was designed left-to-right must be mirrored: navigation menus, form field labels, table headers, modal dialogs, and data visualisations. The CSS must support bidirectional text handling for mixed Arabic-English content in the same field. The component library must have RTL variants for every component. Chart rendering libraries must support RTL axis orientation. Attempting to apply RTL after building an LTR-only product is the equivalent of mirroring the entire frontend codebase. It is a significant engineering effort that costs far more than designing for RTL from the start. This is an architectural decision at the component library level, not a translation pass.
After A bilingual RTL product does not exclude the Arabic-speaking majority of the Gulf market. The first sales conversation with a Dubai or Abu Dhabi enterprise is not derailed by a language that the product does not support.
Before UAE SaaS products billing in USD and converting informally to AED are creating friction for UAE-market customers whose finance teams process invoices in AED and whose accounting software reconciles in AED. UAE VAT at 5% applies to SaaS services supplied in the UAE under the Federal Tax Authority guidelines. Stripe UAE supports AED billing and can be configured with the UAE 5% VAT rule in Stripe Tax. PayTabs and Telr are alternative payment gateways with strong UAE market presence for products requiring local acquirer relationships. The billing architecture decision — which currency, which gateway, how VAT is calculated and displayed — is made at the MVP stage. Changing from USD to AED billing after launch requires a migration of all existing subscription records, a re-issuance of invoices, and a reconfiguration of the billing platform. It is not a setting change.
After AED billing with correct UAE VAT means the customer's finance team receives an invoice they can process directly against their accounting system. The payment friction that comes from USD invoices issued to UAE dirham accounts is eliminated.
Before UAE SaaS products deployed on AWS US-East-1 or AWS EU-West-1 as the default deployment target will fail the IT due diligence of UAE government agencies, semi-government entities, and regulated industries including banking, insurance, and healthcare. These customers require that their data be stored within the UAE or, at minimum, within the GCC. Microsoft Azure UAE North (Abu Dhabi) and AWS Middle East (Bahrain) are the two primary GCC-compliant hosting options. Azure UAE North is the preferred option for products targeting UAE government and semi-government customers given Microsoft's UAE cloud sovereign commitments. Deploying in GCC regions requires a production infrastructure design that explicitly selects UAE/GCC availability zones and does not use global CDN or logging services that route data through non-GCC regions without configuration. This is an infrastructure architecture decision that must be made at the start of the project.
After A product hosted on Azure UAE North or AWS Middle East Bahrain can answer the data residency question in a government or regulated industry sales process with a documented architecture diagram rather than a promise to migrate later.
Before UAE Pass is the UAE government's national digital identity platform, managed by the Telecommunications and Digital Government Regulatory Authority. For SaaS products targeting government-adjacent use cases — public sector procurement tools, regulatory compliance platforms, citizen service applications, or products marketed to UAE government employees — UAE Pass integration is the expected authentication method. Integrating UAE Pass after the authentication system has been built requires significant rework of the auth layer: the existing authentication model must be extended to support UAE Pass as a federated identity provider, the user profile model must accommodate UAE Pass identity attributes, and the login flow must handle the UAE Pass mobile app confirmation step. Building UAE Pass as a supported authentication method from the start adds a small amount of complexity to the initial auth design and removes a major rebuild risk if the product needs government market access.
After UAE Pass integration means the product can be marketed to government agencies, semi-government entities, and public sector employees as a compliant authentication option. Government market access in the UAE requires UAE Pass; having it built in removes a gate that competitors without it cannot pass.
How it works

Process

  1. 01

    UAE SaaS Scoping Session.

    A structured session covering the product's target market, the bilingual UI requirements, the billing currency and VAT configuration, the data residency requirements, the authentication requirements (including UAE Pass), and the GCC infrastructure plan. Output: a scoping document with all UAE-specific architectural decisions recorded.

  2. 02

    Bilingual component library and data model design.

    The RTL-capable component library is designed and the Arabic-English language switching architecture is agreed before the first feature sprint begins. The data model is designed with Arabic text handling, multi-tenant isolation, and the permission model defined.

  3. 03

    Sprint-based MVP build with bilingual validation.

    The MVP is built in two-week sprints with bilingual UI validation as part of the acceptance criteria for every UI component. Arabic text rendering, RTL layout, and bidirectional form handling are tested in each sprint, not as a post-build pass.

  4. 04

    Billing configuration and UAE Pass integration.

    AED billing with UAE 5% VAT is configured and tested with UAE card types before launch. UAE Pass integration, if scoped, is built and tested with the UAE Pass staging environment.

  5. 05

    GCC production deployment and CI/CD setup.

    Production deployment to Azure UAE North or AWS Middle East Bahrain is configured with CI/CD, environment separation, and monitoring. The deployment architecture is documented with the data flow diagram showing that no customer data transits non-GCC infrastructure.

  6. 06

    Launch and post-launch support.

    The product launches with bilingual UI, AED billing, and GCC hosting operational. Post-launch sprint support covers bug fixes, performance work, and the first feature additions from the post-MVP backlog.

Request a SaaS Scoping Session →
Common questions

Frequently asked questions about Custom SaaS Development

How do I build an Arabic-English bilingual SaaS product with RTL UI support from day one?

Building a bilingual RTL SaaS product requires four engineering decisions made at the start of the project: selecting a component library that supports RTL variants (or building a custom one with RTL CSS from the start), configuring the CSS framework with logical properties rather than directional properties (margin-inline-start instead of margin-left), implementing a language and direction context at the application root that all components consume, and setting up a translation management system that handles both LTR and RTL strings. Arabic text in form fields, search inputs, and rich text editors requires bidirectional text handling at the browser level, which is enabled by the HTML dir attribute set correctly on the container. The Arabic font stack must be specified explicitly to ensure correct Arabic script rendering across operating systems.

How do I configure AED billing and UAE 5% VAT in Stripe for a UAE-market SaaS product?

Stripe UAE supports AED as a billing currency. To configure UAE VAT at 5%: enable Stripe Tax in the Stripe dashboard, add the UAE as a tax jurisdiction with the 5% VAT rate, assign tax codes to each Stripe product that map to the FTA's product/service tax classification, and configure customer tax location detection using the customer's billing address. UAE-registered businesses are required to register for VAT if their taxable turnover exceeds AED 375,000. VAT-registered SaaS companies must issue FTA-compliant tax invoices that include the supplier's TRN number, the customer's TRN if the customer is VAT-registered, and a line-item breakdown of the VAT amount.

What are the GCC data residency options for a UAE-market SaaS product?

The two primary GCC-compliant cloud hosting options are Microsoft Azure UAE North, located in Abu Dhabi, and AWS Middle East (Bahrain). Azure UAE North is the preferred option for products targeting UAE government and regulated industry customers due to Microsoft's UAE cloud sovereign commitments and the availability of Azure Government-specific compliance certifications. AWS Middle East (Bahrain) provides the full AWS service catalogue in a GCC location and is suitable for products that are not targeting government customers but need GCC data residency for enterprise customers in banking, insurance, or healthcare. Both options provide the latency profile required for UAE-based users. The decision between Azure and AWS is driven primarily by the customer segment, the compliance certifications required, and the team's operational experience with each platform.

How do I integrate UAE Pass authentication into a UAE SaaS product?

UAE Pass integration uses an OpenID Connect flow where UAE Pass acts as the identity provider. The integration requires registering the SaaS application with the UAE Pass developer portal, implementing the OIDC authorization code flow in the backend, handling the UAE Pass mobile app confirmation step in the user experience, and mapping UAE Pass identity attributes to the SaaS product's user profile model. UAE Pass provides the user's Emirates ID number, name, and verified phone number as identity attributes. The UAE Pass integration is available for both the production environment and a staging environment for testing. The TDRA (Telecommunications and Digital Government Regulatory Authority) must approve the application registration before the production integration is live.

What is the process for setting up a tech company in Dubai to own and commercialise a SaaS product?

A UAE-based SaaS company can be incorporated in the DIFC (as an LLC or Recognised Company), DMCC, or as a mainland UAE LLC. DIFC and DMCC free zones are the most common choices for technology companies due to 100% foreign ownership, no corporate tax on qualifying income under the UAE CT regime, and the ability to operate under common law (DIFC) or a free zone framework (DMCC). Mainland LLC requires 51% UAE national ownership for some activities, though the relevant activity code for software development and SaaS typically permits 100% foreign ownership under the 2021 Commercial Companies Law amendments. The choice between DIFC, DMCC, and mainland depends on the target customer base, the regulatory requirements for the specific SaaS vertical, and the visa requirements of the founding team.

Start here

Closing CTA

A UAE SaaS product that is English-only, USD-billed, and US-hosted is not a UAE SaaS product — it is a product that requires a UAE customer to compromise on language, currency, and data compliance to use it. The founders who build with bilingual RTL UI, AED billing with UAE VAT, GCC data residency, and UAE Pass authentication as day-one architectural requirements are the ones whose enterprise sales conversations are not derailed by IT and finance due diligence. Ignited Nepal builds SaaS products for the Gulf market with these requirements built in from the first sprint, not retrofitted under deal pressure.

Request a SaaS Scoping Session →