
Web
Food360 AI
A SaaS platform that turns restaurant menus into interactive 3D dishes diners can spin before they order.
food360ai.com
3D
Interactive dish views
Multi-venue
Tenanted menu model
Split deploy
Vercel front, Heroku API
The challenge
Photographs flatten food. Restaurants wanted diners to see portion, texture, and plating properly, which means shipping 3D models to a phone browser without a long wait or a hot device — and letting non-technical restaurant staff manage those assets themselves, per venue, per menu, without touching a 3D tool.
Our solution
We split the product: a React + Vite front end tuned for progressive asset loading, and a Nest.js API owning menus, venues, tenancy, and asset pipelines. Models and imagery are stored and transformed through Cloudinary, Neon Postgres via TypeORM holds the relational menu model, and Redux keeps the builder's editing state predictable. MUI and Framer Motion give staff a builder that feels like a normal admin tool rather than 3D software, with Google Maps handling venue discovery.
The results
Restaurant staff publish and reorganise 3D menus from a browser without design help, and diners load an interactive dish view on a phone rather than a static photo grid. The Nest.js API is a clean boundary, so new front ends can be added against the same contract.
Client
Project type
Discipline
What we did
Related services
food360ai.com
Technology
What it's built on
The stack behind this build, grouped by the concern it owns.
Frontend
Backend
Data & storage
Integrations
Delivery
How it ships
Hosting, source control, and the release path from a merged branch to production.
Frontend hosting
Vercel
Backend hosting
Heroku
Source control
GitHub
Frontend hosting
Vercel
Backend hosting
Heroku
Source control
GitHub
Engineering & operations
The parts you only see from the inside
Environments, flags, tooling, and the safeguards that keep a live platform shippable.
Progressive 3D asset loading so a phone is never blocked on a full model
Separate API boundary — new clients can be added without touching the backend
Self-serve menu builder: no developer needed to publish a menu change
Gallery