How this directory was built, and what to be careful about.
Every listing in one place — filter by cuisine, area, rating, budget and whether it is still open. Ratings are Google Maps star averages.
Photos are representative, not of the venue. Every card shows a freely-licensed stock photo matching its cuisine type — a sushi photo on a Japanese listing, not a photograph of that restaurant. No venue in Puchong has a photo available under a licence that permits reuse, so real per-restaurant photos can only be added by hand or through a paid Places API. Where a venue's own photo has been supplied it is used instead and the card's alt text reflects that.
Eco Sanctuary and Sanctuary Mall are inside Bandar Rimbayu and are counted with it. Jalan Aman Sinaria and Persiaran Aman Perdana are not — those roads are in Bandar Tropicana Aman, which is why the fourteen venues on them have their own township here. Two of the fourteen trade under a "Rimbayu" name, but the street address is the locator.
The Reviews button beside Map opens the best and worst Google reviews of the last three months for one venue. They are pulled from Google Maps through Apify's Google Maps Reviews Scraper, and only the newest few per venue are kept, so treat them as a sample of recent opinion rather than a full record. Reviewer names are not republished — the rating, what was written and roughly when is enough to judge a place without dragging anyone's name onto someone else's website. A venue with no reviews in the last three months shows exactly that, which is usually a sign it is new or quiet, not that the score is being hidden.
When the monthly refresh finds restaurants that were not in the directory before, they are added and gathered under a New arrivals heading in the sidebar — one chip per month, with a 🆕 badge on the card. They stay there for three months and then drop out on their own, so the heading disappears entirely in months that added nothing. The 568 places the directory launched with are deliberately not marked as new: only venues discovered since.
Each card carries a Map button that opens the venue's exact Google listing where we hold its Google id — 483 of the 568 places — and falls back to a name search for the rest. That listing is also where Google's own Menu tab lives, which is the closest we can put you to a menu we are not allowed to copy. The Waze button sits beside it and uses Waze's own deep link, so on a phone it opens the app rather than a web page. Where we hold a venue's coordinates it drops you straight into navigation; where we do not, it hands the venue's name and address to Waze's search, which finds the business by name. It never dead-ends.
That split is deliberate. Coordinates only exist for venues whose Google reviews we pulled — they arrive attached to the review data — so 467 of the 568 navigate directly today. We tried filling the rest from OpenStreetMap and it was a dead end at this scale: it does not carry these small neighbourhood restaurants, and the one or two it did return included a highway information board that happened to share a word with a venue's name. Rather than place someone's pin on a road sign, the remaining venues stay on Waze's own name search, which is more likely to be right than a coordinate we guessed.
Near Me asks your browser where you are, then keeps only the venues inside the radius you pick — half a kilometre out to ten, on a slider. It sorts them nearest first, and each card then shows how far away it is. The radius runs on the server, not in the page, so the count is the true number of places in range rather than however many happen to have loaded. If you decline the location prompt nothing is filtered and the panel says why: there is no halfway state where a distance filter quietly applies to a location we never got.
Two limits are worth knowing. A venue we hold no coordinates for cannot be measured at all, so it drops out of any radius search — 467 of the 568 places can be matched today, for the reasons set out under Getting there. And the distance is straight-line, not driving distance. Your coordinates are used only to answer the query and are not saved in the directory; they are not sent to Google, Waze or anyone else.
Where a venue's menu can be pointed at with confidence, its card carries a Menu button. Nothing is copied onto this site — the button opens the venue's own menu, in a new tab, from the source that owns it.
That coverage is small on purpose, and currently seven venues. Most Malaysian menus live on the delivery platforms rather than on restaurant websites, and those platforms actively block automated access — so a link to them cannot be checked, and a menu button that lands on the wrong restaurant is worse than no button at all. We only link where the destination is a menu we can stand behind: either the venue's own site, or a listing whose address names that venue. If a place you use is missing one, send the menu and it can be added.
The data lives in PostgreSQL and is served by a FastAPI backend. The whole app runs as a supervised service and is reachable at eats.evelynlew.cloud. Every filter, and both the sorting and the radius search, run against the live database rather than against whatever the page happens to have loaded.
The site is open to everyone and always will be: every filter, every listing and every review panel works without an account, and nothing is hidden behind a login.
Signing in with Google is optional and adds three things on top of that. You can mark a favourite, keep a personal remark on any place, and share those with friends you invite by email. A favourite or a remark is private to you until you deliberately switch it on for a named person. Nothing is shared by default, each direction is controlled by the person whose list it is — you decide what a friend sees of yours, they decide what you see of theirs — and switching a share off takes the access back immediately.
What is stored is your Google account identifier, your name and email address, the places you marked, your remarks, and who you are connected to. Nothing is sold, nothing is used for advertising, and no remark or favourite is ever shown to anyone you have not shared it with. You can delete your account from the account menu at any time, which erases all of the above; the invitation links you sent stop working with it. Sign-in is only offered on this deployment when Google credentials are configured for it — when they are not, no account code runs at all.
The representative cuisine photos are reused under CC0, CC BY or CC BY-SA licences, which require attribution — that is why this page exists: