MANDAMeckia
Fleet management SaaS, from the office to the field
Designed and built Meckia, a fleet management SaaS/PWA. Teams bring vehicles, maintenance, expenses and documents together in one workspace. The product combines a Next.js interface, a NestJS API, PostgreSQL on Neon and S3-compatible file storage. Field entries can be prepared offline and synchronized after reconnection and session verification. GPS integration is available through Traccar when configured for the organization. The screenshot shows a product preview with sample data.
Fleet management SaaS application
Bring fleet operations, office teams and field work together
Meckia brings vehicles, maintenance, expenses and documents into one organization workspace. I designed and built the product end to end: a Next.js interface, NestJS business API, PostgreSQL on Neon and a PWA workflow for field entries. The image above is the public platform preview with sample data, not customer information.
- Product
- Fleet management SaaS/PWA
- Interface and API
- Next.js and NestJS / TypeScript
- Data
- PostgreSQL on Neon
- Field work
- offline entry, then synchronization
One workspace for fleet operations
Fleet information often ends up spread across spreadsheets, messages and document folders. Meckia organizes it around each vehicle: records, maintenance, expenses and operational events. The interface focuses on clear information and short actions, including on mobile.
The product is organized by company. The API enforces access rules on the server and checks that resources belong to the user's organization, rather than trusting the interface to decide what can be read or changed.
A NestJS architecture with clear integration boundaries
The NestJS API is organized by domain, with validated DTOs, business services, database migrations and focused tests. PostgreSQL on Neon holds relationships and constraints; files live in separate S3-compatible storage.
External services have distinct roles: Resend handles transactional email and Traccar provides the GPS connection when configured. This separation lets fleet workflows evolve without coupling every screen to a third-party provider.
Keep field entry available when the network is not
Connectivity is not guaranteed on the road. Field mode lets users prepare supported entries offline and synchronize them after reconnection. Synchronization rechecks the session and handles duplicate attempts so a retry does not create two events.
This does not mean the whole app or GPS tracking works offline. The PWA covers specific entry workflows; server-backed data still requires a connection.
Explore Meckia
See the platform and its public preview with sample data.
Business application development
Design and development of web apps and SaaS products for business workflows.
Can Meckia be used offline?
Field mode supports preparing specific entries without a connection. They sync after reconnection and session verification. The rest of the app and live data still require a network connection.
Is GPS tracking included in every installation?
No. GPS connectivity uses Traccar and must be configured for the organization. The other fleet-management features do not depend on it.