Feastly | Multi-Restaurant Food Delivery App — Flutter Full App + Next.js Admin (4 Apps + AI)

Feastly is resellable source code for an UberEats / Grab / Foodpanda-style delivery business. It ships four coordinated surfaces on one shared backend — a Customer app, a Rider app, a Restaurant app (all Flutter) and a Next.js Admin panel that is the shared API, AI and realtime backend. Monetize it through per-order commission, deploy it anywhere, and keep zero paid-service lock-in: the realtime layer is self-hosted, email is plain SMTP, and the AI is fully optional.

Why Feastly

• Full 4-app ecosystem — not a lone customer app. Customer, Rider, Restaurant and Admin all ship, all wired to one backend.
• Modern stack — Next.js 15 + React 19 + Flutter 3, not aging PHP/Laravel.
• Optional AI — dual-provider (OpenAI / Gemini) semantic search + recommendations, badged with an “AI Spark” marker, that degrades gracefully with no keys.
• Self-hostable, no lock-in — deploy to Vercel or any Node host; standard PostgreSQL; self-hosted realtime; SMTP email. No mandatory paid third-party service.
• Flawless seeded demo — 12 restaurants, 71 menu items, live and historical orders, ledgers and ratings. No surface ever loads empty.

Customer app

• Email/password onboarding, address book, delivery-zone gating.
• Restaurant discovery with categories, cuisines, filters, sort and AI-assisted search.
• Menu with modifiers/add-ons, veg & allergen tags.
• Cart & checkout: modifiers, notes, tip, delivery vs pickup.
• Cash on Delivery (first-class) and card via Stripe (webhook-confirmed).
• Live order tracking — status timeline + rider location.
• Rate, reorder, order history, and “Recommended for you”.

Rider app

• Online/offline availability toggle.
• Auto-assign or accept-from-pool (admin-configurable).
• Full status flow: accepted → arrived → picked up → en route → delivered, with a location ping.
• Earnings: per-order breakdown + daily/weekly totals + payout status.

Restaurant app

• Menu management: categories, items, modifiers, availability, images.
• Live order board: incoming → accept/reject → preparing → ready.
• Earnings dashboard: gross, commission, net owed.
• Basic analytics: orders, revenue, top items.

️ Admin panel

• Dashboard: GMV, orders, commission earned, top items.
• Restaurant & rider onboarding, approval and suspension.
• Order oversight: search, live status, manual reassign, refund/cancel.
• Commission engine: global default + per-restaurant override → immutable ledger.
• Payout ledger: amounts owed to restaurants and riders, with mark-as-paid.
• Content: banners, categories, cuisines, delivery-zone geofence editor.
• Configuration: payment / AI / maps / SMTP / push keys — all stored server-side.
• Users, roles, disputes and ratings moderation.

Tech stack

• Backend / Admin: Next.js 15 (App Router, React 19), TypeScript.
• Database: PostgreSQL + Drizzle ORM (24 tables, 3 migrations). Works with any Postgres; the docs use Neon’s free tier.
• Auth: Auth.js v5 (admin sessions) + JWT bearer for mobile, bcrypt hashing.
• Jobs: Inngest (order-state jobs, notification fan-out, ledger events).
• Media: Cloudflare R2 (presigned uploads). Email: nodemailer / SMTP.
• Realtime: self-hosted SSE (no Firebase). AI: OpenAI + Gemini embeddings, server-side only.
• Mobile: Flutter 3.24+ / Dart 3.12, Riverpod, GoRouter, freezed, dio, Stripe.