feat(movelt): MOVELT — automated port access (Port of Kribi)

A platform that files and tracks truck access requests for the Port of Kribi in place of an assistant: drivers request from their phone, a software agent submits on the port's portal, supervisors step in when needed.

#automatisation#logistique#saas#multi-organisations#client

$ git diff --stat package.json

+ React+ Vite+ TypeScript+ NestJS+ Playwright+ PostgreSQL+ Redis+ Docker+ WhatsApp API

9 technologies used

$ git log --oneline --grep=result

Result · impact

✓Requests go out with no human in the loop, day or night
✓Supervisors only step in when the agent stops
✓Thirty audit findings fixed and verified before opening to other organisations

$ cat README.md

Context

MOVELT hauls containers by truck to the Port of Kribi. Every entry needs an access code obtained by filing a request on the port's portal — typed in by hand by an assistant, often at night. The success criterion agreed with the client: get rid of that night-time data entry.

What makes it unusual: a mistake doesn't cost a support ticket, it costs a truck stuck at the gate. Most technical choices follow from that.

What I did

A MeshaLabs project, from implementation brief to production:

Web app (React / Vite) with two spaces: drivers trigger their request from their phone at any hour; supervisors follow everything live.
NestJS API: auth, requests, driver and vehicle registries, a Redis-backed work queue, PostgreSQL.
A Playwright agent that files the request on the port's portal, watches for the answer and refuses to cancel any row that isn't exactly the right one.
ISO 6346 container number validation before sending, so a typo never reaches the port.
WhatsApp notifications to drivers and their escorts, technical alerts on Telegram.
Phase 2: moving to a multi-organisation SaaS, with port registries assigned per organisation and guards against crew collisions.

$ Got a similar project in mind? Free first call.

Chat on WhatsApp→