Development

Tech stack

The Acrontec Marketplace Engine ships as a full-stack product. Below is the Nectar Eats reference implementation — the same family of stacks operators license for their own branded marketplaces. Versions evolve with the product.

Flutter apps
Next.js storefront
/api/v3
Laravel Domain
MySQL · Redis · Firebase · Payments

Backend

API, admin, and vendor portals for the marketplace engine.

  • PHP 8.5
  • Laravel 13
  • MySQL 8.4
  • Laravel Passport
  • Octane-ready
  • Redis (Predis)
  • Bootstrap 5.3.8
  • SCSS · Laravel Mix
  • Business logic in app/Domain/ with thin Api/V3 controllers
  • Blade Master Admin, Vendor portal, and Franchisee panel on theme-v2 (Bootstrap + SCSS — not Tailwind)
  • Auth via OAuth2 / API tokens (Passport)
  • Integrations: Stripe, Firebase Admin (FCM), S3-compatible storage
  • PDF / Excel tooling for ops exports and documents

Web frontend

Customer storefront and React admin surfaces.

  • Next.js 16
  • React 19
  • MUI 9
  • Emotion
  • Redux Toolkit
  • TanStack Query
  • Axios
  • Firebase Web
  • App Router storefront talking to /api/v3
  • UI built with MUI + Emotion — Tailwind is not used
  • Client state (Redux + persist) and server state (React Query)
  • Node 22 for builds; long-lived Next server in production deployments

Mobile apps

Native Flutter clients on the same API contract.

  • Flutter
  • Dart 3.5+
  • GetX
  • Firebase Messaging
  • Google Maps
  • HTTP → api/v3
  • Customer (Takeaways) — ordering, tracking, maps, push notifications
  • Partner — merchant operations (same Flutter / Dart baseline, GetX, FCM)
  • Modern Android toolchain (current AGP / Kotlin / compileSdk line)
  • Aligned on delivery-driver naming and a single api/v3 surface

API contract

Web and mobile share one public API version: /api/v3. New marketplace features land on v3 with domain services behind thin HTTP controllers. Resource naming uses delivery driver (not legacy “delivery man”) in paths and payloads where the stack has been migrated.

Product-facing integration docs for Acrontec licensing live on the API documentation page. The Nectar Eats reference deployment uses the same engine patterns described above.

Want an architecture walkthrough?

We can walk engineering and commercial stakeholders through the licensed stack for your demographic.

Contact Acrontec Platform architecture Live demo