The house will decide
Dinner, decided.
You've chosen enough today. Share where you are, ring the bell, and eat what fate serves you.
The house will decide
You've chosen enough today. Share where you are, ring the bell, and eat what fate serves you.
Share your location or type a ZIP. That's the only required ingredient.
One press. The engine filters what's actually open, near, and right for the hour — then lets fate pick from the good stuff.
You get one dish at one place, the reasons why, and a straight line to ordering. Reroll if the chef misread you.
Game Mode dresses the decision in brass: a slot machine of kitchen tickets, or a roulette wheel plated like a lazy susan. The reels spin blind until the engine answers, then land on the real pick — hold a reel to keep the cuisine and gamble the rest. No stakes, no coins, no tricks. Just the anticipation.
The default is zero thought: open now, nearby, right for the hour. But every dial exists when you want it — and each one has a dice button, so you can randomize the settings themselves. Dietary needs and hard exclusions are never randomized. Chaos with manners.
No account. Preferences, saved picks, and history live in your browser and nowhere else.
Coordinates are rounded to about a city block before any lookup. Precise position is never stored or logged.
Every result is badged with its source — live DoorDash CLI, OpenStreetMap, or demo menu. We don't dress fiction up as fact.
The longer version: privacy.
decidemy.food is an independent project, not affiliated with or endorsed by DoorDash. When the DoorDash CLI is configured (it's currently a waitlist-only beta for macOS), recommendations come from live DoorDash data and link straight to ordering. Otherwise we fall back to real nearby places from OpenStreetMap, or a clearly-labeled demo menu — the badge under every result tells you exactly which.
Never. The DoorDash CLI can technically check out, but this app is read-only by design — it only searches restaurants and menus. Ordering always happens on doordash.com, by you, with your own hands. A food roulette wheel should not hold your credit card.
Your precise coordinates never leave the server request — they're rounded to about a city block (~110 m) before any restaurant lookup, and only that coarse point plus a neighborhood label is kept in your browser so you can skip the location step next time. No accounts, no server-side storage, no analytics beacons.
It's a real decision engine, not names in a hat. Hard constraints filter first (open now, dietary needs, budget, distance, exclusions), then soft preferences score what's left (ratings, closeness, meal-time fit, cravings, your familiar-vs-adventurous spirit), and a seeded, temperature-controlled random draw picks from the top so results stay surprising without being dumb. Every pick comes with its reasons, and repeats are penalized so rerolls feel fresh.
No money, no prizes, no odds to beat — the slot machine and roulette wheel are just theatrical ways to watch the same decision engine land. The reels and the wheel always show the real result; nothing is predetermined or rigged for drama.
The DoorDash CLI is a brand-new waitlist-gated beta that only runs on Apple Silicon Macs, so most visitors won't have it wired up. When it isn't, we try OpenStreetMap for real nearby restaurants; if that's unreachable too, you get our fictional tasting menu so you can still play with everything. The result badge is always honest about the source.