Matching is how a city gets personal.
Dubai adds people faster than almost anywhere on earth, and almost all of them make the single most consequential decision of the move — where to live — by scrolling photographs. We think that is a solvable problem, and we think solving it properly changes more than one person's rent.
The listing is the last decision, not the first.
Ask anyone who has moved to Dubai how they chose their area and you will hear the same three answers: a friend recommended it, it was near work, or the photos looked good. None of those is a bad instinct. All of them are single-variable answers to a multi-variable question.
Meanwhile the information needed to answer it properly already exists. Community boundaries are mapped. Rental benchmarks are published. Drive times are computable. Amenity locations are open data. The problem was never missing data — it was that nobody had put a person on the other side of it.
So RealSuggest inverts the usual order. It asks how you live before it shows you anywhere to live, scores every community in the city against that, and shows its working. When the area is settled, it hands you to the portals — because ranking units is a solved problem and ranking places was not.
Never a black box
Every number in a report expands into the arithmetic that produced it. If we cannot explain a score in a sentence, it does not ship.
An honest no beats a soft yes
When no community fits your constraints, we say so plainly. Returning a "closest available" match would be easier and would quietly make the product useless.
Collect the minimum
Destination coordinates are stored at neighbourhood precision. We do not need your building number to do our job, so we do not ask for it.
Stay out of the portal business
The moment we start ranking individual units we start optimising for inventory instead of fit. The handoff is a boundary, not a limitation.
Neighbourhood is the first edge in a much larger graph.
Person to place is where we started because it is the decision with the most leverage. But the same fit logic extends outward, and each layer makes the one before it sharper.
The endpoint is not a bigger property portal. It is a model of how a city and the people in it actually fit together — read forwards by residents choosing where to live, and backwards by the people deciding what to build.
Place · communities and micro-districts
Ranked Dubai communities scored against a stated lifestyle profile, with the reasoning attached.
Daily life · schools, clinics, parks, cafés, corridors
The texture that decides whether a community is livable rather than merely affordable.
Home · unit types and budget bands
Tighter integration with live inventory so the handoff carries your constraints with it.
Work · employment hubs weighed against fit
Commute is never just distance. It is what you are trading for it, and that trade should be quantified.
Future · growth zones and investment potential
The same fit logic applied forward in time, pricing in where a city is heading rather than where it has been.
City · demand heatmaps and amenity gaps
Every match, aggregated and read back as a planning signal for the people who build the place.
A matching product knows uncomfortable things. Ours knows less than it could.
To rank neighbourhoods for you we need to know roughly where you go and roughly what you earn. That is genuinely sensitive, and the correct response is to design for the minimum rather than hoard for a future feature.
Session credentials live in HTTP-only cookies, never in local storage. Destination coordinates are reduced to neighbourhood-level precision before they are written. Preference data is structurally separated from identity.
What we store
Your account, your saved profiles, coarse destination coordinates, and the reports you generated.
What we avoid
Exact home or workplace addresses, precise salary figures, third-party ad identifiers, and cross-site tracking.
What partners see
Only what a client or organisation explicitly shares with them — never a silent export of individual profiles.