Feastly — a complete multi-restaurant food-delivery platform you can rebrand and launch

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.

▶ Try the live demo

Admin panel (live): https://feastly.devsnack.dev/login
Customer app (Android APK): Download
Rider app (Android APK): Download
Restaurant app (Android APK): Download

Demo accounts (all use the password password123):

Platform admin — admin@feastly.dev (Admin panel)
Restaurant owner — owner@feastly.dev (Restaurant app)
Rider — rider@feastly.dev (Rider app)
Customer — customer@feastly.dev (Customer app)

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.

Third-party services & costs (all optional, buyer-provided)

Feastly runs end-to-end with no paid third-party service: Cash on Delivery, in-app / self-hosted realtime, local image handling and a standard PostgreSQL database are all it needs to operate. The integrations below are optional. If you choose to enable one, it is an independent third-party service that you sign up for and connect directly — it is not included in, bundled with, or resold through this item. Each is governed by that provider’s own terms and pricing and may incur costs billed to you by that provider:

Stripe (card payments) — third-party payment processor; per-transaction fees apply per Stripe’s pricing.
Cloudflare R2 (image / media storage) — third-party object storage; usage-based pricing per Cloudflare (free tier available).
OpenAI or Google Gemini (optional AI search & recommendations) — third-party AI APIs; usage-based token / embedding pricing.
Google Maps (maps & geofencing) — third-party API; usage-based pricing per Google (monthly free credit available).
SMTP email provider (transactional email) — any SMTP host you choose; priced by that provider.
Firebase Cloud Messaging (native push, scaffolded) — Google service; free at the time of writing.
PostgreSQL host (the database) — any Postgres works; managed hosts such as Neon offer a free tier plus paid plans.

You supply your own account and API keys for any service you turn on. All keys are stored server-side only and never ship inside a mobile app. Disable them all and Feastly still runs on COD, self-hosted realtime and full-text search.

What you get

Full source for all four surfaces + a shared Dart package.
Drizzle schema with runnable migrations and an idempotent demo seed.
The design system (Inter, orange/green palette, “AI Spark” marker) across web and mobile.
A branding pipeline (SVG/PNG masters → one-command launcher icons).
Full documentation + quick-start guide, per-app tests, and a dependency license audit.
6 months of item support.

⚙️ Setup in minutes

pnpm install
cp .env.example .env — set DATABASE_URL + AUTH_SECRET
pnpm db:migrate && pnpm db:seed
pnpm --filter @feastly/web dev → the admin panel at localhost:3000
flutter pub get, then flutter run in each app

✅ Requirements

Node 24.x (≥ 22) and pnpm 10.x.
Flutter 3.24+ / Dart 3.12+ for the mobile apps.
A PostgreSQL database (a free Neon project works). No other paid service is required.

️ Roadmap & honest limitations

Payments: Stripe and Cash-on-Delivery are fully wired; Razorpay and PayPal have config slots but their adapters are scaffolded (roadmap).
Push: in-app + realtime notifications ship today; native FCM delivery is scaffolded (config slots present, server delivery on the roadmap).
AI: the search/recommendation endpoints have no built-in rate limiter — add one before enabling AI on a public deployment (documented).
Realtime: self-hosted SSE is single-node out of the box; back it with Redis pub/sub for horizontal scale.
Maps: the mobile map dependency is included and native keys are wired; the live in-app map UI is a roadmap item (the admin geofence editor is live).
i18n / currency: V1 ships a single language (i18n scaffold present) and single-currency config, both structured for later expansion.

Support & license

6 months of item support is included (setup help, bug fixes, usage questions). You provide your own hosting, domains and third-party accounts. Sold under the standard Envato Regular and Extended licenses; all dependencies are permissive (MIT / Apache-2.0 / BSD / ISC).

Questions or support requests? Please use the Comments tab on the item page, or the Support tab on our CodeCanyon author profile — we reply there.

Changelog

1.1.0 — 2026-08-03 — Order details across all four apps.

Rider order detail screen (new). Pickup and drop-off cards with one-tap Navigate and Call on each leg, the full item list with modifiers, delivery notes, and the cash-to-collect amount called out on COD orders.
Richer rider job cards. Before accepting, a rider now sees the restaurant, its address, the delivery area with distance, item count, payment method and their payout — instead of just an order number and a total.
Restaurant order board + detail screen. Customer name, itemised order with modifiers, and the assigned rider with a Call button once one is allocated.
Admin order oversight. Expandable pickup / drop-off / assigned-rider contact block on every order row, so support can answer “where is this going, and to whom?”.
Customer tracking. Now shows which restaurant the order is coming from, with its address, Navigate and Call.
Customer privacy model. A customer’s street address and phone number are visible only to the rider actually assigned to their delivery, and to the platform admin. Riders browsing the unclaimed order pool see the delivery area and distance, never the customer’s identity or exact address. Enforced in the database queries, not just hidden in the UI.
Fixes. Delivery coordinates are now saved when a customer checks out with a saved address (previously the rider’s drop-off Navigate button had no destination); two riders can no longer accept the same order; pickup-only orders no longer appear in the rider delivery queue; and the restaurant’s address and phone now reach the customer’s tracking screen.
Demo data. Customer phone numbers, delivery coordinates, item modifiers, and a card-paid order so both the “collect cash” and “already paid” states are visible in the seed.
Upgrading. No database migration. Existing installations should run the one-off coordinate backfill in INSTALL.md §5.

1.0.0 — 2026-07-10 — Initial release: four surfaces on a shared backend, order lifecycle state machine, commission & payout ledgers, COD + Stripe payments, self-hosted realtime tracking, optional AI search + recommendations, idempotent demo seed, full documentation.

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