Agrobia
From farm to door, one supply chain.
An agri and food-supply platform built on a real API backend with a web admin console and a driver app for last-mile delivery. It's an in-build project — the API and admin are the furthest along; the driver app is early.
- 3
- apps
- 6
- in the stack
- 5
- we provided
- 2025
- shipped
Agrobia is an agri and food-supply platform — the engine that moves produce from suppliers to buyers and out for delivery. Rather than a single site, it's built as three surfaces off one shared backbone. The backend is a proper REST API (NestJS + TypeORM over PostgreSQL, JWT auth and Swagger-documented endpoints, with Firebase Admin for identity and push) that owns catalogue, orders, users and dispatch. The admin console is a Next.js dashboard where the operator runs the business — products, orders and the people and drivers behind them. The driver app is the last-mile surface for the people carrying orders to the door. It is honestly a work in progress: the API and admin console carry the most weight today, while the driver app is still early. We're documenting it as proof that Tóg ships beyond the Firestore monorepo pattern — a relational, API-first stack when the domain calls for one.
The engine of the platform — a NestJS REST API over PostgreSQL that owns catalogue, orders, users and dispatch, with JWT auth and Swagger-documented endpoints and Firebase Admin for identity and push.
A Next.js dashboard where the operator runs the business end to end — products, orders, users and the drivers who deliver them — reading live from the API.
The last-mile surface for drivers carrying orders to the door. Early in build today — the delivery workflow is being layered onto the same shared API.
The API backend
The engine of the platform — a NestJS REST API over PostgreSQL that owns catalogue, orders, users and dispatch, with JWT auth and Swagger-documented endpoints and Firebase Admin for identity and push.
- NestJS + TypeORM over PostgreSQL
- JWT / Passport authentication
- Swagger-documented REST endpoints
- Firebase Admin identity & push
- Catalogue, orders & dispatch model
The admin console
A Next.js dashboard where the operator runs the business end to end — products, orders, users and the drivers who deliver them — reading live from the API.
- Products & catalogue
- Orders & fulfilment
- Users & drivers
- Reads live from the API
- Firebase-backed admin auth
The driver app
The last-mile surface for drivers carrying orders to the door. Early in build today — the delivery workflow is being layered onto the same shared API.
- Assigned deliveries (in build)
- Driven by the shared API
- Last-mile delivery workflow
The details that make it special.
Agrobia runs on a real NestJS + PostgreSQL backend with JWT auth and Swagger docs — a relational, API-first architecture chosen because a supply chain earns it, proof Tóg picks the right stack for the domain rather than one house pattern.
The admin console and the driver app are thin clients over a single shared API — add a supplier or buyer portal later and it plugs into the same catalogue, order and dispatch model.
Dispatch and a dedicated driver app are designed in from the start, so moving produce from supplier to door is a first-class flow, not an afterthought.
Platform-grade, top to bottom.
- NestJS
- TypeORM
- PostgreSQL
- Next.js
- Firebase Admin
- TypeScript
Designed, built and handed over.
- Platform architecture
- REST API backend
- Admin console
- Driver app
- Auth & identity
“In build. The API and admin console are the furthest along; the driver app is early. The ambition is a full farm-to-door supply chain — supplier and buyer ordering, live dispatch and last-mile delivery — running off one API-first backbone. No live metrics to claim yet.”
Want a build like Agrobia's?
Book a free discovery call. We'll map your build, show you what's possible, and start the demo while we talk.
