Xamun runs the Dubai real-estate backroom — tenancy, escrow, off-plan transactions and brokerage — as systems you own, with Dubai RERA rules enforced in the workflow rather than tracked beside it.
The portfolio is the same; the regulatory pack is not. These are the obligations the products enforce in this market.
The Real Estate Regulatory Agency rules governing developer escrow, project go-live gating and audit-ready disclosure. EscrowOS enforces these as hard gates: a project cannot advance without the conditions being met.
Statutory caps on rent increases at renewal. Every renewal is validated against the applicable band and issued with a tamper-evident certificate, so the increase you served can be shown to have been lawful.
Tenancy contract registration and re-registration. TenancyOS runs registration as part of the renewal workflow rather than as a downstream administrative task.
Brokerage advertising permits tracked to expiry, with automatic marketing blocks. AgencyOS fails closed on portal syndication when a permit lapses, so an expired listing cannot go out.
Identity and anti-money-laundering checks gating each stage advance in the off-plan sales transaction, handled in DealOS.
Tax treatment and revenue recognition posted from the transaction record itself rather than reconstructed at period end.
Post-dated cheque capture and reconciliation alongside bank and e-wallet payments. In TenancyOS a cheque review is its own gate, so a renewal cannot advance until it clears.
Title-deed and encumbrance checks against DLD records with Arabic owner-name transliteration matched to the claimed owner, handled in LandOS as part of registry adjudication.
Off-plan sale registration in the Interim Property Register. DealOS treats Oqood registration as a hard gate — the deal cannot progress without it.
Service-charge and jointly-owned-property registration, modelled in the GraphIQ UAE graph alongside Ejari so both registration regimes are queryable rather than tracked by hand.
Customer due diligence, sanctions screening, record retention and Real Estate Activity Report obligations to the UAE FIU, held in the GraphIQ graph.
Construction guarantee before go-live and post-completion retention held in escrow against defects, both enforced by EscrowOS as project gating.
Institutional landlords, developers and government-related entities operating in Dubai and the wider UAE — organisations large enough that a compliance failure is a material event, and where the tenancy or escrow book is big enough that manual administration is both a cost and a risk.
TenancyOS is the clearest demonstration of what governed automation means here. It runs a two-minds design: one mind reads the instruments, a separate deterministic mind decides. Every gate cites the instrument it relied on, rules are version-stamped and effective-dated, refusals are cited rather than silent, and the system fails closed by default. A general agent platform will summarise a tenancy contract fluently and occasionally assert something it cannot support. In a Decree 43 renewal that is not a rough edge, it is the liability.
Only the products that genuinely apply in this market are listed. A product built to another jurisdiction’s law is not shown here at all.
The compliance pack is the jurisdiction-specific rule set the products run against, held in GraphIQ as a queryable knowledge graph rather than hard-coded into each application. The same product portfolio serves both markets; swapping the pack is what makes it lawful in each. When a rule changes, the graph changes and every product consuming it changes with it — as part of operations and maintenance, not a re-implementation project.
TenancyOS, EscrowOS, DealOS, AgencyOS, LeaseOS and PlanIQ are available today and each has a live demo you can open, with LandOS following its UAE rework. What you buy is your own separate instance — deployed on your infrastructure, under your brand, source-available, configured to your operation and priced per transaction the system processes.
Every lease renewal is validated against the applicable statutory cap band before a notice goes out, and the validation is issued as a tamper-evident certificate. The decision, the rule version it was made under and its effective date are all recorded, so a challenged increase can be shown to have been lawful at the time it was served.
Registration and re-registration run inside the renewal workflow in TenancyOS rather than as a separate administrative step afterwards, so a renewal cannot quietly complete without its registration obligation being handled.
GraphIQ models UAE property regulation as a queryable knowledge graph that the products consume through an API. When a rule changes, the graph changes and every product enforcing it changes with it, as part of operations and maintenance rather than a re-implementation project.
No. The language model drafts and parses; a separate deterministic engine makes every regulated decision against version-stamped, effective-dated rules and fails closed when its inputs are missing.
Bring us one workflow and we will show you it running under the UAE pack.