Building the operating backbone for a direct freight marketplace.

The operating context

The problem was not only finding a driver.

Traditional freight workflows often rely on informal intermediaries and Telegram brokers. That can make pricing opaque, delay decisions and create significant commission costs. Shippers also need clearer trip records, verified drivers and better visibility into where a load is.

What Gramida is building

1. A modular platform architecture using NestJS and Next.js, designed to keep core domains independently maintainable.
2. A full order lifecycle: load registration, driver allocation, trip documents and financial settlement.
3. Real-time freight signals and geospatial data with PostgreSQL/PostGIS, alongside push notifications.
4. A repeatable delivery process using GitHub Actions, Docker and CI/CD.

Evidence at this stage

The web and mobile platform, management panel, digital document system and documented API are in development. The project has more than 80 critical API tests passing in the test environment. Infrastructure is being prepared for a planned scale of 500,000+ users.

The intended operating change

The product is being designed to make direct shipper–driver coordination more transparent and to reduce reliance on informal intermediaries. The commercial model targets a reduction from the market’s reported 10–30% commission range to below 8%; this is a project objective, not a completed production result.

What this work reinforces

In logistics, location-data accuracy and financial-process security are not secondary details. A modular architecture lets trip, driver and freight domains evolve independently while protecting the stability of the wider platform.