One system runs the whole portfolio.
A lease is signed. Ejari is filed, DEWA is transferred, the deposit is posted, the invoice run is created, the owner is told. Nobody re-enters anything, because there is only one system to enter it into.
Built for UAE and GCC operations — Ejari, DLD, DEWA, UAE PASS, PDCs, service charges, Arabic and English.
- Ejari
- DLD
- DEWA
- UAE PASS
- Tawtheeq
- Post-dated cheques
- Service charges
- VAT
- Arabic + English
This is where the work actually lives.
Not in a system. In eleven of them, plus a group chat and a person who remembers how it all fits together.
- WhatsAppSir the AC in 1204 is leaking again
- SpreadsheetRenewals_Q4_FINAL_v7_USE THIS.xlsx
- EmailRE: RE: FW: Owner statement — August (3rd request)
- Missed callTenant, B-1806 · 3 attempts
- PortalEjari login — password expired
- NotePDC for Nov — in the safe? ask Rashid
- SpreadsheetService_charge_apportionment_TowerB.xlsx
- WhatsAppWhich unit did we quote 132k on?
- EmailDEWA move-in confirmation — forward to accounts
- Ticket#8841 chiller — assigned to? unclear
- NoteReconcile Sept — 14 receipts unmatched
- PortalDLD — re-key unit reference manually
Then one system takes it.
The same eleven jobs, on one record, with the handoffs between them removed rather than digitised.
Most real estate software manages a department. This runs the company.
A lease signed in AQARI ONE posts its own revenue schedule, files its own Ejari registration, opens its own handover inspection and starts its own collection sequence. One record, one ledger, one audit trail — because it was never more than one system.
The stack you have now
- A PMS for units and leases
- A separate accounting package
- A CRM the sales team actually uses
- A helpdesk for maintenance tickets
- Spreadsheets for owner statements
- A folder of scanned PDFs
- Manual re-keying between all six
Six systems, one company, and a person whose job is moving data between them.
AQARI ONE
- One record per property, unit, lease and owner
- One double-entry ledger behind every module
- One pipeline from enquiry to signed lease
- One dispatch queue across every asset
- Owner statements generated, not assembled
- Every document read, indexed and searchable
- Nothing re-keyed, ever
One system, one ledger, one audit trail — and no integration project between them.
Pick something that happens every week.
This is the difference an operating system makes. Not that each step is possible — every vendor can do each step. That there is no gap between them for work to fall into.
Eleven systems, or one record.
In a conventional stack this is four teams, three logins and a spreadsheet. Here it is one record moving through its own lifecycle.
- LeasingUnit selectedPerson
B-1806 · Marina Heights · AED 312,000/yr
- CRMTenant verifiedAuthority
Identity matched via UAE PASS
- LeasingLease generatedAI agent
Drafted from your template and the agreed terms
- Document AIClauses checkedAI agent
2 deviations flagged for legal review
- LeasingApproved and signedPerson
Legal approval, then e-signature
- GovernmentEjari submittedAuthority
Filed from the lease record
- GovernmentDEWA move-in raisedAuthority
Utility account transferred to the tenant
- AccountingDeposit postedPlatform
Dr Bank / Cr Tenant deposit liability
- AccountingRevenue schedule createdPlatform
12 postings queued at signature, not at invoice
- AccountingFirst invoice issuedPlatform
AED 26,000 · due on the lease start date
- FacilitiesHandover inspection bookedPlatform
Snagging list and meter readings scheduled
- Owner portalOwner updatedPlatform
Occupancy, income and statement reflect it immediately
- TenantTenant confirmed on WhatsAppAI agent
Keys, access, payment instructions and portal login
Press Run. Watch what fills in.
Illustrative sample data. In a conventional stack each field above lives in a different system, and somebody types it twice.
- Person
- AI agent
- Authority
- Platform
- Government integrationsEjari · DLD · DEWA · UAE PASS
- Cloud infrastructureMulti-AZ, auto-scaling, UAE region
- Enterprise securityTLS 1.3 · AES-256 · row-level isolation
- 99.9% uptimeContractual SLA with credits
- API-firstEvery object addressable, webhooks signed
- Role-based accessField-level, evaluated server-side
- Audit logsAppend-only, actor and delta on every change
- Scalable by designPartitioned ledger, 15-minute RPO
See it run on your own portfolio.
Bring a real lease and a real invoice. We will put them through the system on the call.
Fourteen modules. One system of record.
Each one is a product in its own right. None of them is a separate database, which is why the lease you sign in leasing is the same object finance bills against.
This isn't software with a chatbot bolted on.
An assistant that can only talk is a search box with better manners. These agents read your records, draft the work, and hand it to a human to approve — which is the only version of AI a finance director will sign off.
Lease Assistant
Drafts and checksBuilds the lease from the negotiated terms, flags every clause that deviates from your template, and prepares the Ejari submission.
Reads your template, flags every deviation
Maintenance Dispatcher
Triages and assignsReads the tenant's description and photo, classifies the trade and urgency, then assigns the technician who is closest, qualified and free.
Classifies trade, urgency and likely parts
Document Reader
Extracts and filesTakes a title deed, cheque, contract, invoice or Emirates ID and returns structured fields linked to the right record.
31 document types recognised
Owner Assistant
Answers and reportsAnswers an owner's question about their own portfolio, in their language, from the live ledger — with the figures cited.
Answers only from your own records
WhatsApp Agent
Handles the front lineTakes enquiries, books viewings, logs maintenance requests and confirms payments over WhatsApp. Escalates the moment it should.
Arabic and English, on the channel it arrived
Voice Agent
Picks up the phoneAnswers inbound calls, identifies the caller against the tenancy, resolves the routine and routes the rest with a written summary.
Identifies the caller against the tenancy
Rent Collection
Chases, politelyRuns the escalation sequence per tenant, per channel, in the right tone, and stops the instant the payment clears.
Stops the moment the payment clears
Invoice Processing
Codes and matchesReads a vendor invoice, matches it to the purchase order and work order, codes the GL account and routes it for approval.
Matches PO, work order and GL account
Reporting
Writes the commentaryProduces the monthly owner and board pack — the numbers from the ledger, the narrative explaining what moved and why.
Numbers from the ledger, narrative from the movement
Predictive Maintenance
Sees it comingWatches asset age, service history and failure patterns across the portfolio and schedules the intervention before the callout.
Schedules against age, history and failure pattern
Four constraints, enforced by the system
These are not policies in a handbook. They are properties of the architecture — an agent cannot violate them, because the query it would need does not return.
Grounded in your data
Every answer is drawn from your own records, scoped to the asking user's permissions. No general-knowledge guessing about your portfolio.
It proposes, you approve
No agent writes to the ledger. It prepares the entry, shows its reasoning and waits for the human with authority to sign it off.
Every action is logged
Which agent, which model, which prompt, which records it read, what it produced and who approved it — all in the audit trail.
Tenant-isolated by construction
Isolation is enforced at the database row level, not in application code. An agent cannot reach another company's data because the query cannot return it.
Eight stages. One record, from title deed to board pack.
A property enters the system once. Everything that happens to it for the next twenty years is an event on that record — never a re-entry into a different system.
- 01Acquire
Property enters the system once
Title deed uploaded, read and verified. Building, units, areas, owners and service charges created from the document — not typed from it.
Document AI extracts 40+ fields
- 02Market
Listings and enquiries
Vacant units publish to portals and your own site. Enquiries from every channel land in one pipeline with the unit already attached.
AI qualifies and books viewings
- 03Lease
Offer to signature
Quotation, negotiation, approval, e-signature and Ejari registration. The revenue schedule and invoice run are created at signature.
Lease drafted and clause-checked
- 04Move in
Handover and inspection
Snagging list, meter readings, key handover, DEWA transfer and the deposit posted to the right liability account.
Inspection scheduled automatically
- 05Operate
Maintenance and facilities
PPM runs on schedule, reactive requests get triaged and dispatched, vendor invoices arrive coded and matched.
AI triage and dispatch
- 06Collect
Rent, PDCs and arrears
Cheques banked on date, payments reconciled against invoices, arrears escalated on a sequence that stops when money lands.
AI collection sequences
- 07Renew
Expiry to renewal
Renewal terms proposed against market comparables and the tenant's payment record, sent, negotiated and re-registered.
Renewal proposed 120 days out
- 08Report
Owners, board and regulator
Owner statements, portfolio performance, VAT returns and the board pack — generated from the same ledger everything else posts to.
AI writes the commentary
Eight screens that would each be a separate product elsewhere.
Same records, same permissions, same ledger. Switch between them without switching systems.
What an owner sees when they log in: income, occupancy, collections and this month's statement — from the live ledger, not a nightly export.
A single asset, floor by floor. Occupancy, expiries, service-charge recovery and compliance status in one view.
The dispatch board. AI classifies each request by trade and urgency, then assigns the technician who is closest, qualified and free.
Ask a question in a sentence. The answer comes from your own records, with the sources cited and any action held for approval.
Portfolio performance computed from the general ledger, so the number on the chart is the number in the accounts.
Every enquiry from every channel in one pipeline, qualified and matched to available units before an agent opens the file.
Terms to signature to Ejari to revenue schedule. Eight stages, one record, no re-keying between them.
Native apps for technicians, inspectors and agents. Full offline capture, because the plant room has never had signal.
Every module, one demonstration.
Forty-five minutes with an engineer who has run a property book, not a slide deck.
The things a platform built elsewhere gets wrong.
Every item below is in the data model, not a custom field added after a customer complained. That is the difference between built for the GCC and localised for it.
Post-dated cheques
A register, not a note in a comment field. Banked on date, cleared, bounced, replaced and re-presented — each with its own accounting entry and its own audit trail.
Service charges
Budgeted, apportioned by area or share, invoiced, recovered and reconciled against the reserve fund. Owner association reporting comes out of the same ledger.
Ejari and Tawtheeq
Tenancy registration is part of the lease workflow, with the reference stored on the lease it belongs to — not in a folder of screenshots.
Arabic and English
Bilingual contracts, correspondence and interface. The AI agents handle enquiries in both, on whichever channel they arrive.
VAT and corporate tax
UAE VAT computed from the general ledger with return preparation, and corporate tax on the same basis. Not a spreadsheet built each quarter.
Multi-emirate portfolios
Different authorities, different utility providers, different registration regimes — on one portfolio, in one system, without a separate tenancy per emirate.
Filed from inside the workflow that created the record.
Not an export, a login and a re-key. When a lease is signed, its Ejari submission is prepared from the lease itself, and the reference comes back onto the same record.
Tenancy contract registration and renewal, prepared from the lease record.
Title verification, transfer status and Oqood for off-plan units.
Property, unit and ownership lookups against the official register.
Account move-in and move-out, meter readings and utility billing.
National digital identity for tenant, owner and signatory verification.
Broker and agent registration checks, service charge and escrow rules.
Abu Dhabi tenancy contract registration and amendment.
Sharjah utility account transfer and consumption billing.
Northern Emirates utility account handling.
Permits, inspection filings and building compliance certificates.
Status is confirmed per emirate and per authority at scoping, and written into the statement of work rather than assumed from this page. AQARI ONE is an independent software vendor: nothing here implies endorsement, partnership or certification by any government authority, and service marks remain the property of their owners.
One platform. A different answer for everyone who has to approve it.
Nobody buys an operating system alone. These are the six questions that decide it, and the honest answer to each.
What is the portfolio actually doing?
Occupancy, income, arrears and expiry exposure across every asset, computed from the ledger rather than assembled from four reports that disagree.
Portfolio view · live, not T+1
Where does the work go?
The routine — invoicing, renewals, filings, dispatch, statements — runs on its own. Your team handles exceptions and approvals, which is what you hired them for.
Workflow engine · approval matrices
Does the money reconcile?
One double-entry ledger behind every module, so there is no second system to agree with. PDCs, VAT, service charges and owner distributions are sub-ledgers of it, not separate products.
Trial balance · audit trail · VAT return
Can my team keep up with the book?
Renewals are proposed 120 days out with market comparables and payment history attached. Arrears escalate on their own and stop when the money lands.
Leasing pipeline · renewal engine
Will the SLA hold?
PPM generates its own work orders. Reactive requests arrive triaged. SLA clocks run on real timestamps, and breaches escalate before they are breaches.
Dispatch board · PPM · asset register
What am I signing up to run?
Row-level tenant isolation in the database, SSO and SCIM, an open REST API the product itself is built on, signed webhooks, and an append-only audit trail.
API · RBAC · residency · DR runbook
The things that decide whether it survives procurement.
Every item here exists because a real customer's security review, finance policy or auditor asked for it.
Granular permissions
Roles down to the field. A junior accountant can post a receipt and never see a salary line.
Workflow automation
Any event can trigger any action. Build the approval chain your finance policy already describes.
Custom forms
Inspection templates, snagging lists, onboarding checklists — built by your team, not by a change request.
Approval matrices
Banded thresholds with real segregation of duties. The person who raises it cannot be the person who approves it.
Document versioning
Every contract, addendum and drawing keeps its history. You can always see what was signed and when.
Notifications
Email, SMS, WhatsApp and in-app, per user, per event, with quiet hours that are actually respected.
Immutable audit logs
Who did what, from where, to which record, with the before and after value. Append-only.
Open REST API
Every object in the platform is addressable. The UI uses the same API you do.
Webhooks
Subscribe to any event with signed, retried delivery and a replayable log.
AI search
Ask for it in a sentence. Across leases, invoices, work orders, documents and messages at once.
The difference isn't features. It's architecture.
Everyone's feature list looks similar on a slide. What separates them is whether the modules share a database or just an export button.
System of record
- Traditional stack
- One per department, reconciled monthly
- AQARI ONE
- One, shared by every module
Accounting
- Traditional stack
- A separate package, synced nightly
- AQARI ONE
- A native double-entry ledger every module posts to
Data entry
- Traditional stack
- The same lease keyed into three systems
- AQARI ONE
- Entered once, or extracted from the document
AI
- Traditional stack
- A chatbot bolted onto the help centre
- AQARI ONE
- Ten agents with permissioned access to real records
Government filing
- Traditional stack
- Export, log in elsewhere, re-key, upload
- AQARI ONE
- Filed from inside the workflow that created it
Reporting
- Traditional stack
- Overnight warehouse, T+1 at best
- AQARI ONE
- Live, from the ledger, with the entries behind it
Mobile
- Traditional stack
- A cut-down viewer
- AQARI ONE
- Native apps with full offline capture
Extensibility
- Traditional stack
- A change request and a quote
- AQARI ONE
- Open API, webhooks and a workflow builder
Audit
- Traditional stack
- Application logs, if enabled
- AQARI ONE
- Append-only trail on every record, always on
Implementation
- Traditional stack
- Typically 12–18 months, phased by module
- AQARI ONE
- Weeks — the modules were never separate
We would rather show you than quote a statistic.
Bring a lease, an invoice and a maintenance request from your own portfolio. In forty-five minutes you will have watched all four of these run, and you will be able to check every figure they produced.
Sign a lease. Watch the ledger.
We take a lease you bring, enter its terms once, and follow the entries out the other side — revenue schedule, deferred income, deposit liability, VAT — into a trial balance that never touched a second system.
You check: Open the journal. Trace any figure back to the lease that created it.
Raise a fault. Watch the dispatch.
Describe a real fault the way a tenant would, with a photo. The triage agent classifies trade and urgency, picks the technician by proximity, skill and load, and starts the SLA clock.
You check: Change the description. Watch the classification and the assignment change with it.
Upload a real contract. Watch it become data.
Bring a tenancy contract, a title deed or a vendor invoice — in Arabic or English. Fields are extracted with confidence scores, validated against the existing record, and anything uncertain is routed for review rather than written.
You check: Check every extracted field against the source document, side by side.
File from the record, not a portal.
We walk the Ejari submission from inside the lease that created it, then the DEWA move-in, then the reference coming back onto the same record — and show you exactly where a human approval sits in each.
You check: Ask what happens when the authority rejects it. We will show you that path too.
AQARI ONE is early enough that we do not have named public references. Rather than publish anonymous figures nobody can audit, we demonstrate against your data and let you draw the conclusion. Reference calls with existing deployments are arranged under NDA during evaluation.
Book the sessionBuilt for the company whose auditor asks hard questions.
Real estate platforms hold title deeds, bank details, salary information and national IDs. That deserves more than a padlock icon on the pricing page.
Encrypted end to end
TLS 1.3 in transit with certificate verification enforced. AES-256 at rest across the database, object storage and backups.
Row-level tenant isolation
Enforced in the database, not the application. The connection role cannot bypass it, so a bug in application code cannot leak across companies.
Role-based access control
Roles, scopes and field-level rules. Permissions are evaluated server-side on every request, never trusted from the client.
Append-only audit trail
Every state change recorded with actor, timestamp, source address and before/after values. Journal lines are immutable once posted.
Backups and recovery
Point-in-time recovery with a 15-minute RPO, automated restore rehearsals and a documented, tested DR runbook.
Compliance programme
GDPR-aligned processing, UAE data residency and DPAs available for enterprise agreements. A SOC 2 Type II programme is under way — AQARI ONE is not yet certified, and we will not say otherwise until the report is issued.
Security documentation, penetration-test summaries and a completed CAIQ are available under NDA during evaluation.
The ones that actually come up.
Asked by the finance directors, IT security teams and operations leads who evaluate this.
How long does implementation actually take?
Most portfolios go live in six to ten weeks. The long pole is data migration, not configuration — because the modules were never separate systems, there is no integration phase between them. We migrate units, leases, owners, opening balances and open work orders, run a parallel month, then cut over.
Can we migrate from our existing PMS and accounting system?
Yes. Migration is a standard part of onboarding: units, leases, owners, documents and open work orders are loaded from whatever you run today — Yardi, MRI, Oracle, Tally, Zoho, QuickBooks or spreadsheets — and opening balances are loaded as a dated trial balance, so the ledger reconciles to your prior system on day one and stays auditable afterwards. The migration plan and its cut-over test are agreed in writing before anything moves.
Is the accounting a real general ledger or a reporting layer?
A real double-entry general ledger with a chart of accounts, journals, control accounts, period close and year-end. Every module — leasing, facilities, AP, AR, owner distributions — posts through the same engine. There is no second ledger to reconcile against.
What does the AI have access to, and can it change our data?
Agents read only what the requesting user is permitted to read, enforced at the database row level. No agent writes to the ledger. Agents propose entries, dispatches and documents; a human with the right authority approves them. Every agent action is logged with its inputs, outputs and approver.
Where is our data hosted?
UAE region by default, with EU and KSA regions available. Data does not leave the selected region, including for AI inference. Enterprise agreements can specify residency contractually.
Do you support Arabic?
Yes — full right-to-left interface, Arabic documents and correspondence, and bilingual tenancy contracts. The AI agents handle enquiries in Arabic and English on every channel.
How does pricing work?
Enterprise agreements priced per unit under management, with modules and integrations bundled rather than sold separately. There is no per-seat charge for technicians, owners or tenants, because charging per seat discourages the adoption the platform depends on.
Can it connect to systems we are not replacing?
Every object is available through the REST API, and webhooks push events out with signed, retried delivery — the product's own interface is built on that API, so there is no second-class surface. Connections to banking files, payment gateways, access control, building management systems and identity providers are scoped per deployment; which ones are already built for your stack is confirmed at scoping, not assumed here.
See it running on your own portfolio.
A 45-minute session with an engineer who knows the domain, not a slide deck. Bring a real lease, a real invoice and your hardest question.
No sales sequence. One engineer, 45 minutes, your data model on screen.