Technical Appendix¶
This appendix gives technical evaluators enough context without making the pitch site depend on the full engineering documentation tree.
Architecture Direction¶
MYConnect starts as a modular platform:
- Next.js web app for internal admin, tenant workspace, and customer portal surfaces.
- Expo/React Native direction for Android-first driver mobile.
- NestJS modular backend API.
- Prisma and PostgreSQL/PostGIS for tenant, operations, device, and location records.
- Redis/BullMQ direction for async work, queues, locks, and retries.
- MQTT and HTTP ingestion patterns for telematics.
- S3-compatible object storage for POD, reports, exports, and evidence.
- Observability direction through OpenTelemetry, Prometheus/Grafana, and structured logs.
Platform Shape¶
The MYConnect application is organized as a pnpm/Turborepo monorepo:
| Area | Purpose |
|---|---|
apps/web | Next.js operational web surfaces. |
apps/api | NestJS API modules. |
apps/mobile | Mobile app direction for driver workflows. |
packages/database | Prisma schema, migrations, seed data, and client exports. |
packages/domain | Shared domain contracts and primitives. |
packages/config | Shared tooling configuration. |
Bounded Modules¶
The product architecture is organized around bounded modules:
- Identity and tenant.
- Workspace experience configuration.
- Master data.
- Device and telemetry.
- Fleet.
- Transport operations.
- Driver workflow.
- Customer portal.
- Safety.
- Cold chain.
- Cargo.
- Finance.
- Integrations.
- Support.
- AI assistance.
- Partner and marketplace.